I have created an updates test group in AD with 5 clients. Clients 2, 3 and 4 appear in the SCCM collection, client 1 refuses to appear even though it is an SCCM client. I have reinstalled the SCCM client on Client1 and also redid the SQL query against a second group but it still does not want to appear. The SQL statement I am using is: 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.SystemGroupName = "DOMAIN\\SCCM Update Test"

Hi, When you right-click client1 in the ConfigMgr console can you check if it has the group names under discovery data? See also: http://www.jannesalink.com/blog1.php/2008/10/16/deploy-sccm-packages-based-on-active-dir Follow me through my blog and Twitter!

Hi James; Thanks for the quick response, There are no group names under the discovery data, what do I need to do to populate? Regards Mark

Instead of reinstalling client on these machines, please uninstall client properly and then reinstall it. just update your collection within few minutes and recheck. Pls let me know what do you get then? thnx.

Hi Atul; Still the same. I have even moved the test group to the correct OU and it appears in the console as a recognised group. One of the computers in question has different groups in SCCM compared with AD; In SCCM, it is a member of Domain and Visio, in AD it is a member of DOmain and Updates Test? Regards Mark

Have you enabled AD system and AD system group discoveries? cd you pls check whether this "Updates test" group/ machine is showing in adsgdis.log/adsysgrp.log respectively. Pls confirm. thnx.

Did your machine finally populate into the collection after discovery was corrected?http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

By the way: there is absolutely no need to reinstall the client in such a scenario as long as the discovery property (= AD group membership) does not appear in the ConfigMgr database. The client is not involved in that process.

After AD discovery ran / and collection refresh it should pull in the remaining client and then the client will appear in the list with the others. We can assume discovery is working because the other computers are listed in the collection.http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com