This service allows users to manage keys across AWS services and hosted applications in a secure way.ĪWS KMS maintains keys in Hardware Security Modules (HSMs) and uses a concept called envelope encryption where encrypted data is stored locally in the AWS service or application along with the key. If you are an AWS user, you must have heard of or used its managed Key Management Service called AWS KMS. You must open User Datagram Protocol (UDP) port 123 to allow the sync.A Key Management Service (KMS) is used to create and manage cryptographic keys and control their usage across various platforms and applications. W32tm /config /manualpeerlist: /syncfromflags:MANUALĪfter the time synchronizes, attempt each of the following commands: w32tm /resync W32tm /config /manualpeerlist: /syncfromflags:MANUAL If the preceding step 1 returned the error 0xC004F074 The Key Management Server (KMS) is unavailable, the time on the cloud server is drastically different than what is on the KMS.Īt this point, you should configure the server to use a Network Time Protocol (NTP) time source by executing the appropriate command. To activate the device, run the below command: slmgr.vbs /atoĮnsure that the server clock synchronizes with the KMS clock Replace %key% with the key from the Microsoft® document. Set the device to KMS activation by using the key found in the previously referenced article and entering the following command: slmgr /ipk %key%
#Do i need to use kms client windows#
OS Name: Microsoft Windows Server 2012 R2 Datacenter To find which server edition you are running, run the following command and look for the section labeled OS name: systeminfo | findstr OSĮxample: PS C:\Users\Administrator> systeminfo | findstr OS If your device uses MAK activation, then you should set the device back to KMS activation.įirst, find and take note of the appropriate KMS client setup key from Microsoft: KMS Client Setup Keys The following images show sample outputs: Volume:GVLK means the device uses to KMS activation, Volume:MAK means the device uses to MAK activation. Look for the Product Key Channel setting. To confirm the activation method set on the device, run the following command: slmgr -dlv If the device does not activate, the server might be set to MAK activation instead of KMS activation. Note: If you receive the error 0xC004F074 The Key Management Server (KMS) is unavailable,Ĭontinue with the following steps to ensure the server clock synchronizes with the KMS clock. Request activation from the KMS: slmgr.vbs /ato
Set the KMS manually within the registry: slmgr.vbs /skms kms-server-from-table-above:1688
#Do i need to use kms client update#
We recommend the followingĪrticle for help resolving the issue: Update ServiceNet routes on cloud Is an interface, hardware, or routing issue.
Note: If there is a reply, continue to step 3. Then, right-click CommandĬonfirm that you can ping the Rackspace KMS server by running the following command: ping kms-server-from-table-above Log in to your cloud server as administrator by clicking Locate the appropriate KMS server in the following list: Data center Ensure that the Windows Server is configured to use the correct KMS server
Use the steps in the following sections to resolve this issue.