locked
Windows 7 clients unable to activate Office 2016 using Licensed KMS key RRS feed

  • Question

  • Hey All,

    For some reason the Windows 7 Enterprise clients in my environment are unable to active their Office 2016 Pro Plus bits against our Server 2008 R2 KMS Host despite the fact that slmgr.vbs /dlv <2016 act id> returns License Status: Licensed.

    The error the clients are all showing when I run ospp.vbs /act is 0xC004F074.

    I have used 5 different VMs from 5 different VDI pools to ensure the KMS server saw at least 5 activation requests from 5 different PCs.

    All my searches on that error code have come up with various solutions but none have worked. The server and clients are fully patched and their time is synced with the network NTP (confirmed). It's also worth noting that we put the same Office 2016 KMS key into our ADBA and that works fine for the Windows 10 clients in the environment. Their versions of Office 2016 activated just fine.

    Is there a step I'm missing for setting up Office 2016 KMS for Windows 7 Enterprise clients?



    • Edited by SSDJr Monday, October 5, 2015 2:21 PM
    Friday, October 2, 2015 2:41 PM

Answers

All replies

  • Sorry to piggyback, but a somewhat related question.  Microsoft lists the Office 2013 activation ID here:

    https://technet.microsoft.com/en-us/library/dn385356.aspx  (it appears to be generic), but hasn't listed it for Office 2016 yet.  I notice you used <2016 act id> above, but since it is generic would you mind publishing?  I can't find it anywhere online yet. and my system's "cscript /dlv All" command only outputs to a window that doesn't allow scrolling. It of course is at the bottom.

    • Proposed as answer by Philip Sellers Thursday, December 10, 2015 3:39 PM
    Friday, October 2, 2015 3:32 PM
  • You should be able to view the information all within your command prompt window by opening an administrative command prompt and typing the following in the C:\Windows\System32 directory:

    cscript slmgr.vbs /dlv all

    That should keep the output in the Command Prompt window allowing you to scroll back through all the output.

    Unfortunately I can't risk giving out my activation ID until I find official Microsoft confirmation that this is still a generic number. If you are able to run the command above you can send me (via maxis_x at Hotmail) the first five and last five characters  of your Activation ID output and if they match we can post up the number for our fellow IT administrators.


    • Edited by SSDJr Friday, October 2, 2015 4:34 PM
    Friday, October 2, 2015 4:17 PM
  • Same issue here. Even manually defined the host, no luck.

    I should note that my KMS Host is 2008 R2 x64, and upon trying to install the KB2757817 update it says "this update is not applicable to your computer".

    KMS Host Output:

    Name: Office 16, Office16KMSHostVL_KMS_Host edition, KMSHostVL edition
    Description: Office 16, VOLUME_KMS channel, VOLUME_KMS channel
    Partial Product Key: xxxxx
    License Status: Licensed

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

    Client:

    cscript ospp.vbs /act returns:

    Installed product key detected - attempting to activate the following product:
    SKU ID: d450596f-894d-49e0-966a-fd39ed4c4c64
    LICENSE NAME: Office 16, Office16ProPlusVL_KMS_Client edition
    LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channel
    Last 5 characters of installed product key: xxxxx
    ERROR CODE: 0xC004F074
    ERROR DESCRIPTION: The Software Licensing Service reported that the product coul
    d not be activated. No Key Management Service (KMS) could be contacted. Please s
    ee 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#Error
    0xC004F074

    cscript ospp.vbs /dstatusall returns

    SKU ID: d450596f-894d-49e0-966a-fd39ed4c4c64
    LICENSE NAME: Office 16, Office16ProPlusVL_KMS_Client edition
    LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channel
    LICENSE STATUS:  ---NOTIFICATIONS---
    ERROR CODE: 0xC004F056
    ERROR DESCRIPTION: The Software Licensing Service reported that the product coul
    d not be activated using the Key Management Service (KMS).
    Last 5 characters of installed product key: xxxxx
            DNS auto-discovery: KMS name not available
            KMS machine registry override defined: xxxxxxxxxxx:1688
            Activation Interval: 120 minutes
            Renewal Interval: 10080 minutes
            KMS host caching: Enabled

    Friday, October 2, 2015 4:43 PM
  • That is really odd, when I type cscript slmgr.vbs /dlv all in an admin cmd prompt window on our other 2012R2 KMS server I get all the slmgr output in the command prompt window.  The only time I get the un-scrollable white pop out window is when I don't include "cscript" before the slmgr.vbs command.
    Friday, October 2, 2015 5:09 PM
  • Please disregard.  I realized I was missing cscript in front on the slmgr.vbs command.  It now outputs to the command line. 
    Friday, October 2, 2015 5:17 PM
  • Just saw this after I realized it too.  thanks!
    Friday, October 2, 2015 5:18 PM
  • No worries, glad you figured it out!
    Friday, October 2, 2015 5:20 PM
  • Here is the output from my 2k8 R2 x64 KMS server when I run cscript slmgr.vbs /dlv all

    Software licensing service version: 6.1.7601.18257
    Name: Office 16, Office16KMSHostVL_KMS_Host edition, KMSHostVL edition
    Description: Office 16, VOLUME_KMS channel, VOLUME_KMS channel
    Activation ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
    Application ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
    Extended PID: xxxxx-xxxxx-xxx-xxxxxx-xx-xxxx-xxxx.xxxx-xxxxxxx
    Installation ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    Partial Product Key: XXXXX
    License Status: Licensed
    Remaining Windows rearm count: 2
    Trusted time: 10/2/2015 7:09:47 AM
    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: 467
        Failed requests received: 31
        Requests with License Status Unlicensed: 0
        Requests with License Status Licensed: 397
        Requests with License Status Initial grace period: 38
        Requests with License Status License expired or Hardware out of tolerance: 1
        Requests with License Status Non-genuine grace period: 0
        Requests with License Status Notification: 0

    Friday, October 2, 2015 5:26 PM
  • Seeing the same thing here. I'm wondering if a 2008 R2 KMS server can actually activate Office 2016. Can't imagine why not but I likewise can't think of anything else. I've even installed the patch to allow the 2008 R2 KMS to activate Win 10 without any change.

    James

    Tuesday, October 6, 2015 3:14 PM
  • I'm having the same issue as well on a Win2k8 KMS server.

    One thing I've noticed is that the APP ID for Office16/2016, Application ID: 0ff1ce15-a989-479d-af46-f275c6370663, is the same as Office15/2013.  My counters on the Office 2016 license are increasing, it seems that the Office 2016 license is activating Office 2013 requests due to the APP ID matching office 2013.

    Thoughts?

    Tuesday, October 6, 2015 3:25 PM
  • I'm having the same issue and every failed activation actually increased the "Failed request received" for both office 15 and 16. Has anyone found solution to this issue?
    Tuesday, October 6, 2015 3:40 PM
  • Same here.
    Tuesday, October 6, 2015 6:11 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 7, 2015 10:36 AM
  • Same problem, Anyone tried to open a ticket with MS?
    Wednesday, October 7, 2015 2:25 PM
  • We are seeing a similar issue, but get code 0xC004F042. About to log it.
    Thursday, October 8, 2015 1:42 AM
  • Same issue with Windows 2008 R2 Server; any help much appreciated.
    Thursday, October 8, 2015 10:05 AM
  • Count us in as having this issue. The key works fine for AD based activation, but the combo of Windows 7 clients and the KMS host (Server 2008 R2) fail.
    • Edited by BryanCP Thursday, October 8, 2015 11:59 AM
    Thursday, October 8, 2015 11:54 AM
  • Same problem here! Definitely sounds like MS needs to come up with some kind of fix.
    Thursday, October 8, 2015 1:40 PM
  • I'm encountering the same issue. KMS host is Win2008r2 and successfully activates all Office and Windows Client/Server products except Office 2016. 

    slmgr /dlv indicates that the KMS host key activation was successful and is LICENSED

    All clients are domain-connected and sync'ing time properly.

    Thursday, October 8, 2015 2:24 PM
  • FYI, I just installed Office 2016 on a Win 10 machine, but still having the same issue, so not just an issue with Win 7 workstations, the issue is most likely just with using a Win 2008 R2 server as the KMS host for Office 2016.

    Hopefully someone can open a ticket with MS to work this out?

    Thursday, October 8, 2015 2:28 PM
  • Agree, hard to believe that all of us misconfigured it. It must be a bug. 
    Thursday, October 8, 2015 2:37 PM
  • Same here...

    We have a W2008R2 KMS host that validate Windows 7, Windows 8.x, Windows 10, Office 2010, Office 2013 and Office 2016.

    Everything is working except for Office 2016.

    Error message from the activation is that the DNS Name cannot be resolved (funny because the OS is validated from the same KMS Host).

    Error message when using ossp.vbs /dhistorykms is that the Host cannot be used to validate the KMS client key.


    Thursday, October 8, 2015 2:47 PM
  • I'll add my name to the list. We are having the same issue as well. 
    Thursday, October 8, 2015 9:28 PM
  • Hi. We are encountering exactly the same problem on our KMS Host Windows 2008 R2.
    Friday, October 9, 2015 12:33 AM
  • FYI, I just installed Office 2016 on a Win 10 machine, but still having the same issue, so not just an issue with Win 7 workstations, the issue is most likely just with using a Win 2008 R2 server as the KMS host for Office 2016.

    Hopefully someone can open a ticket with MS to work this out?

    I've opened a case. I'll post the results.
    Friday, October 9, 2015 1:47 AM
  • thanks!
    Friday, October 9, 2015 5:28 AM
  • We are also having this issue with Office 2016 activations with a KMS host on a Win2008 R2 server.
    Friday, October 9, 2015 12:29 PM
  • FYI, I just installed Office 2016 on a Win 10 machine, but still having the same issue, so not just an issue with Win 7 workstations, the issue is most likely just with using a Win 2008 R2 server as the KMS host for Office 2016.

    Hopefully someone can open a ticket with MS to work this out?

    I've opened a case. I'll post the results.

    Really appreciate it!!! Many thanks JT_DPS, points to you! :)
    Friday, October 9, 2015 1:02 PM
  • 0xC004F074 also happens to me with an 2012R2 KMS Server and as a Client Windows 7 and Windows 10 with Office 2016 Standard.

    The Office 2016 Volume Licencing Pack is installed on from MS on the KMS:

    https://www.microsoft.com/en-us/download/details.aspx?id=49164

    Friday, October 9, 2015 1:50 PM
  • I've opened a case. I'll post the results.

    JP_DPS,

    You may want to mention to MS what ChAoSjg discovered, that the Application ID is the same in Office 2016 as in Office 2015. (Application ID: 0ff1ce15-a989-479d-af46-f275c6370663) Probably part of the problem, and hopefully that will help the MS tech realizing/figuring out the problem, or at least understand that the problem isn't with all of us, but it really is a MS problem.

    Thanks!

    Friday, October 9, 2015 2:16 PM
  • chiming in that I have same issue on Office 2016 KMS on 2008 R2

    ERROR DESCRIPTION: The Software Licensing Service reported that the product could not be activated using the Key Management Service (KMS).

    Friday, October 9, 2015 2:48 PM
  • I am running into the same issue, trying to activate MS Office 2016 ProPlus against our internal KMS Server.

    I downloaded the "SW_DVD5_Office_Professional_Plus_2016_W32_English_KMS_MLF_X20-42865.ISO" file from MVLS and ran the included "kms_host.vbs" script, added my KMS Host keys when it prompted, it reported success.

    I confirmed this by running "cscript slmgr.vbs /dlv all > c:\license-kms.txt" and in the output I can see..

    Name: Office 16, Office16KMSHostVL_KMS_Host edition, KMSHostVL edition
    Description: Office 16, VOLUME_KMS channel, VOLUME_KMS channel

    On my client, if I run ospp.vbs /act to activate my installation, I get the same error..

    C:\Program Files (x86)\Microsoft Office\Office16>cscript ospp.vbs /act
    Microsoft (R) Windows Script Host Version 5.812
    Copyright (C) Microsoft Corporation. All rights reserved.
    
    ---Processing--------------------------
    Installed product key detected - attempting to activate the following product:
    SKU ID: **********************
    LICENSE NAME: Office 16, Office16ProPlusVL_KMS_Client edition
    LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channel
    Last 5 characters of installed product key: *****
    ERROR CODE: 0xC004F074
    ERROR DESCRIPTION: The Software Licensing Service reported that the product could not be activated.
    NOTICE: A KB article has been detected for activation failure: 0xC004F074
    FOR MORE INFORMATION PLEASE VISIT: http://support.microsoft.com/kb/2870357#Error0xC004F074

    Anyone got this to work?


    Mirza Dedic

    Friday, October 9, 2015 4:04 PM
  • 0xC004F074 also happens to me with an 2012R2 KMS Server and as a Client Windows 7 and Windows 10 with Office 2016 Standard.

    The Office 2016 Volume Licencing Pack is installed on from MS on the KMS:

    https://www.microsoft.com/en-us/download/details.aspx?id=49164

    Ah Roll back :/ It works - i forgot to Acitivate the Office 2016 Key in KMS - now its running.
    Monday, October 12, 2015 7:54 AM
  • I am having the same issue, Office 2016 KMS Clients will not activate.  

    Running Windows Server 2008 R2.  2010 and 2013 Office KMS is working just fine and Windows 7 to Windows 10 KMS is working just fine also.

    Monday, October 12, 2015 2:53 PM
  • We will most likely need a hotfix from MS to correct this issue.
    Monday, October 12, 2015 3:34 PM
  • same problem here on Win 2008 R2 KMS, opened a ticket.

    Will keep you up to date

    Tuesday, October 13, 2015 6:38 AM
  • just received 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.

    Tuesday, October 13, 2015 8:47 AM
  • Replied as we need to follow this thread closely

    Come on Microsoft!

    Tuesday, October 13, 2015 9:50 AM
  • Wednesday, October 14, 2015 5:10 AM
  • come on MS
    Wednesday, October 14, 2015 8:20 AM
  • Waiting for the hotfix here too.

    Wednesday, October 14, 2015 1:34 PM
  • Microsoft published this article confirming the issue and and proposing a work-around: https://support.microsoft.com/en-us/kb/3104410 
    • Proposed as answer by TonyInIT Wednesday, October 14, 2015 4:16 PM
    Wednesday, October 14, 2015 4:16 PM
  • bump to keep the pressure on

    unable to deploy our windows 10 / office2016 sccm image without this

    our kms server needs leaving alone for the time being so we cant upgrade it to 2012 r2 yet

    Thursday, October 15, 2015 9:48 AM
  • We finally migrated to Win 2012 R2 KMS host.

    It works: Office 2016 kms and Office 2013 kms

    Thursday, October 15, 2015 1:18 PM
  • I think we will end up building a 2012 r2 server ourselves at this rate
    Friday, October 16, 2015 8:14 AM
  • We too are experiencing the issue.  Figured it wouldn't hurt to add to this thread even though I have seen the Microsoft kb and workaround.  I noticed on the workaround that server 2012 r2 was recommended.  We aren't licensed for r2, just 2012.  Anyone know if that works?
    Monday, October 19, 2015 2:22 PM
  • I am also having same issue on Win 2008 R2 KMS server. Ofice 2016 clients not activating.
    Tuesday, October 20, 2015 6:56 AM
  • bump, come on MS

    need to start building clients and rds servers

    please dont make me build a server just for kms

    Thursday, October 22, 2015 9:48 AM
  • bump to keep the pressure on

    unable to deploy our windows 10 / office2016 sccm image without this

    our kms server needs leaving alone for the time being so we cant upgrade it to 2012 r2 yet

    I too am facing this issue, hoping for a fix from MS. 

    What's the harm in upgrading a 2008r2 KMS server to 2012r2?

    I'm a bit unsure about MS's work around to setup a Win 8.1, Win10 or server 2012r2 KMS server - I don't think I can leave my current KMS server online with existing licenses and setup an additional one just for office can I?  Will a client look to one KMS server for its OS license and another for its office license?  I would think not. 




    • Edited by TheDL Friday, October 23, 2015 1:47 PM
    Friday, October 23, 2015 1:43 PM
  • We finally migrated to Win 2012 R2 KMS host.

    It works: Office 2016 kms and Office 2013 kms

    FWIW I'm also seeing that my office 2013/2016 application IDs are the same.  Once upgraded to Server 2012r2 KMS host do your 2013/2016 office application IDs still show the same ID?
    Friday, October 23, 2015 1:45 PM
  • I am seeing the same issue.  I hope they fix this soon. Has anyone heard anything about a fix?

    Thanks,


    Dwayne Adams

    Monday, October 26, 2015 9:08 PM
  • I wouldn't jump to a rebuild of the server.  We have KMS running on a fully-patched Win 2012 R2 server and we are also seeing the same issues.
    Wednesday, October 28, 2015 8:06 PM
  • No, we are having the same problems on our Win 2012 R2 KMS host.
    Wednesday, October 28, 2015 8:07 PM
  • I think this is server OS agnostic. We are having the same problems on our Win 2012 R2 KMS host.
    Wednesday, October 28, 2015 8:07 PM
  • argh!!!!

    Only checked this thread AFTER building and migrating to 2012 R2

    Still having the same problem, can't find KMS server and won't activate despite running all of the correct commands

    Looks like our refresh of desktop and rds clients will have to wait

    /makes coffee and puts feet up

    also MS are being very sneaky, none of my replies here are being registered against my account history, mmmmmmmmmm

    Monday, November 2, 2015 12:27 PM
  • Exact same issue here...Office 2013 and 2016 KMS on Server 2008R2

    I have read the KB..its been a month...any updates or fixes beyond creating a whole new server?  Thx

    Monday, November 2, 2015 9:20 PM
  • Exact same issue here...Office 2013 and 2016 KMS on Server 2008R2

    I have read the KB..its been a month...any updates or fixes beyond creating a whole new server?  Thx

    New server doesn't work either

    Seems enterprises simply can't roll out Office2016 lol

    Tuesday, November 3, 2015 8:23 AM
  • As some have noted the application ID for Office 2013 and 2016 are the same, for Win 7 and 2008 Host server,  you can't run the 2013 and 2016 KMS Hosts on the same server. I built a new server without Office 2013 KMS installed and this works, I can activate 2016 KMS licenses.  KB Article from MS https://support.microsoft.com/en-us/kb/3104410
    Tuesday, November 3, 2015 11:36 PM
  • Nope,

    We built a new server with only Office 2016 KMS key and it still doesn't activate

    Wednesday, November 4, 2015 9:55 AM
  • Hey all,

    Same issue here.  I can't believe Microsoft has not fixed this yet.  I feel like they are trying to force me to update to 2012 KMS before we are ready and when it makes sense for our business.

    -Dwayne

    Wednesday, November 4, 2015 6:58 PM
  • Same issue here too.  Windows 2008 R2 KMS server which has Office 2013 and 2010 licences installed already.  I noticed too that the product ID for 2016 and 2013 were the same.  Clients trying to activate are Windows 7.  We are currently not ready to move to 2012 server based KMS.  I really hope they fix this soon!
    Thursday, November 5, 2015 1:29 PM
  • Ahh, I see. That's 4 hours of my life I'll never get back. Still glad it wasn't something I was doing wrong.

    I'm seeing this on server 2008 R2, which would be tricky to migrate from but possible. However, some are saying this also affects hosting office 2013 and 2015 on server 2012 R2 as well. The article says this should work. So not sure now...

    SO, just to confirm, If I build a 2nd KMS just for office 2016 (probably server 2012 R2), and add the appropriate DNS SRV record, the clients will check BOTH KMS servers for a licence?

    Cheers

    Andy

    Friday, November 6, 2015 12:47 PM
  • We went ahead and moved kms to server 2012, and it still does not work, as stated by others.  I figured we would have a fix by now.  Very frustrating!
    Friday, November 6, 2015 10:49 PM
  • We are waiting for a fix to this.....................

    Perhaps it is a Microsoft ploy to get our users to desire Windows 10.  I know a few of mine have, since we told them that Office 2016 activates fine on Windows 10 workstations.

    .................I'm kind of ok with that..............even though I shouldn't be.

    Jeff


    Jeff Cummings - tech support and sharepoint project manager

    Saturday, November 7, 2015 2:28 AM
  • ERROR CODE: 0xC004F074
    ERROR DESCRIPTION: The Software Licensing Service reported that the product coul
    d not be activated. No Key Management Service (KMS) could be contacted. Please s
    ee 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#Error
    0xC004F074
    Monday, November 9, 2015 11:09 AM
  • We are waiting for a fix to this.....................

    Perhaps it is a Microsoft ploy to get our users to desire Windows 10.  I know a few of mine have, since we told them that Office 2016 activates fine on Windows 10 workstations.

    .................I'm kind of ok with that..............even though I shouldn't be.

    Jeff


    Jeff Cummings - tech support and sharepoint project manager


    Odd, this is not working for me from Windows 10 either...
    Monday, November 9, 2015 2:50 PM
  • Same issue here as well. I was thinking about just trying to perform an in-place upgrade of my server to 2012R2, but then I thought that it might really bake my all my MS licensing. I just can't wait too much longer for a hotfix, we need to start testing for a spring deployment.
    Monday, November 9, 2015 5:02 PM
  • Don't bother w/an OS upgrade. We have several clients which have Windows 2012/R2 and are still experiencing this issue.
    Monday, November 9, 2015 5:47 PM
  • This is how I resolved it.  Our windows 7 machines showed that same error 0xC004F074 when trying to activate.  We are using xendesktop and had installed Office 2016 on the "golden" image.  When I tried to rearm (office16 directory ospprearm.exe), it gave me the error.  Everything I tried to fix it, would not work.  I moved our kms server from 2008r2 to 2012, ran the keys over and over, used vmat, nothing helped.  It turned out, you have to go to the directory and run the executable directly rather than through a command prompt, and you may have to run it a few times to get it to work.  Even when I got it to work, it still showed those error messages.  Microsoft told me to ignore them.  So, if you run ospprearm and then go to command prompt and type ospp.vbs /dcmid, and it shows an ID, run ospprearm.exe again.  Then, go back and check dcmid and when it says "none", you're good.  Rearm windows and shutdown your golden machine.  After you boot 5 machines with a "none" in dcmid, it will license everything.  I knew all of that, however, I didn't know you had to run ospprearm over and over.  I ran it once and assumed it worked, and all the other errors threw me off as well.  Another thing that threw me off was VAMT.  When I tried to put my product ID there, it gave me errors.  Turns out, ignoring the errors is the way to go once again.  Of course, if you don't run the office 2016 volume license pack, it won't work either.  After running the pack, and putting in your license, getting 5 to check in, you can activate all the rest from VAMT.  Good luck all!
    • Edited by Tiffrog Tuesday, November 10, 2015 7:20 PM
    Tuesday, November 10, 2015 6:43 PM
  • We've been waiting for a hotfix for over a month already. It would nice to get some feedback on when to expect this.
    Thursday, November 12, 2015 5:05 PM
  • I think you need to manually set your 2016 clients to use the correct server, and not doing this is why the fix is not working for a lot of people. 
    Thursday, November 12, 2015 5:08 PM
  • Hi jcoehoorn.

    The fix being to upgrade the OS of the KMS?

    Can I ask, why do you need to manually set the KMS server name on the client if the DNS srv records are all working fine?

    Would this just be via the /sethst switch on ospp.vbs?

    Cheers

    Andy

    Friday, November 13, 2015 8:44 AM
  • We've had no problems with Windows 10 activating Office 2016, so we're actually starting to deploy Windows 10 early ahead of our schedule.  Microsoft is winning.

    I have to admit, so far, I like Windows 10.

    Jeff


    Jeff Cummings - tech support and sharepoint project manager

    Sunday, November 15, 2015 6:58 AM
  • My understanding right now, after reading through everything, is the only thing that is certain to work for everyone is putting the KMS service for Office 2016 on a 2012 R2 or Windows 10 machine. This machine must not have anything installed for Office 2013 KMS activation, meaning there is a split in your KMS infrastructure. You'll want to leave the DNS settings with the old Office 2013 KMS service (because that also has your Windows licensing), and use a manual /sethst to force Office 2016 clients to find the new server when activating Office.

    Based on what I've read so far, this should work for anyone still having trouble. However, it's just based on reading through this and a couple other threads. I haven't tried it myself yet.

    I'm not interested in setting up a separate KMS service or manually activating Office 2016 hosts. We're also deploying Win10 and Office 2016 together, so Win10+O2016 will just have to wait until MS gets it's act together before we upgrade anyone.





    • Edited by jcoehoorn Monday, November 16, 2015 4:39 PM
    Monday, November 16, 2015 4:34 PM
  • https://support.microsoft.com/en-us/kb/3104410

    Time to wait for a hotfix.


    Any timeframe for a fix? Did someone opemed a case ticket to MS, how it is going?
    Friday, November 20, 2015 6:54 AM
  • We really need a solution from Microsoft on this. Currently, we are running our KMS hosts for both Office 2013 and Office 2016 them on a Windows 2012 R2 server and are experiencing this issue.  We are unable to split these hosts onto two separate servers.  This is getting urgent.

    The following KB article is not helpful:

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

    Friday, November 20, 2015 5:32 PM
  • Same exact setup, same issue. Looking for a resolve...
    Sunday, November 22, 2015 8:39 PM
  • https://support.microsoft.com/en-us/kb/3104410

    Time to wait for a hotfix.


    Any timeframe for a fix? Did someone opemed a case ticket to MS, how it is going?

    We have a case opened, but it was closed temporarily while the hotfix is completed by the product group.  I'll ask for a time frame.

    Monday, November 23, 2015 1:16 AM
  • Thanks.  I am almost at the point that I will need to push forward to 2012 R2.  Are some people still having issues even after the upgrade?

    -Dwayne

    Tuesday, November 24, 2015 4:10 PM
  • https://support.microsoft.com/en-us/kb/3104410

    Time to wait for a hotfix.


    Any timeframe for a fix? Did someone opemed a case ticket to MS, how it is going?

    We have a case opened, but it was closed temporarily while the hotfix is completed by the product group.  I'll ask for a time frame.

    Thanks JT_DPS! Doesn't seem like MS is prioritizing getting Office 2016 out there in the business world... "amazing"... ! :/ Their KB article hasn't been updated since 10/14/2015.
    Tuesday, November 24, 2015 4:14 PM
  • I've got the exact same problem with office 2016/server 2008 R2 KMS, any news from MS yet ?

    • Edited by Simoncu Friday, November 27, 2015 9:37 AM
    Friday, November 27, 2015 9:37 AM
  • To your point I just came across this article that indicated you must have a "5 Count" before the KMS will start registering it. https://support.microsoft.com/en-us/kb/983845
    Tuesday, December 8, 2015 1:35 AM
  • JT_DPS,

    Were you able to get a time frame for the hotfix to resolve the issue with Office 2016 and KMS?

    Friday, December 11, 2015 2:58 PM
  • Blimey this is taking a while.

    Or is it just because of the constant drippy nagging in my ear from people who don't have enough work to keep them occupied and simply must play with the latest version of office. :-)

    BTW, If I build a 2nd KMS just for office 2016 (probably server 2012 R2), and add the appropriate DNS SRV record, will the clients check BOTH KMS servers for a licence or just one?

    Andy

    Tuesday, December 15, 2015 10:14 AM
  • We are continuing to install Office 2016 throughout the enterprise.  If we replace all Office 2013 with 2016, do we even need a 2013 KMS?  Isn't that the cause of the problem, the two KMS in the system?

    None of the Windows 7 systems are activating Office 2016.  I've got it installed on approx. 40 systems, with about 30 to 40 systems more to go.

    Just curious what everyone thought of this,

    Jeff


    Jeff Cummings - tech support and sharepoint project manager



    • Edited by OceanJeff40 Wednesday, December 16, 2015 2:42 AM another addition
    Wednesday, December 16, 2015 2:39 AM
  • still the same 2008r2 KMS --> Office 2016 registration

    Hello MS?

    Monday, January 11, 2016 1:08 PM
  • Anyone got any updates to share?!
    Monday, January 11, 2016 10:00 PM
  • too much time to work on solution
    Monday, January 18, 2016 8:01 AM
  • I am also having this issue. I currently have two KMS servers. One Server 2012 that does Windows 10 and Office 2016 installs and a 2008 R2 that does Windows 7 and all other office installs. I currently can't do Windows 7 with Office 2016.
    Tuesday, January 19, 2016 6:09 PM
  • The Microsoft Office 2016 Volume License Pack has been re-issued to resolove the issue.

    "4324.1002 update extends the Key Management Service (KMS) to support co-hosting of Office 2013 and Office 2016 on Windows Server 2008 R2."

    https://www.microsoft.com/en-us/download/details.aspx?id=49164

    • Proposed as answer by JT_DPS Wednesday, January 20, 2016 2:56 AM
    Wednesday, January 20, 2016 2:56 AM
  • The Microsoft Office 2016 Volume License Pack has been re-issued to resolove the issue.

    "4324.1002 update extends the Key Management Service (KMS) to support co-hosting of Office 2013 and Office 2016 on Windows Server 2008 R2."

    https://www.microsoft.com/en-us/download/details.aspx?id=49164

    I have successfully installed the above update and we can now activate Office 2013 and Office 2016 from KMS installed on the same Win2008 R2 server. Thanks JT_DPS for the update!
    Wednesday, January 20, 2016 3:28 PM
  • Yaaaay!!! I'm all good too!! (Win 2008 R2, with both Off 2013&2016) MANY THANKS JT_DPS!!!!
    Friday, January 22, 2016 6:18 PM
  • We installed this today, any ideas how long it takes to work?

    Jeff


    Jeff Cummings - tech support and sharepoint project manager

    Tuesday, February 2, 2016 1:33 AM
  • Ok, yeah, we had to do some troubleshooting, but the activation started immediately.  Not all systems activated, but we can probably easily troubleshoot the few that don't.  My manager installed the update, and the original KMS was on our DC01 (domain controller), but the new install was put onto DC02 (2nd domain controller).  I noticed the clients were all looking at DC01, a particular port, so I asked if that port was open in the firewall on DC01, and then he realized the original install config would work better, so he moved it back, and systems started activating immediately.

    Jeff


    Jeff Cummings - tech support and sharepoint project manager

    Wednesday, February 3, 2016 5:17 PM