locked
KMS Client not activating RRS feed

  • Question

  • I have KMS running in my organization and all win7 clients have been activating with no problem.  I am currently working on a new image and now my machine doesn't want to activate.  I keep getting error code 0xC004E003.  Any help will be greatly appreciated.  here is my log.

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

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
    Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
    Windows Product ID: 00392-918-5000002-85140
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.004
    ID: {3D1864AB-AE54-454B-9794-DFF36ED6DDDA}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Enterprise
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.110408-1631
    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: 109 N/A
    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

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\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>{3D1864AB-AE54-454B-9794-DFF36ED6DDDA}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.004</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-HVTHH</PKey><PID>00392-918-5000002-85140</PID><PIDType>1</PIDType><SID>S-1-5-21-529242991-3923785514-1893041399</SID><SYSTEM><Manufacturer>Supermicro</Manufacturer><Model>C2G41</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1.0b   </Version><SMBIOSVersion major="2" minor="5"/><Date>20091113000000.000000+000</Date></BIOS><HWID>D63E3407018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>SMCI  </OEMID><OEMTableID></OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7601.17514

    Name: Windows(R) 7, Enterprise edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: ae2ee509-1b34-41c0-acb7-6d4650168915
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00392-00170-918-500000-03-1033-7601.0000-1812011
    Installation ID: 007321527772948052309775283044086402187506567886181282
    Partial Product Key: HVTHH
    License Status: Initial grace period
    Time remaining: 40080 minute(s) (27 day(s))
    Remaining Windows rearm count: 1
    Trusted time: 6/30/2011 3:56:05 PM
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000
    Event Time Stamp: N/A
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: MAAAAAEAAgABAAIAAAACAAAAAQABAAEA6GF8eUqKRu2qdpL79qSCfPxoKAoUgUxY

    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   111309  APIC0204
      FACP   111309  FACP0204
      HPET   111309  OEMHPET
      MCFG   111309  OEMMCFG
      SLIC   SMCI    
      OEMB   111309  OEMB0204
      GSCI   111309  GMCHSCI
      SSDT   DpgPmm  CpuPm

     


    Thursday, June 30, 2011 11:11 PM

Answers

  • "JoseRamirez" wrote in message news:1d55ec11-b81f-4f8d-821b-751b5e717ea1...

    I have KMS running in my organization and all win7 clients have been activating with no problem.  I am currently working on a new image and now my machine doesn't want to activate.  I keep getting error code 0xC004E003.  Any help will be greatly appreciated.  here is my log.

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

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
    Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
    Windows Product ID: 00392-918-5000002-85140
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.004

    Other data-->
    SYSTEM><Manufacturer>Supermicro</Manufacturer><Model>C2G41</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1.0b   </Version><SMBIOSVersion major="2" minor="5"/><Date>20091113000000.000000+000</Date></BIOS

     

    Licensing Data-->
    Software licensing service version: 6.1.7601.17514

    Name: Windows(R) 7, Enterprise edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Partial Product Key: HVTHH
    License Status: Initial grace period
    Time remaining: 40080 minute(s) (27 day(s))
    Remaining Windows rearm count: 1
    Trusted time: 6/30/2011 3:56:05 PM
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

     

    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

     
    All Volume licenses are upgrades - in the case of KMS licenses they depend on the BIOS SLIC table to be able to establish this.
    This system has no SLIC table, as it is based on a retail motherboard.
    You need to use an MAK license or a Retail license for this machine, upgrading the existing activated installation.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, July 1, 2011 8:32 AM
    Moderator

All replies

  • "JoseRamirez" wrote in message news:1d55ec11-b81f-4f8d-821b-751b5e717ea1...

    I have KMS running in my organization and all win7 clients have been activating with no problem.  I am currently working on a new image and now my machine doesn't want to activate.  I keep getting error code 0xC004E003.  Any help will be greatly appreciated.  here is my log.

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

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
    Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
    Windows Product ID: 00392-918-5000002-85140
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.004

    Other data-->
    SYSTEM><Manufacturer>Supermicro</Manufacturer><Model>C2G41</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1.0b   </Version><SMBIOSVersion major="2" minor="5"/><Date>20091113000000.000000+000</Date></BIOS

     

    Licensing Data-->
    Software licensing service version: 6.1.7601.17514

    Name: Windows(R) 7, Enterprise edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Partial Product Key: HVTHH
    License Status: Initial grace period
    Time remaining: 40080 minute(s) (27 day(s))
    Remaining Windows rearm count: 1
    Trusted time: 6/30/2011 3:56:05 PM
    Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

     

    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

     
    All Volume licenses are upgrades - in the case of KMS licenses they depend on the BIOS SLIC table to be able to establish this.
    This system has no SLIC table, as it is based on a retail motherboard.
    You need to use an MAK license or a Retail license for this machine, upgrading the existing activated installation.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, July 1, 2011 8:32 AM
    Moderator
  • I added my MAK key and it did validate.  But, I need it to work with my KMS server.  I'm curious if I need to update the BIOS of my machine in order for this to work.  Any ideas?
    Friday, July 1, 2011 8:27 PM
  • "JoseRamirez" wrote in message news:41c0870e-838c-49de-8c8a-c0976ed13763...
    I added my MAK key and it did validate.  But, I need it to work with my KMS server.  I'm curious if I need to update the BIOS of my machine in order for this to work.  Any ideas?

    An MAK Key will work with any kind of server - it only requires connection to the MS servers for activation purposes, .
    I think you are confusing the purpose of a KMS Server (which again is solely for activation purposes)?
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, July 1, 2011 8:29 PM
    Moderator
  • I may be confused about the purpose of the KMS server.  But I only have a finite number of MAK keys that I don't want to burn up.  I thought the purpose of the KMS server was to provide this alternative.  In my organization I could easily go through my MAK key allotment. 
    Friday, July 1, 2011 8:38 PM
  • "JoseRamirez" wrote in message news:4f342e35-445d-48e3-aaab-3fcf50528568...
    I may be confused about the purpose of the KMS server.  But I only have a finite number of MAK keys that I don't want to burn up.  I thought the purpose of the KMS server was to provide this alternative.  In my organization I could easily go through my MAK key allotment. 

    You should discuss this with your licensing manager/advisor/vendor - none of us in these forums can lay claim to being expert in the ramifications of Volume Licensing agreements.
    ...or post in the ITPro forums for advice....
    should get you into the right area.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, July 2, 2011 12:27 AM
    Moderator
  • Thanks.  I'll do that. 
    Tuesday, July 5, 2011 3:18 PM