none
KMS Host not accepting Win7 VL KMS key

    Question

  • I am having the same problem as some posted last year. 
    Here is my senario:
    We have had KMS running for the last two years without issues.
    KMS Server - Windows Server 2008 Standard , Service Pack 2, 32-bit OS

    Recently acquired our Win7 KMS key.
    Opened an elevated prompt on the KMS server and ran the typical
    slmgr -dli shows this:
    ----------
    Name: Windows Server(R), ServerStandard edition
    Description: Windows Operating System - Widnows Server(R),
    VOLUME_KMS_R2_B channel
    Partial Product Key: 123yz
    License Status: Licensed

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

    Key Management Service cumulative requests received from clients
       Total requests received: 6421
    -----------
    running  slmgr -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
    produces this:
    Run 'slui.exe 0x2a 0xC004F015' to display the error text.  Error: 0xC004F015

    running slui.exe 0x2a 0xC004F015
    produces this:
    The Software Licensing Service reported that the license is not installed.

    Please help me with this!

    Thanks
    pjkelly
    Friday, October 02, 2009 6:27 PM

Answers

All replies

  • Hi,

     

    Please refer to this article first:

     

    An update is available for Windows Vista and for Windows Server 2008 to extend KMS activation support for Windows 7 and for Windows Server 2008 R2

    http://support.microsoft.com/kb/968912/en-us

     

    Hope it helps.

     

    Tim Quan - MSFT

    Monday, October 05, 2009 6:05 AM
    Moderator
  • Hi,

     

    How are things going? I have not heard back from you in a few days and wanted to check on the status of the issue. Please let me know how things turned out.

     

    Tim Quan - MSFT

    • Marked as answer by pjkelly Wednesday, October 21, 2009 3:24 PM
    • Unmarked as answer by pjkelly Wednesday, October 21, 2009 3:24 PM
    Wednesday, October 07, 2009 1:53 AM
    Moderator
  • I ran into the same exact error message.  However, in my case I was simply looking at the wrong product key for the edition of windows I was deploying.  The error message just isn't very descriptive.
    Tuesday, January 12, 2010 10:33 PM