Office 2016 KMS Issues

[Frut02]

Hi All,

 

Having an issue that is starting to drive me a little insane. I have 350 machines in the school that all have office 2016 on. Setting up the KMS server and it only reports a count of 1 even though it's had 400 + requests. I've tried instaling the update for ffice 2016 kms host. I've been looking at this for days now and i cant figure it out? Windows 7 activates really well. I've even investigated ways of manually increasing the count on the server to 5 so that it will start activating, but have not had much luck with finifn one for office.

 

Any ideas, i've put the details for the office bit from a slmgr.vbs /dlv below

 

Name: Office 16, Office16KMSHostVL_KMS_Host edition, Office16KMSHostVL_KMS_Host edition

 

Description: Office 16, VOLUME_KMS channel, VOLUME_KMS channel

 

Activation ID: (Removed)

 

Application ID: (Removed)

 

Extended PID: 55041-00206-437-366861-03-2057-7601.0000-2292016

 

Installation ID: 020581783545481365065510675340472626653764402914876226

 

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: FCQJR

 

License Status: Licensed

 

Remaining Windows rearm count: 3

 

Trusted time: 16-Aug-16 9:03:40 AM

 

 

 

Key Management Service is enabled on this machine

 

Current count: 1

 

Listening on Port: 1688

 

DNS publishing enabled

 

KMS priority: Normal

 

 

 

Key Management Service cumulative requests received from clients

 

Total requests received: 494

 

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: 494

 

Many Thanks

 

Nick

[jdell]

I have seen a similar issue elsewhere when moving from 2k13 to 2k16.

 

What server OS are you running your KMS on?

What KMS version are you running?

 

How many unique machinces have you got running Office 2016 trying to activate?

[3s-gtech]

Do the Office 2016 clients have the KMS key installed in them? Ideally in your installation script but it can be added afterwards using VAMT 3.1.

[Frut02]

My KMS server is running on windows 2008 r2. KMS Version is 3.1. We have just rebuilt the entire network over the summer so it's a brand new install. I currently have about 60 unique machines on which i'm trying to activate office. The KMS server sees that they have the product and allows me to install the product key onto them without a problem. However just s not adding them to the count, which remains at 1.

[3s-gtech]

Are you using the right KMS client key - XQNVK-8JYDB-WJ9W3-YJ8YR-WFG99 is one (yes this is a publicly available KMS client key) or have you put the KMS host key on the clients? Common mistake.

[Frut02]

Using the KMS key provided to me from Microsoft Volume licence center. I have installed onto sever and not directly onto clients

[3s-gtech]

The clients use the key I posted to tell them to talk to your KMS host. Without that, they may not call in at all and you'll get these symptoms. Try pushing that key to five clients with VAMT and seeing what happens - you won't do any harm.

[Frut02]

Tried your key instead of the KMS one i had. Pushed it to 10 clients (just to be safe) Still the same KMS count is still 1.

 

I checked on the client adn it's looking at the correct server and port and the DNS setting for it is correct

[FN-GM]

Did you rearm the office installation before you captured the image as shown here? - https://technet.microsoft.com/en-gb/library/dn385362.aspx

 

The link does say Office 2013 but it also applies to 2016.

[Frut02]

That Worked!!! Just had to rearm 4 of them and now they are all activating - Thank you

[FragglePete]

Sorry I didn't see this earlier, but I'm glad you got this sorted. I had a similar issue myself a while back:

 

Office 2013 & KMS Activations - Blogs - EduGeek.net

 

Wasn't sure in Office2016 needed pre-arm before Sysprep so did it anyway, but you've just confirmed that it's needed on 2016 as well.

 

Pete

[Duke5A]

Sorry I didn't see this earlier, but I'm glad you got this sorted. I had a similar issue myself a while back:

 

Office 2013 & KMS Activations - Blogs - EduGeek.net

 

Wasn't sure in Office2016 needed pre-arm before Sysprep so did it anyway, but you've just confirmed that it's needed on 2016 as well.

 

Pete

 

Do you have your image auto logon after reboot when done to run post install scripts? Add these lines to your answer file.

 

               
                   false
                   3
                   "C:\Program Files (x86)\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"
                   Rearm Office
               
               
                   false
                   4
                   Activate Office
                   cscript "C:\Program Files (x86)\Microsoft Office\Office15\ospp.vbs" /act