What follows are some detailed explanations how the KMS infrastructure works.
Understanding Key Management Service¶
KMS activates Microsoft products on a local network, eliminating the need for individual computers to connect to Microsoft. To do this, KMS uses a client–server topology. A KMS client locates a KMS server by using DNS or a static configuration, then contact it by using Remote Procedure Call (RPC) and tries to activate against it. KMS can activate both physical computers and virtual machines, but a network must meet or exceed the activation threshold (minimum number of computers that KMS requires) of 25. For activation, KMS clients on the network need to install a KMS client key (General Volume License Key, GVLK), so the product no longer asks Microsoft server but a user–defined server (the KMS server) which usually resides in a company’s intranet.
py-kms is a free open source KMS server emulator written in Python, while Microsoft gives their KMS server only to corporations that signed a Select contract. Furthermore py-kms never refuses activation since it is without
restrictions, while the Microsoft KMS server only activates the products the customer has paid for. py-kms supports KMS protocol versions
Although py-kms does neither require an activation key nor any payment, it is not meant to run illegal copies of Windows. Its purpose is to ensure that owners of legal copies can use their software without restrictions, e.g. if you buy a new computer or motherboard and your key will be refused activation from Microsoft servers due to hardware changes.
Activation with py-kms is achieved with the following steps:
Run py-kms on a computer in the network (this is KMS server or local host).
Install the product on client (or said remote host, which is the computer sending data to local host) and enter the GVLK.
Configure the client to use the KMS server.
Note that KMS activations are only valid for 180 days, the activation validity interval, or 30 to 45 days with consumer-only products. To remain activated, KMS client computers must renew their activation by connecting to the KMS server at least once every 180 days. For this to work, you have to should ensure that a KMS server is always reachable for all clients on the network. Also remember you can’t activate Windows 8.1 (and above) on a KMS server hosted on the same machine (the KMS server must be a different computer than the client).
About GVLK keys¶
The GVLK keys for products sold via volume license contracts (renewal every 180 days) are published on Microsoft’s Technet web site.
There are also not official keys for consumer-only versions of Windows that require activation renewal every 45 days (Windows 8.1) or 30 days (Windows 8). A more complete and well defined list is available here.
SLMGR and OSPP commands¶
The software License Manager (
slmgr.vbs) is a Visual Basic script used to configure and retrieve Volume Activation information. The script can be run locally or remotely on the target computer, using the Windows-based script host
wscript.exe) or the command-based script host (
cscript.exe) - administrators can specify which script engine to use. If no script engine is specified, SLMGR runs using the default script engine (it is recommended to utilize
cscript.exe script engine that resides in the system32 directory). The Software Licensing Service must be restarted for any changes to take effect. To restart it, the Microsoft Management Console (MMC) Services can be used or
running the following command:
net stop sppsvc && net start sppsvc
The SLMGR requires at least one parameter. If the script is run without any parameters, it displays help information. The general syntax of
slmgr.vbs is as follows (using the
cscript.exe as the script engine):
cscript slmgr.vbs /parameter cscript slmgr.vbs [ComputerName] [User] [Password] [Option]
Where command line options are:
[ComputerName] Name of a remote computer (default is local computer). [User] Account with the required privilege on the remote computer. [Password] Password for the account with required privileges on the remote compute. [Option] Options are shown in the table below.
Following tables lists SLMGR more relevant options and a brief description of each. Most of the parameters configure the KMS host.
||Attempts to install a 5×5 ProductKey for Windows or other application identified by the ProductKey. If the key is valid, this is installed. If a key is already installed, it's silently replaced.|
||Prompts Windows to attempt online activation, for retail and volume systems with KMS host key. Specifying the ActivationID parameter isolates the effects of the option to the edition associated with that value.|
||Display license information. Specifying the ActivationID parameter displays the license information for the specified edition associated with that ActivationID. Specifying All will display all applicable installed products’ license information. Useful for retrieve the current KMS activation count from the KMS host.|
||Display detailed license information.|
||Display the activation expiration date for the current license state.|
||Some servicing operations require the product key to be available in the registry during Out-of-Box Experience (OOBE) operations. So this option removes the product key from the registry to prevent from being stolen by malicious code.|
||Installs the LicenseFile specified by the required parameter.|
||Reinstalls all licenses stored in %SystemRoot%\system32\oem and %SystemRoot%\System32\spp\tokens.|
||Resets the activation timers.|
||Resets the licensing status of the specified application.|
||Resets the licensing status of the specified SKU.|
||Uninstalls the product key of the current Windows edition. After a restart, the system will be in an unlicensed state unless a new product key is installed.|
||Displays installation ID for offline activation of the KMS host for Windows (default) or the application that is identified when its ActivationID is provided.|
||Activate product with user-provided ConfirmationID.|
|KMS client options||Description|
||Specifies the name and the port of the KMS host computer to contact. Setting this value disables auto-detection of the KMS host. If the KMS host uses IPv6 only, the address must be specified in the format [hostname]:port.|
||Sets the specific DNS domain in which all KMS SRV records can be found. This setting has no effect if the specific single KMS host is set with the /skms option. Use this option, especially in disjoint namespace environments, to force KMS to ignore the DNS suffix search list and look for KMS host records in the specified DNS domain instead.|
||Removes the specified KMS hostname, address, and port information from the registry and restores KMS auto-discovery behavior.|
||Enables KMS host caching (default), which blocks the use of DNS priority and weight after the initial discovery of a working KMS host. If the system can no longer contact the working KMS host, discovery will be attempted again.|
||Disables KMS host caching. This setting instructs the client to use DNS auto-discovery each time it attempts KMS activation (recommended when using priority and weight).|
||Changes how often a KMS client attempts to activate itself when it cannot find a KMS host. Replace ActivationInterval with a number of minutes between 15 minutes an 30 days. The default setting is 120.|
||Changes how often a KMS client attempts to renew its activation by contacting a KMS host. Replace RenewalInterval with a number of minutes between 15 minutes an 30 days. The default setting is 10080 (7 days).|
||Sets the TCP communications port on a KMS host. It replaces PortNumber with the TCP port number to use. The default setting is 1688.|
||Enables automatic DNS publishing by the KMS host.|
||Disables automatic DNS publishing by a KMS host.|
||Sets the priority of KMS host processes to Normal.|
||Set the KMS priority to Low.|
||Sets a value in the registry that limits volume activation to a single type. ActivationType 1 limits activation to active directory only; 2 limits it to KMS activation; 3 to token-based activation. The 0 option allows any activation type and is the default value.|
The Office Software Protection Platform script (
ospp.vbs) can help you to configure and test volume license editions of Office client products. You must open a command prompt by using administrator permissions and navigate to the
folder that contains the mentioned script. The script is located in the folder of the Office installation (use
\Office14 for Office 2010,
\Office15 for Office 2013 and
\Office16 for Office 2016):
%installdir%\Program Files\Microsoft Office\Office15.
If you are running a 32-bit Office on a 64-bit operating system, the script is located in the folder:
%installdir%\Program Files (x86)\Microsoft Office\Office15.
Running OSPP requires the
cscript.exe script engine. To see the help file, type the following command, and then press ENTER:
cscript ospp.vbs /?
The general syntax is as follows:
cscript ospp.vbs [Option:Value] [ComputerName] [User] [Password]
Where command line options are:
[Option:Value] Specifies the option and Value to use to activate a product, install or uninstall a product key, install and display license information, set KMS host name and port, and remove KMS host. The options and values are listed in the tables below. [ComputerName] Name of the remote computer. If a computer name is not provided, the local computer is used. [User] Account that has the required permission on the remote computer. [Password] Password for the account. If a user account and password are not provided, the current credentials are used.
||Activates installed Office product keys.|
||Installs a ProductKey (replaces existing key) with a user-provided ProductKey.|
||Uninstalls an installed ProductKey with the last five digits of the ProductKey to uninstall (as displayed by the /dstatus option).|
||Installs a LicenseFile with user-provided path of the .xrm-ms license.|
||Displays license information for installed product keys.|
||Displays license information for all installed licenses.|
||Displays the failure history for MAK / Retail activation.|
||Displays Installation ID for offline activation.|
||Activates product with user-provided ConfirmationID.|
||Resets the licensing status for all installed Office product keys.|
||Resets the licensing status for an Office license with a user-provided SKUID value. Use this option with the SKUID value specified by using the /dstatus option if you have run out of rearms and have activated Office through KMS or Active Directory-based activation to gain an additional rearm.|
||Displays the description for a user-provided ErrorCode.|
|KMS client options||Description|
||Displays KMS client activation history.|
||Displays KMS client computer ID (CMID)|
||Sets a KMS host name with a user-provided HostName.|
||Sets a KMS port with a user-provided Port number.|
||Removes KMS hostname (sets port to default).|
||Allows or denies KMS host caching. Parameter Value can be TRUE or FALSE.|
||(Windows 8 and later only) Sets volume activation type. Parameter Value can be: 1 (for Active Directory-based), 2 (for KMS), 0 (for both).|
||(Windows 8 and later only) Sets the specific DNS domain in which all KMS SRV records can be found. This setting has no effect if the specific single KMS host is set by the /sethst option. Parameter Value is the Fully Qualified Domain Name (FQDN).|
||(Windows 8 and later only) Clears the specific DNS domain in which all KMS SRV records can be found. The specific KMS host is used if it is set by the /sethst option. Otherwise, auto-discovery of the KMS host is used.|
Note that it is possible to activate all versions in the VL (Volume License) channel, so long as you provide the proper key to let Windows know that it should be activating against a KMS server. KMS activation can’t be used for Retail channel products, however you can install a VL product key specific to your edition of Windows even if it was installed as Retail. This effectively converts Retail installation to VL channel and will allow you to activate from a KMS server. However, this is not valid for Office’s products, so Office, Project and Visio must be always volume license versions. Newer version may work as long as the KMS protocol does not change…