Change KMS Hosts to KMS Clients
I have two Windows 2008 Servers that were activated using a corporate KMS key incorrectly. The problem is that these both are acting as KMS hosts. Corporate IT now has a KMS server for use to activate with. How would I convert the 2008 KMS host machines to become KMS clients to the new KMS server? Is there a way to blow out the original activation? I guess I would need to delete the srv records also.
Any help would be appreciated.
Thank you,
Steve
Any help would be appreciated.
Thank you,
Steve
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for the feedback but I do not have the "/skms" option for slmgr.vbs. I think it is because it is already a KMS host.
Capture.JPG
Capture.JPG
oh... sorry, it looks like you need to clear the KMS host first...
-ckms
Clear name of KMS computer used (sets the port to the default)
cscript slmgr.vbs -ckms
-ckms
Clear name of KMS computer used (sets the port to the default)
cscript slmgr.vbs -ckms
ASKER
The It department for our parent company told me to do a repair install. I guess I have no choice.
Thank you for your responses.
Also, I did not have the ability to use -ckms either.
Steve
Thank you for your responses.
Also, I did not have the ability to use -ckms either.
Steve
oh... wiat... I ran into something similar before...
I was also missing the CKMS switch... and the SKMS option...
I then found out that this particular machine was using a KMS key that was not correct. (To me, it looked as if it was a KMS Host... but it really wasn't....it just had a KMS key (client) installed that was not compatible with our organization.
To solve the problem, I looked at the product key... you can see the commands to run so, that you can see a partial Product key of the Windows 2008 OS.
I learned that this was the wrong key... so, there are commands to change the key without reloading the OS. (Screen shot shows these commands...)
After I did this, I was able to activate the OS using a remote KMS host.
1-14-2010-8-22-04-AM.png
I then found out that this particular machine was using a KMS key that was not correct. (To me, it looked as if it was a KMS Host... but it really wasn't....it just had a KMS key (client) installed that was not compatible with our organization.
To solve the problem, I looked at the product key... you can see the commands to run so, that you can see a partial Product key of the Windows 2008 OS.
I learned that this was the wrong key... so, there are commands to change the key without reloading the OS. (Screen shot shows these commands...)
After I did this, I was able to activate the OS using a remote KMS host.
1-14-2010-8-22-04-AM.png
So, I would assume that the new KMS host servers are populated in DNS and are healthy and activating clients today? If this is true, I would simiply uninstall the KMS service (or shut down the service) on the old machines.