Moving KMS to a New Server

-

In this guide, I'll take you through the process of uninstalling a Key Management Service (KMS) host key and then installing it on a new server, step-by-step.

Step 1: Uninstall the KMS Host Key

To remove the current KMS host key from the server, run the following command: cscript.exe C:\windows\system32\slmgr.vbs -upk

This command will uninstall the KMS host key.

Step 2: Install the Default KMS Key

Install the default KMS key by running the following command: cscript.exe C:\windows\system32\slmgr.vbs /ipk [KMS Client Setup Key] You can find the default KMS client setup keys here.

Step 3: Delete the Record from DNS

Open the DNS console and expand the _tcp node under the domain.com. You'll see a record called _VLMCS. Delete this record.

Now, the KMS server is uninstalled.

Step 4: Install KMS on a New Server

To install KMS on a new server, enter the following command: cscript.exe C:\windows\system32\slmgr.vbs /ipk

Step 5: Activate the KMS Host

Activate the KMS host by entering this command: cscript.exe C:\windows\system32\slmgr.vbs /ato

Step 6: Restart the Software Licensing Service

Restart the Software Licensing Service by running this command: Restart-Service LicenseManager (PowerShell) or net stop LicenseManager && net start LicenseManager (DOS)

By following these steps, you can successfully uninstall a KMS host key and install it on a new server. This can be useful when migrating to a new server or replacing an existing KMS host.

Comments

Post a Comment

Popular posts from this blog

Dell Latitude 5501 64GB of RAM? Yes!

-
Image
Imagine my surprise when my Dell Latitude 5501 was able to be upgraded to 64GB of RAM when the specifications state it has a maximum of 32GB. My guess is marketing. They want to sell you a more expensive model that officially supports more RAM. Here is a link to the RAM that worked for me. Anyway, if you are looking to upgrade your 5501, go ahead and move to 64GB.
Read more

ConfigMgr Task Sequence Fails Immediately with "The software could not be found on any servers at this time."

-
Image
Happy Monday, fellow ConfigMgr administrators! I ran across a pretty difficult Task Sequence last week that had me scratching my head. It involved a pretty complex Task Sequence that contained over 50 applications. The Task Sequence would fail within 5 seconds upon launch from the Software Center with an message of  “The software could not be found on any servers at this time.” No error code was given. I ended up removing all the apps from the TS and adding them back one at a time. Many of the applications had at least one supersedence, dependencies and dependency chaining. It turned out there was one particular superseded application that  was missing its content!! Yeah, that would do it. Unfortunately, ConfigMgr did not log what application or package ID had its content missing so it was a crap shoot trying to find it.  I really feel like there should have been a log somewhere that gave this information. This is the only log info...
Read more

Unable to open Start or Search after Window 7 to Windows 10 1809 Upgrade

-
Image
This one was a real head scratcher. After upgrading from Windows 7 to Windows 10 1809, you could not open the Start Menu. When you would click on it, nothing would happen. You could also not perform a search. I saw in the System event log: "The server Microsoft.Windows.ShellExperienceHost _10.0.17763.1_neutral_neutral_cw5n1h2txyewy! App did not register with DCOM within the required timeout." about every 30 seconds. I noticed the same thing with Cortana. and "The server Microsoft.Windows.Cortana _1.11.6.17763_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXfbn8w4s0jbk3tjevpcn9kaxerc6rby8k.mca did not register with DCOM within the required timeout." I captured a procmon trace and found: Both ShellExperienceHost.exe and SearchUI.exe exit with an error (-1073741790 which is Access Denied) as soon as they try to load sysfer.dll (part of Symantec Endpoint Protection). See https://support.symantec.com/us/en/article.TECH252314.html Evidently, sysf...
Read more