Failing to reinstall client
We found several SCCM 2007 R2 clients that had duplicate GUIDs, we got most of them cleaned up but there are a few that will not reinstall. Initially we tried stopping CCMExec, deleting the certificates, deleting/renaming SMSCfg.ini, then restarting CCMExec. This worked for most, but a few did not get a new GUID so we uninstalled/reinstalled. CCMsetup.log shows success, CCMExec is running, a new SMSCfg.ini gets created but it doesn't have the "SMS Unique Identifier" line. ClientIDManagerStartup.log shows this every time: Client settings prohibit local GUID generation, no smsid will be (re)generated. Smsid is missing but (re)generation is disabled. I found a few posts that talk about deleting the certificates, but we've tried that using the MMC and command line tools. ClientIDManagerStartup.log RegTask - Executing registration task synchronously. ClientIDManagerStartup 8/27/2010 10:34:34 AM 7004 (0x1B5C) Evaluated SMBIOS (encoded): 4A00500033004C0039004B003122 ClientIDManagerStartup 8/27/2010 10:34:34 AM 7004 (0x1B5C) SMBIOS unchanged ClientIDManagerStartup 8/27/2010 10:34:34 AM 7004 (0x1B5C) SID unchanged ClientIDManagerStartup 8/27/2010 10:34:34 AM 7004 (0x1B5C) HWID unchanged ClientIDManagerStartup 8/27/2010 10:34:34 AM 7004 (0x1B5C) RegTask: Initial backoff interval: 1 minutes ClientIDManagerStartup 8/27/2010 10:34:35 AM 7004 (0x1B5C) RegTask: Reset backoff interval: 257 minutes ClientIDManagerStartup 8/27/2010 10:34:35 AM 7004 (0x1B5C) GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=TRUE ClientIDManagerStartup 8/27/2010 10:34:36 AM 7004 (0x1B5C) Computed HardwareID=2:BAC1017831F16DABA0AC62C3DC19660E3944B7EE Win32_SystemEnclosure.SerialNumber=OO3L9K1 Win32_SystemEnclosure.SMBIOSAssetTag=<empty> Win32_BaseBoard.SerialNumber=.OO3L9K1.CN129619572855. Win32_BIOS.SerialNumber=OO3L9K1 Win32_NetworkAdapterConfiguration.MACAddress=<Not used on laptop> ClientIDManagerStartup 8/27/2010 10:34:36 AM 7004 (0x1B5C) RegTask: Client is not registered. Sending registration request... ClientIDManagerStartup 8/27/2010 10:34:36 AM 7004 (0x1B5C) RegTask: Client registration is pending. ClientIDManagerStartup 8/27/2010 10:34:36 AM 7004 (0x1B5C) RegTask: Client is pending registration. Sending confirmation request... ClientIDManagerStartup 8/27/2010 10:34:37 AM 7004 (0x1B5C) RegTask: Server requested reset. Restarting client registration ClientIDManagerStartup 8/27/2010 10:34:37 AM 7004 (0x1B5C) RegTask: Initial backoff interval: 1 minutes ClientIDManagerStartup 8/27/2010 10:34:39 AM 7004 (0x1B5C) RegTask: Reset backoff interval: 257 minutes ClientIDManagerStartup 8/27/2010 10:34:39 AM 7004 (0x1B5C) Already refreshed within the last 10 minutes, Sleeping for the next 9 minutes before reattempt. ClientIDManagerStartup 8/27/2010 10:34:39 AM 7004 (0x1B5C) GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=TRUE ClientIDManagerStartup 8/27/2010 10:44:35 AM 7004 (0x1B5C) Computed HardwareID=2:BAC1017831F16DABA0AC62C3DC19660E3944B7EE Win32_SystemEnclosure.SerialNumber=OO3L9K1 Win32_SystemEnclosure.SMBIOSAssetTag=<empty> Win32_BaseBoard.SerialNumber=.OO3L9K1.CN129619572855. Win32_BIOS.SerialNumber=OO3L9K1 Win32_NetworkAdapterConfiguration.MACAddress=<Not used on laptop> ClientIDManagerStartup 8/27/2010 10:44:35 AM 7004 (0x1B5C) RegTask: Client is not registered. Sending registration request... ClientIDManagerStartup 8/27/2010 10:44:35 AM 7004 (0x1B5C) RegTask: Client is registered. ClientIDManagerStartup 8/27/2010 10:44:35 AM 7004 (0x1B5C) RegTask: Client is registered. Exiting. ClientIDManagerStartup 8/27/2010 10:44:35 AM 7004 (0x1B5C) Read SMBIOS (encoded): 4A00500033004C0039004B003122 ClientIDManagerStartup 8/27/2010 10:44:35 AM 2052 (0x0804) Evaluated SMBIOS (encoded): 4A00500033004C0039004B003122 ClientIDManagerStartup 8/27/2010 10:44:35 AM 2052 (0x0804) No SMBIOS Changed ClientIDManagerStartup 8/27/2010 10:44:35 AM 2052 (0x0804) SMBIOS unchanged ClientIDManagerStartup 8/27/2010 10:44:35 AM 2052 (0x0804) SID unchanged ClientIDManagerStartup 8/27/2010 10:44:35 AM 2052 (0x0804) HWID unchanged ClientIDManagerStartup 8/27/2010 10:44:35 AM 2052 (0x0804) Client settings prohibit local GUID generation, no smsid will be (re)generated. ClientIDManagerStartup 8/27/2010 10:44:35 AM 2052 (0x0804) Smsid is missing but (re)generation is disabled. ClientIDManagerStartup 8/27/2010 10:44:35 AM 2052 (0x0804) Any ideas? thanks!
August 27th, 2010 9:23pm

I'd probably try running ccmclean on one, delete the SMSCFG.ini file if ccmclean doesn't do that. Delete the record from the database, then re-push the client. Be aware though that ccmclean is unsupported on SCCM client but I have used it and I've had no issues with it. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
August 28th, 2010 9:57pm

Thanks for the suggestion. I tried again using ccmclean.exe and deleting the smscfg.ini and record in the DB. No luck, same errors. I noticed ccmclean did not delete the 2 SMS certificates, so I tried again and deleted those manaully, same errors. It also leaves behind the SMS registry key, I tried deleting that as well. Using WbemTest.exe I made sure the CCM namespace in WMI was gone, and rebooted the client just to be safe. Does anyone even know what these lines in ClientIDManagerStartup.log are talking about? What "settings" are prohibiting this? I saw a post from the great Wally a while back saying he didnt even know what this was referring to. Client settings prohibit local GUID generation, no smsid will be (re)generated. Smsid is missing but (re)generation is disabled.
August 31st, 2010 8:51pm

Update: Deleting the old resource from the SCCM console before re-installing worked for a couple machines, but not most. I'm out of ideas!
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2010 1:59am

Another thing that is confusing, Roger Zander's SCCM Client Center still shows the old (duplicate) GUID, when it should be empty. This is after I stopped the CCMExec service, renamed SMSCfg.ini, then started the service, and a new SMSCfg.ini was created without a GUID in it. This tells me that the old GUID is still stored in WMI or somewhere besides the INI file. I'll do a little WbemTest spelunking.
September 3rd, 2010 6:21pm

That's interesting. I have manually changed them before and his tool instantly knew it. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
September 4th, 2010 12:58am

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

Other recent topics Other recent topics