none
KMS Activation for Office 2010

    Question

  • We can't get KMS to activate Office 2010. There are at least 7 clients with Office 2010 installed and all of them report that the product needs to be activated. The event logs on all the the clients confirm that they have successfully issued an activation request to the KMS host (event ID 12288) and have received a response from the KMS host (event ID 12289).

    I checked the Volume Activation Technical Refernce Guide to help interpret the event log entries but am not finding very much useful information in those log entries.

    Is there a tool like slmgr for Win7 that will display information about Office 2010 on the KMS host? I would like to see where the request count sits - I suspect that the KMS host is not incrementing that value and thus the problem.

    I'm looking for any diagnostic tools or procedures that might shed some light on the problem. Have been searching the web for two days without much luck.

     

    Thursday, March 31, 2011 1:10 PM

Answers

  • PROBLEM SOLVED.

    Unlike Windows 7, the CMID for Office 2010 is created on the client machine when any Office application is launched the first time. When I built the customized installation for the Windows 7 LTI deployment (on the reference computer) I tested the Office 2010 installation by launching a couple of the Office apps.

    That action created the Office CMID on the reference computer and I went on my merry way and created my deployment image from that computer. The CMID then was the same for every machine to which the image was deployed. So, the KMS host thought it was the same client every time any of those machines hit the KMS host to attempt to activate Office 2010. Thus, the KMS host did not increment the counter.

    The moral to the story - when building the customized installation for deployment make sure no Office 2010 apps are launched before the image is captured.

    This process also served to correct a misconception on my part. For KMS volume activation, there are two different CMIDs - one for Windows and one for Office 2010. I thought a client machien ID (CMID) was unique to the client machine, not to the applications.

     

    • Proposed as answer by B. Meyer Thursday, March 31, 2011 8:08 PM
    • Marked as answer by TT-ICCSD Thursday, March 31, 2011 8:39 PM
    Thursday, March 31, 2011 7:14 PM

All replies

  • Have you installed the Office 2010 Host pack on the KMS server?

    Thursday, March 31, 2011 1:53 PM
  • slmgr remains the tools to view KMS host status for Office 2010. If the host is receiving the request, I doubt the counter is not being incremented. KMS is a simple, nearly foolproof service.

    Are you using VAMT? If not, you should be.


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Thursday, March 31, 2011 2:10 PM
  • Andrew - Yes (at least that's what my network guys said).

    Jason - slmgr on the KMS host shows details about Windows 7 but nothing about Office 2010.

    The Windows log on the client machines is also now showing the following event. Trying now to find something on the web that can translate this into a readable state.

    Log Name:      Application

    Source:        Office Software Protection Platform Service

    Date:          3/31/2011 8:45:40 AM

    Event ID:      1003

    Task Category: None

    Level:         Information

    Keywords:      Classic

    User:          N/A

    Computer:      [hidden]

    Description:

    The Software Protection service has completed licensing status check.

    Application Id=59a52881-a989-479d-af46-f275c6370663

    Licensing Status=

    1: 191301d3-a579-428c-b0c7-d7988500f9e3, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]

    2: 6f327760-8c5c-417c-9b61-836a98287e0c, 1, 1 [(0 [0xC004E003, 0, 0], [( 1 0xC004F056 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)( 1 0xC004F056 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)(?)(?)])(1 )(2 [0x00000000, 0, 0], [( 5 0xC004F009 30 0)( 5 0xC004F009 30 0)( 1 0x00000000 0 0 msft:rm/algorithm/flags/1.0 0x00000000 0)(?)(?)( 9 0x00000000 0xC004F056)])]

    3: fdf3ecb9-b56f-43b2-a9b8-1b48b6bae1a7, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]

      

    Thursday, March 31, 2011 2:22 PM
  • You can use the ospp.vbs script in the office 2010 folder to debug your issue with kms activation. Use an elevated command prompt.
    Thursday, March 31, 2011 2:23 PM
  • Thanks JFD7.

    I used ospp.vbs to decode the hex error that is being presented (0xC004F038) and it has confirmed that activation failed because "the count reported by your Key Management Service (KMS) is insufficient".

    So, the source of the problem is indeed the failure of the KMS server to increment the counter when receiving an activation request. Just gotta figure out why that's happening now. Anybody ever encounter this particular error situation with KMS?

     

    Thursday, March 31, 2011 2:45 PM
  • cscript slmgr.vbs /dlv will show you all KMS activation information, you just have to sift through it: http://blogs.technet.com/b/odsupport/archive/2010/06/01/office-2010-kms-installation-and-troubleshooting.aspx.
    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Thursday, March 31, 2011 2:59 PM
  • I thought so too, but in our case it shows just the Windows 7 stuff and it's a pretty short display. There isn't much there to sift through.

    However, if I run this one then I get the Office 2010 information:

    cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864

    I got that suggestion from here http://technet.microsoft.com/en-us/library/ee624355.aspx#section1

     

    Thursday, March 31, 2011 3:06 PM
  • PROBLEM SOLVED.

    Unlike Windows 7, the CMID for Office 2010 is created on the client machine when any Office application is launched the first time. When I built the customized installation for the Windows 7 LTI deployment (on the reference computer) I tested the Office 2010 installation by launching a couple of the Office apps.

    That action created the Office CMID on the reference computer and I went on my merry way and created my deployment image from that computer. The CMID then was the same for every machine to which the image was deployed. So, the KMS host thought it was the same client every time any of those machines hit the KMS host to attempt to activate Office 2010. Thus, the KMS host did not increment the counter.

    The moral to the story - when building the customized installation for deployment make sure no Office 2010 apps are launched before the image is captured.

    This process also served to correct a misconception on my part. For KMS volume activation, there are two different CMIDs - one for Windows and one for Office 2010. I thought a client machien ID (CMID) was unique to the client machine, not to the applications.

     

    • Proposed as answer by B. Meyer Thursday, March 31, 2011 8:08 PM
    • Marked as answer by TT-ICCSD Thursday, March 31, 2011 8:39 PM
    Thursday, March 31, 2011 7:14 PM
  • Also, Office 2010 KMS activation requires at least 5 activation requests before it will push out activations.

    Somewhat similarly, Windows 7 requires 25 requests.

    Thursday, March 31, 2011 8:13 PM
  • Hi,

    When you build your reference image with Office 2010, it is important to rearm the Office installation before capturing Windows 7:

    In command prompt, launch this  C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\ospprearm.exe.

    A message similar to the following displays if the operation succeeds: "Microsoft Office rearm successful."

    The path might be \Program Files (x86)\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform if you install a 32-bit edition of Office 2010 on a 64-bit edition of Windows.

    regards,


    Revue du Geek | Déployer Windows 7 | Améliorer les performances de Windows 7
    Friday, April 01, 2011 12:06 AM
  • slmgr remains the tools to view KMS host status for Office 2010. If the host is receiving the request, I doubt the counter is not being incremented. KMS is a simple, nearly foolproof service.

    Are you using VAMT? If not, you should be.


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys


    Jason - I do indeed want to use VAMT and in fact we are trying to get it running. But it reports complete information only for the computer on which it is installed. I can add computers from our domain but all I get is just the machine name. All other columns show <unknown>.

    The VAMT Configuration document says that in order for this to work VAMT has to have access to client computers by modifying the Windows firewall to allow WMI. In our environment the Windows firewall is turned off on all clients as well as on the KMS host, so I'm at a loss as to why this info isn't availaable in VAMT.

     

    Friday, April 01, 2011 1:18 PM
  • VAMT is a little bit of a tricky beast to get used to. Did you initiate a scan of the systems? VAMT has to connect to each system to query its status and retrieve information about it. It will not do this automatically; you have to manually intiate this action (sorry don't have it installed where I'm at so I can't tell you the exact steps). If you have done this, are you receiving any errors? Also, do you have the latest version of VAMT -- 2.0?
    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Friday, April 01, 2011 1:51 PM
  • Yes, I ran an Active Directory scan and used a filter to limit the output to just the collection of machines on which we have installed Windows 7 and Office 2010. We're just beginning the process of migrating from XP to 7 (as you could probably tell from the flood of posts I have made lately on this forum).

    VAMT successfully finds and lists all those clients (no errors), but the only column that contains any information for those machines is Computer Name. All other columns in all rows show <unavailable>.

    I am running VAMT 2.0.

     

    Friday, April 01, 2011 2:07 PM
  • The AD scan just finds them, it doesn't actually query them. You have to right-click the systems found and choose Update Status for this (you can multi-select also).
    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Friday, April 01, 2011 2:34 PM
  • Hi,

    When you build your reference image with Office 2010, it is important to rearm the Office installation before capturing Windows 7:

    In command prompt, launch this  C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\ospprearm.exe.

    A message similar to the following displays if the operation succeeds: "Microsoft Office rearm successful."

    The path might be \Program Files (x86)\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform if you install a 32-bit edition of Office 2010 on a 64-bit edition of Windows.

    regards,


    Revue du Geek | Déployer Windows 7 | Améliorer les performances de Windows 7


    Yannick - if I never launch any of the Office applications in my reference image before actually capturing the image is it still necessary to rearm it? I guess what I'm asking is, exactly when does Office get armed and what causes it to get armed?

     

     

    Friday, April 01, 2011 7:51 PM
  • Yannick - if I never launch any of the Office applications in my reference image before actually capturing the image is it still necessary to rearm it? I guess what I'm asking is, exactly when does Office get armed and what causes it to get armed?

    Yes, you have to do this before the capture even if you didn't launch Office.

    And after do not open an Office application or run ospp.vbs until you have captured the image. You can rearm 5 times, unless you activate Office 2010 by using a KMS host. If you run out of rearms, activating by using a KMS host lets you rearm one time.

    For the next time you could use a command line action in the TS for this.


    Revue du Geek | Déployer Windows 7 | Améliorer les performances de Windows 7
    Friday, April 01, 2011 8:08 PM
  • Yes, you have to do this before the capture even if you didn't launch Office.

    And after do not open an Office application or run ospp.vbs until you have captured the image. You can rearm 5 times, unless you activate Office 2010 by using a KMS host. If you run out of rearms, activating by using a KMS host lets you rearm one time.

    For the next time you could use a command line action in the TS for this.


    Revue du Geek | Déployer Windows 7 | Améliorer les performances de Windows 7

    Thanks for the information, much appreciated. This really creates a problem for us because history has shown that, in our operation, we have to update images quite frequently. It would not be unusual for us to have to modify and recapture an image more than 5 times, and if I understand correctly we can no longer do that because eventually the Office installation in the image would become unusable.

    When we do hit that problem, do you know if uninstalling and reinstalling Office in the image would give us another 5 rearms?

     

    Friday, April 01, 2011 8:16 PM
  • When we do hit that problem, do you know if uninstalling and reinstalling Office in the image would give us another 5 rearms?
    I will ping some MS guys for this one. But I don't think so.
    Revue du Geek | Déployer Windows 7 | Améliorer les performances de Windows 7
    Friday, April 01, 2011 8:20 PM
  • The answer is Yes. I tested it.

     

    Thursday, April 07, 2011 7:22 PM
  • Thursday, April 07, 2011 7:25 PM