Primary not discovering AD Groups
We have some primary sites that are running system group discovery for the first time and it's finding zero objects. We have some other sites that are looking at the same OU and discovering the groups as expected. I've verified the LDAP queries. Can anyone point me in the right direction on this? We are querying AD groups for workstation membership and those site's collections are looking pretty bare. Thanks!!
January 25th, 2010 6:44pm

Are the boundaries set up correctly on the systems that are not finding anything?
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2010 8:04pm

Boundaries and name resolution are not involved in AD system GROUP discovery (they would come into play when talking about AD system discovery). HansPedro: any chance that you are trying to discover in multiple OUs and that those OUs have similar names?
January 26th, 2010 8:07pm

Ok, that makes much more sense... I assumed I knew what the system group discovery was... but was completely wrong. It sounds like it doesn't discover an "item" but rather more info about your systems, such as the ou and related groups. If you are expecting to discover systems with this, its not what it is designed to do... I hope I'm not way off on this.
Free Windows Admin Tool Kit Click here and download it now
January 27th, 2010 12:32am

Sorry for the dalay. We've verified that our LDAP queries are looking for OUs with unique names. Thanks.We actually are discovering the OU that contains the groups rather than the workstations with our System Group Discovery. So this was a learning point. We are however currently surviving using automated direct membership rules populated by a script that we have enabled to run more frequently than the discovery intervals. And it sounds like R3 will give us a chance to go back and revisit this with the delta discovery options. Thanks everyone.
February 16th, 2010 8:33pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics