Answered by:
Cannot activate oem windows 7 pro machines that have been reimaged with windows 7 pro vlk kms

Question
-
Hello,
We have a problem activating some new Windows 7 Pro computers. They were purchased from Dell with Windows 7 Pro OEM and came pre-activated from factory.
We are using SCCM to re-image these computers with our corporate image of Windows 7 Pro VLK (KMS), that is configured to use KMS on a Windows 2008 R2 domain controller acting as the KMS server. We have some computers already successfully running with Windows 7 Pro (KMS) from this same image, however I think the existing computers which are successfully activated were never pre-activated by Dell, they are probably 1.5 years older Dell hardware. Maybe Dell has changed their policy to pre-activate OEM now, I am not sure that is only my theory at this stage ?
Now my theory is that since Dell has pre-activated this latest set of computers we are having problems activating them after we re-image them from OEM to our VLK (KMS) image. If so, I believe the Hardware ID of that computer has already been activated (By Dell) so when our KMS server tries to activate the new image, it is failing.
I have run the "slmgr /dli" command on the affected computer and here is what it says:
Name: Windows 7 Pro
Description: Windows 7, VOLUME_KMS_W7
License status: Initial Grace Period
xx days remaining.Now, when I try to force the activation with "slmgr /ato" I get the following error:
Error: 0xC004C008 The activation server determined that the specified product key could not be used.
That error is not very helpful. I have visited MS websites and found some information: http://support.microsoft.com/kb/938450
----------------------------------------------------------------------------------------------
Symptom
When you try to use KMS to activate one or more computers, you may receive the following error message:0xC004C008
The activation server determined that the specified product key could not be used.Cause
This issue may occur if the KMS key has exceeded the activation limit. KMS keys will activate up to 10 times on six different computers.
Workaround
If you need more activation times, contact the Product Activation Call Center.
--------------------------------------------------------------------------------------Now, I do not understand how this is relevant: 6 KMS activations, since I am activating clients not hosts. We only have 1 KMS host (server 2008), I thought that KMS client is completely separate based on our license agreement, and not limited to 6 or 10 !? Please clarify...
So I also rang Microsoft support and they suggested I phone activate every computer, sorry but this is simply not possible with hundreds of computers.I believe we are well within our re-image licensing rights to re-image using our VLK media since we had purchased separate VLK agreement, as per article: http://technet.microsoft.com/en-us/library/ff730914.aspx
Would an expert please help ?
Thank you
Tuesday, April 5, 2011 6:51 AM
Answers
-
Nevermind, I have figured out the problem thanks to a MS Blog. Thank you to Scott McArthur
http://blogs.technet.com/b/askcore/archive/2009/03/09/kms-error-0xc004c008-activating-client.aspx
We were using KMS Host key on clients in our image, something before my time with this company though. :)
- Marked as answer by Nullsec Wednesday, April 6, 2011 1:33 AM
Wednesday, April 6, 2011 1:33 AM
All replies
-
"Digian" wrote in message news:43a5f844-2b94-4493-a3d4-116f132bc639...
Hello,
We have a problem activating some new Windows 7 Pro computers. They were purchased from Dell with Windows 7 Pro OEM and came pre-activated from factory.
We are using SCCM to re-image these computers with our corporate image of Windows 7 Pro VLK (KMS), that is configured to use KMS on a Windows 2008 R2 domain controller acting as the KMS server. We have some computers already successfully running with Windows 7 Pro (KMS) from this same image, however I think the existing computers which are successfully activated were never pre-activated by Dell, they are probably 1.5 years older Dell hardware. Maybe Dell has changed their policy to pre-activate OEM now, I am not sure that is only my theory at this stage ?
Now my theory is that since Dell has pre-activated this latest set of computers we are having problems activating them after we re-image them from OEM to our VLK (KMS) image. If so, I believe the Hardware ID of that computer has already been activated (By Dell) so when our KMS server tries to activate the new image, it is failing.
I have run the "slmgr /dli" command on the affected computer and here is what it says:
Name: Windows 7 Pro
Description: Windows 7, VOLUME_KMS_W7
License status: Initial Grace Period
xx days remaining.Now, when I try to force the activation with "slmgr /ato" I get the following error:
Error: 0xC004C008 The activation server determined that the specified product key could not be used.
That error is not very helpful. I have visited MS websites and found some information: http://support.microsoft.com/kb/938450
----------------------------------------------------------------------------------------------
Symptom
When you try to use KMS to activate one or more computers, you may receive the following error message:0xC004C008
The activation server determined that the specified product key could not be used.Cause
This issue may occur if the KMS key has exceeded the activation limit. KMS keys will activate up to 10 times on six different computers.
Workaround
If you need more activation times, contact the Product Activation Call Center.
--------------------------------------------------------------------------------------Now, I do not understand how this is relevant: 6 KMS activations, since I am activating clients not hosts. We only have 1 KMS host (server 2008), I thought that KMS client is completely separate based on our license agreement, and not limited to 6 or 10 !? Please clarify...
So I also rang Microsoft support and they suggested I phone activate every computer, sorry but this is simply not possible with hundreds of computers.I believe we are well within our re-image licensing rights to re-image using our VLK media since we had purchased separate VLK agreement, as per article: http://technet.microsoft.com/en-us/library/ff730914.aspx
Would an expert please help ?
Thank you
Please post an MGADiag report from one of the affected machines - it may show more detail.To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
Once saved, run the tool.
Click on the Continue button, which will produce the report.
To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed SlothTuesday, April 5, 2011 9:02 AMModerator -
This is from an affected computer:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-*****-*****-2HWJJ
Windows Product Key Hash: Skm2Dqduw0BWe0YOwzL8/2ec2HU=
Windows Product ID: 55041-037-6979954-86513
Windows Product ID Type: 7
Windows License Type: Volume KMS Server
Windows OS version: 6.1.7600.2.00010100.0.0.048
ID: {C48305CD-95AF-42A6-9D44-92A395A44B9E}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000000
Build lab: 7600.win7_gdr.100618-1621
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 Small Business 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
Browser Data-->
Proxy settings: redacted.com.au:8080
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-->
File Mismatch: C:\WINDOWS\system32\wat\watadminsvc.exe[Hr = 0x80070003]
File Mismatch: C:\WINDOWS\system32\wat\npwatweb.dll[Hr = 0x80070003]
File Mismatch: C:\WINDOWS\system32\wat\watux.exe[Hr = 0x80070003]
File Mismatch: C:\WINDOWS\system32\wat\watweb.dll[Hr = 0x80070003]
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{C48305CD-95AF-42A6-9D44-92A395A44B9E}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-037-6979954-86513</PID><PIDType>7</PIDType><SID>S-1-5-21-646589406-1067744879-3997161493</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>OptiPlex 780 </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A08</Version><SMBIOSVersion major="2" minor="5"/><Date>20110121000000.000000+000</Date></BIOS><HWID>3FB93607018400F8</HWID><UserLCID>0C09</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>E. Australia Standard Time(GMT+10:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL </OEMID><OEMTableID>B10K </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-00CA-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Small Business 2007</Name><Ver>12</Ver><Val>33FBD2455ADDD88</Val><Hash>+azvhnB24AU2FEiLhV1Wych2r28=</Hash><Pid>89395-708-5137075-65180</Pid><PidType>14</PidType></Product></Products><Applications><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"/></Applications></Office></Software></GenuineResults>
Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7600.16385
Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, VOLUME_KMS_W7 channel
Activation ID: d188820a-cb63-4bad-a9a2-40b843ee23b7
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00172-037-697995-03-3081-7600.0000-0842011
Installation ID: 001483356170981491233223414853191604270061046915739504
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: 2HWJJ
License Status: Initial grace period
Time remaining: 26100 minute(s) (18 day(s))
Remaining Windows rearm count: 1
Trusted time: 6/04/2011 8:45:15 AM
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Not Registered - 0x80040154
Admin Service: Not Registered - 0x80040154
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: MAAAAAEAAgABAAIAAQABAAAAAQABAAEA6GHskUowyOtylpr3QAVY46jjHg/y/EbK
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 DELL B10K
FACP DELL B10K
HPET DELL B10K
BOOT DELL B10K
MCFG DELL B10K
SSDT DELL st_ex
ASF! DELL B10K
TCPA DELL B10K
____ DELL B10K
SLIC DELL B10K
SSDT DELL st_ex
SSDT DELL st_ex
SSDT DELL st_ex
Tuesday, April 5, 2011 10:49 PM -
Nevermind, I have figured out the problem thanks to a MS Blog. Thank you to Scott McArthur
http://blogs.technet.com/b/askcore/archive/2009/03/09/kms-error-0xc004c008-activating-client.aspx
We were using KMS Host key on clients in our image, something before my time with this company though. :)
- Marked as answer by Nullsec Wednesday, April 6, 2011 1:33 AM
Wednesday, April 6, 2011 1:33 AM -
"Digian" wrote in message news:a5b5ab2f-2d58-423a-9605-2ecca4ba8fdf...
Nevermind, I have figured out the problem thanks to a MS Blog. Thank you to Scott McArthur
http://blogs.technet.com/b/askcore/archive/2009/03/09/kms-error-0xc004c008-activating-client.aspx
We were using KMS Host key on clients in our image, something before my time with this company though. :)
YepWindows Product ID: 55041-037-6979954-86513Windows Product ID Type: 7Windows License Type: Volume KMS Server
does tend to be a bit of a giveaway, doesn't it <g>Well spotted - good luck
--
Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed SlothWednesday, April 6, 2011 6:54 AMModerator