Transfer KMS Server (2012 R2 to 2012 R2) OS and Office 2013/2010 activation?

I am looking to migrate a KMS server from one 2012 R2 server to another.
Reason is we're getting rid of the server KMS is on now since we no longer need that server taking up so much space.
We'll be relying on the KSM for activatign Windows Server 2012 R2 and lower to Windows 7, as well as Office 2010 and 2013.

Am I correct in that the following plan is the right approach? If not, please advise any recommended corrections.

Steps on "old" KMS server that will be decommissioned:

1. Gather the partial product keys that are installed, and find complete keys online, note the full keys
2. Disable DNS publishing by running "slmgr /cdns"
3. Uninstall KMS keys by running "slmgr /upk"
4. Clear keys from registry by running "slmgr /cpky"
5. shutdown the VM of server and wait until approved for deleting

Steps on "new" KMS server":

1. Run "slmgr /upk"
2. Install KMS key for 2012 R2 Standard/Data edition (from the Volume licensing website for our organization) by running "slmgr /ipk <the kms key from volume licensing website>"
3. Activate with slmgr /ato
4. Disable DNS publishing
5. Update existing _VLMCS DNS record manually to point from old KMS server to the new KMS server hostname.
6. Restart Software Protection Service with command "net stop sppsvc && net start sppsvc"
7. Download and install both the Office 2010 and Office 2013 Volume License Packs and install and add their KMS keys from our Volume Licensing website (current deployments of Office are configured to activate over KMS. have 2010 and 2013 deployed)?
garryshapeAsked:
Who is Participating?
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.

DrDave242Commented:
I'm not sure what the first step means. If you're referring to the existing KMS clients, there's no need to mess with their keys at all; they won't change when they start activating with the new server.

Also, you don't have to remove the old server before installing the new one. You can have multiple KMS servers in an environment. In fact, you can use a single KMS host key on up to six servers. If both servers are registered in DNS and one is unresponsive (for example, if it's been taken offline), clients will simply connect to the other one.
0
garryshapeAuthor Commented:
The first step I mean is regarding the KMS host, I don't have any plans to do anything with workstations activating besides letting them do their own thing to activate against the new server next time they check in with DNS.

My understanding with step 1 is that the server in order to activate clients on the network will need a unique key installed on it that is from volume licensing website?
0
DrDave242Commented:
My understanding with step 1 is that the server in order to activate clients on the network will need a unique key installed on it that is from volume licensing website?
The new server will need a KMS host key, which is unique to your environment. You're right, you'll obtain this from the Volume Licensing Service Center site. (You should already have credentials for this site.)
0

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
RizzleCommented:
Hi Gary,

Sorry for being an old threat back to life, but we have a similar requirement but our clients are pointing to our current KMS using ospp.vbs /skms and I was wondering if moving the KMS host to a different server has any affect or does that work using the MLVCS record aswell?
0
garryshapeAuthor Commented:
When I decommissioned the old KMS server and setup a new one and I updated DNS (I'm not using Active Directory for activation since it's mostly Windows 7 and I want Windows + Office activation method to have conformity), I didn't run into any issues.

I think there were only a few boxes out of a few hundred that needed commands run in their command prompt to force point them to the new KMS activation server.
0
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
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.