Looking for some direction on how to troubleshoot this issue. I've had my production SCCM implementation up for about two months now. Last week I noticed that some values are no longer updating as new machines join into SCCM. For example, I have been building collections based on System OU membership. I would typically use the query builder to select "System Resource - System OU Name" as the "where" and press the Values button to enumerate all OU detected thus far. I've got about 100 results in that values window now, and I've joined nearly a thousand machines over the past few days, all members of OU's yet to be introduced to SCCM. None of those new OU values are showing in the Values box now. Any ideas? I'd be happy to submit logs if I knew which ones to look at. The fact that this was working and now isn't leads me to believe that someone changed permissions somewhere (AD or SQL), but I'm not sure how to track that down. Thanks!

Sounds like your OU discovery isn't running. Have you checked your logs for discovery?http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

OU information is gathered by AD System Group Discovery and the log file for it is adsysgrp.log. You should start by reviewing the configuration of this component and its log file.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

My adsysgrp.log shows the following two entries after each discovered computer object: WARN: Could not get property (domain) for system (0x80005010) WARN: Could not get property (memberOf) for system SCCMCLIENT (0x80005010) The status messages for component SMS_AD_SYSTEM_DISCOVERY_AGENT occasionally show a message similar to this: SMS Active Directory System Discovery Agent reported errors for 261 objects. DDR's were generated for 0 objects that had errors while reading non-critical properties. DDR's were not generated for 261 objects that had errors while reading critical properties.Possible cause: The SMS Service might not have access to some properties of this object. The container specified might not have the properties available.Solution: Please verify the Active Directory schema for properties that are not replicated or locked. Refer to the discovery logs for more information. I have verified that the primary site server and two secondary site servers are members of the domain admins group, and also have full control over the "System Management" container in AD. Anything else I can check?

To successfully create a discovery data record (DDR) for a computer, Active Directory System Discovery must be able to identify the computer account and then successfully resolve the computer name to an IP address. From AD System Discovery flowchart the following attributes are mandatory: Active Directory Site Name ObjectGUID Active Directory Path Operating System Domain Active Directory System Group Discovery provides additional information about group memberships for resources previously discovered by Active Directory System Discovery. This method does not discover new resources; it adds group information to previously discovered resources. Code 0x80005010 means E_ADS_COLUMN_NOT_SET As my investigation if AD System Discovery works and computers are discovered then in All systems collection you can find them, you can ignore this WARN message. As I know it's a known bug to Microsoft, and their suggestion is: The discovery record for this computer is used to push the SCCM client agent out. Once the SCCM client agent installs it collects the %domain% within Inventory and sends back up to the SCCM SQL dB. So, WARN: Could not get property (domain) for system (0x80005010) is not the root cause of AD System Discovery failed to create DDRs. My suggestion is, open the adsysdis.log check whether any other errors there. Thanks

To successfully create a discovery data record (DDR) for a computer, Active Directory System Discovery must be able to identify the computer account and then successfully resolve the computer name to an IP address. From AD System Discovery flowchart the following attributes are mandatory: Active Directory Site Name ObjectGUID Active Directory Path Operating System Domain Active Directory System Group Discovery provides additional information about group memberships for resources previously discovered by Active Directory System Discovery. This method does not discover new resources; it adds group information to previously discovered resources. Code 0x80005010 means E_ADS_COLUMN_NOT_SET As my investigation if AD System Discovery works and computers are discovered then in All systems collection you can find them, you can ignore this WARN message. As I know it's a known bug to Microsoft, and their suggestion is: The discovery record for this computer is used to push the SCCM client agent out. Once the SCCM client agent installs it collects the %domain% within Inventory and sends back up to the SCCM SQL Database. So, WARN: Could not get property (domain) for system (0x80005010) is not the root cause of AD System Discovery failed to create DDRs. My suggestion is, open the adsysdis.log for any error exists. Thanks