Switching Office from MAK to KMS

JaredBusch

Tonight, I setup a KMS server at a client to handle all of their Office activations.

I had no real trouble getting the KMS Host set up. Simply downloaded a couple executables from Microsoft and then followed the instructions. One for Office 2013 and one for Office 2010 as that is what the client has installed all over their facility.

The next thing I wanted to do was switch the clients from MAK to KMS and that is where I ran into a roadblock.

Google quickly led me to this post, but the process did not work. It gave me invalid key errors.

A little more searching showed me that the 2013 KMS client key in that example was for Office 2013 Pro Plus. My client only uses Office Standard as they have zero need for MS Access.

Well great, there is the 2013 keys, but now how about a 2010 list Microsoft? Yeah, nope, back to Google we go.

I finally found this list of KMS client keys and it includes Office 2010.

I connect to 5 machines and run the standard Office script to redo licensing. THe first 4 said there were not enough registrations on the server and then #5 activated.

#-- Office 2010 Standard KMS Client key
cscript ospp.vbs /inpkey:V7QKV-4XVVR-XYV4D-F7DFM-8R6BM
#-- change to your KMS server DNS name
cscript ospp.vbs /sethst:kms.ad.domain.com 
cscript ospp.vbs /act

Went back to the first 4 and ran the activation command again. All activated.

cscript ospp.vbs /act