For those interested… I ended up opening a case with MS as I was unable to put together the right combination to solve the issue on my thin clients… Here is what we ended up with that will get you a new GUID
copy %WINDIR%\smscfg.ini %WINDIR%\smscfg.old start /wait c:\windows\ccmsetup\ccmsetup.exe /uninstall del %WINDIR%\smscfg.ini "%~dp0ccmdelcert.exe" "%~dp0ccmclean.exe" /all /q start /b /wait \\server\share\test.cmd<file:///\\server\share\test.cmd> the last line is simply calling ccmsetup with some params to reinstall cm client From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of steven hosking Sent: Friday, July 11, 2014 3:37 PM To: mssms@lists.myitforum.com Subject: Re: [mssms] RE: Resolving duplicate GUIDs Are the thin clients on the same domain as your SCCM server? And have you. Turned on HTTPS and defined a PKI? From: Jimmy Martin<mailto:jimmy.mar...@bmhcc.org> Sent: Saturday, 12 July 2014 6:02 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> True… you really have to do both… fix the cause and cure the children From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Jason Sandys Sent: Friday, July 11, 2014 2:07 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] RE: Resolving duplicate GUIDs You really should take a step back and solve the issue (root cause instead of the symptom) here though as getting a duplicate GUID is not normal. J From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Paul Winstanley Sent: Wednesday, July 2, 2014 9:30 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] RE: Resolving duplicate GUIDs Indeed. You should get a new GUUID On Wed, Jul 2, 2014 at 2:03 PM, Daniel Ratliff <dratl...@humana.com<mailto:dratl...@humana.com>> wrote: Yes, Paul’s method is exactly what we do. If you want to truly see what is happening with the GUID just look at c:\windows\smscfg.ini and see what happens when you clean it then restart the service. Daniel Ratliff From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] On Behalf Of Jimmy Martin Sent: Wednesday, July 02, 2014 8:47 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] RE: Resolving duplicate GUIDs I tried that commandline and it does work but I get no better end result… have you found THE successful formula? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Wednesday, July 02, 2014 7:43 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] RE: Resolving duplicate GUIDs Step#3, is that truly a replacement for ccmdelcert? If so, AWESOME. Daniel Ratliff From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Paul Winstanley Sent: Wednesday, July 02, 2014 8:29 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: Re: [mssms] RE: Resolving duplicate GUIDs 1. Stop the SMS Host Service – to do this run the command net stop ccmexec as an administrator 2. Delete the SMSCFG.ini file from the Windows folder – to do this run the command del %WINDIR%\smscfg.ini 3. Delete the SMS certificates – to do this run the following line in PowerShell – Remove-Item -Path HKLM:\Software\Microsoft\SystemCertificates\SMS\Certificates\* -Force or from DOS using powershell -command “Remove-Item -Path HKLM:\Software\Microsoft\SystemCertificates\SMS\Certificates\* -Force” 4. Restart the SMS Host service On Wed, Jul 2, 2014 at 1:23 PM, Jimmy Martin <jimmy.mar...@bmhcc.org<mailto:jimmy.mar...@bmhcc.org>> wrote: Anything on this question? I too have duplicate guids and doing the suggestions of smsdelcert…. Tranguid… just don’t seem to get it anymore… the GUID stays the same on these. Inmy case, they are thin clients running wes standard 2009… Jimmy Martin (901) 227-8209<tel:%28901%29%20227-8209> From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] On Behalf Of Corkill, Daniel Sent: Thursday, June 26, 2014 12:36 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] Resolving duplicate GUIDs I just wanted to know the process of resolving resources that have duplicate GUIDs. I’ve found a few articles for SMS 2003 and CM 2007 but can’t find a clear process for CM 2012. ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
