Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Fails KMS activation - Windows 7 HP Elite 8100 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We are experiencing an issue on the HP Elite 8100 desktop.  They fail to activate no matter what you do, I disabled all firewalls and AV.  I know the KMS server is functioning correctly as the same image can be activated on other hardware.  slmgr.vbs and VAMT 2.0 reports same error on these machines.  These machine are purchased thru HP - China.

    I have even attempted a fresh clean install on a wiped system from the enterprise DVD, it is still unable to activate. These HP 8100's will not even activate if I use the MAK key, actually fails to load MAK stating the invalid upgrade.

    Any help would be appreciated.

    Info from MGADIAG:

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
    Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
    Windows Product ID: 00392-918-5000002-85116
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7600.2.00010100.0.0.004
    ID: {744285F9-248E-48F1-B03B-4B23C86C2E5F}(1)
    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: 7600.win7_gdr.110408-1633
    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: B4D0AA8B-604-645_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>{744285F9-248E-48F1-B03B-4B23C86C2E5F}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.004</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-HVTHH</PKey><PID>00392-918-5000002-85116</PID><PIDType>1</PIDType><SID>S-1-5-21-2101498718-4069688172-3470217641</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq 8100 Elite SFF PC</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>786H1 v01.08</Version><SMBIOSVersion major="2" minor="6"/><Date>20110207000000.000000+000</Date></BIOS><HWID>1FB93607018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>China Standard Time(GMT+08:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-BPC</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.7600.16385

    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-7600.0000-2932009
    Installation ID: 015380945012973250270403901051442584060625014583979245
    Partial Product Key: HVTHH
    License Status: Notification
    Notification Reason: 0xC004F035.
    Remaining Windows rearm count: 0
    Trusted time: 6/14/2011 11:26:52 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:11:2011 04:04
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: LgAAAAEAAgABAAEAAAACAAAAAQABAAEA6GEehKIUmJHmdpZBltmmYMjViABcXQ==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: no, invalid SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   COMPAQ  IBEXPEAK
      FACP   COMPAQ  IBEXPEAK
      HPET   COMPAQ  IBEXPEAK
      MCFG   COMPAQ  IBEXPEAK
      ASF!   COMPAQ  IBEXPEAK
      TCPA   COMPAQ  IBEXPEAK
      SLIC   HPQOEM  SLIC-BPC

    Tony
    • Edited by Spamhater007 Tuesday, June 14, 2011 9:40 AM added detail
    Tuesday, June 14, 2011 9:37 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    To explain the problem, I first need to explain the requirement for KMS Client software.

    KMS Client software has a requirement that it must be installed on a PC (from a Large manufacturer) that originally came with Windows Pre-installed.  These types of PCs use a unique Product Activation system that uses a OEM Bios Flag (known as a SLIC table) to allow Windows to self activate.

    The way Microsoft enforces this KMS requirement is that when a KMS Client is installed on a PC, it looks for any OEM Bios flag (the SLIC table).  If one is found, it knows the requirement has been satisfied.  However, if no Bios Flag is found, the KMS software will fail to activate as you have described.

     

    In your Diagnostic Report we see:

    "BIOS valid for OA 2.0: no, invalid SLIC table"

     

    This means there is no OEM Bios flag found in the Bios of that PC. Since the PC is an HP, there should be a Bios flag, but for an unknown reason, there isn't one.  Most likely a new or custom Bios was installed that didn't have a SLIC table. and this is why your KMS software isn't working in those PCs.

     

    There are a few things you can try that should resolve this issue.

    1) Contact HP and see if you can get the original Bios for that model of PC.  Once that Bios is installed (and it contains a SLIC table) this would enable the KMS software to function correctly.

    2) Use a MAC volume key instead of KMS.  The MAC volume key doesn't have the Bios Flag requirements that KMS does, but the trade off is the MAC key must be activated (either over the internet or by phone) with Microsoft instead of activated through your KMS Server.

    You should be able to trade some of your KMS licenses for MAC keys.  I am not sure of the exact process to do this, but you should be able to find out through the same people/company that sold you the KMS licenses.

    Hope this was helpful,

    Darin MS
    Tuesday, June 14, 2011 10:39 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Khalid,

    Sorry the only solution it to purchase the Windows version.  We had to return the machines to HP and order the Windows version which includes the SLIC table.  Our china purchasing dept was re-instructed again to purchase the machines exactly as specified.

    Thanks, Tony

    Tony
    Sunday, December 4, 2011 1:54 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    "SPAMHATER007" wrote in message news:444dff90-228f-4abd-b6bf-f2e463e233be...

    We are experiencing an issue on the HP Elite 8100 desktop.  They fail to activate no matter what you do, I disabled all firewalls and AV.  I know the KMS server is functioning correctly as the same image can be activated on other hardware.  slmgr.vbs and VAMT 2.0 reports same error on these machines.  These machine are purchased thru HP - China.

    I have even attempted a fresh clean install on a wiped system from the enterprise DVD, it is still unable to activate. These HP 8100's will not even activate if I use the MAK key, actually fails to load MAK stating the invalid upgrade.

    Any help would be appreciated.

    Info from MGADIAG:

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
    Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
    Windows Product ID: 00392-918-5000002-85116
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7600.2.00010100.0.0.004

    Tony


    All I can think of is that you need to use System Recovery to reinstall the original OS, and then upgrade from that
     
    Darin will be in later, and may be able to offer more advice on the magical incantations involved in KMS and MAK activations - or you could try posting a parallel thread in the ITPro forums....

    --

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, June 14, 2011 11:12 AM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote

    To explain the problem, I first need to explain the requirement for KMS Client software.

    KMS Client software has a requirement that it must be installed on a PC (from a Large manufacturer) that originally came with Windows Pre-installed.  These types of PCs use a unique Product Activation system that uses a OEM Bios Flag (known as a SLIC table) to allow Windows to self activate.

    The way Microsoft enforces this KMS requirement is that when a KMS Client is installed on a PC, it looks for any OEM Bios flag (the SLIC table).  If one is found, it knows the requirement has been satisfied.  However, if no Bios Flag is found, the KMS software will fail to activate as you have described.

     

    In your Diagnostic Report we see:

    "BIOS valid for OA 2.0: no, invalid SLIC table"

     

    This means there is no OEM Bios flag found in the Bios of that PC. Since the PC is an HP, there should be a Bios flag, but for an unknown reason, there isn't one.  Most likely a new or custom Bios was installed that didn't have a SLIC table. and this is why your KMS software isn't working in those PCs.

     

    There are a few things you can try that should resolve this issue.

    1) Contact HP and see if you can get the original Bios for that model of PC.  Once that Bios is installed (and it contains a SLIC table) this would enable the KMS software to function correctly.

    2) Use a MAC volume key instead of KMS.  The MAC volume key doesn't have the Bios Flag requirements that KMS does, but the trade off is the MAC key must be activated (either over the internet or by phone) with Microsoft instead of activated through your KMS Server.

    You should be able to trade some of your KMS licenses for MAC keys.  I am not sure of the exact process to do this, but you should be able to find out through the same people/company that sold you the KMS licenses.

    Hope this was helpful,

    Darin MS
    Tuesday, June 14, 2011 10:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    AN HP BIOS update for a HP Compaq 8100 Elite SFF PC is readily available from HP Support & Drivers.

    Also, the PCs TimeZone appears to be set to China Standard Time.  You should make sure this is correct or if not, change it.

    Carey Frisch

    Tuesday, June 14, 2011 10:54 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Darin,

    Thank you for your response.  We are a large company with Enterprise Licensing and have deployed internal KMS server.  We do not perform upgrades over the vendor-supplied OS, we completely wipe the system and install our Corporate designed image which has worked flawlessly (over 1,200 deployed) until we received these new machines from HP-China.  The HP-USA systems do not have this issue.

    I have attempted loading HP's latest BIOS version, but still get the invalid SLIC table.  This apparently is a vendor hardware issue and we will need to bring these machines back to HP to be corrected.

    What is interesting, is that these machines will not even accept changing the KEY to a MAK key using slmgr.vbs -ipk, get error message about invalid upgrade (not exact text).

    Thanks for your assistance, Tony

    Tony
    Wednesday, June 15, 2011 6:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Carey, yes have tried updating to the latest BIOS.

    The machine is located in China and purchased from HP-China.  I suspect the HP China division is doing something different from the US Division.

    Tony
    Wednesday, June 15, 2011 6:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Tony,

    Yes, that is correct, The KMS doesn't require an Upgrade install since (like you) many companies image their PCs.  The requirement, as I understand it, is that the PC has to have originally come with Windows pre-installed (which means it would have an OEM Bios Flag).  This is why the requirement is enforced using the Bios Flag instead of requiring KMS be installed through an Upgrade install (which would be a major hassle for large companies).

    One thing you may want to test is if the Bios being used in the HP-USA systems will work in the HP-China PCs.  Since you know the HP-USA bios have the SLIC table, if you used that Bios in the HP-China PCs either the SLIC table would be found and the KMS software would work or the SLIC table would not be found and you would know for certain that there is a hardware(bios specific) issue with the HP-China PCs.

     

    As for the change product key error, that is odd and I don't know why that would happen. I would recommend contacting Microsoft Assisted support (either through your Microsoft Enterprise support contract, if you have one, or through http://support.microsoft.com/) for assistance with troubleshooting that.

     

    Thank you,

    Darin MS
    Wednesday, June 15, 2011 9:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Darin,

    After further research, it is exactly as you described.  The purchasing dept here in China modified our US specifications and ordered these machines without any OS installed, so this has resulted in machines without the OEM Bios Flag.

    Thanks, for your assistance!

    Tony

    Tony
    Thursday, June 16, 2011 3:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    May I know how did you resolve this problem? Did HP China helped?

    I have exactly the same problem (New HP PCs in China, No OS pre-installed, Windows image not being activated through KMS, and no SLIC table). Your post saves me further troubleshooting. Your help would be really appreciated.

    Best Regards,

    Khalid 

    Sunday, December 4, 2011 5:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Windows 7 Enterprise Volume License editions are "upgrade only" licenses.  Since you stated there are no qualifying OS installed, you must install one.

    "You cannot buy full Windows operating system licenses for desktop PCs through Microsoft Volume Licensing programs. Volume Licensing only provides Windows upgrade licenses. You must first have licensed and installed a "qualified" full desktop PC operating system on your device before you are eligible to acquire an upgrade license for the Windows desktop PC operating system for that device through Microsoft Volume Licensing programs."

    Ref: Frequently Asked Questions About Product Licensing

    Carey Frisch
    Sunday, December 4, 2011 6:08 AM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote

    Khalid,

    Sorry the only solution it to purchase the Windows version.  We had to return the machines to HP and order the Windows version which includes the SLIC table.  Our china purchasing dept was re-instructed again to purchase the machines exactly as specified.

    Thanks, Tony

    Tony
    Sunday, December 4, 2011 1:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you all...
    Monday, December 5, 2011 12:56 AM