none
Adding Office 2016 KMS key to WS2012R2 KMS host

    Question

  • Hi, 

    could someone describe the procedure of adding Office 2016 KMS key to WS2012R2 KMS host. There is no "MS Office 2016 Volume License Pack" or "Office Professional Plus 2013 Key Management Service Host" available as far as I know.

    Thank you in advance.



    Friday, September 25, 2015 7:08 AM

Answers

  • Download SW_DVD5_Office_Professional_Plus_2016_W32_English_KMS_MLF_X20-42865.iso from VLSC

    mount the image on your kms host server and in an elevated command window run cscript kms_host.vbs

    When the Volume Activation Tools launch, enter and install your KMS key, Follow the prompts and you should be all licensed at the end!

    Cheers.

    Cory


    • Proposed as answer by Cory Teale Thursday, October 01, 2015 7:24 PM
    • Edited by Cory Teale Thursday, October 01, 2015 7:25 PM
    • Marked as answer by bplancic Friday, October 02, 2015 12:37 PM
    Thursday, October 01, 2015 7:15 PM
  • I am guessing we might see the KMS Host License Pack for 2016 on Oct. 1, when the VL versions are released to the portal.
    • Proposed as answer by SergSV Thursday, October 01, 2015 7:14 AM
    • Marked as answer by bplancic Friday, October 02, 2015 12:37 PM
    Monday, September 28, 2015 1:58 PM

All replies

  • I would also like to know how to do this.

    I recently set up a Windows Server 2012 R2 KMS activated with Windows Srv 2012R2 DataCtr/Std KMS for Windows 10.  I also installed the Microsoft Office 2013 Volume License Pack and activated Office 2013 Suites and Apps KMS.

    However when I enter the Office 2016 Suites and Apps KMS key I get the message "Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid".


    Monday, September 28, 2015 4:21 AM
  • Hi all,

    we've exact the same issue, I download the office 2016 pro plus from MSDN and now we are tried the activate via our KMS but it will not accecpt the KMS Key. I hobe this will be fixed if the download is in the Volumen Acitivation Center.

    Monday, September 28, 2015 5:36 AM
  • There is no official documents about this, at least I can't find any.

    You will need to have volume license pack and possibly asking VLSC will help:

    https://www.microsoft.com/Licensing/servicecenter/default.aspx

    -Jeff

    Monday, September 28, 2015 5:52 AM
  • I am guessing we might see the KMS Host License Pack for 2016 on Oct. 1, when the VL versions are released to the portal.
    • Proposed as answer by SergSV Thursday, October 01, 2015 7:14 AM
    • Marked as answer by bplancic Friday, October 02, 2015 12:37 PM
    Monday, September 28, 2015 1:58 PM
  • I don't see Office or KMS Host as of yet today. :(

    There's no place like 127.0.0.1

    Thursday, October 01, 2015 4:09 PM
  • it's there...

    SW_DVD5_Office_Professional_Plus_2016_W32_English_KMS_MLF_X20-42865.iso

    the question is:  how to use it?  didn't come with any instructions...

    Thursday, October 01, 2015 6:51 PM
  • Download SW_DVD5_Office_Professional_Plus_2016_W32_English_KMS_MLF_X20-42865.iso from VLSC

    mount the image on your kms host server and in an elevated command window run cscript kms_host.vbs

    When the Volume Activation Tools launch, enter and install your KMS key, Follow the prompts and you should be all licensed at the end!

    Cheers.

    Cory


    • Proposed as answer by Cory Teale Thursday, October 01, 2015 7:24 PM
    • Edited by Cory Teale Thursday, October 01, 2015 7:25 PM
    • Marked as answer by bplancic Friday, October 02, 2015 12:37 PM
    Thursday, October 01, 2015 7:15 PM
  • did that....even had the script modify the DNS settings (it modified it incorrectly, I had to manually correct that)

    I even restarted "sppsvc" service.

    I did "ipconfig/release" and "ipconfig/renew" my computer...

    STILL, it says my Office 2016 is not licensed...

    sigh...

    Thursday, October 01, 2015 7:35 PM
  • Hey The guy down the hall,

    Your slmgr /dlv all output should have something like this if you did things correctly:

    Name: Office 16, Office16KMSHostVL_KMS_Host edition

    Description: Office 16, VOLUME_KMS channel

    Partial Product Key: YHQC8

    License Status: Licensed

    Did your Volume Activation Tools pop up when you ran the vbs script?

    Also, don't forget that your trigger count has to be high enough for the KMS server to start authorizing clients.

    Cory


    • Edited by Cory Teale Thursday, October 01, 2015 7:46 PM
    Thursday, October 01, 2015 7:44 PM
  • mount the image on your kms host server and in an elevated command window run cscript kms_host.vbs

    When the Volume Activation Tools launch, enter and install your KMS key, Follow the prompts and you should be all licensed at the end!

    Cheers.

    Works! :D

    There's no place like 127.0.0.1

    Thursday, October 01, 2015 7:50 PM
  • Hi,

    With regard to activating Office 2016 Pro Plus/Standard KMS host, you can try doing the following

    1. Download Microsoft Office 2016 Volume License Pack by going to this website www.microsoft.com/en-us/download/details.aspx?id=49164

    2. After installing it, it will prompt you to input the product key and set up the Volume Activation Tool

    3. Set it up by adding a KMS License key and activate it.

    • Proposed as answer by Wenggay1985 Thursday, October 01, 2015 10:05 PM
    Thursday, October 01, 2015 10:05 PM
  • This fixed my problem!! Thank you!!
    Thursday, October 01, 2015 10:08 PM
  • Hey The guy down the hall,

    Your slmgr /dlv all output should have something like this if you did things correctly:

    Name: Office 16, Office16KMSHostVL_KMS_Host edition

    Description: Office 16, VOLUME_KMS channel

    Partial Product Key: YHQC8

    License Status: Licensed

    Did your Volume Activation Tools pop up when you ran the vbs script?

    Also, don't forget that your trigger count has to be high enough for the KMS server to start authorizing clients.

    Cory


    Hi,

    What is the activation ID to check this? 

    slmgr.vbs /dlv only show the windows infomation.

    Friday, October 02, 2015 2:46 AM
  • Hey The guy down the hall,

    Your slmgr /dlv all output should have something like this if you did things correctly:

    Name: Office 16, Office16KMSHostVL_KMS_Host edition

    Description: Office 16, VOLUME_KMS channel

    Partial Product Key: YHQC8

    License Status: Licensed

    Did your Volume Activation Tools pop up when you ran the vbs script?

    Also, don't forget that your trigger count has to be high enough for the KMS server to start authorizing clients.

    Cory


    Hi,

    What is the activation ID to check this? 

    slmgr.vbs /dlv only show the windows infomation.

    Hi.

    I think you missed something. You have to type SLMGR /DLV ALL. That should give you all the information you need.

    Inge

    Friday, October 02, 2015 7:45 AM
  • Works, TY
    Friday, October 02, 2015 12:38 PM
  • Hey The guy down the hall,


    Also, don't forget that your trigger count has to be high enough for the KMS server to start authorizing clients.

    Cory


    Office 2016 status is "Licensed" on my server (Windows server 2008 R2), but i can't activate office 2016 on my clients.

    Can you tell me the minimum value of the trigger count ? (Win 10 KMS needs 25 computers)

    Friday, October 02, 2015 2:05 PM
  • Hi Cbartsys

    For Office 2016 KMS, there should be at least 5 KMS clients notifying the KMS host for activation. It is better to manage these activation using Volume Activation Management Tool 3.0. You can download that from herehttp://go.microsoft.com/fwlink/p/?LinkId=526740 . For more information on how to use it, you can go to this websitehttps://technet.microsoft.com/en-us/library/hh825164.aspx


    You can also run "slmgr /dlv all" in an elevated command prompt to check the count for "notification", that way it is easier for you to check if you have enough number of computers requesting for activation.
    • Proposed as answer by Wenggay1985 Friday, October 02, 2015 3:32 PM
    • Edited by Wenggay1985 Friday, October 02, 2015 3:42 PM
    Friday, October 02, 2015 3:30 PM
  • Is it safe/ok to add offfice 2016 keys to a kms server activating office 2013 and windows 8?
    Friday, October 02, 2015 5:18 PM
  • Hi BeefMcNugget,

    Office 2016 kms host key will only work with Office 2016. if you wanted to activate Office 2013 kms host and windows 8.1 , you need to use the corresponding keys for Office 2013 and windows 8.1 which you can get from the VLSC site https://www.microsoft.com/Licensing/servicecenter/default.aspx

    Friday, October 02, 2015 5:50 PM
  • yeah I understand, my server is already activating office 2013 and windows 2012/8 

    I need to know if its safe to add 2016 keys to that same kms server.

    Friday, October 02, 2015 6:17 PM
  • Hi BeefMcNugget,

    Oh sorry for the misunderstanding. Yes it is safe to add Office 2016 on the KMS server. Just use VAMT to manage the client machines for activation.

    Friday, October 02, 2015 7:35 PM
  • Hi.

    Mine says a little bit different (inserting screenshot)

    I smeared some lines, in case I am giving away my license key...

    By the way, on a side note, may I say "SLMGR /DLV ALL" may perhaps the worst command line coming out from Redmond?  My output was about 10 screen long, when I "move" the windows, it doesn't "stick" to the windows position...that's why I had to capture the output with my phone camera.

    Cory, where do I find "trigger count"?  This is the first workstation that has Office 2016 installed.

    Friday, October 02, 2015 8:24 PM
  • Hi The guy down the hall

    can you try running this instead in the elevated command prompt? "cscript slmgr.vbs /dlv <activation id of office 2016>"... the activation id of office 2016 is the same as the one on the screenshot you have provided <d450596fXXXXXXXX>. that should show the current count for Office 2016 kms.

    Friday, October 02, 2015 8:59 PM
  • wenggay1985, are you not able to see the screenshot that I attached above?

    Anyway, I ran as you suggested and the output is below.

    The thing is my product key is no where correct from what's shown in the output:

    Name: Office 16, Office16ProPlusVL_KMS_Client edition
    Description: Office 16, VOLUME_KMSCLIENT channel
    Activation ID: d450596f-894d-49e0-XXXXXXXXXXXXXX64
    Application ID: 0ff1ce15-a989-XXXXXXXXXXXXXXXX70663
    Extended PID: 03612-03391-000-000000-03-1033-10240.0000-2742015
    Product Key Channel: Volume:GXXK
    Installation ID: 0576915660833146940464779670887XXXXXXXXXXXXXXXXXXXXXXX4832403
    Partial Product Key: WXXX9
    License Status: Initial grace period
    Time remaining: 40329 minute(s) (29 day(s))
    Remaining App rearm count: 3
    Remaining SKU rearm count: 3
    Trusted time: 10/3/2015 10:55:12 AM

    Saturday, October 03, 2015 6:02 PM
  • Hi The guy down the hall... it seems like you ran the cscript on the client machine itself since it is showing KMS CLIENT... run the "cscript slmgr.vbs /dlv all" on the kms host server itself to get the status of the office 2016 kms host
    Sunday, October 04, 2015 3:47 AM
  • Thank you for the answer but I still have a problem:

    On the server host:

    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Software licensing service version: 6.1.7601.23159

    Name: Office 16, Office16KMSHostVL_KMS_Host edition, KMSHostVL edition
    Description: Office 16, VOLUME_KMS channel, VOLUME_KMS channel
    Activation ID: 98ebfeXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Application ID: 0ff1ce15-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Extended PID: 55041XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Installation ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
    Partial Product Key: 8BR3G
    License Status: Licensed
    Remaining Windows rearm count: 0
    Trusted time: 05/10/2015 16:21:00

    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: 44875
        Failed requests received: 321
        Requests with License Status Unlicensed: 0
        Requests with License Status Licensed: 41524
        Requests with License Status Initial grace period: 2241
        Requests with License Status License expired or Hardware out of tolerance: 23
        Requests with License Status Non-genuine grace period: 0
        Requests with License Status Notification: 766

    I have 5 KMS client on which Office 2016 is installed but not activated.

    I tried with the command line:

    c:\Program Files\Microsoft Office\Office16>cscript OSPP.VBS /act
    Microsoft (R) Windows Script Host Version 5.812
    Copyright (C) Microsoft Corporation. Tous droits réservés.

    ---Processing--------------------------
    ---------------------------------------
    Installed product key detected - attempting to activate the following product:
    SKU ID: dXXX
    LICENSE NAME: Office 16, Office16ProPlusVL_KMS_Client edition
    LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channel
    Last 5 characters of installed product key: WFG99
    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
    FOR MORE INFORMATION PLEASE VISIT: http://support.microsoft.com/kb/2870357#Error0xC004F074
    ---------------------------------------
    ---------------------------------------
    ---Exiting-----------------------------

    c:\Program Files\Microsoft Office\Office16>

    The product key seems to be different... Do you have an idea ?

    I can force on the clients the KMS host name, same results, office is not activated.

    Monday, October 05, 2015 2:30 PM
  • wow, cbartsys, how did you produce the text output from the server?  all I got was a uncopyable text windows.
    Monday, October 05, 2015 2:49 PM
  • To begin, on the KMS Host:

    • cd c:\Windows\System 32
    • cscript slmgr.vbs /dlv ALL | more
    • Stop when you see: Name: Office 16, Office16KMSHostVL_KMS_Host edition, KMSHostVL edition
    • Then copy the Activation ID 
    • Command:  cscript slmgr.vbs /dlv MY-ACTIVATION-ID-HERE

    Monday, October 05, 2015 2:52 PM
  • oh wow, "cscript" in the front is the trick...THANKS!!
    Monday, October 05, 2015 3:04 PM
  • this is what I got from the KMS server:

    C:\Windows\System32>cscript slmgr.vbs /dlv 98ebfe73-XXXX-XXXX-XXXX-XXXXXXXXXXXXXX
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Software licensing service version: 6.3.9600.17809

    Name: Office 16, Office16KMSHostVL_KMS_Host edition
    Description: Office 16, VOLUME_KMS channel
    Activation ID: 98ebfe73-XXXX-XXXX-XXXX-XXXXXXXXXXXXXX
    Application ID: 0ff1ce15-a989-479d-XXXX-XXXXXXXXXXXXX
    Extended PID: 06401-00206-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Product Key Channel: Volume:CSVLK
    Installation ID: 0129568497630XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Use License URL: https://activation.sls.microsoft.com/SLActivateProduct/SLActiva
    teProduct.asmx?configextension=o14
    Validation URL: http://go.microsoft.com/fwlink/?LinkID=187557
    Partial Product Key: JQD9K
    License Status: Licensed
    Remaining App rearm count: -1
    Remaining SKU rearm count: -1
    Trusted time: 10/5/2015 08:07:11

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

    Key Management Service cumulative requests received from clients
        Total requests received: 0
        Failed requests received: 0
        Requests with License Status Unlicensed: 0
        Requests with License Status Licensed: 0
        Requests with License Status Initial grace period: 0
        Requests with License Status License expired or Hardware out of tolerance: 0

        Requests with License Status Non-genuine grace period: 0
        Requests with License Status Notification: 0

    Monday, October 05, 2015 3:12 PM
  • Activation doesn't work for you ?

    Do you have 5 KMS clients ?

    I still have the same problem

    Monday, October 05, 2015 3:15 PM
  • Hi cbartsys... Do you have Volume Activation Management Tool installed on the server? If yes, run it as administrator, click Office on the left side and click discover products. this will display all the computers that has office on it. once it populated, highlight all and update the license status. after that, use the filter option on the left side to narrow down the products. you have to look for "Office 2016 KMS Clients", highlight the result, then click on activate online using current credentials.

    Monday, October 05, 2015 3:41 PM
  • Hi The guy down the hall. base on the result, the server is not receiving any notifications yet from the client machines that has Office 2016. it is either there's no computer that has office 2016 on it or the computers are on a different domain/network. if you have a computer that has office 2016, try checking the connection by pinging the ip or computer name of the kms server. you should have at 5 client machines to do the kms activation
    Monday, October 05, 2015 3:44 PM
  • I have VAMT 3.1 on my server, I have the following error:

    "The software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted.

    Please see the Application Event log for additionnal information".

    Server log: 

    An activation request has been processed.
    Info: XXXX, Client-1 XXXXXXXX

    Firewalls are desactivated on all clients.


    • Edited by cbartsys Monday, October 05, 2015 3:56 PM
    Monday, October 05, 2015 3:55 PM
  • Hi cbartsys, can you try doing he following:

    1. get the ip of the kms host

    2. on the client machine, run the following script in the elevated cmd

    -cscript "location of the ospp.vbs" /sethst:"ip of the server"

    -do this on the 5 machines

    3. if it will not work, on VAMT, highlight the client machines, then select "Install KMS Client Key"

    4. try activating after

    *Make sure that you can ping the ip of the kms host using the client machines

    Monday, October 05, 2015 4:03 PM
  • hmmm....I just have one computer with Office 2016, I guess I just need to install four more?
    Monday, October 05, 2015 4:10 PM
  • I have the following error when trying to install KMS client Key for my laptop:

    "Product key not available"

    I can ping the server from my 5 clients...
    • Edited by cbartsys Monday, October 05, 2015 4:20 PM
    Monday, October 05, 2015 4:19 PM
  • yes... four more to do the activation
    Monday, October 05, 2015 5:02 PM
  • hi cbartsys... have you tried running the cscript for the "sethst"? if not yet, try searching for the location of the ospp.vbs on the client machine... base on your info above, this is were the root folder of the office. c:\Program Files\Microsoft Office\Office16... base on this location.... try the following ts

    1. run command prompt as admin

    type in "cscript "c:\Program Files\Microsoft Office\Office16\ospp.vbs" /sethst:<ipofthekmshost>

    2. if the setting of host is successful,

    type "cscript "c:\Program Files\Microsoft Office\Office16\ospp.vbs" /act"

    if this one will not work, I would suggest for you to call support.

    Monday, October 05, 2015 5:12 PM
  • Thank you for the reply but it doesn't work.

    I noticed something strange:

    On kms host: Partial Product Key: 8BR3G

    On kms client: Last 5 characters of installed product key: WFG99

    The key seems to be different but i don't know why...

    We have only one key on our VLSC for offiice 2016 (kms), so i'm pretty sure we are using the right key.

    Do you have an idea ?

    EDIT: 

    i tried on KMS host: slmgr.vbs /upk Office-2016-Activation-ID

    then on KMS client ospp.vbs /act and i have the same error.

    I think something is wrong with my office key.


    • Edited by cbartsys Tuesday, October 06, 2015 8:19 AM
    Tuesday, October 06, 2015 8:16 AM
  • Hi cbartsys... With Office 2010/2013, the KMS host key is usually different from what is really showing on the computer since the computer will recognize the default kms client key. here's what I can suggest

    1. download the kms license pack for office 2016 on the kms host server and install it (http://www.microsoft.com/en-us/download/details.aspx?id=49164)

    2. after you have done installing it, the volume activation tool will pop up and asked you to set it up, you need to set it up using kms. follow the wizard to complete the activation

    3. once it is activated, run command prompt as admin and run this script "cscript slmgr.vbs /dlv 98ebfe73-2084-4c97-932c-c0cd1643bea7"..this will check the activation status for office 2016 kms host

    4. after running it, open the Volume Activation Management Tool and discover all the office products, one it discovers all computers that has office, highlight all and update license status, then filter it to show only computers that has Office 2016 KMS client, highlight all and activate online using current credential

    5. if the step above doesn’t work, I would suggest for you to do the activation on the client machine itself by running the following script

    a. "cscript "c:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus  : this will show the current information for the office

    b. if the result says KMS client, run this script… "cscript "c:\Program Files\Microsoft Office\Office16\ospp.vbs" /sethst: <ip address of the kms host server>…this command will direct the notification to the kms host itself

    c. if it is successful, run this script "cscript "c:\Program Files\Microsoft Office\Office16\ospp.vbs" /act”… this should activate the office now

    It is recommended to use the Volume Activation Management Tool to manage the activation specially if you have more than 5 machines connecting to the server

    You can also refer to this site http://support.microsoft.com/kb/2870357 to fix activation issues on client machines.

    Tuesday, October 06, 2015 1:19 PM
  • i also have this problem on 2008r2.

    2010 and 2013 work fine, 2016 get an error.

    https://social.technet.microsoft.com/Forums/getfile/730305

    https://social.technet.microsoft.com/Forums/getfile/730306

    https://social.technet.microsoft.com/Forums/getfile/730307

    Wednesday, October 07, 2015 10:43 AM
  • Yep, same here...
    Wednesday, October 07, 2015 12:28 PM
  • if the steps provided did not work, then this is a possible issue with Office 2016 kms
    Wednesday, October 07, 2015 1:07 PM
  • looks like it.
    Wednesday, October 07, 2015 1:08 PM
  • We opened a trouble ticket and i'm working with the MS support.

    I uploaded logs to MS support, an engineer will analyze it. I will tell you if we find something.

    Thank you Wenggay1985 but it doesn't work.



    • Edited by cbartsys Wednesday, October 07, 2015 2:44 PM
    Wednesday, October 07, 2015 2:38 PM
  • Great! Thanks for dong that. I'm having the same issue after following all the steps. It just doesn't like my KMS key.
    Wednesday, October 07, 2015 4:18 PM
  • I think it has nothing to do with the key, could be a known issue for the activation on the kms client. Microsoft might be checking this already
    Wednesday, October 07, 2015 6:49 PM
  • I have done all that with no issue. When I commit the changes I get:

    The following error has occurred. Please resolve the error and try again.

    Description: Status_Success

    Sure sounds like it worked but it won't commit so the KMS host  is never registered under slmgr /dlv

    This is with a working Windows 10 KMS host box I am just trying to add the Office 2016 to it

    Any ideas?

    Thursday, October 08, 2015 2:09 PM
  • Actually found this one on my own. The KMS port defaults to zero just change it to the 1688 or whatever port you use and it will commit.

    No for the question no one can answer why does MS punish the people that buy it's volume products with this mess of a procedure!

    Thursday, October 08, 2015 2:20 PM
  • My issue is different. I'm able to activate the our 2016 KMS key on the KMS server using the ISO I downloaded. It shows correctly with /dlv - but when I try to add the KMS key in the "Product Keys" section of VAMT (so I can install the key from the VAMT) I get an error:

    "The specified product key is invalid, or is unsupported by this version of VAMT. An update to support additional products may be available online."

    Thursday, October 08, 2015 4:07 PM
  • Same here. KMS Host is good, client doesn't activate. Can activate Windows 10 against the same KMS host. Can activate Office 2013 against the same host. Issue is definitely with Office 2016.
    Thursday, October 08, 2015 5:36 PM
  • I know this will not help the issue but I can report that using VA Services via Server Manager I was able to setup my KMS key using activate directory based activation.  The only problem is that VAMT does not recognize Office 2016.
    Friday, October 09, 2015 3:19 AM
  • I also have problem with activation of the product key by phone on windows7.
    Kms is working for Office 2010,2013 but 2016 no.

    Friday, October 09, 2015 1:47 PM
  • I can confirm that copying pkeyconfig-office-kmshost.xrm-ms from the office 2016 license pack to C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig fixes the issue for Office 2016.


    Monday, October 12, 2015 4:09 PM
  • Hello Matziq,

    can you be more specific ? I tried your solutiont but it doesn't work.

    MS Support is working on a fix, they succeeded to reproduce the bug.

    Tuesday, October 13, 2015 7:17 AM
  • I can confirm that copying pkeyconfig-office-kmshost.xrm-ms from the office 2016 license pack to C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig fixes the issue for Office 2016.


    its not working.
    Tuesday, October 13, 2015 8:03 AM
  • What I did is download the 2016 office activation kit. Then I used WINRAR to decompress the EXE to a folder, located the pkeyconfig-office-kmshost.xrm-ms file and copied to the location above (where VAMT is installed). Once I did that and rebooted it took my 2016 keys.

    John W. Rea

    Tuesday, October 13, 2015 1:30 PM
  • Hello,

    Microsoft proposed me to do that:

    https://support.microsoft.com/en-us/kb/3104410

    I have to use an other server...

    Wednesday, October 14, 2015 3:18 PM
  • What I did is download the 2016 office activation kit. Then I used WINRAR to decompress the EXE to a folder, located the pkeyconfig-office-kmshost.xrm-ms file and copied to the location above (where VAMT is installed). Once I did that and rebooted it took my 2016 keys.

    John W. Rea

    Worked for me.

    Thanks, John!


    Thursday, October 15, 2015 9:50 PM
  • What I did is download the 2016 office activation kit. Then I used WINRAR to decompress the EXE to a folder, located the pkeyconfig-office-kmshost.xrm-ms file and copied to the location above (where VAMT is installed). Once I did that and rebooted it took my 2016 keys.


    John W. Rea

    Worked for me.

    Thanks, John!


    Same here.

    That folder already had a couple of files in in that looked related to Office 2016, but they were dated from back in June.  The files from the KMS kit are all dated 8 September and don't show up anywhere in the VAMT3 folder.

     File naming convention of them matched the 2013 versions - "pkeyconfig-OfficeXXyyyy" where XX is the version (15 or 16) and yyyy is the type (Client or KMSHost).  Seems like VAMT is ignoring the v16 ones.

    Thursday, November 05, 2015 3:17 PM
  • 1. W2012R2 should be up to date with latest VAMT. (i had it from Windows 10 ADK)

    2. Open an elevated Command Prompt and run these commands:

    C:\Windows\system32> cscript slmgr.vbs /ipk YourOffice2016KMSKey

    C:\Windows\system32> cscript slmgr.vbs /ato

    to see the result run:

    C:\Windows\system32> cscript slmgr.vbs /dlv all

    Wednesday, November 11, 2015 1:22 PM
  • Hi Cory, I know this is an older thread but I am trying to get Office Pro Plus 2016 KMS working on our existing 2012R2 KMS server. Here you state that we need to just add our KMS key in the volume activation tools stuff and that is great and all but I cannot find our KMS key on the volume licensing site. Can you possibly tell me where I can get that now?

    Thanks in advance,


    Dave

    Tuesday, June 21, 2016 8:47 PM
  • Is it safe to do this on an existing working KMS Host server?

    The screen prompt says "Create a new KMS host by...."

    I don't want to break what is there already, is this just misleading text?

    Terrified of stopping my whole company's activation of Windows etc!

    Thanks,


    No sig is a good sig

    Tuesday, July 05, 2016 9:16 AM
  • Hi Dave Cour,

    https://www.microsoft.com/en-us/download/details.aspx?id=49164&fa43d42b-25b5-4a42-fe9b-1634f450f5ee=True - says this:

    " All volume editions of Office 2016 client products are pre-installed with a Generic Volume License Key (GVLK) key, which supports automatic activation for both KMS and Active Directory-Based Activation, so you will not need to install a product key. "

    Which might also explain why I can't find a KMS key for Office 2016 either. :)

    UPDATE - Reddit says this: the correct place in your VLSC portal? In VLSC go to Licenses -> Relationship Summary -> Select your active licensing ID -> Product Keys. The product name is "Office 2016 Suites and Apps KMS".

    Though I don't have one...

    UPDATE 2 - I called the VLSC and had to request the Office 2016 KMS key.


    Doug Kinzinger, MCSE



    Thursday, August 18, 2016 5:30 PM
  • Wednesday, January 11, 2017 9:34 AM
  • This worked for me, thank you!

    Monday, June 05, 2017 5:48 PM