locked
Activating Office 2010 using KMS RRS feed

  • Question

  • Hello

    I am having a problem with activating Office 2010 using the KMS. We are using a Server 2008 R2 for the KMS host, our clients are Win7, it is published in DNS correctly and the clients are requesting activation. Below is a screenshoot from the server. The 2 that are showing licensed are two that I manually ran the ospp.vbs /act on. This shows they are talking to the kms host. They just will not activate via the host. Any suggestions would be greatly appreciated.


    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: 55041-00096-199-127681-03-1033-7601.0000-0792012
    Installation ID: 001825849592802441841335857475402780819673354324279256
    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: CP7QW
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 3/20/2012 9:39:33 AM

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

    Key Management Service cumulative requests received from clients
        Total requests received: 14
        Failed requests received: 0
        Requests with License Status Unlicensed: 0
        Requests with License Status Licensed: 2
        Requests with License Status Initial grace period: 12
        Requests with License Status License expired or Hardware out of tolerance:

        Requests with License Status Non-genuine grace period: 0
        Requests with License Status Notification: 0

    • Edited by Kat7881 Tuesday, March 20, 2012 1:49 PM
    Tuesday, March 20, 2012 1:49 PM

Answers

  • Hi Kathy,
    the section titled "Key Management Service cumulative requests received from clients" will accumulate over time as clients phone-home to the KMS and are activated and also re-activated. So a single client over the period of a couple of months will tick over these counters several times. Clients in different licensing states will tick over the various counters. If the KMShost server, or the KMS windows service, is restarted, I expect the "Key Management Service cumulative requests received from clients" counters will reset, although the KMS itself will retain its own activated status (subject to the minimum threshold).
    The KMS "current count" is the threshold value, and it stops counting at twice the threshold. So for Office it will count up to 10 and not count beyond that. The KMS will begin issuing activations at a count of 5 (the threshold minimum), and it will cease issuing activations if the current count drops below 5.

    2 days to activate via KMS is unusual from my experience (unless there is s threshold not met) all my clients activate immediately on the first attempt.

    you need to examine the KMS event viewer logs on the server, and correlate this with the event logs on the clients, to see what's going on. This link explains how to interpret the events: http://technet.microsoft.com/en-us/library/ee939272.aspx

    I would look for the following things in the logs:
    a) did the client attempt to activate in the expected timeframe?
    b) did the client resolve/locate the KMS server correctly?
    c) did the KMShost receive the activation request?
    d) did the KMShost issue an activation or refuse/reject the client?
    e) did the client receive the activation (or refusal)?
    f) did the client correctly process the KMShost response?

    You can always raise a case with MS CSS (via Premier if you have that, or use your SAB points if you have those)


    Don


    • Edited by DonPick Tuesday, April 3, 2012 9:14 PM
    • Marked as answer by Kat7881 Wednesday, April 4, 2012 8:36 PM
    Tuesday, April 3, 2012 9:13 PM

All replies

  • Hi Kathy,

    what events/errors are displayed (onscreen) & logged (event logs) on the client when you fire ospp.vbs /act ?

    You will likely need to confirm that there are no duplicated CMID's (as these will cause exactly this issue)
    http://technet.microsoft.com/en-us/library/ee624355.aspx

    The next link is mainly referring to Windows activation via KMS but the same principles apply for Office:
    http://technet.microsoft.com/en-us/library/ee939272.aspx

    For Office, on the client, you may need to use a combination of slmgr.vbs and ospp.vbs, to get the complete picture.
    Your KMShost looks ok (active etc) as it has activated 6 unique clients (which is above the threshold of 5)


    Don



    • Edited by DonPick Wednesday, March 21, 2012 8:19 PM
    Wednesday, March 21, 2012 8:14 PM
  • There are no errors anywhere. It looks as if they are licensing but KMS is not reporting the fact until I manually run the /act command.

    Status of Machine before and after running the ospp.vbs /act. It was not counted on the KMS host until running the /act command.


    C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /dstatus
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    ---Processing--------------------------
    ---------------------------------------
    SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
    LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition
    LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
    LICENSE STATUS:  ---LICENSED---
    ERROR CODE: 0 as licensed
    Last 5 characters of installed product key: H3GVB
    REMAINING GRACE: 177 days  (255100 minute(s) before expiring)
    ---------------------------------------
    ---------------------------------------
    ---Exiting-----------------------------

    C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /act
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    ---Processing--------------------------
    ---------------------------------------
    Installed product key detected - attempting to activate the following product:
    SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
    LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition
    LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
    Last 5 characters of installed product key: H3GVB
    <Product activation successful>
    ---------------------------------------
    ---------------------------------------
    ---Exiting-----------------------------

    C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /dstatus
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    ---Processing--------------------------
    ---------------------------------------
    SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
    LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition
    LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
    LICENSE STATUS:  ---LICENSED---
    ERROR CODE: 0 as licensed
    Last 5 characters of installed product key: H3GVB
    REMAINING GRACE: 180 days  (259200 minute(s) before expiring)
    ---------------------------------------
    ---------------------------------------
    ---Exiting-----------------------------

    Machine that is not counted on KMS Host as being licensed and the /act command was not ran on.

    C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /dstatus
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    ---Processing--------------------------
    ---------------------------------------
    SKU ID: 6f327760-8c5c-417c-9b61-836a98287e0c
    LICENSE NAME: Office 14, OfficeProPlus-KMS_Client edition
    LICENSE DESCRIPTION: Office 14, VOLUME_KMSCLIENT channel
    LICENSE STATUS:  ---LICENSED---
    ERROR CODE: 0 as licensed
    Last 5 characters of installed product key: H3GVB
    REMAINING GRACE: 177 days  (255100 minute(s) before expiring)
    ---------------------------------------
    ---------------------------------------
    ---Exiting-----------------------------

    Thanks in advance for all your help.

    Kat 


    Kathy Wingfield

    Thursday, March 22, 2012 2:40 PM
  • Also no duplicate CMID's.

    Thanks

    Kathy


    Kathy Wingfield

    Thursday, March 22, 2012 7:35 PM
  • Machine that is not counted on KMS Host as being licensed and the /act command was not ran on.

    C:\Program Files\Microsoft Office\Office14>cscript ospp.vbs /dstatus
    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    ---Processing--------------------------
    ---------------------------------------
    LICENSE STATUS:  ---LICENSED---
    ERROR CODE: 0 as licensed
    REMAINING GRACE: 177 days  (255100 minute(s) before expiring)

    Kat,

    this machine was activated 3 days ago (180-177=3). there is no unlicensed aspect to this machine.

    When you say it's not being counted on the KMShost - which number are you referring to/how are you concluding this?
    You said there are no errors, but what do the event logs on the client reveal?
    Any activation refusals? Or no attempt recorded in the client event log? Or no request recorded in the KMShost event log?

    Or, is it that you are expecting the KMShost counters to logically increment once for each new client activation?
    (that's not how it works...)

    The KMShost tells you this:

    Key Management Service cumulative requests received from clients
    .....
    These numbers are not 1 for 1 (they are not # of clients, they are # of requests, and a single client makes multiple requests)


    Don


    • Edited by DonPick Thursday, March 22, 2012 8:54 PM
    Thursday, March 22, 2012 8:50 PM
  • Sorry Don I have been out of town.

    Key Management Service cumulative requests received from clients
        Total requests received: 14
        Failed requests received: 0
        Requests with License Status Unlicensed: 0
        Requests with License Status Licensed: 2
        Requests with License Status Initial grace period: 12
        Requests with License Status License expired or Hardware out of tolerance:

        Requests with License Status Non-genuine grace period: 0
        Requests with License Status Notification: 0

    When I manually activated Microsoft office 2010 the Requests with License Status Licensed increased. I guess I was assuming that it would increase with each machine that licensed. It took 2 days for them to license via KMS. Is this normal? Does the license count increase?

    Thanks

    Kathy


    Kathy Wingfield

    Tuesday, April 3, 2012 2:53 PM
  • Hi Kathy,
    the section titled "Key Management Service cumulative requests received from clients" will accumulate over time as clients phone-home to the KMS and are activated and also re-activated. So a single client over the period of a couple of months will tick over these counters several times. Clients in different licensing states will tick over the various counters. If the KMShost server, or the KMS windows service, is restarted, I expect the "Key Management Service cumulative requests received from clients" counters will reset, although the KMS itself will retain its own activated status (subject to the minimum threshold).
    The KMS "current count" is the threshold value, and it stops counting at twice the threshold. So for Office it will count up to 10 and not count beyond that. The KMS will begin issuing activations at a count of 5 (the threshold minimum), and it will cease issuing activations if the current count drops below 5.

    2 days to activate via KMS is unusual from my experience (unless there is s threshold not met) all my clients activate immediately on the first attempt.

    you need to examine the KMS event viewer logs on the server, and correlate this with the event logs on the clients, to see what's going on. This link explains how to interpret the events: http://technet.microsoft.com/en-us/library/ee939272.aspx

    I would look for the following things in the logs:
    a) did the client attempt to activate in the expected timeframe?
    b) did the client resolve/locate the KMS server correctly?
    c) did the KMShost receive the activation request?
    d) did the KMShost issue an activation or refuse/reject the client?
    e) did the client receive the activation (or refusal)?
    f) did the client correctly process the KMShost response?

    You can always raise a case with MS CSS (via Premier if you have that, or use your SAB points if you have those)


    Don


    • Edited by DonPick Tuesday, April 3, 2012 9:14 PM
    • Marked as answer by Kat7881 Wednesday, April 4, 2012 8:36 PM
    Tuesday, April 3, 2012 9:13 PM
  • Thank You for all of your help. This is a new experience for me and at times got to be very frustrating.

    Kathy


    Kathy Wingfield

    Wednesday, April 4, 2012 8:37 PM