Jump to content


taylormcc

duplicate guid in SCCM 2012 R2

Recommended Posts

Hi, I am running SCCM 2012 R2 and I have an issue with duplicate GUIDs. At any given time, only one of this group of machines appear in the SCCM console.

The machines were unfortunately made from the same image that already had a SCCM client installed on it.

I have tried the following on the client:

stop the sms agent host service

delete smscfg.ini

delete the certificates from the sms certificate store

run ccmdelcert on the machine

run tranguid /r

uninstall the client

reinstall the client

 

 

After this, the machines still have the same:

SMS Unique Identifier

SMS Hardware Identifier 2

 

And they still only one of them shows up at a time in the console

 

Please help me to resolve this issue

Thanks

Share this post


Link to post
Share on other sites


After some testing I found that I can cause the client to generate a new GUID, but the moment it connects to the server, the GUID in smscfg.ini is replaced with the bad common GUID.

Share this post


Link to post
Share on other sites

Stop the SMS Agent Host service. Run CMD as admin and run "c:\windows\ccmsetup\ccmsetup.exe resetkeyinformation=true"

Share this post


Link to post
Share on other sites

Stop the SMS Agent Host service. Run CMD as admin and run "c:\windows\ccmsetup\ccmsetup.exe resetkeyinformation=true"

Hi Jorlando,

Thank you so much for your suggestion. I tried this on 4 of the 17 computers that are having this problem.

 

Unfortunately, after the ccmsetup completes, the computers still have the same guid. They do not uniquely show up in the console.

 

Do you have any other suggestions?

 

Thanks,

Taylor

Share this post


Link to post
Share on other sites

This is what shows up in the ClientIDManagerStartup log

<![LOG[[RegTask] - Client is not registered. Sending registration request for GUID:A9F683AB-4A0A-4ED2-AECC-A83C391DDF8D ...]LOG]!><time="12:02:34.539+240" date="08-25-2014" component="ClientIDManagerStartup" context="" type="1" thread="396" file="regtask.cpp:1609">
<![LOG[[RegTask] - Client registration is pending. Server assigned ClientID is GUID:861CA527-E4CA-4963-B943-96AE1046AD61]LOG]!><time="12:02:34.617+240" date="08-25-2014" component="ClientIDManagerStartup" context="" type="1" thread="396" file="regtask.cpp:1639">
<![LOG[[RegTask] - Sleeping for 60 seconds ...]LOG]!><time="12:02:34.632+240" date="08-25-2014" component="ClientIDManagerStartup" context="" type="1" thread="396" file="regtask.cpp:1420">
<![LOG[[RegTask] - Client registration is pending. Sending confirmation request for GUID:861CA527-E4CA-4963-B943-96AE1046AD61 ...]LOG]!><time="12:03:34.648+240" date="08-25-2014" component="ClientIDManagerStartup" context="" type="1" thread="396" file="regtask.cpp:1721">
<![LOG[[RegTask] - Client is registered. Server assigned ClientID is GUID:861CA527-E4CA-4963-B943-96AE1046AD61. Approval status 0]LOG]!><time="12:03:34.726+240" date="08-25-2014" component="ClientIDManagerStartup" context="" type="1" thread="396" file="regtask.cpp:1730">

 

 

I can make the client think that it should have a new GUID, but as soon as it communicates with the server, the server assigns it the old bad common GUID.

I have deleted all of the clients from the SCCM console, but they seem to be lingering in the server database.

 

 

Share this post


Link to post
Share on other sites

have you tried the below:-

 

Identify the systems with a duplicate GUID

  1. Delete the c:\windows\smscfg.ini file from the client
  2. Run CCMDELCERT on the client (*)
  3. Restart the SMS Client agent (SMS Agent Host)
  4. A new GUID will be generated

Share this post


Link to post
Share on other sites

 

have you tried the below:-

 

Identify the systems with a duplicate GUID

  1. Delete the c:\windows\smscfg.ini file from the client
  2. Run CCMDELCERT on the client (*)
  3. Restart the SMS Client agent (SMS Agent Host)
  4. A new GUID will be generated

 

Hi, thank you for your suggestion. When I do this, the client temporarily gets a new GUID. Once it has contacted the server, the server assigns it the old common GUID.

The ClientIDStartupManager.log shows the following:

<![LOG[[RegTask] - Client is not registered. Sending registration request for GUID:45E5384F-3D9F-4C0F-B40A-9C14EA574785 ...]LOG]!><time="10:13:59.626+240" date="09-03-2014" component="ClientIDManagerStartup" context="" type="1" thread="3488" file="regtask.cpp:1609">

<![LOG[[RegTask] - Client registration is pending. Server assigned ClientID is GUID:19CE6066-6190-4C98-A616-ABB793D29601]LOG]!><time="10:13:59.720+240" date="09-03-2014" component="ClientIDManagerStartup" context="" type="1" thread="3488" file="regtask.cpp:1639">

<![LOG[[RegTask] - Sleeping for 60 seconds ...]LOG]!><time="10:13:59.735+240" date="09-03-2014" component="ClientIDManagerStartup" context="" type="1" thread="3488" file="regtask.cpp:1420">

<![LOG[[RegTask] - Client registration is pending. Sending confirmation request for GUID:19CE6066-6190-4C98-A616-ABB793D29601 ...]LOG]!><time="10:14:59.749+240" date="09-03-2014" component="ClientIDManagerStartup" context="" type="1" thread="3488" file="regtask.cpp:1721">

<![LOG[[RegTask] - Client is registered. Server assigned ClientID is GUID:19CE6066-6190-4C98-A616-ABB793D29601. Approval status 0]LOG]!><time="10:14:59.827+240" date="09-03-2014" component="ClientIDManagerStartup" context="" type="1" thread="3488" file="regtask.cpp:1730">

 

Where 45e53... was the new GUID

and 19ce60... was the bad old common GUID.

 

Thanks again.

 

post-21382-0-30741300-1409753719_thumb.png

Share this post


Link to post
Share on other sites

Does anyone else have any insight on this? We are going to be opening up a support case with Microsoft for this but I would like to try everything possible before making the call.

Thank you in advance.

Share this post


Link to post
Share on other sites

Did you find a solution to this? I have the same problem and symptoms... Computers imaged with SCCM client installed. I can get the GUID to change using ccmdelcert or deleting smscfg.ini but upon a reboot it will revert back to the old/bad GUID. Thanks.

Share this post


Link to post
Share on other sites

Did you find a solution to this? I have the same problem and symptoms... Computers imaged with SCCM client installed. I can get the GUID to change using ccmdelcert or deleting smscfg.ini but upon a reboot it will revert back to the old/bad GUID. Thanks.

Hi Rudy,

Unfortunately I did not find a solution. The tech from Microsoft tried many things but eventually said I'd need to make a new clean image (without the SCCM client on it)

Share this post


Link to post
Share on other sites

What i have done is , I run SCCM build task sequence to build the Gold master, which puts the gold master in the domain. then I do these steps:

Open administrative cmd prompt, do a NET STOP CCMEXEC to stop this service

* Open the certificate console for the local computer, delete the two certs displayed in the SMS node (MMC > Certificates > Local Computer)

* Delete the smscfg.ini from C:\windows\

* Lastly, sysprep the VM with an unattained answer file.

Sys prep puts the PC into a workgroup. then I take the snap shot for VDI.

once the pool is recompose with this GM, the first VM to come online from the pool gets a unique GUID (this is different to the GM GUID) and shows up in the SCCM console. once the second vm comes online, that VM takes the same GUID as the first VM and the first VM disappear from the SCCM console and only the second VM shows up in the console. once all the VMs comes online in that pool. only the last VM to come online appears in the SCCM console because they all have the same GUID.

not sure what i am doing wrong.

Share this post


Link to post
Share on other sites

I also have a duplicate GUID problem and have tried all solutions with no success. It sounds like the database is not removing the duplicate GUID when the computer is removed from SCCM. Is there a way to go into the database and delete the duplicate GUIDs? I know that sounds scary but attacking this problem from the client end is not resolving the issue.

Share this post


Link to post
Share on other sites

Hi,

 

Could you go in Certificates > Local Computer > Personal, and check on two machines that have duplicate GUID if they do not share the same machine certificate due to image ? If not, just take a look in the other folders to check suspicious duplicate certificate.

Share this post


Link to post
Share on other sites

Hi,

Has this problem been resolved? We had this same problem.

 

After several calls to MS my homeslice and I got it working.

 

 

Identifed 2 machines

 

Stopped the CCMEXEC service on the client

 

Deleted the SMS certificates (if any)

 

Deleted SMSCFG.ini

 

Ran the sql query using both machine names to clean the db. (see below)

 

Uninstalled the Client using ccmsetup.exe /uninstall

 

Reinstalled the client.

 

 

 

Run this query on the DB server. If you have dups, this will confirm it. Replace "computername" with the problem device and execute.

 

select * from System_DISC where Name0 like '%computername%'

 

In order to delete duplicate guids, run this.Replace "computername" with the problem device.

DECLARE @Name VARCHAR(25)
SET @Name = 'compuername'
DELETE FROM SYSTEM_DISC WHERE Name0 = @Name
DELETE FROM ClientKeyData WHERE SMSID IN (SELECT SMS_Unique_Identifier0 FROM SYSTEM_DISC WHERE Name0 =@Name)
DELETE FROM MachineIdGroupXRef WHERE MachineID IN (SELECT ItemKey FROM SYSTEM_DISC WHERE Name0 = @Name)
DELETE FROM System_AUX_Info WHERE Netbios_Name0 = @Name
DELETE FROM ImportedMachineIdentity WHERE ItemKey IN (SELECT ItemKey FROM SYSTEM_DISC WHERE Name0 = @Name)

 

 

Good luck...What a pain in the the #$#$ this was!

 

 

 

Share this post


Link to post
Share on other sites

This is to add onto what Scott Schaaf mentioned. 

 

I wanted to share my experience in case people out there needs help.

You can get a report that shows computers that might share the same GUID.

I am using SCCM 1810.

On the lower left, you will see "Monitoring".  It's in between "Software Library" and "Administration"

 


Now click on "Overview" then "Reporting".  Click on "Reports".  From the search area type in the word unique and search for it.  You will see a report that is named "Computers that might share the same Configuration Manager Unique Identifier".  Open that.

 

That's is just the beginning, to completely give a unique SMS GUID, you need to do this.


1.Run the SQL
2.Stop SMS Agent Host service
3.Delete SMSCFG from C:\Windows
4.Delete the SMS Certificate
5.CCMSetup.exe /uninstall
6.CCMSetup.exe


1. Run the SQL

Do this on the SQL server that SCCM is on. If you have multiple databases, select the SCCM database and do a "New Query"

You run two queries.  One query is to find the duplicate GUID based on the computer name.  The second query is to delete the duplicate GUID based on the computer name.
**I didn't write the queries and all credits goes to the person who wrote it**

Run this query on the DB server.
If you have dups, this will confirm it. Replace "ComputerName" with the problem device and execute.

select * from System_DISC where Name0 like '%ComputerName%'

In order to delete duplicate guids, run this.
Replace "ComputerName" with the problem device.

DECLARE @Name VARCHAR(25)
SET @Name = 'ComputerName'
DELETE FROM SYSTEM_DISC WHERE Name0 = @Name
DELETE FROM ClientKeyData WHERE SMSID IN (SELECT SMS_Unique_Identifier0 FROM SYSTEM_DISC WHERE Name0 =@Name)
DELETE FROM MachineIdGroupXRef WHERE MachineID IN (SELECT ItemKey FROM SYSTEM_DISC WHERE Name0 = @Name)
DELETE FROM System_AUX_Info WHERE Netbios_Name0 = @Name
DELETE FROM ImportedMachineIdentity WHERE ItemKey IN (SELECT ItemKey FROM SYSTEM_DISC WHERE Name0 = @Name)


2. Stop SMS Agent Host service

Open a RUN command and type services.msc.
Browse to SMS Agent Host and STOP the service.

3. Delete SMSCFG.ini from C:\Windows

4. Delete the SMS Certificate

Open a RUN command and type MMC
Go to File and select "Add/Remove Snap-in"
Add the "Certificates"
Click OK
Radio check "Computer account"
Clikc Next
Radio check "Local Computer"
Click Finish
Click OK

Scroll down to SMS >> Certificates.
Delete the SMS Certificates

5. CCMSetup.exe /uninstall

Open File Explorer and browse to
C:\Windows\ccmsetup

Open a command prompt and change directory
cd C:\Windows\ccmsetup

Type the following
ccmsetup.exe /uninstall

*Refresh your File Explorer and make sure that only two items exist.
The two items are: Logs and ccmsetup.exe
If you don’t see other items being deleted, make sure to run the command again and keep refreshing your File Explorer each time until you see the data being deleted.  Remember, only two items should exist.

Monitor the uninstallation of Configuration Manager from the Control Panel. Give it a few minutes and refresh the Control Panel. Make sure the Configuration Manager is gone.


6.CCMSetup.exe

Make sure your File Explorer is still open.  If not, browse to
C:\Windows\ccmsetup
Open a command prompt and change directory
cd C:\Windows\ccmsetup
Click Enter on your keyboard to move to the next line
Type in the following and press Enter once done

CCMSetup.exe

*Monitor the C:\Windows\ccmsetup directory.  You will start to see other items populating the directory.
If you don’t, execute the command above again.


You can view the SMSCFG.ini files to see the unique key in C:\Windows

You can view in SCCM the status of the client.  Give it a few minutes and it will turn green.

 

 

Edited by slyaii

Share this post


Link to post
Share on other sites

Hi Scott and slyaii

THANK YOU VERY MUCH FOR YOUR SOLUTION

Could you please suggest how to avoid this Duplicate UUID assignment by SCCM going forward ? do we need to remove the config mgr client from the master VM template and install separately once the server built?

Each time the manual steps fix will be a time consuming. so how to avoid this issue in future.

Thanks & Regards,

Dhanabal M

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...