Hi Geniuses, I have a very strange problem with the collection query based on a OU. For example.: i have 600 active clients in a OU and i can see them in the default collections in SCCM. Then i created a new collection based on OU. only 100+ clients can be found in that collection. and this not only happen on one or two OU. seems all the OUs in my domain have the same issue. AD system discover is enabled and all the LDAP added. Query is like this 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 = "company.org/company/APAC/site/COMPUTERS" Does anyone kindly give me some threads? any mistake i did? Thanks a lot! Jason

can you check if all the 600 computers are in single OU OR are they in subOU's as well ? Check this out if you want to include sub OU computers as well http://eskonr.com/2009/11/collections-based-on-the-ou/ You can also monitor AD system Group discovery as well http://technet.microsoft.com/en-us/library/bb694071.aspx Try with this Qeury : 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 like "company.org/company/APAC/site/COMPUTERS%" //Eswar Koneti @ http://eskonr.com/

Hi Eswar, Appreciate your suggestion. i will try it now for the question: these computer are under 2 sub OU Computer/Desktops and Computer/Mobiles. But as far as i know. whatever which query i used. it was supposed to include sub OUs by default. weird. thanks Jason

Hi Eswar, just tried your query. no change...:(

If the query doesnt give you all the machines with OU criteria,SCCM DB might not have OU information for the rest of the machines . What does adsysgrp.log says ? Do you see any warnings/errors messges under SMS_System_group discovery_agent ? //Eswar Koneti @ http://eskonr.com/

Lot of errors like this INFO: discovered object with ADsPath = 'LDAP://HDC-INFR-DC03.ubisoft.org/CN=XXX-WKS-AA008,OU=Mobile,OU=Computers,OU=site,OU=region,OU=company,DC=company,DC=org' SMS_AD_SYSTEM_DISCOVERY_AGENT 1601/1/1 0:00:00 14312 (0x37E8) WARN: Could not get property (domain) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 1601/1/1 0:00:00 14312 (0x37E8)

take a look at this thread on this http://social.technet.microsoft.com/Forums/en/configmgrgeneral/thread/a6be8c13-334d-4a93-9141-d55d6e5bf441 //Eswar Koneti @ http://eskonr.com/

Thanks !

I'm seeing the same error, "Could not get property (domain)", in both, the AD system discovery log and the AD system group discovery log. INFO: DDR was written for system 'XXX-LAP-AA204' - D:\SCCM\inboxes\auth\ddm.box\adh66s3q.DDR at 8/5/2010 2:0:1. SMS_AD_SYSTEM_GROUP_DISCOVERY_AGENT 1601/1/1 0:00:00 11956 (0x2EB4) it does seem that the DDRs are being created and applied to the systems' properties. but this didn't explain my question. why I can see the clients in SCCM just cannot query them into a collection by use OU query?

The 600 computer are assigned to the same SCCM site? Do you have many SCCM sites or only one?

Try and find one (or a few) of the computers that are in the all systems collection, but not in your OU query collection. Once you've found one, right click it and choose properties. Scroll down the information and check what is displayed for the OU details. If it's got the correct OU information in, then it narrows it down to a query problem, but if the OU information isn't displayed there you've got a discovery issue. Let us know, SBMy System Center Blog

The 600 computer are assigned to the same SCCM site? Do you have many SCCM sites or only one? Yes..assigned to one site code. but we have 3 SCCM sites.

Did you enabled system group discovery on each sites? System group disovery works only on assigned client, so you need to enable it on each site where you have clients

Any feedback on my previous question above for a bit more info as like jdulongc says above it would help to narrow down if it's a discovery that needs enabling or a query issue.My System Center Blog

Try and find one (or a few) of the computers that are in the all systems collection, but not in your OU query collection. Once you've found one, right click it and choose properties. Scroll down the information and check what is displayed for the OU details. If it's got the correct OU information in, then it narrows it down to a query problem, but if the OU information isn't displayed there you've got a discovery issue. Let us know, SB My System Center Blog I've checked some problem clients. seems them missing the information like below System OU Name[0] System OU Name[1] System OU Name[2] Is that related to a discovery issue?

Any feedback on my previous question above for a bit more info as like jdulongc says above it would help to narrow down if it's a discovery that needs enabling or a query issue. My System Center Blog Hi Steve, Thanks for your suggestions. I've checked some problem clients. seems them missing the information like below System OU Name[0] System OU Name[1] System OU Name[2] Is that related to a discovery issue?

Here's a way to approach troubleshooting this. - Pick 1 specific computer that does not have OU information (System OU Name[0], etc). - Determine which site code that computer belongs to (I'll make one up, call it ABC) - On the Site Settings for the site ABC, confirm that System Group Discovery is enabled, and that it is defined to discover resources in the domain and OU to which you have already independently (by looking at Active Directory Users and Computers) confirmed that this 1 specific computer belongs to. - On that Site, while monitoring adsysgrp.log, invoke a System Group Discovery (run as soon as possible). Monitor adsysgrp.log for that specific computer name, and see if that specific computer fails to be discovered. Potential tip: if you have tons of computers on that site, you *could* *maybe*, remove all of the existing system group discovery rules, and put in just 1 single rule for the specific OU in which that sample computer lives, to narrow the number of entries you get in the log file. All of the above is simply to monitor the log, and hopefully get an idea of why sysgrp discovery is failing to gather the OU information. It's not a fix--it's a troubleshooting step just to see what is going on more accurately.Standardize. Simplify. Automate.

Now that we've narrowed it down to what looks like a discovery problem, I couldn't have suggested a better way to troubleshoot further than what Sherry just has! Let us all know how you get on. Cheers, SBMy System Center Blog

Hi, Thanks a lot for the answer. the problem was because i didn't add the Computers OU in group discovery. Now it working fine. Regards Jason