To use KMS, you need to have a KMS host available on your local network. Computers that activate with a KMS host need to have a specific product key. This key is sometimes referred to as the KMS client key, but it's formally known as a Microsoft Generic Volume License Key (GVLK). Computers that are running volume licensing editions of Windows Server and Windows client are, by default, KMS clients with no extra configuration needed as the relevant GVLK is already there.
There are some scenarios, however, where you'll need to add the GVLK to the computer you wish to activate against a KMS host, such as:
Converting a computer from using a Multiple Activation Key (MAK)
Converting a retail license of Windows to a KMS client
If the computer was previously a KMS host
Important
To use the keys listed here (which are GVLKs), you must first have a KMS host available on your local network. If you don't already have a KMS host, please see how to create a KMS host to learn more.
If you want to activate Windows without a KMS host available and outside of a volume-activation scenario (for example, you're trying to activate a retail version of Windows client), these keys won't work. You will need to use another method of activating Windows, such as using a MAK, or purchasing a retail license. Get help to find your Windows product key and learn about genuine versions of Windows.
Install a product key
If you're converting a computer from a KMS host, MAK, or retail edition of Windows to a KMS client, install the applicable product key (GVLK) from the list in this article. To install a client product key, open an administrative command prompt on the client, and run the following command and then press Enter:
slmgr /ipk <product key>
For example, to install the product key for Windows Server 2022 Datacenter Edition, run the following command and then press Enter:
slmgr /ipk WX4NM-KYWYW-QJJR4-XV3QB-6VM33
Generic Volume License Keys
In the tables that follow, you'll find the GVLKs for each version and edition of Windows. LTSC is Long-Term Servicing Channel, while LTSB is Long-Term Servicing Branch.
Windows Server, versions 20H2, 2004, 1909, 1903, and 1809
Operating system edition
KMS Client Product Key
Windows Server Standard
N2KJX-J94YW-TQVFB-DG9YT-724CC
Windows Server Datacenter
6NMRW-2C8FM-D24W7-TQWMY-CWH2D
Important
Windows Server, version 20H2 reached end of service on August 9, 2022 and is no longer receiving security updates. This includes the retirement of Windows Server Semi-Annual Channel (SAC) with no future releases.
Customers using Windows Server SAC should move to Azure Stack HCI. Alternatively, customers may use the Long-Term Servicing Channel of Windows Server.
As a Windows Server hybrid administrator, you integrate Windows Server environments with Azure services and manage Windows Server in on-premises networks.