How to migrate KMS server from one computer to another?

One of our Windows 2008 R2 domain controllers (DC) needs to be removed from the Active Directory (AD) domain. However, before I’m going to do that, Key Management Service (currently installed and activated with the Windows 8, 2012, Office 2013 licences) needs to be moved (migrated) onto the new Windows 2012 R2 server. After successful KMS migration from one server to another I also need to activate Windows 10 KMS licences.

From what I have understood by googling “here and there”, you need to deactivate KMS from one server and activate it on another one. But, you have to do it right way otherwise you could “lock” you activation licences keys and you will ended up calling Microsoft for help. I need that “right way". Something like: “Step 1 – run this command …, etc.”
Thanks in advance
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

What you have to do depends a bit on the history of how KMS keys were used at your site. When first setting things up, before KMS reached its threshhold, you may have activated as many as 5 (or is it 6?) servers with the KMS key.

To make things clean, you would want to find all of those other potential KMS servers and use the slmgr tool to replace their keys with the appropriate published client key, including the one you want to decommission. Reboot or restart the Software Licensing Service. Delete any DNS SRV entries  _VLMCS  that point to unwanted servers. These DNS entries are how you would likely discover that other hosts could potentially be acting as KMS servers.

You can then use the slmgr tool to activate your KMS keys on the server you want to act as your new KMS server. This is the place where you could get locked up if there are already 5 (or is it 6?) activations already in place.

There will be a period while clients figure out who is the new KMS server and they may get warnings about being unable to activate. This should all sort itself out automatically, but you may be able to speed things up with a reboot of the new KMS server and checking to see that it has the _VLMCS entry in DNS SRV pointing to it. Until the new KMS server has been contacted by 5 clients, it's going to reject activations, but there's a grace period that should be sufficient to let you ignore the warnings.

I should add that the old KMS server doesn't contain anything that would need to be "migrated". The old KMS server could have been vaporized and all you'd have to do to recover is activate a new KMS server.

Perhaps one of the "here and there" places you saw was this article from Yuri's blog: Moving your Key Management Server (KMS) to another server or host []

He has the step-by-step set of slmgr commands he used, but to my mind he was trying to force things so not all of the steps are actually required.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
OlevoAuthor Commented:
Thanks jmcg for your help.
To make things clean, you would want to find all of those other potential KMS servers
There are only one KMS server on our AD domain. I can check DNS and see what servers are listed as KMS Servers based on the service records.
nslookup -type=srv _vlmcs._tcp

Before I am going to setup and activate licence keys on new KMS server do I need to deactivate/remove licence keys from the old KMS server?
I suppose it could be done in either order, before or after you set up the new KMS server by activating it with a KMS key. Since you're pretty sure you only have one server with the KMS key, that's the level of assurance that you have that you won't have reached the activations limit.

Deactivating the old server (by instaling the KMS client key) and stopping it from advertising to DNS that it's a KMS server should be sufficient. You'll want to do that before you demote it from being a domain controller and having it exit AD.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.