Skip to content

Categories:

windows activation KMS fails on ec2 instances

I’ll make this really short, but for some reason the windows 2008 instances in the amazon cloud showed that windows wasn’t genuine “Windows not genuine” – and when trying to activate using
slmgr.vbs /ato the error received was:
0xC004F074 with description “The Key Management Server (KMS) is unavailable” (this error: https://support.microsoft.com/en-ca/kb/974998)

Trying to set the KM server to various ips I found in amazon documentation did not work.
For example some IPs for various regions are listed here:
http://cloudstacking.com/posts/windows-product-activation-for-aws-ec2-imported-vms.html

But looking in the settings file for the ec2 client helped: c:\program files\amazon\Ec2ConfigService\settings\ActivationSettings.xml (more info: http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/UsingConfig_WinAMI.html)

That’s where the private IP of the KMS server is hidden.

So, then executing
slmgr.vbs /skms privateip-from-xml-file
and then
slmgr.vbs /ato
worked!

further info:

Windows Server: KMS client behind firewall


https://forums.aws.amazon.com/message.jspa?messageID=227937#418321

Be Sociable, Share!

Posted in code.


2 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. joe says

    Hi, just wanted to say thank you. I just ran into this myself. Your instructions did the trick. Many thanks from Jacksonville, FL. 🙂

  2. joe says

    Forgot to add in my previous comment, if you were curious how I got here, you were the sixth search result when I searched with the following string. (qdr:w means limit results to last week)

    https://www.google.com/#q=aws+ec2+windows+not+genuine&tbs=qdr:w



Some HTML is OK

or, reply to this post via trackback.