Solved

slmgr.vbs /rearm does not reset the guid

Posted on 2012-03-21
5
3,528 Views
Last Modified: 2012-03-27
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
Comment
Question by:hartwellcorp
  • 3
  • 2
5 Comments
 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
Comment Utility
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
 

Author Comment

by:hartwellcorp
Comment Utility
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
 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
Comment Utility
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
 

Accepted Solution

by:
hartwellcorp earned 0 total points
Comment Utility
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
 

Author Closing Comment

by:hartwellcorp
Comment Utility
I called MS and got the answer.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

In a hurry?.. scroll down to "HERE's HOW TO DO IT" Section. Greetings All, I was going to post this as question/solution, but its seems more appropriate as an article considering its length.  I felt it important to illucidate all the details c…
Citrix XenApp, Internet Explorer 11 set to Enterprise Mode and using central hosted sites.xml file.
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now