Virtual Machines created with MCS might acquire duplicate SCCM GUIDs

Virtual Machines created with MCS might acquire duplicate SCCM GUIDs

book

Article ID: CTX236683

calendar_today

Updated On:

Description

After creating multiple Virtual Machines, using Machine Creation Services, the SCCM (System Center Configuration Manager) might display only one Virtual Machine on its console.
This behavior is seen because all the Virtual Machines acquire a duplicate SCCM GUID.
Because all the machines have the same SCCM GUID, the SCCM Console only shows one Virtual Machine.

Looking at the smscfg.ini file on each Virtual Machine you can confirm that all of them in fact have the same SCCM GUID.
Following is an example of the smscfg.ini file (unrelated content was removed):

[Configuration - Client Properties]
SMS Unique Identifier=GUID:XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Previous SMSUID=GUID:XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
SMS Certificate Identifier=SMS;XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

The ClientIDManagerStartup.log shows that the SCCM Server assigns a duplicate GUID even when the Virtual Machine creates a new Unique GUID.
Following is an example of what might be found in the ClientIDManagerStartup.log file:
Note: in the following example the Unique GUID is represented as the text "UNIQUE GUID" and the duplicate as "DUPLICATE GUID". In a real log this values would show actual GUIDs.
Generated a new ClientID GUID:"UNIQUE GUID" as Identity store is empty. Re-registration is required.
[RegTask] - Client is not registered. Sending registration request for GUID:"UNIQUE GUID" ...
[RegTask] - Client registration is pending. Server assigned ClientID is GUID:"DUPLICATE GUID"
[RegTask] - Sleeping for 60 seconds ...
[RegTask] - Client registration is pending. Sending confirmation request for GUID:"DUPLICATE GUID" ...
[RegTask] - Client is registered. Server assigned ClientID is GUID:"DUPLICATE GUID". Approval status 1

Resolution

Solution 1 :
Make sure the SMS Host Service is configured to "Automatic Delayed Start" on the Master Image.

This should be the default setting in most circumstances, but it can be manually changed or configured through Group Policy.

Solution 2 :
- Delete VDI machines from SCCM. (Right click on the machine name and select Delete)
- Execute following on the VDI
net stop "SMS Agent Host"
del c:\windows\SMSCFG.ini
certutil –delstore SMS SMS
net start "SMS Agent Host"


- Run Discovery on SCCM server
On SCCM Console -> Administration
Right click on "Active Directory System Discovery" and select "Run Full Discovery Now"


- Wait for some time to get those VDIs listed in SCCM Console

Solution 3 :
If above solutions do not resolve the issue please contact Microsoft Support.




 

Problem Cause

This behavior seems to be caused by the SMS Agent Service starting during the Image Preparation phase of the Machine Creation Services process.

During this Preparation phase the following happens:
  • When the SMS Host service starts, it creates a certificate and adds it to the Windows Certificate store to be used by the SMS Host Service.
  • This Certificate then gets saved in the Base Disk so every Machine created by MCS will have this Certificate.
  • When the SMS Agent starts in the resulting machines, it creates a new Unique GUID, but because the certificate is the same for all the Machines, the SCCM Server ignores the Unique GUID and assigns a duplicate GUID to each and every Machine.