I have a collection based on a OU query for a OU with machines in it, and it populates the collection with machines, so thats fine. But when i compare my collection to the OU in AD the collection has more computers in it then the OU in AD. This is my query: select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System where SMS_R_System.SystemOUName = "domain.local/Shipping/HR/Clients/Desktops" Replacing the last string with my own path Any ideas? Thanks

When you run the AD system group discovery process you need to make sure you run it against OU's where all computer represented. Otherwise the objects will not be updated which is why you have some objects in a colection eventhough it's not in an OU.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Hello - All the computers in that OU are present in "all Systems" collection? Otherwise, we may need to look into discovery process and schedules.Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The AD system group discovery runs at the company.domain.local, so it will find all the OUs under that, right? Here is the path under the process: LDAP:\\DC=Company,DC=domain,DC=local Recursive = yes, Group = Excluded

Some are missing in all systems and a couple has double entries in all systems. One with Client = yes and One with clint = No

Every time you re-image a workstation a new SCCM object is created for it - even if you give it the same name. The old object then becomes "obsolete" and if you have the tasks to delete obsolete objects enabled (they are disabled by default) eventually the those are completely deleted from the database. There are other occasions where multiple objects might be created for the same computer as well, but this would help explain the duplicate entries you have. As for you missing entries, a DDR is only created for a computer if it can be resolved into an IP address during System Discovery. Check your AD System Discovery log file to see if there where any errors reported for the computers you cannot see in there. In short, it sounds like you just have to keep you data a bit more tidy really... One of the things I normally do for AD OU based collections is to limit them to my collection of "healthy clients" - i.e., objects that have a client installed, are not obsolete, have a site code, are assigned and did a last inventory check less than 90 days ago. That removes all the duplicate ones and gives me only the ones I know I can actually deploy things to. Hope this helps, cogu

If some are missing then those objects are not discovered through SCCM discovery mechanism?Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I agree with Cogu. AD Discovery is not a (two-way) synch. Not everything will be "discovered" and deletions in AD do not propogate to ConfigMgr. AD Discovery simples polls AD for valid objects and creates (or updates) the resource in ConfigMgr. That's it.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

One strange things is that I have clients that one day has some advertisment in RAP and the next day the RAP is empty and the are to clients in All systems one with a client and one without. What can be wrong then?