For organizations managing a significant number of Windows servers and clients, efficient license activation is crucial. Key Management Service (KMS) offers a centralized solution to this challenge. But what exactly is a Key Management Server, and how does it streamline the activation process? This article delves into the concept of KMS, explaining its functionality, benefits, and the role of KMS client keys in volume activation.
Understanding the Key Management Server (KMS)
A Key Management Server, or KMS host, is a server on your local network that activates volume licensed Microsoft products, including Windows operating systems and Office suites. Instead of each computer individually connecting to Microsoft’s activation servers over the internet, they activate against the KMS host within your network. This centralized approach simplifies the activation process and is particularly beneficial for organizations with a large number of devices.
Think of a KMS server as your organization’s in-house activation authority. When a computer configured as a KMS client attempts to activate, it queries the network for a KMS host. Once located, the client attempts activation with the KMS host, without needing direct internet access for activation with Microsoft.
How KMS Streamlines Volume Activation
The KMS activation process is designed to be transparent and require minimal administrative overhead after initial setup. Here’s a simplified overview of how it works:
-
KMS Host Setup: An administrator sets up a designated server to act as the KMS host. This involves installing the Volume License Pack and activating the KMS host itself with a KMS host key obtained from the Volume Licensing Service Center (VLSC).
-
KMS Client Discovery: KMS client computers, running volume license editions of Windows, are pre-configured to automatically discover KMS hosts. They use DNS to locate the
_vlmcsservice record, which points to the KMS host server. -
Activation Request: Once a KMS client finds the KMS host, it sends an activation request. This request includes a Generic Volume License Key (GVLK), also known as a KMS client key. These keys are pre-installed in volume license editions of Windows and Windows Server.
-
Activation and Renewal: The KMS host counts the number of computers requesting activation. Once a threshold (activation count) is met, the KMS host starts activating clients. KMS activations are valid for 180 days (activation validity interval). To remain activated, KMS clients must renew their activation by connecting to the KMS host at least once every 180 days. Renewal attempts occur every 7 days.
Alt text: Command Prompt interface displaying the ‘slmgr /ipk’ command, used to install a KMS Client Product Key for Windows Server activation.
Key Components Working Together
For KMS to function effectively, several components work in concert:
-
KMS Host: The central server running the Key Management Service. It requires initial activation with Microsoft using a KMS host key. It needs to be reliably available on the network for clients to activate and renew their licenses.
-
KMS Client: Computers running volume licensed editions of Windows and Windows Server. These are pre-configured to find and activate against a KMS host. They use Generic Volume License Keys (GVLKs) for communication with the KMS host.
-
DNS (Domain Name System): DNS plays a crucial role in KMS client auto-discovery. The KMS host publishes its service location in DNS, allowing clients to easily find it on the network.
Benefits of Implementing a KMS Server
Utilizing a KMS server offers significant advantages for organizations using volume licensing:
- Centralized Activation: Manage and control activations from a single point, simplifying license management.
- Simplified Deployment: No need to individually activate each machine online, making large-scale deployments faster and easier.
- Cost-Effective: Reduces the need for individual retail licenses for each machine, leveraging the cost benefits of volume licensing.
- Maintains Compliance: Ensures all volume licensed systems are properly activated and compliant with Microsoft licensing terms.
- Offline Activation: KMS allows activation within the internal network, without requiring every machine to have internet access for activation.
When are KMS Client Keys (GVLKs) Necessary?
In most volume licensing scenarios, KMS client keys (GVLKs) are already pre-installed in volume editions of Windows and Windows Server. However, there are situations where you might need to manually install a GVLK:
- Converting from MAK Activation: If a computer was previously activated using a Multiple Activation Key (MAK) and you want to switch to KMS activation.
- Converting from Retail License: To convert a retail licensed version of Windows to a KMS client for volume activation within your organization.
- Reconfiguring a Former KMS Host: If a computer was previously acting as a KMS host and you need to convert it to a KMS client.
It’s important to remember that these GVLKs are specifically for KMS client activation and will only work when a KMS host is available on your network. They are not meant for retail activation or activating Windows without a KMS infrastructure.
Installing KMS Client Keys (GVLKs)
Installing a GVLK is a straightforward process. You can use the slmgr.vbs (Software License Manager) command-line tool in Windows.
To install a KMS client product key, follow these steps:
-
Open an Administrative Command Prompt. (Right-click on the Start button and choose “Command Prompt (Admin)” or “Windows PowerShell (Admin)”).
-
Type the following command and press Enter:
slmgr /ipk <GVLK>Replace
<GVLK>with the appropriate Generic Volume License Key for your version of Windows from the tables provided below.Example: To install the GVLK for Windows Server 2022 Datacenter Edition, you would use:
slmgr /ipk WX4NM-KYWYW-QJJR4-XV3QB-6VM33After running the command, you should see a confirmation dialog indicating that the product key was installed successfully.
Generic Volume License Keys (GVLKs) for Windows
The following tables provide the Generic Volume License Keys (GVLKs) for various versions and editions of Windows Server and Windows client operating systems. These keys are used for KMS client activation.
Windows Server LTSC (Long-Term Servicing Channel)
| Operating system edition | KMS Client Product Key |
|---|---|
| Windows Server 2025 Standard | TVRH6-WHNXV-R9WG3-9XRFY-MY832 |
| Windows Server 2025 Datacenter | D764K-2NDRG-47T6Q-P8T8W-YP6DF |
| Windows Server 2025 Datacenter: Azure Edition | XGN3F-F394H-FD2MY-PP6FD-8MCRC |
| Windows Server 2022 Standard | VDYBN-27WPP-V4HQT-9VMD4-VMK7H |
| Windows Server 2022 Datacenter | WX4NM-KYWYW-QJJR4-XV3QB-6VM33 |
| Windows Server 2022 Datacenter: Azure Edition | NTBV8-9K7Q8-V27C6-M2BTV-KHMXV |
| Windows Server 2019 Standard | N69G4-B89J2-4G8F4-WWYCC-J464C |
| Windows Server 2019 Datacenter | WMDGN-G9PQG-XVVXX-R3X43-63DFG |
| Windows Server 2019 Essentials | WVDHN-86M7X-466P6-VHXV7-YY726 |
| Windows Server 2016 Standard | WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY |
| Windows Server 2016 Datacenter | CB7KF-BWN84-R7R2Y-793K2-8XDDG |
| Windows Server 2016 Essentials | JCKRF-N37P4-C2D82-9YXRT-4M63B |
Windows Server Semi-Annual Channel
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 Semi-Annual Channel (SAC) has been retired, with no future releases planned. Customers are advised to move to Azure Stack HCI or the Long-Term Servicing Channel of Windows Server.
Windows 11 and Windows 10 Semi-Annual Channel
Refer to the Windows lifecycle fact sheet for details on supported versions and end-of-service dates.
| Operating system edition | KMS Client Product Key |
|---|---|
| Windows 11 Pro/Windows 10 Pro | W269N-WFGWX-YVC9B-4J6C9-T83GX |
| Windows 11 Pro N/Windows 10 Pro N | MH37W-N47XK-V7XM9-C7227-GCQG9 |
| Windows 11 Pro for Workstations/Windows 10 Pro for Workstations | NRG8B-VKK3Q-CXVCJ-9G2XF-6Q84J |
| Windows 11 Pro for Workstations N/Windows 10 Pro for Workstations N | 9FNHH-K3HBT-3W4TD-6383H-6XYWF |
| Windows 11 Pro Education/Windows 10 Pro Education | 6TP4R-GNPTD-KYYHQ-7B7DP-J447Y |
| Windows 11 Pro Education N/Windows 10 Pro Education N | YVWGF-BXNMC-HTQYQ-CPQ99-66QFC |
| Windows 11 Education/Windows 10 Education | NW6C2-QMPVW-D7KKK-3GKT6-VCFB2 |
| Windows 11 Education N/Windows 10 Education N | 2WH4N-8QGBV-H22JP-CT43Q-MDWWJ |
| Windows 11 Enterprise/Windows 10 Enterprise | NPPR9-FWDCX-D2C8J-H872K-2YT43 |
| Windows 11 Enterprise N/Windows 10 Enterprise N | DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4 |
| Windows 11 Enterprise G/Windows 10 Enterprise G | YYVX9-NTFWV-6MDM3-9PT4T-4M68B |
| Windows 11 Enterprise G N/Windows 10 Enterprise G N | 44RPN-FTY23-9VTTB-MP9BX-T84FV |
Windows Enterprise LTSC and LTSB
| Operating system edition | KMS Client Product Key |
|---|---|
| Windows 11 Enterprise LTSC 2024/Windows 10 Enterprise LTSC 2021/Windows 10 Enterprise LTSC 2019 | M7XTQ-FN8P6-TTKYV-9D4CC-J462D |
| Windows 11 Enterprise N LTSC 2024/Windows 10 Enterprise N LTSC 2021/Windows 10 Enterprise N LTSC 2019 | 92NFX-8DJQP-P6BBQ-THF9C-7CG2H |
| Windows IoT Enterprise LTSC 2024/Windows IoT Enterprise LTSC 2021 | KBN8V-HFGQ4-MGXVD-347P6-PDQGT |
Note: For ImageVersion: 10.0.19044.2905 or later, refer to Windows IoT Enterprise LTSC in Volume License.
| Operating system edition | KMS Client Product Key |
|---|---|
| Windows 10 Enterprise LTSB 2016 | DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ |
| Windows 10 Enterprise N LTSB 2016 | QFFDN-GRT3P-VKWWX-X7T3R-8B639 |
| Windows 10 Enterprise LTSB 2015 | WNMTR-4C88C-JK8YV-HQ7T2-76DF9 |
| Windows 10 Enterprise N LTSB 2015 | 2F77B-TNFGY-69QQF-B8YKP-D69TJ |
Earlier Versions of Windows Server
| Operating system edition | KMS Client Product Key |
|---|---|
| Windows Server Standard | PTXN8-JFHJM-4WC78-MPCBR-9W4KR |
| Windows Server Datacenter | 2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG |
| Windows Server Standard | DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4 |
| Windows Server Datacenter | 6Y6KB-N82V8-D8CQV-23MJW-BWTG6 |
| Windows Server 2012 R2 Standard | D2N9P-3P6X9-2R39C-7RTCD-MDVJX |
| Windows Server 2012 R2 Datacenter | W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9 |
| Windows Server 2012 R2 Essentials | KNC87-3J2TX-XB4WP-VCPJV-M4FWM |
| Windows Server 2012 | BN3D2-R7TKB-3YPBD-8DRP2-27GG4 |
| Windows Server 2012 N | 8N2M2-HWPGY-7PGT9-HGDD8-GVGGY |
| Windows Server 2012 Single Language | 2WN2H-YGCQR-KFX6K-CD6TF-84YXQ |
| Windows Server 2012 Country Specific | 4K36P-JN4VD-GDC6V-KDT89-DYFKP |
| Windows Server 2012 Standard | XC9B7-NBPP2-83J2H-RHMBY-92BT4 |
| Windows Server 2012 MultiPoint Standard | HM7DN-YVMH3-46JC3-XYTG7-CYQJJ |
| Windows Server 2012 MultiPoint Premium | XNH6W-2V9GX-RGJ4K-Y8X6F-QGJ2G |
| Windows Server 2012 Datacenter | 48HP8-DN98B-MYWDG-T2DCC-8W83P |
| Windows Server 2012 Essentials | HTDQM-NBMMG-KGYDT-2DTKT-J2MPV |
| Windows Server 2008 R2 Web | 6TPJF-RBVHG-WBW2R-86QPH-6RTM4 |
| Windows Server 2008 R2 HPC edition | TT8MH-CG224-D3D7Q-498W2-9QCTX |
| Windows Server 2008 R2 Standard | YC6KT-GKW9T-YTKYR-T4X34-R7VHC |
| Windows Server 2008 R2 Enterprise | 489J6-VHDMP-X63PK-3K798-CPX3Y |
| Windows Server 2008 R2 Datacenter | 74YFP-3QFB3-KQT8W-PMXWJ-7M648 |
| Windows Server 2008 R2 for Itanium-based Systems | GT63C-RJFQ3-4GMB6-BRFB9-CB83V |
| Windows Web Server 2008 | WYR28-R7TFJ-3X2YQ-YCY4H-M249D |
| Windows Server 2008 Standard | TM24T-X9RMF-VWXK6-X8JC9-BFGM2 |
| Windows Server 2008 Standard without Hyper-V | W7VD6-7JFBR-RX26B-YKQ3Y-6FFFJ |
| Windows Server 2008 Enterprise | YQGMW-MPWTJ-34KDK-48M3W-X4Q6V |
| Windows Server 2008 Enterprise without Hyper-V | 39BXF-X8Q23-P2WWT-38T2F-G3FPG |
| Windows Server 2008 HPC | RCTX3-KWVHP-BR6TB-RB6DM-6X7HP |
| Windows Server 2008 Datacenter | 7M67G-PC374-GR742-YH8V4-TCBY3 |
| Windows Server 2008 Datacenter without Hyper-V | 22XQ2-VRXRG-P8D42-K34TD-G3QQC |
| Windows Server 2008 for Itanium-Based Systems | 4DWFP-JF3DJ-B7DTH-78FJB-PDRHK |
Earlier Versions of Windows Client
| Operating system edition | KMS Client Product Key |
|---|---|
| Windows 8.1 Pro | GCRJD-8NW9H-F2CDX-CCM8D-9D6T9 |
| Windows 8.1 Pro N | HMCNV-VVBFX-7HMBH-CTY9B-B4FXY |
| Windows 8.1 Enterprise | MHF9N-XY6XB-WVXMC-BTDCT-MKKG7 |
| Windows 8.1 Enterprise N | TT4HM-HN7YT-62K67-RGRQJ-JFFXW |
| Windows 8 Pro | NG4HW-VH26C-733KW-K6F98-J8CK4 |
| Windows 8 Pro N | XCVCF-2NXM9-723PB-MHCB7-2RYQQ |
| Windows 8 Enterprise | 32JNW-9KQ84-P47T8-D8GGY-CWCK7 |
| Windows 8 Enterprise N | JMNMF-RHW7P-DMY6X-RF3DR-X2BQT |
| Windows 7 Professional | FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 |
| Windows 7 Professional N | MRPKT-YTG23-K7D7T-X2JMM-QY7MG |
| Windows 7 Professional E | W82YF-2Q76Y-63HXB-FGJG9-GF7QX |
| Windows 7 Enterprise | 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH |
| Windows 7 Enterprise N | YDRBP-3D83W-TY26F-D46B2-XCKRJ |
| Windows 7 Enterprise E | C29WB-22CC8-VJ326-GHFJW-H9DH4 |
| Windows Vista Business | YFKBB-PQJJV-G996G-VWGXY-2V3X8 |
| Windows Vista Business N | HMBQG-8H2RH-C77VX-27R82-VMQBT |
| Windows Vista Enterprise | VKK3X-68KWM-X2YGT-QR4M6-4BWMV |
| Windows Vista Enterprise N | VTC42-BM838-43QHV-84HX6-XJXKV |
In Conclusion
Key Management Servers are a cornerstone of efficient volume license management for organizations utilizing Microsoft products. By providing centralized activation services, KMS simplifies administration, reduces costs, and ensures licensing compliance. Understanding what a Key Management Server is and how it operates is essential for any IT professional managing a Windows environment at scale. The Generic Volume License Keys (GVLKs) listed in this article are vital for KMS client computers to communicate with and activate against the KMS host, completing the volume activation ecosystem. Remember to always use these keys in conjunction with a properly configured KMS host on your network and not for retail activation purposes.
