KMS Activating Office 2010, 2013 and 2016

Jbir — Wed, 27 Apr 2016 13:04:38 GMT

I have had KMS setup and working for quite a while now, activating my office 2010 and 2013 pools (we have to keep 2010 on a certain pool for a particular app that works with it). I recently updated a couple of pools to office 2016 so i setup the KMS host to actovate 2016 also. All working well, or so i thought!

I now have discovered my 2010 pools are saying they are not activated and whatever i try i just can't get them to work with KMS. I can see on the KMS host that office 2010 is there:

C:\Windows\system32>cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864

Microsoft (R) Windows Script Host Version 5.8

Software licensing service version: 6.3.9600.17809

Name: Microsoft Office 2010, KMSHost edition

Description: Microsoft Office 2010 KMS, VOLUME_KMS channel

Activation ID: bfe7a195-4f8f-4f0b-a622-cf13c7d16864

Application ID: 59a52881-a989-479d-af46-f275c6370663

Extended PID: 06401-00096-199-341355-03-2057-9600.0000-1042015

Product Key Channel: Volume:CSVLK

Installation ID: 003623079516076780582002258641875076602862180693854691

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

License Status: Licensed

Remaining App rearm count: -1

Remaining SKU rearm count: -1

Trusted time: 27/04/2016 11:58:43

Key Management Service is enabled on this machine

Current count: 1

Listening on Port: 1688

DNS publishing disabled

KMS priority: Normal

Key Management Service cumulative requests received from clients

Total requests received: 281

Failed requests received: 0

Requests with License Status Unlicensed: 0

Requests with License Status Licensed: 197

Requests with License Status Initial grace period: 34

Requests with License Status License expired or Hardware out of tolerance: 5

Requests with License Status Non-genuine grace period: 0

Requests with License Status Notification: 0

But whenever i try and activate the count does not increase, it stays at 1 and on the client trying to activate it says the standard error about the count reorted by KMS is insufficient. However, when i run ospp.vbs /dstatusall i get an error saying the product key is not available. I have checked the registry and the keys are in place for the KMS server under HKLM\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform.

C:\Program Files\Microsoft Office\Office14>ospp.vbs /dstatusall

Microsoft (R) Windows Script Host Version 5.8

---Processing--------------------------

---------------------------------------

SKU ID: 191301d3-a579-428c-b0c7-d7988500f9e3

LICENSE NAME: Office 14, OfficeProPlusAcad-MAK edition

LICENSE DESCRIPTION: Office 14, RETAIL channel

LICENSE STATUS: ---UNLICENSED---

ERROR CODE: 0xC004F014

ERROR DESCRIPTION: The Software Licensing Service reported that the product key

is not available.

---------------------------------------

SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c

LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition

LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel

LICENSE STATUS: ---OOT_GRACE---

ERROR CODE: 0x4004F00D

ERROR DESCRIPTION: The Software Licensing Service reported that the application

is running within the valid out of tolerance grace period.

Last 5 characters of installed product key: H3GVB

REMAINING GRACE: 30 days (43199 minute(s) before expiring)

---------------------------------------

SKU ID: fdf3ecb9-b56f-43b2-a9b8-1b48b6bae1a7

LICENSE NAME: Office 14, OfficeProPlus-MAK edition

LICENSE DESCRIPTION: Office 14, RETAIL channel

LICENSE STATUS: ---UNLICENSED---

ERROR CODE: 0xC004F014

ERROR DESCRIPTION: The Software Licensing Service reported that the product key

is not available.

---------------------------------------

---Exiting-----------------------------

So, i thought i'd quickly create a temp snapshot using a MAK key and recompose the pool, but users now get prompted to activate the key online and when they click to do so get told that this action requires admin privilieges.

Any ideas appreciated. KMS drives me to despair with office but i thought i had it all working. Are 2016 and 2010 not supported on the same KMS server? Do i need to reinstall the 2010 kms host.

Re: KMS Activating Office 2010, 2013 and 2016

pbastiaans — Thu, 03 Jan 2019 21:12:36 GMT

Did you ever resolve this? I am having a similar issue. Thanks.

Re: KMS Activating Office 2010, 2013 and 2016

Bremen88 — Mon, 14 Jan 2019 10:45:17 GMT

After installing Office on your Master Image, you should not start Office (word, ecxel ..).

Office may not get a License

If Office already started, you need to "ream" the License on our Master.

cscript ospp.vbs /rearm

Re: KMS Activating Office 2010, 2013 and 2016

harnie1979 — Fri, 25 Feb 2022 10:58:29 GMT

I migrated the KMS server to a new Windows Server 2022 machine and installed the KMS host key (CSVLK) for Windows server 2022 datacenter. This key will also be used for activating my clients lower then the Server 2022 OS.
Besides this i installed the Office volume license packs for Office 2013/2016/2019/LTSC2021 and i tried doing the same for Office 2010.
Unfortunate the Volume License Pack for Office 2010 is only supported untill server 2012R2 and wont let it install on Server 2022, but it installed what i needed anyway.
After installing the Volume Licensepack Office LTSC 2021 i did not close the wizard but i clicked next to add another product. I added the Office 2010 CSVLK KMS key and activated the server.
Hope this helps
Cheers

topic Re: KMS Activating Office 2010, 2013 and 2016 in Horizon Desktops and Apps

KMS Activating Office 2010, 2013 and 2016

Re: KMS Activating Office 2010, 2013 and 2016

Re: KMS Activating Office 2010, 2013 and 2016

Re: KMS Activating Office 2010, 2013 and 2016