Windows License activation errors
See instructions below provided by amazon,
when I was in step 4 and 5 I finally was able to fix server 24.
Windows on EC2 uses KMS licensing to activate Windows. With this system each instance would connect to an Amazon controlled KMS server that activates Windows for a set amount of time and the instance would attempt before expiry of that time to re-activate via KMS to extend the active license time period. If it loses contact to the KMS server and the license period expires your instance will alert you that it is no longer running an active Windows License.
There are a few things we can try to remedy the situation. Please before you make any critical changes to your machine ensure that you have made backups and/or snapshots of your machine.
http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/Creating_EBSbacked_WinAMI.html
http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ebs-creating-snapshot.html
1. Update the EC2 Config service and then restart the instance. You can read up more about the tool and download it from here:
http://aws.amazon.com/developertools/5562082477397515
Once restarted run the below to force Windows to attempt activation:
Start > Run > slmgr.vbs /ato
2. If this step fails activation then we are going to first that networking from the instance to the KMS server is functioning and once done then we will confirm that configuration of KMS Client is correct.
Do a telnet test to the KMS servers from the instance:
telnet 169.254.169.250 1688
telnet 169.254.169.251 1688
3. if the telnet fails please check the following
Run the command: “route print” and check the following route:
Network Destination / Netmask / Gateway / Interface / Metric
169.254.169.250 / 255.255.255.255 / / / 10
169.254.169.251 / 255.255.255.255 / / / 10
Which the VPC Gateway is the gateway of the instance in VPC subnet and the interface is the primary interface ip address.
4. If entries exist but don’t match your VPC Gateway/ENI configuration you can delete the existing routes by running the below in a CMD prompt
route DELETE 169.254.169.251
route DELETE 169.254.169.250
If no matching entries exist please add them by running the below in a CMD prompt:
route -p ADD 169.254.169.251 MASK 255.255.255.255
route -p ADD 169.254.169.250 MASK 255.255.255.255
Now re-test telnet connection to the KMS servers:
telnet 169.254.169.250 1688
telnet 169.254.169.251 1688
5. Checking the firewall
If these routes are present please check Windows Firewall or other security products on your instance are not blocking outbound TCP connections on port 1688 to the KMS Servers 169.254.169.250 and 169.254.169.251. Once the telnet test establishes a connection you know that the communication between your instance and the KMS server is functioning as expected and so at this point you can initiate an activation attempt by running:
slmgr.vbs /ato
6. Specify KMS servers manually
Sometimes the instance is looking for a different KMS server, instead of the AWS KMS servers. In order to correct this please run the following commands:
slmgr.vbs /skms 169.254.169.250:1688
slmgr.vbs /skms 169.254.169.251:1688
slmgr.vbs /ato
If you still can't activate the instance, please run this command and provide the screenshot of the output:
slmgr.vbs /dlv
Error on 5/16/17
the Metric 10 change to 25.
If this happen make sure that its 10 or 1