For anyone trying to use Windows 11 KMS Activation with their existing KMS activation server, here are the simple steps to follow to get it up and running. There have been some changes process-wise since I wrote the original Windows 10 version of this post, most notably, VLSC doesn’t exist anymore.
First, if you haven’t already entered the KMS Client Setup Key for your version of Windows 11, here are the published client keys. Obviously, these are not your unique KMS Server Keys, finding those is still the trickiest part and I’ll go over that in step 3.
| Windows 11 Edition | KMS Client Product Key |
|---|---|
| Pro | W269N-WFGWX-YVC9B-4J6C9-T83GX |
| Pro N | MH37W-N47XK-V7XM9-C7227-GCQG9 |
| Pro for Workstations | NRG8B-VKK3Q-CXVCJ-9G2XF-6Q84J |
| Pro Education | 6TP4R-GNPTD-KYYHQ-7B7DP-J447Y |
| Education | NW6C2-QMPVW-D7KKK-3GKT6-VCFB2 |
| Enterprise | NPPR9-FWDCX-D2C8J-H872K-2YT43 |
| Enterprise N | DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4 |
| Enterprise LTSC 2024 | M7XTQ-FN8P6-TTKYV-9D4CC-J462D |
(Full official table, including N and Education N variants, is on Microsoft’s KMS Client Activation Keys page if your edition isn’t listed above.)
To install the client key, open an administrative command prompt and run:
slmgr /ipk <product key>Second, there are a few prerequisites for your KMS Server, and this is where things diverge from the Windows 10 version of this guide if your KMS host is older hardware/OS:
- Windows Server 2016, 2019, 2022, or 2025 with the Volume Activation role installed (Windows Server 2012 R2 can still technically host KMS, but I’d move off it at this point given it’s long out of mainstream support)
- If your KMS host is still on Windows Server 2016 or 2019, you need the October 2021 KMS update (KB5003478) installed. This is the update that actually taught older hosts how to recognize and activate Windows 11 and Windows Server 2022 clients, without it your Windows 11 machines will just fail to activate against an otherwise-working KMS host.
- Your KMS host doesn’t need to be running the latest Windows Server version, it just needs the patch above plus a valid host key for the products you want it to activate.
Third, and final step, is finding your unique KMS host key, and this is the part that’s genuinely different from 2015. VLSC (Volume Licensing Service Center) was retired in April 2024. Everything that used to live there now lives in the Microsoft 365 Admin Center.
- Sign into admin.microsoft.com with an account that has a VL (Volume Licensing) role, being a Global Admin alone isn’t enough
- Go to Billing → Your products → Volume licensing
- Look for the Windows Server KMS host key tied to your active agreement (e.g. “Windows Srv 2022 DataCtr/Std KMS”)
- If your organization’s licenses didn’t carry over cleanly during the VLSC migration (this happened to a fair number of people), you’ll need to open a support case in the admin center under Help & Support, or contact your local Microsoft Activation Center directly rather than digging through the old VLSC phone tree, that phone number I posted back in 2015 is long dead along with the portal itself.
- Once you have the host key, install it on your KMS host with
slmgr /ipk <host key>followed byslmgr /atoto activate.
One thing that hasn’t changed: if you’re running Active Directory-Based Activation instead of a dedicated KMS host, the process is still just as painless as it was with Windows 10, install the client GVLK, and domain-joined machines pick up activation automatically with zero user interaction.