Inplace uprade from 08' to 12' R2. KMS server keys no longer working. Please help!

No backing up to a snapshot etc. An in-place KMS server upgrade was performed and almost all keys are working except of course the BIGGEST one for 2012R2/Windows 10. Grabbed the key from MS Volume licensing and tried to add to the Microsoft Volume licensing activation tool (10.0.10240) and cannot for the life of me even after updates get the key to work. Key getting "invalid or a VAMT mismatch error". Not sure how this worked in 2008 and not now?
Have you guys ran into this/found a solution?
admitechAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
LesterClaytonConnect With a Mentor Commented:
When you install the new key, you do slmgr.vbs /ipk product-key-here

after that, you do slmgr.vbs /ato

Can you confirm the OS of the KMS server?
0
 
LesterClaytonCommented:
In order to make the Windows 2012 R2 with Windows 10 key to work, you have to install KB3058168

This will add the necessary product ID's into the KMS Database.  Once this is done, you can restart the Volume Activation Services, and then install the product key you want.  Remember to activate it afterwards.

The product key is named "Windows Srv 2012R2 DataCtr/Std KMS for Windows 10" and you will find it in VLSC, under "Licenses -> Relationship summary -> License ID -> Product Keys"

TheKeyYouWant
0
 
admitechAuthor Commented:
Thanks Lester! Unfortunately that KBB (both downloads) says "not applicable". We do seem to have the right key added to volume activation tool....
What do you mean by:  "Remember to activate it afterwards."
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
admitechAuthor Commented:
I was successful installing slmgr.vbs /ipk {Windows 2012 R2 KMS for Windows 10} after a fresh Server 2012 install. KB3058168 was installed and the server is completely up to date on Windows Updates. However all clients when running a "slmgr.vbs /ato" return either an unable to contact KMS or "the count reported by your Key Management Service (KMS) is insufficient..."
Port 1688 is wide open and I can getting hits to the server I can see with "slmgr /dlv". However nothing is activating for Windows 10. Office 2010, 2013 and Office 2016 are working fine.
0
 
LesterClaytonConnect With a Mentor Commented:
OK this is a good situation :)  What you need now is at least 10 Windows 10 machines to attempt activation, and then activations will start working.  KMS will only activate once a certain threshold of machines have requested activations.
1
 
admitechConnect With a Mentor Author Commented:
Close Lester! :) 25 for Win 10 Clients and 5 for Office 2013/16. All is well now! Feel like I could teach this now thanks to your help and my research!! Good deal!
0
All Courses

From novice to tech pro — start learning today.