Frazer Posted August 30, 2012 Posted August 30, 2012 Starting to rollout windows 7 enterprise across the site. Finished the image and getting activation problems on all clients. Error on client machine: C:\Windows\system32>cscript slmgr.vbs /ato Microsoft ® Windows Script Host Version 5.8 Copyright © Microsoft Corporation. All rights reserved. Activating Windows® 7, Enterprise edition (ae2ee509-1b34-41c0-acb7-6d4650168915) ... Error: 0xC004F038 The software Licensing Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator Ive ran slmgr.vbs -ato on 30+ machines manually to be sure, but still getting the same error. When finishing the the image, I ran: OSPPREARM.EXE for office 2010 and sysprep /oobe /shutdown /unattend:unattend.xml /generalize (xml contains 1 is this the problem?) The KMS host is installed on a DC and has been activating office 2010 clients previously fine. Its registered using a 2008 R2 Enterprise KMS key so should be activating the windows 7 clients. KMS Host: C:\Windows\System32>cscript slmgr.vbs /dlv Microsoft ® Windows Script Host Version 5.8 Copyright © Microsoft Corporation. All rights reserved. Software licensing service version: 6.1.7601.17514 Name: Windows Server®, ServerEnterprise edition Description: Windows Operating System - Windows Server®, VOLUME_KMS_R2_B channel Activation ID: c99b641f-c4ea-4e63-bec3-5ed2ccd0f357 Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f Extended PID: 55041-00168-314-091599-03-2057-7601.0000-2432012 Installation ID: 006342440811704726433054397380252540355245726955439902 Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342 Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343 Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345 Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344 Partial Product Key: JP8XJ License Status: Licensed Remaining Windows rearm count: 3 Trusted time: 30/08/2012 14:36:11 Key Management Service is enabled on this machine Current count: 14 Listening on Port: 1688 DNS publishing enabled KMS priority: Normal Key Management Service cumulative requests received from clients Total requests received: 4849 Failed requests received: 14 Requests with License Status Unlicensed: 0 Requests with License Status Licensed: 560 Requests with License Status Initial grace period: 1672 Requests with License Status License expired or Hardware out of tolerance: 0 Requests with License Status Non-genuine grace period: 0 Requests with License Status Notification: 2603 Help! Back to school on Tuesday!
SYNACK Posted August 30, 2012 Posted August 30, 2012 Did you sysprep the image before deploying it. If not they will all try to activate with the same SID and machine id so KMS will see the requests from all the different machines as coming from one.
andy_nic Posted August 30, 2012 Posted August 30, 2012 The way I image them is to clone them all the same then use slmgr.vbs - rearm on 25 machines
Frazer Posted August 30, 2012 Author Posted August 30, 2012 (edited) @SYNACK When finishing the the image, I ran: OSPPREARM.EXE for office 2010 and sysprep /oobe /shutdown /unattend:unattend.xml /generalize (xml contains 1 is this the problem?) Sysprep ran fine when I did it, no errors. @andy_nic im just trying slmgr.vbs /rearm on 29 of them now (followed by a reboot) see what happens. EDIT: its only give them the standard 30-days additional time, no activation. Edited August 30, 2012 by Frazer
andy_nic Posted August 30, 2012 Posted August 30, 2012 (edited) is this a new kms set up? never mind I see you have used the type B key on the host kms in your original post. Edited August 30, 2012 by andy_nic
andy_nic Posted August 30, 2012 Posted August 30, 2012 after you did slmgr.vbs /rearm did it bring up a message saying that it was successfully? before you restarted?
Frazer Posted August 30, 2012 Author Posted August 30, 2012 @andy_nic I used psexec remotely to run the command, exited with error code 0 (successful) then did a remote restart. I think I mustnt have waited long enough (a good 5 or 10 minutes wasnt enough!). Since rearming those 29 machines, they have actually activated along with the other 'non-rearmed' ones in other rooms. Dont know why It needed a rearm to start it off and not on the remaining machines! Maybe If 1 was not in the xml I wouldnt have encountered this problem. Either way it appears to be solved! Thanks
SYNACK Posted August 30, 2012 Posted August 30, 2012 You don't need to use psexec, the slmgr.vbs can target another machine slmgr.vbs remoteMachine /rearm slmgr.vbs remoteMachine /ato is what I used ages ago when I had messed up an image. It only woked for me at that point as there was more than 25 on when I did it so even with the same uid it activated them all happily and showed up that change the next time it was restarted.
DavidIrwin Posted August 31, 2012 Posted August 31, 2012 Activating Windows® 7, Enterprise edition (ae2ee509-1b34-41c0-acb7-6d4650168915) ... Error: 0xC004F038 The software Licensing Service reported that the computer could not be activated. The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator I think the problem you have here may be quite simple... A KMS server reports will only start activating once it has reacher a minimum number of requests. In the case of Windows 7 this is 25. Your KMS server appears to have only received 14 requests for activation so far: Key Management Service is enabled on this machine Current count: 14 Listening on Port: 1688 DNS publishing enabled KMS priority: Normal You can get more information from the KMS server by running Slmgr.vbs -dli (from How to troubleshoot Volume Activation error codes in Windows 7, in Windows Server 2008, and in Windows Vista. There is also some useful intofmation in How to troubleshoot the Key Management Service (KMS) I hope this helps.
hudzen76 Posted August 31, 2012 Posted August 31, 2012 Dunno if it'll help, but spent ages mucking around with command line then found the Volume Activation Management Tool which made process loads easier; bulk deploy keys and activate remotely. Think we've got KMS keys deployed properly in the Windows 7 and Office 2010 image but using VAMT got me out of hole...! Process I use is to update status for PCs in question, deploy KMS keys, then activate. The DNS entry went in easily enough so they find the server automatically. Download: VAMT 2.0 - Microsoft Download Center - Download Details
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now