No Key Management Service (KMS) could be contacted.
Last 5 characters of installed product key:ĮRROR DESCRIPTION: The Software Licensing Service reported that the product could not be activated. LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channel LICENSE NAME: Office 16, Office16ProPlusVL_KMS_Client edition Installed product key detected - attempting to activate the following product: Name: Office 16, Office16KMSHostVL_KMS_Host edition, KMSHostVL editionĭescription: Office 16, VOLUME_KMS channel, VOLUME_KMS channelīut when i launch cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /act i receive: On KMS host Windows 2008 R2 i have this situation If you think your DNS is missing the KMS information, use this to turn on the KMS DNS settings: slmgr.vbs /sdns (I see this sometime when cloning a PC) ospprearm.exe If this fails on the client, then rearm the activation first. If your Office 2016 has still not activated on the client, you can force it with this: cd C:\Program Files (x86)\Microsoft Office\Office16 Requests with License Status Notification: 103 Requests with License Status Non-genuine grace period: 0 Requests with License Status License expired or Hardware out of tolerance: 28 Requests with License Status Initial grace period: 51 Requests with License Status Licensed: 7060 Requests with License Status Unlicensed: 0 Key Management Service cumulative requests received from clients Key Management Service is enabled on this machine Name: Office 16, Office16KMSHostVL_KMS_Host editionĭescription: Office 16, VOLUME_KMS channelActivation ID: xxx When your done you should see something like this inside c:\KMS2016\license-kms.txt: In the elevated Command Prompt window, verify that the current directory is C:\Windows\System32.ĬD \Windows\System32 cscript slmgr.vbs /dlv all > c:\KMS2016\license-kms.txt Open up an Elevated Command Prompt window Now check your KMS status and dump it to a text file (mine didn't fit on the screen)
It will not screw up your Windows 10 or Server 2012 R2 KMS Keys, and even leaves your Office 2013 keys in place if you have them.ĥ. My KMS is on my Server 2012 R2 domain controller and has the latest KMS for Windows 10, so this is all based on that.įor this example I will place the extracted "Office Professional Plus 2016 Key Management Service Host" files on the KMS server here:ġ. Open an elevated Command Prompt window, verify that the current directory is C:\KMS2016 if that is where you put your files.ģ. After the updates are installed the Volume activation tools will open and you will need to enter your Office 2016 KMS key and activate it using this tool. You know you have the right ISO if it's only about 1mb in size and has kms_host.vbs in the root of the mounted ISO. Now that you have mounted the SW_DVD5_Office_Professional_Plus_2016_W32_English_KMS_MLF_X20-42865.ISO that you just downloaded, you can extract the files and place them on your KMS server. I didn't download the rest because I didn't need the Multilanguage version, I went and got the standard Office Professional Plus 2016 instead.
Your going to want the "Office Professional Plus/Standard 2016 32 Bit English KMS" ISO Download. Look for "Office Professional Plus 2016 Key Management Service Host" in the Downloads and Keys section.
When you get your KMS keys, then you are ready to download the update from the Microsoft Volume Licensing Service Center (VLSC) that will allow you to activate the KMS on your Server. When you add your Office 2016 KMS keys it will cover everything office including Visio and Project. Here is my Office 2016 with SA License agreement: I need KMS keys generated for Office 2016 please. Update: They now have a web form for you to fill out to request KMS keys: If you want to call them, use this number: (866) 230-0560 If you are missing the KMS keys from the MVLSC for office 2016 then you need to contact Microsoft at to get your MAK key converted to KMS. It's that time again! Time to add your Office 2016 KMS Keys to your Volume Activation Server!