SCCM Clients appear twice in Console after OS re-installation
Hi, When we re-install a client computer, (Win XP to Win 7), the SCCM client appears in double in the Configuration Manager Console. The first one appears as an "Obsolete" client and the second one appears correctly. We created collections that are linked to OU and we can see the "obsolete" client in the collection. But when we delete the "obsolete" client in SCCM, the collection doesn't show the SCCM client in the OU collection. Here's the process that the technician is doing when reimaging: - Delete computer from SCCM (Because the Task sequence is advertise to Unknown Computers) - Reset account in Active Directory (to keep the same computer name) - Re-Image the pc from Windows XP to Windows 7 using Task sequence The computer joins the domain correctly. We can connect remotely on the client using remote tools. The Hardware and Software scans are ok.
March 25th, 2011 6:04pm

Hi, Here is a great post explaining why obsolete records are created.. http://danielssccmworld.blogspot.com/2010/09/managing-conflicting-records-and.html I normally use the following solution for merging obosolete records with a script. http://ccmexec.com/?p=1047 I hope this helps, Regards, jörgen-- visit my System center blog at http://ccmexec.com --
Free Windows Admin Tool Kit Click here and download it now
March 25th, 2011 6:42pm

Hi, We got some development for this problem. We found that the problem was caused by the poll from the AD system Group Discovery. The polling is schedule to run every day at midnight. When we reimage a computer, we delete the sccm client from the console. During the reimage process, it creates the SCCM Client correctly, but when the polling runs, it recreates the second SCCM client with no attributes. So we have 2 SCCM clients in the console for the same computer. 1 that is having the correct info and the other one is containing no informations at all. (Obselete column is empty) It looks like that during the installation of the SCCM Client in the imaging process, it doesn't link the client to AD object (That we reset the account before start the image process) Is there's something we are doing wrong or that we should do differently.
March 29th, 2011 9:01am

Take a look at this explaining why there will be multiple records when OS gets installed on the target computer and how to handle Duplicate SMSID's. http://support.microsoft.com/kb/837374 //Eswar Koneti @ www.eskonr.com
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2011 9:29am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics