Nowhere on the interwebs have I been able to find a problem quite like what I started seeing yesterday. Maybe I'm just terrible at Google, but this issue has such a generic description I get results for every "Change/View Office Key" article on the inteet. God forbid I have to call Microsoft to get to the bottom of this dilemma.
I have a KMS key and a MAK key installed on my 2012R2 VAMT 3.0 server (With all the Win10/Office 2016 patches). It's been ruing great for a few months with no hiccups using the GVLK/KMS host keys. The MAK key I have installed was for testing, and was limited to 500 installs (Even though on the Microsoft Volume License Service Center it claims to have 2.1k seats??).
My issue is simple. I install the GVLK key on my client, then a few minutes later (or after opening Office) the key is reverted to my MAK key. Where my MAK key ran out of seats. I've even tried removing the MAK key from the KMS server, and ensured there were no AD Activation keys floating around. I italicize ensured because I can't actually find the AD configuration OU in my AD, just what I see in the VAMT interface.
So here's what I see after setting up my key
ospp.vbs /unpkey:MAK-Key
ospp.vbs /inpkey:KMS-Key
ospp.vbs /act
This appears to work great, then looking at ospp.vbs /dstatusall
C:Program FilesMicrosoft OfficeOffice16>cscript OSPP.VBS /dstatusall
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
---------------------------------------
SKU ID: 0ed94aac-2234-4309-ba29-74bdbb887083
LICENSE NAME: Office 16, Office16StandardVL_MAK edition
LICENSE DESCRIPTION: Office 16, RETAIL(MAK) chael
LICENSE STATUS: ---UNLICENSED---
ERROR CODE: 0xC004F014
ERROR DESCRIPTION: The Software Licensing Service reported that the product key is not available.
---------------------------------------
SKU ID: dedfa23d-6ed1-45a6-85dc-63cae0546de6
LICENSE NAME: Office 16, Office16StandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT chael
LICENSE STATUS: ---LICENSED---
ERROR CODE: 0x4004F040 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the product was activated but the owner should verify the Product Use Rights.
REMAINING GRACE: 179 days (259192 minute(s) before expiring)
Last 5 characters of installed product key: XXXXX (GVLK Key working activation)
Activation Type Configuration: KMS
DNS auto-discovery: KMS name not available
KMS machine registry override defined: vmnocaplicens01:1688
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---------------------------------------
---------------------------------------
---Exiting-----------------------------
I've read online that the error I see about verifying the Product Use Rights should be fine and still function correctly. Though I can't find how to remedy this. Side Tangent...
Anyways, a few minutes later (or after rebooting) dstatusall says this:
C:Program FilesMicrosoft OfficeOffice16>cscript OSPP.VBS /dstatusall
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
---------------------------------------
SKU ID: 0ed94aac-2234-4309-ba29-74bdbb887083
LICENSE NAME: Office 16, Office16StandardVL_MAK edition
LICENSE DESCRIPTION: Office 16, RETAIL(MAK) chael
LICENSE STATUS: ---LICENSED---
Last 5 characters of installed product key: XXXXX (MAK Key out of seats)
---------------------------------------
SKU ID: dedfa23d-6ed1-45a6-85dc-63cae0546de6
LICENSE NAME: Office 16, Office16StandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT chael
LICENSE STATUS: ---UNLICENSED---
ERROR CODE: 0xC004F014
ERROR DESCRIPTION: The Software Licensing Service reported that the product key is not available.
---------------------------------------
---------------------------------------
---Exiting-----------------------------
I am so perplexed by this. KMS and MAK automatically switch places with their respective keys, even though I have no scripts/policies set to enforce this MAK key. This still occurs when I delete the MAK key from VAMT, I've added my KMS key to AD Activation but it says "The KMS host key used to create this AD activation object does not support any products that are capable of AD activation".
My License server works great with Windows 10 licensing using the GVLK key and AD activation. It seems my license server is available in DNS (and subsequent errors from MAK licensing show errors from license server)
C:Program FilesMicrosoft OfficeOffice16>nslookup -type=all _vlmcs._tcp
Server: dnsserver.peninsula.wednet.edu
Address: 10.0.0.x
_vlmcs._tcp.Peninsula.wednet.edu SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = licenseserver.peninsula.wednet.edu
licenseserver.peninsula.wednet.edu inteet address = 10.0.0.xx
I've ran slmgr /dlv all on my license server and can see my KMS key listed.
Name: Office 16, Office16KMSHostVL_KMS_Host edition
Description: Office 16, VOLUME_KMS chael
Activation ID: 98ebfe73-2084-4c97-932c-c0cd1643bea7
Application ID: 0ff1ce15-a989-479d-af46-f275c6370663
Extended PID: 06401-00206-437-112084-03-1033-9600.0000-0882016
Product Key Chael: Volume:CSVLK
Installation ID: 020865070204500731152076103234482290589666005651171436
Use License URL: https://activation.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=o14
Validation URL: http://go.microsoft.com/fwlink/?LinkID=187557
Partial Product Key: XXXXX (KMS Key from Microsoft)
License Status: Licensed
Remaining App rearm count: -1
Remaining SKU rearm count: -1
Trusted time: 8/4/2016 3:23:36 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: 46170
Failed requests received: 34101
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 11406
Requests with License Status Initial grace period: 313
Requests with License Status License expired or Hardware out of tolerance: 224
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 126
I'm hoping somebody has seen this issue, or knows where to find related issues online. I'm crossing my fingers that it is a simple issue that I have overlooked. If not, hopefully I'll figure it out and this will aid somebody in the future. If I need to post more details please Thank you.