Add your Office 2016 KMS Keys to your Volume Activation Server

It's that time again!  Time to add your Office 2016 KMS Keys to your Volume Activation Server!
Yes, I forgot how to do it too.. so here are my notes for doing it.

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.
If you want to call them, use this number: (866) 230-0560

Here is the format of my email to them:

Update: They now have a web form for you to fill out to request KMS keys:

------------  Start email Template  ------------
I need KMS keys generated for Office 2016 please.

Here is my Office 2016 with SA License agreement:
License ID: XXX
Parent Program: XXX

------------  End email Template  ------------

When you add your Office 2016 KMS keys it will cover everything office including Visio and Project.

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.
Look for "Office Professional Plus 2016 Key Management Service Host" in the Downloads and Keys section.
Your going to want the "Office Professional Plus/Standard 2016 32 Bit English KMS" ISO Download.
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.

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.

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.
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.

For this example I will place the extracted "Office Professional Plus 2016 Key Management Service Host" files on the KMS server here: 

1. Open an elevated Command Prompt window, verify that the current directory is C:\KMS2016 if that is where you put your files.
 CD C:\KMS2016

2. Run this command:
 cscript kms_host.vbs

3. 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.
 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.

4. Now restart the KMS server Service:
net stop sppsvc && net start sppsvc

5.  Now check your KMS status and dump it to a text file (mine didn't fit on the screen)
 Open up an Elevated Command Prompt window
 In the elevated Command Prompt window, verify that the current directory is C:\Windows\System32.
 CD \Windows\System32
 cscript slmgr.vbs /dlv all > c:\KMS2016\license-kms.txt

When your done you should see something like this inside c:\KMS2016\license-kms.txt:

Name: Office 16, Office16KMSHostVL_KMS_Host edition
Description: Office 16, VOLUME_KMS channelActivation ID: xxx
Application ID: xx
Extended PID: xxx
Product Key Channel: Volume:CSVLK
Installation ID: xxx
Use License URL:
Validation URL:
Partial Product Key: XXXX
License Status: Licensed
Remaining App rearm count: -1
Remaining SKU rearm count: -1
Trusted time: 10/1/2015 1:53:31 PM

Key Management Service is enabled on this machine
    Current count: 10
    Listening on Port: 1688
    DNS publishing enabled
    KMS priority: Normal

Key Management Service cumulative requests received from clients
    Total requests received: 7245
    Failed requests received: 3
    Requests with License Status Unlicensed: 0
    Requests with License Status Licensed: 7060
    Requests with License Status Initial grace period: 51
    Requests with License Status License expired or Hardware out of tolerance: 28
    Requests with License Status Non-genuine grace period: 0
    Requests with License Status Notification: 103

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
cscript ospp.vbs /act

If this fails on the client, then rearm the activation first. (I see this sometime when cloning a PC)ospprearm.exe

If you think your DNS is missing the KMS information, use this to turn on the KMS DNS settings:slmgr.vbs /sdns


PetriAsikainen said…

I'm struggling with kms and office 2016. After installing kms and activating
our licence office 2016 licence information shows up like:

Name: Office 16, Office16KMSHostVL_KMS_Host edition, KMSHostVL edition
Description: Office 16, VOLUME_KMS channel, VOLUME_KMS channel
Activation ID: xxxxxxxxxxxxxxxxx-xxxxxxxxxxxxxxxxx-xxxx
Application ID: 0ff1ce15-xxxx-xxxxxx-xxxxxxxxxx-xxxxxxxx

Could you confirm that your application id also starting as 0ff1ce15 like us
(and not like 0ff1ce16 as I assume it should)?

On KMS host Windows 2008 R2 i have this situation

Name: Office 16, Office16KMSHostVL_KMS_Host edition, KMSHostVL edition
Description: Office 16, VOLUME_KMS channel, VOLUME_KMS channel
Activation ID:
Application ID:
Extended PID:
Installation ID:
Processor Certificate URL:
Machine Certificate URL:
Use License URL:
Product Key Certificate URL:
Partial Product Key: blablabla
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 06/10/2015 10:34:24

Key Management Service is enabled on this machine
Current count: 10
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal

but when i launch cscript "C:\Program Files (x86)\Microsoft Office\Office16\ospp.vbs" /act i receive:

Installed product key detected - attempting to activate the following product:
LICENSE NAME: Office 16, Office16ProPlusVL_KMS_Client edition
Last 5 characters of installed product key:
ERROR CODE: 0xC004F074
ERROR DESCRIPTION: The Software Licensing Service reported that the product could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.
To view the activation event history run: cscript ospp.vbs /dhistorykms
NOTICE: A KB article has been detected for activation failure: 0xC004F074

some bugs on 2008 r2 kms host?

Petri i confirm i have

Application ID: 0ff1ce15-a989-xxxxxxxxxxxxxxxxxxxxx
bunny214 said…
Hi Ed,
I run into the same issue that Michele describes above. Do you have any info on if MS Office 2016 can be activated using Server 2008R2 KMS host?
Aloysius said…
Same problem here too. Windows server 2008 r2 kms and office 2016 pro plus. KMS was already patched for windows 10 activation. Has anyone found the solution ?
Ed Hammond said…
Yes, I too noticed the Application ID: 0ff1ce15-xxxx
You would think they would have caught that.

They now have a site for Downloading the "Microsoft Office 2016 Volume License Pack"

Here is the text from that page:

Supported Operating System
Windows 10 , Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

KMS Host: Windows Server 2008 R2, Windows 7 (volume editions), Windows Server 2012, or Windows 8.

Active Directory-Based Activation
Set-up and Configuration: Windows Server 2012, Windows 8 or newer.

Domain controller: Active Directory Domain Services with the Windows Server 2012 schema installed.
Tried the "Microsoft Office 2016 Volume License Pack" way...same issue
Looks like a very large problem with 2008 R2

i have opened a ticket with MS, will keep you informed
Just received an update from MS support:

ERROR CODE: 0xC004F074 if Office 2016 KMS Host is Win 2008 R2
· Issue was already reported to PG and they have been able to repro the issue.
· Until issue will be fixed, you can inform affected customers that Office clients are running within the 30-day grace period and can be rearmed if needed beyond the initial 30 days.
PetriAsikainen said…
KMS was running on 2008 R2 server and we got that 0xC004F074 error with office 2016 activation.

After we moved KMS service to Windows 2012 R2 , Office 2016 is now activatig just fine.
Moved to Win 2012 R2 KMS host.
Works like a charm now
Simoncu said…
I just tried to install the kms on W2008R2, and run into the problem. Unfortunately I cannot upgrade to 2012, so if MS has come up with a solution, I'm in for it !!!!!
Franck V. said…
Hi guys, worked out for me on a 2008r2 KMS, follow up the KB:
Ed Hammond said…
I deleted this post by mistake..

Simoncu has left a new comment on your post "Add your Office 2016 KMS Keys to your Volume Activ...":

@Frank V. : Your article is about Windows 10 not office 2016.... I did that already for W10 and it's working good, but that doesn't answer the question about office 2016 ....
Ed Hammond said…
Would the spammers please stop trying to post links back to License key hacking sites.
I'm getting tired of marking them as spam every day.
The comments on my blog are moderated.
Simoncu said…
No news yet from MS about it ?
Unknown said…
Any updates to this? I'm having this issue, and this thread is 3 months old...
Unknown said…
So glad I found this thread - have been trying so long without success to license 2016 on a Windows 2008R2 KMS host! Re-visiting it now as we're thinking about doing a site-wide migration to 2016 in the coming months.

Issue still exists I see?
VK said…
I have a KMS running in our environment which is used for activating the Windows 7 and Office. Windows 7 activation does happen successfully. But for Office, when i try to activate, it gives the following
SKU ID: 83e04ee1-xxxx-xxxx-xxxxxxxxx7
license name: Office 16, Office16SkypeforBusinessVL_KMS_Client edition
REMAINING GRACE: 177 days (256285 minute(s) before expiring)
Last 5 chanracters of installed product key: XXXXX
KMS machine from DNS:
Activation Interval :120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled

Not sure why i get the Beta expiration date and the the remaining grace even though it is licensed.
Jiro Ueda said…
would this office KMS be able to run along side with VOLUME_KMS_2012-R2_WIN10 channel?
Ed Hammond said…
The KMS for office is separate from the one for Windows, so it will not be a problem.
You, Sir, have made my day! After having struggled a lot with this issue your solution worked like a dream. Thank you very much!


Popular Posts