I am attempting to setup collections by OU in SCCM using the following in my criterisAttribute Class = System ResourceAttribute = System OU NameWhen I click on values, it only shows OU options for 2 of my 6 domains, is there something I am missing to get it to see the other domains?I already have collections setup based on all the domains, and those populate as normal, but SCCM will only see the OU's listed for 2 of the 6 domainsThanks

Ou information is discovered via the AD System Group Discovery agent. confirm those other 4 domains' containersare listed in that discovery agent's properties, and your site server can read the objects in those domains and ous.Standardize. Simplify. Automate.

Just to add a note to Sherry's reply. Also make sure that the computers in the console are marked as assigned.Kent Agerlund | http://agerlund.spaces.live.com/blog/

Thank you for the responses, I checked the settings under my AD Sys group discovery, and the "Enable Active Directory Group Discovery" is not checked. However, the console is able to see the OU's in the parent domain, and one of the sub-domains already with this unchecked, but not the rest of the subdomains :\From the SCCM server, I can navigate to all the domain controllers for the subdomains and vice versa. Could it be a permissions issue?Thanks/Kris

So, it is NOT checked, and yet you have OU information for individual computer objects?Do you have child primary sites? and on *those* they have AD System Group Discovery on, and that's where the OU data is coming from? Or perhaps you've implemented something like systemCenterTools.com's ESD?Standardize. Simplify. Automate.

Make sure you run the discovery again as well. The one mentioned by Sherry. Just adding the OU's doesn't make them appear and likely it will take 24 hours if you left at default.

I only have one primary site, all the subdomains have a distribution point only, and the 'Enable AD system group discovery is unchecked, so I am not sure why I see any OU information at all.I am going to setup the discovery method tonight, and let the discovery run. Ill post back when I get results.Thanks again

Thanks for the responses everyone, after enabling the AD system group discovery agent, and adding the subdomains to the custom LDAP/GC Query, I am now able to see the OUs for all the child domains :)Kris

Hello, Thanks Morrison!! it helped me too :)

Good Work!!! This tip solve my problem!! in addition I had to run the discovery ass son as posible