- 3Replace Product Key with KMS Client Key
- 6Activate
Purpose
Detach all client processes connected to this data pump job and then orderly shutdown the currently running job Table 6.4: Additional IMPDP Parameters Get the Complete. For example, a KMS client with a rearm count of 1 issues a rearm using the remaining single rearm, and reboot. Upon reboot after the KMS client activates, the rearm count will return to a count of 1. In all of the preceding scenarios, a successful KMS configuration for a Provisioning Services vDisk, does not require you to rearm the vDisk except the first time when it is configured.
This article gives the commands to activate a Windows system to a KMS licensing server. This applies to Vista or later.
Prerequisite
- Windows must have been installed from volume licensing (VL) media.
- Open Command Prompt as Administrator
Replace Product Key with KMS Client Key
Determine if a KMS Client key is installed
Example
VOLUME_MAK_B channel in the description. That stands for Multiple Activation Key and is not a KMS client key.
Obtain a KMS Client Key
The KMS client keys are universal to all customers and a list of them can be found on the Microsoft Technet web site HERE.
Uninstall Current Key (Optional)
The Install command replaces the existing key.
Install KMS Client Key
Example
Take note of the VOLUME_KMSCLIENT channel in the description.
Determine if KMS Host Has Service Record in DNS
Set KMS Server Manually (Skip if in DNS)
If your network does not support DDNS, you need to manually assign a KMS host to your KMS clients. Manually assigning a KMS host disables auto-discovery of KMS on a KMS client.
Example
Activate
Static Registered KMS Server Example
Take note of the key name Registered KMS machine name.
Dynamic DNS Registered KMS Server Example
Take note of the KMS machine name from DNS.
Related Articles
- (Reference) KMS Client Keys
Sources
Retrieved from 'https://www.bonusbits.com/index.php?title=HowTo:Manually_Activate_Windows_with_KMS&oldid=1088'