Trigger AD scan when new computer object is detected

Hi Jonas,

I believe the option to run AD scans more often has been submitted previously as a Feature Request.

The other issue of having an alert available for new computer objects would be a Feature Request as well.

You can submit Feature Requests here, they are reviewed periodically by the Development Team for review
thwack.solarwinds.com/.../feature-requests

I hope this helps :)

Edit: as noted by Marcus (Allmecht) the Group Membership alert should work for this, as group membership change alert would be triggered by adding a computer documentation.solarwinds.com/.../set-alerts-for-ous-domains.htm

Well, thank you. I will submit a feature request.
On the other hand, that means that there is no quick solution, I guess. :')

Yes, the issue about 'daily' being the most frequent for an AD scan has come up previously, so I know there have been FR for it submitted several times. It's not a long process for most environments, so an hourly option would be viable for many users.

Adding alert types is always a good suggestion, and hopefully easy to implement.

Be sure to submit them separately so each can be considered on its own merit.

We had the same problem almost a decade ago and back in the days Protected Networks implemented exact what you need. AFAIK it made it to the major product release.

OK this may be the Group Membership alert
https://documentation.solarwinds.com/en/success_center/arm/content/set-alerts-for-ous-domains.htm

Adding computers would involve changes to group membership, so an alert would be generated.

Thank you both,

That sounds like a good solution:
Set an alert on the 'domain computers' group so that the AD scan script is triggered when a change is detected.
The only downside is that the script will also be triggered if an object is removed from the group. But this is fine.

Unfortunately, the solution does not work as hoped.

Apparently the AD Logga does not log any changes to the ‘domain computer’ group.
Is there a switch that can be set in the pnServer.config to force the group to be monitored?

This one helps:

support.solarwinds.com/.../How-to-include-new-user-or-computer-object-created-outside-ARM-in-the-ARM-database

Hiho, this link doesn't work anymore (404 error). Do you have a working link?