none
KMS client activation failed, but got server response? RRS feed

  • Question

  • I've been using KMS for several years. Generally there are no problems with KMS, but I have a single machine that is refusing to activate, and I cannot determine why. I've been doing extensive web searching but I'm not finding anything useful.

    Windows 7 Pro client is using the Windows 7 Pro KMS client key GPDD4 as usual.

    KMS Server is in Windows 2008 R2

    The event log says the client is getting a response from KMS server (see below).

    ============================

    Server: slmgr /dlv

    Name: Windows Server(R), ServerStandard edition
    Description: Windows Operating System - Windows Server(R), VOLUME_KMS_R2_B channel
    Partial Product Key: 7GCM2
    License Status: Licensed

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

    Key Management Service cumulative requests received from clients
        Total requests received: 444
        Failed requests received: 297
        Requests with License Status Unlicensed: 0
        Requests with License Status Licensed: 86
        Requests with License Status Initial grace period: 12
        Requests with License Status License expired or Hardware out of tolerance: 2
        Requests with License Status Non-genuine grace period: 0
        Requests with License Status Notification: 47

    ===============================

    Client ability to find KMS Server: 

    C:\Users\foo>nslookup -type=srv _vlmcs._tcp
    Server:  UnKnown
    Address:  172.20.0.8

    _vlmcs._tcp.XXXXXXXXXXXX        SRV service location:
              priority       = 0
              weight         = 0
              port           = 1688
              svr hostname   = dc3.XXXXXXXXXXX
    dc3.XXXXXXXXX        internet address = 172.20.0.11

    ===============================

    Client: slmgr /dlv

    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Software licensing service version: 6.1.7601.17514

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: b92e9980-b9d5-4821-9c94-140f632f6312
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00170-868-000000-03-1033-7601.0000-2092014
    Installation ID: 011751536521019726056115618440708701492313365893152065
    Partial Product Key: GPDD4
    License Status: Initial grace period
    Time remaining: 43200 minute(s) (30 day(s))
    Remaining Windows rearm count: 1
    Trusted time: 7/28/2014 9:36:41 AM
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

    =========================

    Client:    slmgr /ato

    Microsoft (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Activating Windows(R) 7, Professional edition (b92e9980-b9d5-4821-9c94-140f632f6312) ...
    Error: Product activation failed.

    =========================

    Client: Application Event log

    Security-SPP Event ID 12288

    The client has sent an activation request to the key management service machine.
    Info:
    0x00000000, 0x00000000, dc3.XXXXXXXXXX:1688, 637b796e-5348-4ce1-b0b5-4d750e9d471e, 2014/07/28 14:43, 0, 2, 43200, b92e9980-b9d5-4821-9c94-140f632f6312, 25

    ---------------------------

    Security-SPP Event ID 12289

    The client has processed an activation response from the key management service machine.
    Info:
    0x00000000, 0x00000000, 1, 0, 50, 120, 10080, 2014/07/28 14:43

    --------------------------

    Security-SPP Event ID 1033

    These policies are being excluded since they are only defined with override-only attribute.
    Policy Names=(IIS-W3SVC-MaxConcurrentRequests) (Microsoft.Windows.Smc-Enabled) (Shell-InBoxGames-FreeCell-EnableGame) (Shell-InBoxGames-Hearts-EnableGame) (Shell-InBoxGames-Minesweeper-EnableGame) (Shell-InBoxGames-PurblePlace-EnableGame) (Shell-InBoxGames-Shanghai-EnableGame) (Shell-InBoxGames-Solitaire-EnableGame) (Shell-InBoxGames-SpiderSolitaire-EnableGame) (Shell-MultiplayerInboxGames-Backgammon-EnableGame) (Shell-MultiplayerInboxGames-Checkers-EnableGame) (Shell-MultiplayerInboxGames-Spades-EnableGame) (Shell-PremiumInBoxGames-Chess-EnableGame) (Telnet-Client-EnableTelnetClient) (Telnet-Server-EnableTelnetServer) (TiffIFilterLicensing-EnableTiffIFilter) (WindowsAnytimeUpgrade-CanUpgrade) 
    App Id=55c92734-d682-4d71-983e-d6ec3f16059f
    Sku Id=b92e9980-b9d5-4821-9c94-140f632f6312

    -------------------------

    Security-SPP Event ID 1003

    The Software Protection service has completed licensing status check.
    Application Id=55c92734-d682-4d71-983e-d6ec3f16059f
    Licensing Status=
    1: 4de78642-0f7f-4b61-9392-8add86d70ae8, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    2: 50e329f7-a5fa-46b2-85fd-f224e5da7764, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    3: 5a79ecd8-d33f-406c-a619-7785899b5d59, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    4: 770bc271-8dc1-467d-b574-73cbacbeccd1, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    5: 90a61a0d-0b76-4bf1-a8b8-89061855a4c9, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    6: 92f9d22a-65f5-49a7-90fe-06491b4fc379, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    7: 9abf5984-9c16-46f2-ad1e-7fe15931a8dd, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    8: 9ccffaf9-86a2-414e-b031-b2f777720e90, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    9: b92e9980-b9d5-4821-9c94-140f632f6312, 1, 0 [(0 [0xC004E003, 0, 0], [( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)(?)(?)])(1 )(2 [0x00000000, 0, 1], [(?)( 5 0x00000000 30 43200)( 1 0x00000000 0 0 msft:rm/algorithm/flags/1.0 0x00000000 0)(?)(?)(?)])]
    10: c1027486-8ae8-4633-9cf9-9658ed80504d, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    11: c1e88de3-96c4-4563-ad7d-775f65b1e670, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    12: c33001fc-5e9c-4f27-8c05-e0154adb0db4, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    13: cf3c5b35-35ff-4c95-9bbd-a188e47ad14c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    14: cff07cac-7534-4cc3-b3f3-99e1a0aa3c20, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    15: d188820a-cb63-4bad-a9a2-40b843ee23b7, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    16: d8e04254-f9a5-4729-ae86-886de6aa907c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    17: da22eadd-46dc-4056-a287-f5041c852470, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    18: e120e868-3df2-464a-95a0-b52fa5ada4bf, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    19: e838d943-63ed-4a0b-9fb1-47152908acc9, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    20: 4a8149bb-7d61-49f4-8822-82c7bf88d64b, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
    21: afd5f68f-b70f-4000-a21d-28dbc8be8b07, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]

    ---------------------------

    Security-SPP Event ID 1003

    The Software Protection service has completed licensing status check.
    Application Id=55c92734-d682-4d71-983e-d6ec3f16059f
    Licensing Status=
    1: b92e9980-b9d5-4821-9c94-140f632f6312, 1, 1 [(0 [0xC004E003, 0, 0], [( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)(?)(?)])(1 )(2 [0x00000000, 0, 1], [(?)( 5 0x00000000 30 43200)( 1 0x00000000 0 0 msft:rm/algorithm/flags/1.0 0x00000000 0)(?)(?)(?)])]

    ============================


    Client MGA output:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-J8D7P-XQJJ2-GPDD4
    Windows Product Key Hash: xgsndMkYdJsYmUng0qIJ/thx+HI=
    Windows Product ID: 00371-868-0000007-85411
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {5A310AE8-BFD2-49F1-A8BF-688D339981E8}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.140303-2144
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Professional Plus 2007 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-b01a_E2AD56EA-766-0_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{5A310AE8-BFD2-49F1-A8BF-688D339981E8}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-GPDD4</PKey><PID>00371-868-0000007-85411</PID><PIDType>1</PIDType><SID>S-1-5-21-3521851180-3244512111-2218252725</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Inspiron 546 </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A09</Version><SMBIOSVersion major="2" minor="5"/><Date>20090808000000.000000+000</Date></BIOS><HWID>095F3D07018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>FX09   </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0011-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Plus 2007</Name><Ver>12</Ver><Val>1208E0A87E81D86</Val><Hash>FlQRxKwAwaRad03SQZkKxNggIRU=</Hash><Pid>89409-707-0082056-65245</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7601.17514

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: b92e9980-b9d5-4821-9c94-140f632f6312
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00170-868-000000-03-1033-7601.0000-2092014
    Installation ID: 011751536521019726056115618440708701492313365893152065
    Partial Product Key: GPDD4
    License Status: Initial grace period
    Time remaining: 43200 minute(s) (30 day(s))
    Remaining Windows rearm count: 1
    Trusted time: 7/28/2014 9:31:36 AM
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 6:23:2014 07:16
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: MgAAAAEABAABAAEAAAACAAAAAQABAAEAJJRe04hAjl+cEVTyEDPMabbK6kXsLQilArQ=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid Windows marker
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name OEMID Value OEMTableID Value
      APIC DELL   FX09   
      FACP DELL   FX09   
      HPET DELL   OEMHPET 
      MCFG DELL   OEMMCFG 
      SLIC DELL   FX09   
      OSFR DELL   FX09   
      OEMB DELL   FX09   
      SSDT A M I POWERNOW

    ================================

    Windows 7 Pro was installed on this machine using Microsoft's volume activation media, and is a standard image applied via Windows Deployment Services to some 200 other computers with no problems. 

    We also use a variety of surplus/off-lease machines, usually Dell brand, never with any activation problems.



    Monday, July 28, 2014 3:14 PM

Answers

  • ============================


    Client MGA output:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------


    HWID Data-->
    HWID Hash Current: MgAAAAEABAABAAEAAAACAAAAAQABAAEAJJRe04hAjl+cEVTyEDPMabbK6kXsLQilArQ=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid Windows marker
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name OEMID Value
    OEMTableID Value
      APIC DELL  


    The BIOS marker is missing. KMS will never work if this is missing. You'll need to use MAK.

    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!)

    • Marked as answer by Dale Mahalko Tuesday, July 29, 2014 4:10 PM
    Tuesday, July 29, 2014 10:01 AM

All replies

  • Hi,

    What's the error message in Event log when you using command to activate system failed?

    Error: Product activation failed.

    According to your description, it's not KMS server problem, there maybe some service or application on this Client prevent system activate.

    Please try to boot this client into SafeMode with networking, then activate this system for test.


    Roger Lu
    TechNet Community Support

    Tuesday, July 29, 2014 6:41 AM
    Moderator
  • ============================


    Client MGA output:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------


    HWID Data-->
    HWID Hash Current: MgAAAAEABAABAAEAAAACAAAAAQABAAEAJJRe04hAjl+cEVTyEDPMabbK6kXsLQilArQ=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid Windows marker
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name OEMID Value
    OEMTableID Value
      APIC DELL  


    The BIOS marker is missing. KMS will never work if this is missing. You'll need to use MAK.

    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!)

    • Marked as answer by Dale Mahalko Tuesday, July 29, 2014 4:10 PM
    Tuesday, July 29, 2014 10:01 AM
  • It's a Dell Inspiron desktop. Apparently a "for the home" system? Yet it was bought with Win 7 Pro OEM installed, and so I had hoped I could roll it into the KMS easily. Tried updating the BIOS but still acts the same.

    How can a "home edition" BIOS that's incompatible with KMS come with Win 7 Pro OEM?

    Oddly, we have several Dell XPS systems that are using KMS just fine. Those are almost exclusively marketed as "power gamer" systems for home use. I should see if there's some way to figure out which specific Dell products do this so they can be avoided.

    ,

    Fortunately it seems Windows 7 Pro edition software does not care if I use the OEM key from the sticker, so I typed that in and it activated.

    (Great, one weird machine that has to be treated specially from everything else we've got.)

    Tuesday, July 29, 2014 4:21 PM
  • It's a Dell Inspiron desktop. Apparently a "for the home" system? Yet it was bought with Win 7 Pro OEM installed, and so I had hoped I could roll it into the KMS easily. Tried updating the BIOS but still acts the same.

    How can a "home edition" BIOS that's incompatible with KMS come with Win 7 Pro OEM?

    Oddly, we have several Dell XPS systems that are using KMS just fine. Those are almost exclusively marketed as "power gamer" systems for home use. I should see if there's some way to figure out which specific Dell products do this so they can be avoided.

    ,

    Fortunately it seems Windows 7 Pro edition software does not care if I use the OEM key from the sticker, so I typed that in and it activated.

    (Great, one weird machine that has to be treated specially from everything else we've got.)


    Probably a question for Dell to answer. For whatever reason, Dell have not performed all the necessary OEM Activation (OA) configuration tasks on this machine, perhaps due to their manufacturing/marketing strategy for this model, or perhaps due to a defective configuration pass in the factory. Perhaps the mainboard in this machine was repaired or replaced at some stage, and wasn't correctly re-configured. Only Dell can resolve the missing marker, since it requires OEM tools.
    Activating using the COA sticker product key, doesn't depend on the marker being present.

    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!)

    Tuesday, July 29, 2014 9:23 PM
  • this information is incorrect.  bios markers are not invovled in KMS activation. OEM activation using xrm-ms files use BIOS markers.  i am so tired of bad info.
    Monday, November 5, 2018 9:52 PM
  • this information is incorrect.  bios markers are not invovled in KMS activation. OEM activation using xrm-ms files use BIOS markers.  i am so tired of bad info.

    your experience may be different to mine.

    in my ~18 years experience in enterprise licensing and deployment and support this has been validated countless times, personally and also within MS forums (technet and partner)


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Tuesday, November 6, 2018 8:30 PM