SCCM 2012 R2 CU5 - Duplicate GUID on clients

Environment: SCCM 2012 R2 CU5, OS: Windows 2008 R2, Clients: Windows 7 SP1

I'm having some serious issues with duplicate GUIDs, after a new OSD of Windows 7 the configuration manager client has a unique identifier as confirmed in C:\Windows\SMSCFG.INI on the client, after another reboot the clients GUID changes to a common GUID. We have around 30 clients with this common GUID now, of course these cannot be managed correctly.

I have used the various scripts to change the GUID's so they are unique but they reset back shortly after. It seems the GUID is stored somewhere on the clients or in the SQL CM_DB. I've tried uninstalling the client and removing the SMSCG.ini completely but what ever I do they always seem to end up on the same GUID.

Any help is appreciated!

• Edited by Hutchnet Wednesday, May 13, 2015 8:16 AM

• Edited by Hutchnet Wednesday, May 13, 2015 10:41 AM

I've never had this issue running a build and capture with

Is anyone aware of a way of deleting duplicates from SQL, the below query highlights a number of duplicates:

* from v_GS_System inner join v_HS_System on v_HS_System.ResourceID = v_GS_System.ResourceID where v_GS_System.Name0 <> v_HS_System.Name0

As mentioned, it's time to open a case with Microsoft CSS. Messing with SQL directly is unsupported and could cause all kinds of havoc because of the many triggers, relationships, etc. happening behind t

Hi

After a lot of troubleshooting I logged a call with Microsoft, the conclusion was that for some reason the reference image was the culprit even though we checked and it did not have a config agent installed, after recreation of the reference image new clients have unique GUID's. The fix for already affected clients is a complete rebuild! But this was just our case, if your issue is not image related you should be able to do the following:

Stop the CCMEXEC service

Rename c:\windows\SMSCFG.INI
Delete the SCCM certs at a command prompt run: certutil delstore SMS SMS

Start the service

If all new 2012 builds have the issue you should consider recreating your base image/build.

Cheers

• Marked as answer by Hutchnet Tuesday, August 25, 2015 1:15 PM

Hi

After a lot of troubleshooting I logged a call with Microsoft, the conclusion was that for some reason the reference image was the culprit even though we checked and it did not have a config agent installed, after recreation of the reference image new clients have unique GUID's. The fix for already affected clients is a complete rebuild! But this was just our case, if your issue is not image related you should be able to do the following:

Stop the CCMEXEC service

Rename c:\windows\SMSCFG.INI
Delete the SCCM certs at a command prompt run: certutil delstore SMS SMS

Start the service

If all new 2012 builds have the issue you should consider recreating your base image/build.

Cheers

Hi Hutchnet,

The problem servers where installed long before we had implemented SCCM in our organization. I don't know what image they used to install these servers, but i think that is the problem. We don't have any troubles with our other 350 servers.

The trick to remove the .ini and certificates does not resolve the problem, so i will start to rebuild the servers.

Thanks for your help,

Marcel

This seems to be the same issue that I am having. I also talked with Jason about this in another thread. Did you by chance use VMware for the base image?  

This is my scenario.

Initial build was a standalone 2008r2 server with hyper-v. I used a windows 7 hyper-v as the base machine will all applications installed (did not install sccm). I used MDT to capture the image from the hyper-V machine and deployed the image from the 2008 r2 server using WDS. Those machines were then rolled into the domain and then the sccm client was pushed to them. They are working just fine.

We then set up a small DHCP scope on the network and I moved the image files from the standalone machine to the main network on a 2012 server using MDT and WDS. I needed to make a change to the image and I used a VMware windows 7 VM to make the changes and then captured the image just like the 2008 r2 server using sysprep. That VMware image was the same except for just adding a license key or something else minor. I deployed the image to a few machines and it looked like all was good and that SCCM was working correctly, but it wasn't. The GUIDs were the same, deleting and recreating the .ini file seemed to gen a new guid but after a refresh the new .ini would revert back to a GUID that was in use. I also noticed that the SID when checking the properties in SCCM showed -500 for all machines that had the duplicate guid issue which is the local admin account.

So If you used VMware to create the image that maybe the issue, but I am not sure why or where the issue is. Rebuilding the machines over again sucks, but its something that maybe the only fix. I have used VMware to create windows 7 images before and no issue until this network.

Duplicate GUID Query#1
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 join SMS_GH_System_System on SMS_R_System.ResourceID = SMS_GH_System_System.ResourceID where SMS_R_System.Name <> SMS_GH_System_System.Name 

 Duplicate GUID Query#2
 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 join SMS_G_System_System on SMS_R_System.ResourceID = SMS_G_System_System.ResourceID where SMS_R_System.Name <> SMS_G_System_System.Name 

 Duplicate GUID Query#3
 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.ResourceID in (select SMS_GH_System_System.ResourceID from SMS_G_System_System join SMS_GH_System_System on SMS_G_System_System.ResourceID = SMS_GH_System_System.ResourceID where SMS_G_System_System.Name <> SMS_GH_System_System.Name)

• Edited by Wright54 16 hours 44 minutes ago

This seems to be the same issue that I am having. I also talked with Jason about this in another thread. Did you by chance use VMware for the base image?  

This is my scenario.

Initial build was a standalone 2008r2 server with hyper-v. I used a windows 7 hyper-v as the base machine will all applications installed (did not install sccm). I used MDT to capture the image from the hyper-V machine and deployed the image from the 2008 r2 server using WDS. Those machines were then rolled into the domain and then the sccm client was pushed to them. They are working just fine.

We then set up a small DHCP scope on the network and I moved the image files from the standalone machine to the main network on a 2012 server using MDT and WDS. I needed to make a change to the image and I used a VMware windows 7 VM to make the changes and then captured the image just like the 2008 r2 server using sysprep. That VMware image was the same except for just adding a license key or something else minor. I deployed the image to a few machines and it looked like all was good and that SCCM was working correctly, but it wasn't. The GUIDs were the same, deleting and recreating the .ini file seemed to gen a new guid but after a refresh the new .ini would revert back to a GUID that was in use. I also noticed that the SID when checking the properties in SCCM showed -500 for all machines that had the duplicate guid issue which is the local admin account.

So If you used VMware to create the image that maybe the issue, but I am not sure why or where the issue is. Rebuilding the machines over again sucks, but its something that maybe the only fix. I have used VMware to create windows 7 images before and no issue until this network.

Duplicate GUID Query#1
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 join SMS_GH_System_System on SMS_R_System.ResourceID = SMS_GH_System_System.ResourceID where SMS_R_System.Name <> SMS_GH_System_System.Name 

 Duplicate GUID Query#2
 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 join SMS_G_System_System on SMS_R_System.ResourceID = SMS_G_System_System.ResourceID where SMS_R_System.Name <> SMS_G_System_System.Name 

 Duplicate GUID Query#3
 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.ResourceID in (select SMS_GH_System_System.ResourceID from SMS_G_System_System join SMS_GH_System_System on SMS_G_System_System.ResourceID = SMS_GH_System_System.ResourceID where SMS_G_System_System.Name <> SMS_GH_System_System.Name)

• Edited by Wright54 Friday, July 10, 2015 3:03 PM

net stop "SMS Agent Host"
del c:\windows\SMSCFG.ini
certutil delstore SMS SMS
net start "SMS Agent Host"

This works as long as the client object that is deleted is an ACTIVE object. That is, the machine client object name must show Client YES. 

• Edited by tmac3931 11 hours 37 minutes ago

net stop "SMS Agent Host"
del c:\windows\SMSCFG.ini
certutil delstore SMS SMS
net start "SMS Agent Host"

This works as long as the client object that is deleted is an ACTIVE object. That is, the machine client object name must show Client YES. 

• Edited by tmac3931 Friday, September 04, 2015 8:17 PM