locked
0xC004F074 when trying to activate a windows7 client against our Window2008 SP2 KMS server. RRS feed

  • Question

  • The KMS is active and activates 2008 servers.   Applied the Update for Windows Server 2008 (KB968912) patch on 8.25.09 which is suppose to updated the KMS to take win7 activations.  Get the 0xC004F074 error.  However when I got to he KMS server, the KMS event log show the win7 workstation trying to activate and give a 0xC004F042  error in the log.  I've read some of these blogs and some talk about just rebooting, others talk about Key Management Service v1.2.   Rebooting did not work.  And appears the KMS 1.2 is what KB968912 put in place. Need some help. thanks.
    Tuesday, September 1, 2009 9:18 PM

Answers

  • I found a post on this forum, it is the same error 0xC004F074 when activating a Wind 7 client against Win 2008 KMS server. The following solution is really helpful for this error.

    1. Uninstall KMS license Key on host - slmgr.vbs /upk
    2. Install Windows Server 2008 R2 KMS license key - slmgr.vbs /ipk <Your Key>
    3. Activate KMS server online: slmgr.vbs /ato

    I hope it is useful. For more information, please refer to the following link:

    Server 2008 (R1) KMS server to activate Win7
    http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/936e7dbf-2ed5-4369-9504-b8d0393f205c

    Good luck!

    • Marked as answer by cybrd9 Thursday, September 3, 2009 10:08 PM
    Thursday, September 3, 2009 9:24 AM
  • 1. Uninstall KMS license Key on host - slmgr.vbs /upk
    2. Install Windows Server 2008 R2 KMS license key - slmgr.vbs /ipk <Your Key>
    3. Activate KMS server online: slmgr.vbs /ato

    This seem to be the fix.   My windows 2008 w/SP2 STD to the STD R2 KMS key.   I'd really like to know where the heck that is documented in MS's instructions that you have to change keys and apply a R2 key on a Non R2 server!!!

    Anyway after the change and reactivation, I'm getting the errror for the count not high enough for activation.  So I think that fixes it.   I hope what MS said about win7 activations could be Virtual now to count towards the count on activations.
    Thanks.

    • Marked as answer by cybrd9 Thursday, September 3, 2009 10:08 PM
    Thursday, September 3, 2009 10:08 PM

All replies

  • After you installed your Server 2008 R2/Win7 key using "slmgr /ipk <product key>" did you run "slmgr /ato"? If so did the activation go through there on your KMS Host? Is the correct key showing when you run "slmgr /dlv"?
    Tuesday, September 1, 2009 10:40 PM
  • I found a post on this forum, it is the same error 0xC004F074 when activating a Wind 7 client against Win 2008 KMS server. The following solution is really helpful for this error.

    1. Uninstall KMS license Key on host - slmgr.vbs /upk
    2. Install Windows Server 2008 R2 KMS license key - slmgr.vbs /ipk <Your Key>
    3. Activate KMS server online: slmgr.vbs /ato

    I hope it is useful. For more information, please refer to the following link:

    Server 2008 (R1) KMS server to activate Win7
    http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/936e7dbf-2ed5-4369-9504-b8d0393f205c

    Good luck!

    • Marked as answer by cybrd9 Thursday, September 3, 2009 10:08 PM
    Thursday, September 3, 2009 9:24 AM
  • Thanks for you reply:   On each win7 box, I apply these commands...
    slmgr /ipk 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
    slmgr /skms <server IP>
    slmgr /ato

    The slmgr /dlv show the HVTHH.   I use a batch file to apply these, it works (with different Key) for all my 2008 servers.   But I've manually entered these cmds with the same result.

    After the /ato cmd the 0xC004F074 error is given.  The same error is given when you used the activate now button in System properties.  THE KMS show that it's talking to the PCs., however its Key Management Log show the reason as 0xC004F042, 25/
    Thursday, September 3, 2009 8:40 PM
  • 1. Uninstall KMS license Key on host - slmgr.vbs /upk
    2. Install Windows Server 2008 R2 KMS license key - slmgr.vbs /ipk <Your Key>
    3. Activate KMS server online: slmgr.vbs /ato

    This seem to be the fix.   My windows 2008 w/SP2 STD to the STD R2 KMS key.   I'd really like to know where the heck that is documented in MS's instructions that you have to change keys and apply a R2 key on a Non R2 server!!!

    Anyway after the change and reactivation, I'm getting the errror for the count not high enough for activation.  So I think that fixes it.   I hope what MS said about win7 activations could be Virtual now to count towards the count on activations.
    Thanks.

    • Marked as answer by cybrd9 Thursday, September 3, 2009 10:08 PM
    Thursday, September 3, 2009 10:08 PM
  • Confirming this. Installing R2 key to NON R2 server, fixes the problem. This definitely should be documented somewhere.
    Thank you Nina Liu :)
    Wednesday, September 16, 2009 8:57 AM
  • The most easyest way to solve this problem is to check time sync.
    Your client machine time must be in sync with activation server.

    • Proposed as answer by Atef Saleh Tuesday, July 27, 2010 12:25 PM
    Tuesday, January 12, 2010 9:56 AM
  • In my case the error 0xC004F074 has been connected by that on server KMS windows firewall blocked port 1866.
    Wednesday, February 3, 2010 6:02 AM
  • I also had to reboot the servers after going through these steps.  Thank you for the help, it was a combination of using /upk, /ipk, /ato then rebooting that made it all come together.  I have KMS running on two Windows Server 2008 x64 Enterprise SP2 servers with a Group C key.

    Thursday, March 11, 2010 3:54 PM
  • The most easyest way to solve this problem is to check time sync.
    Your client machine time must be in sync with activation server.


    Dear think, just want to thank you a billion time, they should have handeled this isue in amore clear manner and display the time sync issue clearly, you are the man.
    Thursday, April 22, 2010 10:49 AM
  • Не помогли проделанные процедуры. В журнале приложений, на рабочей станции - фиксировалось обращение к серверу, на котором, когда-то была служба активации KMS, но в последствии была удалена.

    комманды:  slmgr.vbs /ckms и /skms host:port, не меняли значение в ветке реестра: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\KeyManagementServiceName =

    После перезаписи значения KeyManagementServiceName на правильное, активация прошла.

     

    • Proposed as answer by shipovalov Monday, December 30, 2013 7:28 AM
    Tuesday, November 22, 2011 11:58 AM