Kms keys

Hello,
We have a customer that has installed a kms host key on 6 servers, so now they have 6 KMS hosts running. They have contacted us because they realize they have done something wrong. I am new to kms and have been reading on technet for serveral hours now, but still some thing are unclear to me
If I understand correctly deployment of kms should be simple and straightforward
The easiest way (read to support the most kms clients) is to install a 2008 R2 server with a 2008 R2 host key. This will support vista, 7, 2003, 2008 and 2008R2 kms systems and enable them to activate. Is this correct ?
I install a windows vista machine or windows 7 machine using a volume license product key. After installation the activation will occur automatically against the kms host and no extra manual steps are needed. I do not need to install/add a kms client key on the vista or windows 7 machine. Is this correct ?
Can i deactivate systems that were actived directly (before deployment of the kms host) with Microsoft and reactivate them with the kms host ?
s it possible to uninstall a kms host and thus making it a regular kms client (to reduce the number of kms hosts from 6 to 2) ?
Thanks in advance
Kind Regards
Stijn Delen

Regarding this question:
Question 1: "I install a windows vista machine or windows 7 machine using a volume license product key. After installation the activation will occur automatically against the kms host and no extra manual steps are needed. I do not need to
install/add a kms client key on the vista or windows 7 machine. Is this correct ?"
Answer: Yes, if your KMS host is set up properly, no extra steps are needed, they will activate automatically.
Question 2: "Can i deactivate systems that were activated directly (before deployment of the kms host) with Microsoft and reactivate them with the kms host ?"
Answer: You should not need to deactivate any systems. If they were activated with a MAK key, they're good forever...whether the KMS overrides the MAK, I don't know, but they can exist together peacefully. We have a mix in our environment of pcs we've
deployed using MAK keys (when we were first getting started) and pcs contacting our KMS server (pcs we've deployed more recently).

Similar Messages

How do I install multiple KMS keys on one server?

I currently am working at Phelps County Regional Medical Center in Rolla, MO and my question is: How do I install multiple KMS keys onto one server? This is very urgent and I have the KMS activating Windows 7 but, I also need all my Office keys, Windows
8, and Windows 8.1 to be activated via KMS. the current KMS is a Windows Server 2008 R2 server. Please help me out and thank you for your time! :)

you need to apply the following update (http://support.microsoft.com/kb/2885698)to your KMS server so you can license up to Windows 8.1. From there your key for 8.1/2012R2 will license everything
downwards and then you can also install your Office KMS key without issue. If its Office 2013 then you need to download the files here (http://www.microsoft.com/en-us/download/details.aspx?id=35584)
Be kind and Mark as Answer if I helped.

Adding a Windows 8/2012 KMS key to a 2008 R2 KMS server.

Hello,
I have my KMS keys for Windows 8/2012. Can these be added to a 2008 R2 KMS server or is there a document that details this?
Shawn

yes, There is a separate hotfix for Win 8.1 and 2012 R2.
kb#2885698
I have been successful install the hotfix, rebooting, and then adding the 2012 r2 key. I am still unsuccessful adding the windows 8/8.1 keys. Receiving the error:
kb#2752119
which tells me that it doesn't like the hotfix... but you can give it a shot!
Other forums say that that the 2012 r2 key will activation windows 8.1, but i am still unsuccessful in activating my workstation.
The WS2012R2 KMShost product key *will* successfully issue activations for Win8.1, but note that you must have 25 KMSclients communicating to a KMShost, for a "Client" OS edition to KMS-activate.
You cannot install the Win8.1 KMShost product key on a Windows Server OS - you must use the Windows Server KMShost product key if your KMShost OS is Windows Server.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Install Windows 2008 R2 KMS Key Error "0xC004F050 The software licensing service reported that the product key is invalid"

My KMS server is running on Windows Server 2012 R2 and activated by Server 2012 KMS Key.
I would like to use the KMS server to activate many Windows 2008 R2 server, however, Error message "0xC004F050 The software licensing service reported that the product key is invalid" is appear when adding Windows Server 2008R2 KMS Key. The Windows
Server 2008 R2 KMS key is confirmed and validated by Microsoft Telephone service.
Command used:
slmgr /ipk <Windows Server 2008 R2 KMS Key>
Anyone can help? thanks.

Hi Samson,
Based on my research, we need to choose associated KMS key based on the highest product being deployed in the product grouping hierarchy.
To choose the right Volume License key, please refer to this article:
How to Choose the Right Volume License Key for Windows
Please type the cmd "slmgr /dlv" on KMS Host and check if it has been activated successfully.
After configure KMS host, By default these KMS client computers will query DNS and locate your KMS host and activate
KMS Client Setup Keys
To reset computers to be KMS clients type the following at elevated command prompt:
Slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is the generic VL key from the following link.
https://technet.microsoft.com/en-us/library/jj612867.aspx
For more detailed information to activate KMS client, please refer to the article below:
Installing KMS Hosts
Configuring KMS Clients
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How do I update my Office 2010 KMS key?

I renewed our EES contract with Microsoft and in turn got a new Office 2010 key. Our current clients are saying I have 30 days to activate so I would like to update the KMS key on the server with the new one so they'll pick it up. I haven't found any solid
instructions anywhere so am posting a new question. How do I update the KMS key for Office 2010? What commands do I need to run?
Thanks in advance for any help.

Thanks for the reply. That got me a little further. I updated my EES agreement this summer and got new keys, so thought maybe that was the issue with Office giving me the "This copy of Microsoft Office is not activated." when launching any Office
product. I installed and activated the new key now but am still getting the same error in Office. The error code it gives me is 0xc004f074. Looking into that error it looks like a KMS issue. These were activating fine last year and I haven't made any changes
except just updating the key today, but it was doing this before that.
Here is what was returned before updating the key:
Name: Microsoft Office 2010, KMSHost edition
Description: Microsoft Office 2010 KMS, VOLUME_KMS channel
Activation ID:
Application ID:
Extended PID:
Installation ID:
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: (last 5 of old key)
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 8/14/2014 12:29:28 PM
Key Management Service is enabled on this machine
Current count: 4
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 21779
Failed requests received: 3
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 19665
Requests with License Status Initial grace period: 304
Requests with License Status License expired or Hardware out of tolerance: 1783
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 24
Here is what was returned after:
Name: Microsoft Office 2010, KMSHost edition
Description: Microsoft Office 2010 KMS, VOLUME_KMS channel
Activation ID:
Application ID:
Extended PID:
Installation ID:
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: (last 5 of new key)
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 8/14/2014 12:53:57 PM
Key Management Service is enabled on this machine
Current count: 4
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 21785
Failed requests received: 9
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 19665
Requests with License Status Initial grace period: 304
Requests with License Status License expired or Hardware out of tolerance: 1783
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 24
I appreciate your willingness to help me with this issue and if you can offer any further insight I would greatly appreciate it.
Thanks!
EDIT: I removed all of the ID numbers as I don't know if they mean anything to anyone else or not.

Multiple KMS keys for same product (i.e. Office 2013)

So on this domain I support, they have a KMS host which is set up correctly for Office 2013 and there is no problem with it, but recently additional licenses for Office 2013 were purchased.
On the volume licensing website, it shows Office 2013 and the number of licenses has increased as a result of the new purchase, so that is correct as well. Under license keys though there is another MAK and KMS key.
What do I do with the new KMS key? Anything? Clearly Microsoft have got the correct licensing total. Never been in a situation before where licenses were purchased incrementally like this.

"slmgr.vbs /dlv all" can also be used, this will display all product keys
At a guess, MS have issued a new set of VL keys for the new/additional purchase, which I'd agree is a little unexpected/unnecessary, given you already have these products in your agreement.
It's probably some kind of automatic action that doesn't take into account a previous purchase in the same agreement period.
Yes, KMS is fiddly, especially the bolt-on aspects of Office. MS have tackled that, with the new ADBA approach, which makes things a lot simpler to manage via a builtin GUI in WS2012.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Cannot install KMS key in VAMT for KMS clients

Dear Sir / Madam,
I have some technical problems about setup the KMS host and KMS clients.
OS of the KMS host: Windows Server 2012 Standard
OS of the KMS client: Windows 7 Professional (32bit)
Question 1:
I want to use KMS host server to handle KMS keys and activations for KMS clients. Which type of KMS key need to install in KMS host ?
Would I need to install Windows 7 Professional KMS key or
Windows Server 2012 Standard KMS key in the Volume Activation Management Tool (VAMT) ?
Question 2:
I found that I cannot installed the Windows 7 Professional KMS key in the Volume Activation Management Tool (VAMT), it pop-up an error message said that the KMS key invalid. How can I fix the problem?
Thanks for your help!

Hi Siu Wai,
You can also follow these steps:
1. Select a computer that you want to be your KMS host:
2. Install Windows Server.
3. At cmd prompt type the following:
Slmgr.vbs /ipk <your KMS KEY from MVLS>
The /ipk installs your MVLS key. Note if you need to change your key. For example change from a KMS_B to KMS_C key you must restart the Software Licensing service.
4. At cmd prompt type the following:
Slmgr.vbs /ato
The /ato activates the KMS host with Microsoft. You must activate the KMS host.
5. Restart the Software Licensing service.
6. Install the KMS client computers by using volume license media. You should not be prompted for cdkey during installation
7. By default these KMS client computers will query DNS and locate your KMS host and activate
KMS Client Setup Keys
To reset computers to be KMS clients type the following at elevated command prompt:
Slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is the generic VL key from the following link.
http://technet.microsoft.com/en-us/library/ee355153.aspx#EFAA
Refer to:
Is it possibile to host multiple KMS Keys
on a single KMS server?
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Differnce Between MAK key & KMS key

I need the difference between MAK key & KMS key under volume licensing/

Hi
MAK allows you to activate multiple machines over the Internet with that one key, the total is dependant on the licensing program with which you acquired the product key.
KMS activation allows you to activate your machine internally against a KMS host which you set up on your internal network.
Ref: http://louwrentius.com/understanding-windows-kms-and-mak-volume-license-activation.html
http://social.technet.microsoft.com/Forums/windowsserver/en-US/a74c0e24-d97b-41ce-897c-18afa2284b6f/kms-vs-mac-activation
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How do clients get KMS keys

We are trying to understand how the KMS Works. We deploy our PC using sccm 2012 R2 and we have KMS server installed with valid keys. After the installation of the clients, Windows or Office are not activated, we go to the KMS server, discover the clients
and them Activate them manually, from that, all are fine and everytime the clients come to the KMS server to Update the keys without a problem. My question was that, why do newly installed clients (using sccm) not just come to the KMS server and activate Windows
and Office products ? Or is it the way it works, we first have to discover the clients and Update them manually using KMS Volume Activation Manager Tool 3.1 ? May be we are missing something
The KMS server is registered in the DNS.

Hi,
Usually, KMS clients query SRV record to locate KMS host. We can manually add SRV record or configure KMS host to publish itself. I think SRV record is not created properly
in DNS.
This article tells how to configure DNS for KMS host.
Configuring DNS
http://technet.microsoft.com/en-us/library/ff793405.aspx
Hope this helps.

How to activate Windows 8.1 on a Windows 2008 R2 KMS server when I don't have Windows 2012 R2 kms host key

I only have windows 8.1 kms host key but I can't add a client OS kms key to Windows 2008 R2 kms server. And I don't have Windows 2012 R2 license either. Is there any way I can activate Windows 8.1 using my existing kms server? Thanks.

I would like a yes no clarification answer. So does this mean that EVEN WITH THE PATCH. My Server 2012 Standard edition that currently hosts KMS VA for clients running Win7, Win 8, Office15, Server 2008, Server 2012. Will not be able to host windows 8.1?
I will have to install 8.1 and use as a host?
if you have a KMShost product key for WS2012R2, you can patch a down=level Server and be fine.
(the OP didn't renew SA or otherwise has no KMShost pkey for WS2012R2)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)
I'm having similar issues and have a similar question that doesn't seem to be answered:
My KMS server is Windows 2008 R2 (Also is my domain controller). I want to activate Windows 2012 R2 and Windows 8.1 machines off this KMS server. I can install the 2012 R2 key just fine but receive error 0xC004F015 (The Software Licensing Service reported
that the license is not installed) when I try to install my 8.1 KMS key.
What I'm gathering from this thread is that I have to set up a Windows 8.1 host and set it up to be a KMS server exclusively for activating Windows 8.1. Is this correct? If so, Microsoft needs to fix that. I have a SERVER for activations for a reason: it
is a server, not a client. If I am mis-understanding, how do I get my Windows 2008 R2 server to accept the Windows 8.1 KMS key for activating 8.1 clients?
Thanks!
You don't need Windows 8.1 KMS key. Your 2012 R2 KMS key will be able to activate your Windows 8.1 machines. So your current set up is fine, no need to set up another Windows 8.1 KMS host.
My problem is I don't have 2012 R2 KMS key as I didn't buy any Windows 2012 R2 license. So I can't use 2012 R2 KMS key to activate my Windows 8.1.
Oh that's interesting. I guess I need to play around more because my 8.1 test machine isn't activating. I'll start a new thread for that if needed. Sorry for the confusion.

Multiple KMS host keys

I have installed Windows Server 2012 R2 with Volume Activation Services service role.
I would like to install several KMS keys on this server (keys for windows 8.1, windows 8, windows 7, server 2012 R2, server 2012, server 2008, Office 2013, Office 2010,...).
Will that work correctly ?
thanks..

I have installed Windows Server 2012 R2 with Volume Activation Services service role.
I would like to install several KMS keys on this server (keys for windows 8.1,8,7, server 2012 R2, 2012,2008, Office 2013, Office 2010,...).
Will that work correctly ?
thanks..
You cannot install more than a single Windows product key on a system. You must choose the "highest" product/version KMShost pkey.
You must install any needed patches/updates that are pre-requisite, then install that Windows pkey.
Windows KMShost pkeys will activate all KMSclients at the same product/version *and* below.
For Office KMShost, you must install the relevant patch/update for each Office KMS pack, and also install each Office KMShost pkey.
This wiki article I wrote may be helpful:
http://social.technet.microsoft.com/wiki/contents/articles/22510.volume-activation-kms-mak-adba-avma.aspx
If your KMShost machine is WS2012R2, and you want to issue activations for WS2012R2 and all possible KMSclients (Windows KMSclients
and Office KMSclients):
Install the WS2012R2 KMShost pkey (no patches/updates are needed, because WS2012R2 is the latest release).
Install the Office2010 KMShost patch/update/pack, and, the Office2010 KMShost pkey.
Install the Office2013 KMShost patch/update/pack, and, the Office20103 KMShost pkey.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

KMS: activating 2008 R2 key disables 2012 key & vice versa

In my lab network, doing a "slmgr.vbs /dlv All" command, my Server 2008 R2 KMS entry shows "Unlicensed" and installation ID is blank. Using the /ipk switch, I then enter in our VLSC 2008 R2 kms key, & then activate
via phone with a provided confirmation ID (with the /ATP switch), and it then shows Licensed and shows an installation ID, but then the Server 2012 R2 KMS entry loses it's installation ID and shows "Unlicensed" (where before it showed
fine). If I then license 2012 R2 , the 2008 R2 entry shows as "Unlicensed" again and has a blank installation ID again. Maddening! The KMS server itself is 2008 R2 by the way. (and is an exact mirror
of our production KMS server which is working perfectly fine). The production and lab networks are isolated from each other.

Hi dilbert2013,
The active and license issue we can call the telephone to active center, they will give the detail and official support answer. In forum we can
not determine what key type you are using or whether the key is valid or whether the key has locked. If you are using OEM system you can ask your OEM vendor for the active help. You can get communication way from following web site:
Existing Customers
Product Activation and Key Information
http://www.microsoft.com/licensing/activation/existing-customers/product-activation.aspx
With KMS activation your organization must have at least five (5) computers to activate servers running Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 and
at least twenty-five (25) computers to activate client systems running Windows Vista, Windows 7, or Windows 8,please confirm your environment meet the requirement.
The related KB:
Frequently Asked Questions About Volume License Keys
http://www.microsoft.com/licensing/existing-customers/product-activation-faq.aspx
KMS Client Setup Keys for Volume Activation
https://technet.microsoft.com/en-us/library/dn502535.aspx?f=255&MSPPError=-2147217396
I’m glad to be of help to you!

Server 2012r2 KMS host will not accept any keys except that for Server 2012

I am attempting to upgrade our infrastructure to server 2012r2 from 2008r2. I've have run into issues with the KMS volume activation for our clients.
I've installed the Volume Activation Services Role and added a 2012r2 KMS key fine. Everything looks to be setup OK in DNS etc. However when I try and install additional KMS keys for Office 2010/13 Windows 7/8 the wizard tells me the key is invalid.
"Invalid product key or license mismatch"
I've tried installing the Key Host management hot fixes but these just report not for this operating system. I guess am I am missing something or misunderstanding but what?
Any help appreciated, I don't want to have to leave the 2008r2 running just for licensing.

OK worked it out.......
The 2012 key will activate windows 7/8 etc
Office 2010 needed this update to the server
http://www.microsoft.com/en-us/download/confirmation.aspx?id=25095
Office 2013 needs this update
http://www.microsoft.com/en-us/download/details.aspx?id=35584
All working now.......

Adding MS Project 2013 key to KMS server

Hello,
We just recently got a KMS key for MS project, and when I attempted to add the key to the KMS server, it causes the Office Professional Plus 2013 key to become unlicensed. I understand Project is an office product, and I have an active KMS key for
Office Professional Plus 2013, does this mean that key is what will be used to activate Project?
Thank You,
Thad

Hi Thad,
Please see the similar thread and Mr. Don has explained:
https://social.technet.microsoft.com/forums/office/en-US/d9fc307f-cbab-45c9-9fd4-e8a728fab308/installing-visio-2013-kms-key-on-kms-server
I copied here:
====
when I login to VLSC, I don't have different KMS pkeys for Office vs. Visio vs. Project.
they are named "Office 2010 Suites and Apps [KMS]" and "Office 2013 Suites and Apps [KMS]"
Depending on how you search or navigate within VLSC, there might appear to be KMS key for each suite/product, but you should find that the Office one is the same pkey as Visio and also Project.
Every time I've ever installed a KMS (I have done quite a few), the Office KMS will happily activate Office Std, Office ProPlus, Visio Std/Pro/Prem, Project Std/Pro.
(actually it's really easy to activate Visio Prem, since Prem is the default for the VL package of Visio. which is a problem if the customer is only licensed for a lesser edition of Visio.....)
====
Then we can use: slmgr.vbs /dli all
and also check the event logs on your KMShost, to see what it's getting and what it's giving out
Project 2013 uses the same activation ID as the matching Office suite, so if Project 2013 is not activating then Office 2013 would also be busted.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Activating MS Office 2013 ProPlus via KMS running on the same server

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Windows Script Host
Software licensing service version: 6.1.7601.17946
Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
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: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2015 10:00:12 AM
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
OK
Output of cscript ospp.vbs /dstatus
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004f00c
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c
Last 5 characters of installed product key: GVGXT
DNS auto-discovery: KMS name not available
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---Exiting-----------------------------

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Windows Script Host
Software licensing service version: 6.1.7601.17946
Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
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: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2015 10:00:12 AM
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
OK
Output of cscript ospp.vbs /dstatus
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004f00c
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c
Last 5 characters of installed product key: GVGXT
DNS auto-discovery: KMS name not available
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---Exiting-----------------------------

Kms keys

Similar Messages

Maybe you are looking for