This topic describes how to use specific Key Management Service (KMS) domain names to activate a Windows Elastic Compute Service (ECS) instance that is deployed in a virtual private cloud (VPC).
The following table describes the Alibaba Cloud region-specific KMS domain names.
If you want to allow access to or from the IP address that corresponds to a KMS domain name in the firewall or security groups, you can run the
ping <KMS domain name> command to query the IP address that corresponds to the KMS domain name. For example, to query the IP address that corresponds to the KMS domain name specific to regions inside the Chinese mainland, run the
ping kms.cloud.aliyuncs.com command.
KMS domain name
Regions inside the Chinese mainland
China (Hong Kong)
US (Silicon Valley)
Malaysia (Kuala Lumpur)
This section describes how to activate a Windows instance that is deployed in a VPC in a region inside the Chinese mainland. If you want to activate a Windows instance in a region outside of the Chinese mainland, replace the KMS domain name in the sample commands with the KMS domain name specific to the region.
Connect to the Windows instance that you want to activate.
For more information, see Connect to a Windows instance by using a password or key.
On the Windows desktop, choose , enter cmd, and then press the Enter key to open the Command Prompt.
Run the following command to change the KMS domain name:
slmgr -skms kms.cloud.aliyuncs.comImportant
If the KMS domain name fails to be changed, check whether the Domain Name System (DNS) server that you use is an Alibaba Cloud DNS server. If the DNS server is not an Alibaba Cloud DNS server, the resolution of
kms.cloud.aliyuncs.comfails. For an instance that is deployed in a VPC, we recommend that you set the default DNS server to 100.100.2.136 or 100.100.2.138.
If your instance is deployed in the classic network, run the
slmgr -skms kms.aliyun-inc.comcommand to change the KMS domain name.
Run the following command to activate KMS:
Windows may fail to be activated due to various reasons, such as network exceptions, server clock synchronization issue, or an incorrect activation code. For more information, see Failed to activate the Windows ECS instance.