Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4259
  • Last Modified:

slmgr.vbs /rearm does not reset the guid

Many of my client PCs are getting 'activation failed' after months of being installed and working fine. I checked my KMS server and its only reporting a count of 16, well under the minimum of 25. So my next step was to find out why it only counts 16 when i have over 40 Win7 clients, and of course it is because many of our computers have duplicate GUID numbers, I verified this from the KMS event log. Apparently, when these computers were imaged they were not sysprepped at all. So now my task is to reset the GUID numbers on all the computers using slmgr.vbs /rearm and this is where my problem is. When I run the command, nothing happens, the GUID stays the same and I cannot figure out why.

I find many articles explaining the relationship between slmgr.vbs /rearm and the skiprearm key in the registry. The key did not exist at all, probably because sysprep was never run. I tried running rearm without the registry key and I also tried creating the registry key and running rearm again. No luck, when I check the KMS event log this computer is still using the same GUID.

I am aware that Microsoft does not support the rearm command being used in this scenario, they will ask me to sysprep the image properly and then reimage all of the computers. That's great, I want to do that, but reimaging 30 or more computers is simply not feasible, we're talking many days of work and delays to our workers.

Does anyone know how to get the GUID changed on these computers?
0
hartwellcorp
Asked:
hartwellcorp
  • 3
  • 2
1 Solution
 
David Johnson, CD, MVPOwnerCommented:
on each pc just run sysprep and then restart the pc and rejoin the pc to the domain.

slmgr /rearm has nothing at all to do with the guid
0
 
hartwellcorpAuthor Commented:
Sorry i meant the CMID.

slmgr.vbs /rearm resets the CMID according to Microsoft.
http://blogs.technet.com/b/askcore/archive/2009/10/16/kms-host-client-count-not-increasing-due-to-duplicate-cmid-s.aspx

My questions is why this is not working in my situation, what am i missing?
0
 
David Johnson, CD, MVPOwnerCommented:
While it is possible to run slmgr.vbs /rearm to reset the machines CMID that does not leave the machine in a supported state. Images deployed without using Sysprep to prepare the image are not supported by Microsoft. Sysprep executes ~30 sysprep providers. These providers are written to correct issues with various components when you duplicate the installation. By not running sysprep it is unknown what types of issues you could encounter and many components will be in a broken state. The supported solution is to rebuild the image using the Sysprep /generalize switch and redeploy the systems.

again I reiterate run sysprep on each machine and then restart that machine and rejoin it to the to the domain
0
 
hartwellcorpAuthor Commented:
Okay, I just got off the phone with Microsoft. I was not running the command promt 'as administrator'. After we did that, the CMID was changed and we are now activating fine. That's what I missed, you must right-click the command prompt and choose 'run as administrator'. you must also reboot the client twice. the event log on the client can be used to verify the CMID being used (event 12288). Thanks Anyway!
0
 
hartwellcorpAuthor Commented:
I called MS and got the answer.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now