+ Post New Thread
Results 1 to 10 of 10
Windows 7 Thread, Windows 7 Enterprise not Activating 0xC004F038 (more than 25 machines) in Technical; Starting to rollout windows 7 enterprise across the site. Finished the image and getting activation problems on all clients. Error ...
  1. #1

    Join Date
    Sep 2005
    Posts
    143
    Thank Post
    0
    Thanked 3 Times in 3 Posts
    Rep Power
    19

    Windows 7 Enterprise not Activating 0xC004F038 (more than 25 machines)

    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 (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Activating Windows(R) 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 <skiprearm>1</skiprearm> 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 (R) Windows Script Host Version 5.8
    Copyright (C) Microsoft Corporation. All rights reserved.

    Software licensing service version: 6.1.7601.17514

    Name: Windows Server(R), ServerEnterprise edition
    Description: Windows Operating System - Windows Server(R), 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: 00634244081170472643305439738025254035524572695543 9902
    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!

  2. #2

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,271
    Thank Post
    884
    Thanked 2,749 Times in 2,322 Posts
    Blog Entries
    11
    Rep Power
    785
    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.

  3. #3
    andy_nic's Avatar
    Join Date
    Jun 2008
    Location
    Peterborough
    Posts
    451
    Thank Post
    31
    Thanked 39 Times in 33 Posts
    Rep Power
    20
    The way I image them is to clone them all the same then use slmgr.vbs - rearm on 25 machines

  4. #4

    Join Date
    Sep 2005
    Posts
    143
    Thank Post
    0
    Thanked 3 Times in 3 Posts
    Rep Power
    19
    @SYNACK
    Quote Originally Posted by Frazer View Post

    When finishing the the image, I ran:
    OSPPREARM.EXE for office 2010 and
    sysprep /oobe /shutdown /unattend:unattend.xml /generalize (xml contains <skiprearm>1</skiprearm> 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.
    Last edited by Frazer; 30th August 2012 at 03:51 PM.

  5. #5
    andy_nic's Avatar
    Join Date
    Jun 2008
    Location
    Peterborough
    Posts
    451
    Thank Post
    31
    Thanked 39 Times in 33 Posts
    Rep Power
    20
    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.
    Last edited by andy_nic; 30th August 2012 at 03:59 PM.

  6. #6
    andy_nic's Avatar
    Join Date
    Jun 2008
    Location
    Peterborough
    Posts
    451
    Thank Post
    31
    Thanked 39 Times in 33 Posts
    Rep Power
    20
    after you did slmgr.vbs /rearm did it bring up a message saying that it was successfully? before you restarted?

  7. #7

    Join Date
    Sep 2005
    Posts
    143
    Thank Post
    0
    Thanked 3 Times in 3 Posts
    Rep Power
    19
    @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 <skiprearm>1</skiprearm> was not in the xml I wouldnt have encountered this problem. Either way it appears to be solved!

    Thanks

  8. #8

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,271
    Thank Post
    884
    Thanked 2,749 Times in 2,322 Posts
    Blog Entries
    11
    Rep Power
    785
    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.

  9. #9

    Join Date
    Aug 2011
    Location
    Nottingham, England
    Posts
    59
    Thank Post
    6
    Thanked 7 Times in 6 Posts
    Rep Power
    8
    Quote Originally Posted by Frazer View Post

    Activating Windows(R) 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:

    Quote Originally Posted by Frazer View Post
    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.

  10. #10
    hudzen76's Avatar
    Join Date
    Mar 2009
    Location
    Forest of Dean
    Posts
    14
    Thank Post
    8
    Thanked 3 Times in 3 Posts
    Rep Power
    12
    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



SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 28
    Last Post: 28th May 2012, 06:35 PM
  2. KMS host activated loads more pcs than we have
    By ITtech35 in forum Licensing Questions
    Replies: 5
    Last Post: 11th April 2012, 10:12 PM
  3. Replies: 3
    Last Post: 9th May 2010, 05:24 PM
  4. Replies: 60
    Last Post: 13th March 2008, 06:39 PM
  5. Windows Volume not loud enough
    By ChrisH in forum Windows
    Replies: 10
    Last Post: 11th November 2006, 08:30 PM

Thread Information

Users Browsing this Thread

There are currently 2 users browsing this thread. (0 members and 2 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •