locked
Windows 7 Professional deactivating. RRS feed

  • Question

  • Hi,

    Over the past few weeks we have been having issue where laptops on our domain are deactivating. Laptops that might have been in use over a year. Below is an output from the MGADiag tool from one of the Laptops:

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-J8D7P-XQJJ2-GPDD4
    Windows Product Key Hash: xgsndMkYdJsYmUng0qIJ/thx+HI=
    Windows Product ID: 00371-868-0000007-85728
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {539F8F62-1D7B-4FBD-B401-654A9E2F5625}(1)
    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.120305-1505
    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 Project Professional 2007 - 100 Genuine
    Microsoft Office Visio Professional 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

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Users\rnorris\AppData\Local\Google\Chrome\Application\chrome.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>{539F8F62-1D7B-4FBD-B401-654A9E2F5625}</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-85728</PID><PIDType>1</PIDType><SID>S-1-5-21-543297256-498961329-4237451757</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP EliteBook 8540p</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>68CVD Ver. F.21</Version><SMBIOSVersion major="2" minor="6"/><Date>20120329000000.000000+000</Date></BIOS><HWID>DB833007018400FC</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-003B-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Project Professional 2007</Name><Ver>12</Ver><Val>A2FE75F8BE95ECC</Val><Hash>vlVtozU0Rb5Y5PO3pW73PEFUjZI=</Hash><Pid>84889-870-0642011-63043</Pid><PidType>8</PidType></Product><Product GUID="{91120000-0051-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Visio Professional 2007</Name><Ver>12</Ver><Val>5751F7BEC219ECC</Val><Hash>JAeIM4p1+Pq4HGaUwBSYf1M7yEE=</Hash><Pid>84890-870-0642002-63218</Pid><PidType>8</PidType></Product></Products><Applications><App Id="3A" Version="12" Result="100"/><App Id="53" 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-2057-7600.0000-0772011
    Installation ID: 008205643120731055204871079024842785212652611702571860
    Partial Product Key: GPDD4
    License Status: Notification
    Notification Reason: 0xC004F00F.
    Remaining Windows rearm count: 4
    Trusted time: 21/09/2012 13:36:03
    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: 9:21:2012 13:28
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: NAAAAAEABAABAAEAAAABAAAAAwABAAEAln3WOVAmmr348CL8RG1+/ryG1AE0OBIPNl5cXQ==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information: 
      ACPI Table Name OEMID Value OEMTableID Value
      APIC HPQOEM 1521    
      FACP HPQOEM 1521    
      HPET HPQOEM 1521    
      MCFG HPQOEM 1521    
      TCPA HPQOEM 1521    
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      SLIC HPQOEM SLIC-MPC
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      ASF! HPQOEM 1521    

    Each of these Laptops to tend to be HP, and do contain a COA. To get past the problem we have been using the COA key to activate against the Laptop. It does work. And below is the output after that.

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

    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-P3BB8-THWFC-CJV93
    Windows Product Key Hash: KmVuBEygw3c0wZLi11KcxD2Wa0g=
    Windows Product ID: 00371-OEM-9307952-59230
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {539F8F62-1D7B-4FBD-B401-654A9E2F5625}(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.120305-1505
    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 Project Professional 2007 - 100 Genuine
    Microsoft Office Visio Professional 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

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Users\rnorris\AppData\Local\Google\Chrome\Application\chrome.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>{539F8F62-1D7B-4FBD-B401-654A9E2F5625}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-CJV93</PKey><PID>00371-OEM-9307952-59230</PID><PIDType>8</PIDType><SID>S-1-5-21-543297256-498961329-4237451757</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP EliteBook 8540p</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>68CVD Ver. F.21</Version><SMBIOSVersion major="2" minor="6"/><Date>20120329000000.000000+000</Date></BIOS><HWID>DB833007018400FC</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-003B-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Project Professional 2007</Name><Ver>12</Ver><Val>A2FE75F8BE95ECC</Val><Hash>vlVtozU0Rb5Y5PO3pW73PEFUjZI=</Hash><Pid>84889-870-0642011-63043</Pid><PidType>8</PidType></Product><Product GUID="{91120000-0051-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Visio Professional 2007</Name><Ver>12</Ver><Val>5751F7BEC219ECC</Val><Hash>JAeIM4p1+Pq4HGaUwBSYf1M7yEE=</Hash><Pid>84890-870-0642002-63218</Pid><PidType>8</PidType></Product></Products><Applications><App Id="3A" Version="12" Result="100"/><App Id="53" 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, OEM_COA_SLP channel
    Activation ID: da22eadd-46dc-4056-a287-f5041c852470
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00186-079-559230-02-2057-7601.0000-2652012
    Installation ID: 003933372742161755604970244996766730938334183791698752
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: CJV93
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 21/09/2012 13:40:43

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 9:21:2012 13:28
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: NAAAAAEABAABAAEAAAABAAAAAwABAAEAln3WOVAmmr348CL8RG1+/ryG1AE0OBIPNl5cXQ==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information: 
      ACPI Table Name OEMID Value OEMTableID Value
      APIC HPQOEM 1521    
      FACP HPQOEM 1521    
      HPET HPQOEM 1521    
      MCFG HPQOEM 1521    
      TCPA HPQOEM 1521    
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      SLIC HPQOEM SLIC-MPC
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      SSDT HPQOEM SataAhci
      ASF! HPQOEM 1521    

    Is anyone able to give a clear answer as to why it became deactivated, and if activating with the COA is a legitimate way of solving our problem.

    Friday, September 21, 2012 12:56 PM

Answers

  • The error flag from the KMS activation is that the hardware hash has changed beyond tolerance - this can often be the result of updating basic drivers such as chipset, or changing network adapators (even enabling/disabling NIC's in BIOS can trigger this)

    Have you checked the SID's of the machines in question - are they perhaps duplicated by problem in the image used?


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Friday, September 21, 2012 2:43 PM
    Moderator
  • If you have no KMS server, then the situation is going to get worse rapidly!

    ALL KMS clients MUST re-activate within 180 days against the KMS server or they will become non-genuine. Under normal conditions, this re-activation takes place every 5-10 days - you can expect all such clients to become unactivated over that sort of time period, and hence show as non-genuine.

    Using Acronis to install multiple machines is not (so far as I know) a supported method, and means that all machines will at least start with the same SID and machine name - this is guranteed to confuse everything, including activation servers, Domain servers, and probably users :)

    For better advice on that aspect, I suggest you post in the ITPro forums (these WGA orums are primarily for end-user support) - http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/threads - if you're a TechNet subsciber, then you will get responses sfrom MS techs, but if not, then you'll get (very) experienced responses from other SysAdmins.


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Friday, September 28, 2012 9:32 AM
    Moderator

All replies

  • The error flag from the KMS activation is that the hardware hash has changed beyond tolerance - this can often be the result of updating basic drivers such as chipset, or changing network adapators (even enabling/disabling NIC's in BIOS can trigger this)

    Have you checked the SID's of the machines in question - are they perhaps duplicated by problem in the image used?


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Friday, September 21, 2012 2:43 PM
    Moderator
  • Hi Noel,

    No I haven't. But I will when undoubtedly the next one becomes deactivated. This does seem to happen with Laptops that were activated with a KMS... As far as I was aware our company didn't have a Server running KMS, but we could have at one point, or that our company does specialize in take overs, therefore could have adopted the laptops in question. As we don't currently have a KMS running, we have MAK keys. However the MAK keys we have only seem to work with Windows 7 Enterprise. We have recently setup a couple of WDS servers which build our Desktops and Laptops with Windows 7 Enterprise, of which we don't have a problem with.

    It was just odd, this was happening to all HP's all running Windows 7 Professional. A couple of months ago, these were all activated laptops, all running genuine Windows 7 Professional. However like you said in regards to driver updates, it could be the case.

    I'll keep an eye out for any more that crop up, and will post any information I have regarding the SID, as it may help others who could be having the same issue.

    My Suspicions were that an old building method for these laptops (which were shipped from our US office), was that they would build the image, load all our software we need, then use Acronis to back up the image, and then restore new laptops we got with that image... Could that be causing the problem too? That method isn't used now. Since you mentioned about the SIDs... I thought that could also be causing the problem.


    Friday, September 28, 2012 9:07 AM
  • If you have no KMS server, then the situation is going to get worse rapidly!

    ALL KMS clients MUST re-activate within 180 days against the KMS server or they will become non-genuine. Under normal conditions, this re-activation takes place every 5-10 days - you can expect all such clients to become unactivated over that sort of time period, and hence show as non-genuine.

    Using Acronis to install multiple machines is not (so far as I know) a supported method, and means that all machines will at least start with the same SID and machine name - this is guranteed to confuse everything, including activation servers, Domain servers, and probably users :)

    For better advice on that aspect, I suggest you post in the ITPro forums (these WGA orums are primarily for end-user support) - http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/threads - if you're a TechNet subsciber, then you will get responses sfrom MS techs, but if not, then you'll get (very) experienced responses from other SysAdmins.


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Friday, September 28, 2012 9:32 AM
    Moderator
  • Hi Noel, 

    Thanks very much for your insight. You have been very helpful in this matter. I think you've hit the nail on the head with the mentioning the 180 days activation for KMS, when we don't have a KMS server. I thought that would e the case but hearing it from someone else has helped. No idea what they were thinking before with Acronis int he past. But it's not used now. I'll relay this back the rest of my team.

    Thanks once again.

    Friday, October 5, 2012 9:12 AM
  • You're welcome - good luck!

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Friday, October 5, 2012 9:29 AM
    Moderator