Migrating KMS Services from Server 2003 Servers to Server 2012 R2

Question

We have two Windows Server 2003 boxes that a previous administrator had setup as our KMS Servers. 
These servers appear to be activating Office 2010, Windows 7, and Windows Server 2008R2 and 2003
I can see these activations taking place in the KMS logs on each server.
The question is what are the steps that we need to take to get the KMS Services migrated to Server 2012 without causing any activation issues in the current environment?  I've be unable to come up with the proper order of operations from researching
blogs and I'm just not sure how to get where I need to go, what keys to use etc.
Since this was setup by a previous administrator, there is no documentation on what was done, what keys were used etc.
KMS Server 1:
slmgr /dlv   
Name:  Office(TM) 14, ProPlusKMSHost edition   (Partial Product Key C6PWX)
Description:  Office(TM) 14 KMS, VOLUME_KMS channel
Name:   Windows(TM) Server 2003 KMS, W7R2-Kms3 edition
Description:   Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_B channel (Partial Product Key VX348)
KMS Server 2:
slmgr /dlv   
Name:  Office(TM) 14, ProPlusKMSHost edition   (Partial Product Key 3T9QW)
Description:  Office(TM) 14 KMS, VOLUME_KMS channel
Name:   Windows(TM) Server 2003 KMS, W7R2-Kms3 edition
Description:   Windows(TM) Server 2003 KMS, VOLUME_KMS_R2_B channel (Partial Product Key TT78P)
Of Note, we are a Microsoft Software Assurance customer and have Volume Licensing
In Summary, I would like to understand how to move my KMS Services to a new 2012 Server(s) and decommission the old 2003 boxes running KMS without disruption.  As a final step I'd also like to be able to activate Windows 8, Server 2012, and Office 2013.

Answer 1

Hi,
If you wanted to slowly transition and verify... you could stand up new KMS host and make the priority of the SRV record lower so that clients will always connect to new server first and fall back to original box second.
Steps to migrating the KMS:
1. Uninstall the KMS host key first by running the following command:
slmgr -upk
2. Then, install the default kms key by running the following command:
slmgr /ipk [KMS Client Setup Key]
The default KMS client setup keys can be found here:
http://technet.microsoft.com/en-us/library/cc303280.aspx
3. Delete the record from the DNS:
Open DNS console:
Expand _tcp node under the domain.com. There will be a record _VLMCS. Delete this record.
4. The KMS server is uninstalled.
5. To install KMS on a new server, enter:
cscript C:\windows\system32\slmgr.vbs /ipk <KmsKey>
then to activate the KMS host, enter:
cscript C:\windows\system32\slmgr.vbs /ato
6. After activation is complete, restart the Software Licensing Service.
7. Verify that the record is created for the new server in the DNS.
To verify that the KMS host is configured correctly, you can check the KMS count to see if it is increasing. Run slmgr.vbs /dli on the KMS host to obtain the current KMS count. You can also check the Key Management Service log in the Applications and Services
Logs folder for 12290 events, which records activation requests from KMS clients. Each event displays the name of the computer and the time-stamp of an individual activation request.
https://social.technet.microsoft.com/Forums/windows/en-US/cd4177bd-8df5-4a66-afdc-c760398b7e7f/migrating-kms-server-from-one-computer-to-another
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]