All, We are seeing a strange problem where if we build a new client or server machine, we will notice the machine show up twice in the All System's collection. The first entry will show that it is Approved and the client is installed. The second entry will show it is not approved and no client installed. When I double click on the computer to view its information, I find the following: Machine that says it is approved: Shows that the Agent Name[1] is MP_ClientRegistration Machine that says it is not approved: Shows that the Agent Name[1] is SMS_AD_SYSTEM_GROUP_DISCOVERY Which makes sense because we run the SMS AD system group discovery as we have built collections which have queries based on a machines AD OU membership. The problem is that the machine that shows it is not approved ends up being the one that goes into the AD query based collection we setup and the correct one (the one that is approved) stays in the All Systems collection. Any suggestions on how I can solve this? Thanks!

Were those machines previuosly SCCM clients?

Were those machines previuosly SCCM clients? Nope, they are brand new client installs -- machines fresh out of the cardboard box.

Hi Sam, 1. Reson is It happens when the computer joins the domain during OSD and an AD system discovery runs before the client on the machine registers and heartbeats in to the MP. 2.If the AD discovery runs between the the time the TS contacts the computer to AD and the ConfigMgr client talks to the MP you'll have 2 systems in the console with the same name. One will have the client and one will be found by the AD system discovery. If I delete the duplicate that doesn't have the client, the next time AD discovery runs, it adds the information to the existing computer. 3.If the AD discoveries run after the client does the MP_ClientRegistration and Heartbeat discovery it only has one record Solution : 1. Go to Site Database>>Site Management>>SITE>>Site Settings>>Discovery Methods ( Disable the discovery or cahnge the schecdule so that it should not conflict wit TS timing) 2. Note the Disable option is for testing whether AD Discovery is really the issue or not? 3. Below is the link why i am giving more blame to discovery method . http://www.myitforum.com/articles/42/view.asp?id=11264 Hope this will help u to solve the issue ?

Hi Sam, 1. Reson is It happens when the computer joins the domain during OSD and an AD system discovery runs before the client on the machine registers and heartbeats in to the MP. 2.If the AD discovery runs between the the time the TS contacts the computer to AD and the ConfigMgr client talks to the MP you'll have 2 systems in the console with the same name. One will have the client and one will be found by the AD system discovery. If I delete the duplicate that doesn't have the client, the next time AD discovery runs, it adds the information to the existing computer. 3.If the AD discoveries run after the client does the MP_ClientRegistration and Heartbeat discovery it only has one record Solution : 1. Go to Site Database>>Site Management>>SITE>>Site Settings>>Discovery Methods ( Disable the discovery or cahnge the schecdule so that it should not conflict wit TS timing) 2. Note the Disable option is for testing whether AD Discovery is really the issue or not? 3. Below is the link why i am giving more blame to discovery method . http://www.myitforum.com/articles/42/view.asp?id=11264 Hope this will help u to solve the issue ? Amy, You got it spot on, thank you. Now that you mention it, I noticed this happening after we enabled the Delta updates (new feature in SP3). Turning off the Delta updates seems to have resolved the issue. Thank you for this!