KMS or Key Management Services is usually a Windows Server computer configured to be a KMS host computer by installing the Volume Activation Services role. When an Enterprise uses KMS keys to activate computers, it will need the KMS Host to verify. In this guide, we are sharing some KMS Activation Troubleshooting tips. While we have shared Volume Activation troubleshooting tips to resolve individual error code, in this post, we have covered some basic KMS Activation troubleshooting tips to get you started.
- What Is Windows Kms
- Windows 2008 Kms Client Key
- Windows Kms Client Activation Key
- Windows Kms Server
- Windows 2016 Kms Client Key
KMS Client Setup Key. KMS client setup key are the default key to redirect Windows to find a KMS server on the network. Those should be use only on a Windows 10 client to redirect them to KMS server if they were activated by a MAK key. By default, Windows will look for a KMS server automatically if no key is specified in the setup or after Windows installation. If you are converting a computer from a KMS host, MAK, or retail edition of Windows to a KMS client, install the applicable setup key (GVLK) from the following tables. To install a client setup key, open an administrative command prompt on the client, type slmgr /ipk and then press Enter. KMS Activator For Windows 10 Professional Free download. It provides (key management service) is a type of technology used by Microsoft in order to active Microsoft Products. During working, It inserts a new key into your system by replacing with the old one. It uses a technique by inserting a Product key which enforces the client machine to active against KMS server. Installing a KMS host key on a computer running Windows 10 allows you to activate other computers running Windows 10 against this KMS host and earlier versions of the client operating system Please refer to this documentation for a hint.
Most of us are aware that to configure KMS in Windows 10, open an elevated command prompt and execute one of the following commands:
- To install a KMS key, type slmgr.vbs /ipk <KmsKey>.
- To activate online, type slmgr.vbs /ato.
- To activate by using the telephone, type slui.exe 4.
After activating the KMS key, restart the Software Protection Service. If you face issues, read on.
Troubleshoot KMS Activation on Windows
Here are some common issues that can occur during KMS activations as well as steps for resolving them.
Is the KMS client computer activated?
To check if the client computer is properly activated, you can either check in the Control Panel System or run the SLMgr script in the command prompt. To check run Slmgr.vbs with the /dli command-line option.
It will give you details about the Windows installation and its activation and licensing status. The admin also gets to see the last five characters of partial product key as well.
The KMS client computer will not activate
When KMS is used to activate the computer, it needs a minimum count of computers to activate its client. If any of your clients receive an error “The KMS client computer will not activate”, you will need to check KMS host has a count of 5 at the minimum. Windows Server 2008 R2 KMS clients require a KMS count of 5 for activation.
Also, you need to check on the Application event log for event ID 12289 on both Client and Host.
On the KMS client machine check against the below-mentioned questions:
- Is the result code 0? Anything else is an error.
- Is the KMS host name in the event correct?
- KMS port is correct?
- Is the KMS host accessible?
- If the client is running a non-Microsoft firewall, does the outbound port need to be configured?
On the KMS host, look in the KMS event log for event ID 12290. Check this event for the following:
- Did the KMS host log a request from the client computer?
- Verify that the name of the KMS client is on the list.
- Verify that the client and KMS host can communicate.
- Did the client receive the response?
If there are no event logs for these questions, it is possible that the request from the client did not reach the KSM Host. Make sure that the routers in the company are not blocking traffic using TCP port 1688 (if the default port is used). Also, make sure the KSM client can reach the host properly.
What does this error code mean?
To find out the exact meaning of the error code in a KMS client or host machine from the Slmgr.vbs command, you can use SLUI.
Clients are not adding to the KMS count
If the KMS host assumes that the client computer looks identical, then it will not count them as separate KMS clients. To resolve this, run sysprep /generalize or slmgr /rearm to reset the client computer ID (CMID) and other product-activation information.
KMS hosts are unable to create SRV records
SRV records are created by KMS hosts on the DNS database so the KMS clients can detect them automatically. If the KMS host doesn’t have write access to the DNS database, then it doesn’t have proper permission. You will need to go through the Volume Activation Deployment Guide to fix this.
Only the first KMS host is able to create SRV records.
If the organization has more than one KMS host, the other hosts might not able to update the SRV RR. This will resolve when the SRV default permissions are changed. For more information about this issue, see the Volume Activation Deployment Guide.
I installed a KMS key on the KMS client.
This means that KMS keys, i.e., one that is meant to activate KMS host is set on the KMS client. To restore the computer to a KMS client, the admin will need to use setup keys with command slmgr.vbs -ipk.
Post this, restart the computer, and let it connect with the actual KMS host.
KMS Host Failover
In this situation, the only option is to set up a new host and use the same KMS host key on it. Post-activation makes sure to make sure KMS host has an SRV RR in the DNS database.
Post this; the KMS host will start finding out new clients, renew and activate them. This works when the KMS client computers are set to a fix KMS host IP. If they are set to auto-discovery, the client can choose another KMS host.
To update KMS client computers run this commandto set the KMS server and the port used for KMS activation;
This guide lists the most common issues, their resolution, and tips that one can face with KMS Server and Client.
Hope this helps!
TIP: Download this tool to quickly find & fix Windows errors automatically
Related Posts:
-->Applies to: Windows Server 2019, Windows Server Semi-Annual Channel, Windows Server 2016, Windows 10
Computers that are running volume licensed editions of Windows Server, Windows 10, Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 R2, Windows Vista, and Windows Server 2008 are, by default, KMS clients with no additional configuration needed.
Note
In the tables that follow, 'LTSC' stands for 'Long-Term Servicing Channel,' while 'LTSB' refers to the 'Long-Term Servicing Branch.'
To use the keys listed here (which are GVLKs), you must first have a KMS hostrunning in your deployment. If you haven't already configured a KMS host, seeDeploy KMS Activation for steps to set one up.
If you are converting a computer from a KMS host, MAK, or retail edition ofWindows to a KMS client, install the applicable setup key (GVLK) from thefollowing tables. To install a client setup key, open an administrative commandprompt on the client, type slmgr /ipk <setup key> and then press Enter.
If you want to… | …use these resources |
---|---|
Activate Windows outside of a volume-activation scenario (that is, you're trying to activate a retail version of Windows), these keys will not work. | Use these links for retail versions of Windows: |
Fix this error that you get when you try to activate a Windows 8.1, Windows Server 2012 R2 or newer system: “Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid”… | Install this update on the KMS host if it is running Windows 8.1, Windows Server 2012 R2, Windows 8, or Windows Server 2012. |
If you are running Windows Server 2008 R2 or Windows 7, be on the lookoutfor an update to support using those as KMS hosts for Windows 10 clients.
Windows Server Semi-Annual Channel versions
Windows Server, version 1903 and Windows Server, version 1809
Operating system edition | KMS Client Setup Key |
---|---|
Windows Server Datacenter | 6NMRW-2C8FM-D24W7-TQWMY-CWH2D |
Windows Server Standard | N2KJX-J94YW-TQVFB-DG9YT-724CC |
Windows Server, version 1803
Operating system edition | KMS Client Setup Key |
---|---|
Windows Server Datacenter | 2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG |
Windows Server Standard | PTXN8-JFHJM-4WC78-MPCBR-9W4KR |
Windows Server, version 1709
Operating system edition | KMS Client Setup Key |
---|---|
Windows Server Datacenter | 6Y6KB-N82V8-D8CQV-23MJW-BWTG6 |
Windows Server Standard | DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4 |
Windows Server LTSC/LTSB versions
Windows Server 2019
Operating system edition | KMS Client Setup Key |
---|---|
Windows Server 2019 Datacenter | WMDGN-G9PQG-XVVXX-R3X43-63DFG |
Windows Server 2019 Standard | N69G4-B89J2-4G8F4-WWYCC-J464C |
Windows Server 2019 Essentials | WVDHN-86M7X-466P6-VHXV7-YY726 |
Windows Server 2016
Operating system edition | KMS Client Setup Key |
---|---|
Windows Server 2016 Datacenter | CB7KF-BWN84-R7R2Y-793K2-8XDDG |
Windows Server 2016 Standard | WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY |
Windows Server 2016 Essentials | JCKRF-N37P4-C2D82-9YXRT-4M63B |
Windows 10, all supported Semi-Annual Channel versions
See the Windows lifecycle fact sheet for information about supported versions and end of service dates.
![Kms Kms](/uploads/1/2/6/0/126074579/404598168.png)
Operating system edition | KMS Client Setup Key |
---|---|
Windows 10 Pro | W269N-WFGWX-YVC9B-4J6C9-T83GX |
Windows 10 Pro N | MH37W-N47XK-V7XM9-C7227-GCQG9 |
Windows 10 Pro for Workstations | NRG8B-VKK3Q-CXVCJ-9G2XF-6Q84J |
Windows 10 Pro for Workstations N | 9FNHH-K3HBT-3W4TD-6383H-6XYWF |
Windows 10 Pro Education | 6TP4R-GNPTD-KYYHQ-7B7DP-J447Y |
Windows 10 Pro Education N | YVWGF-BXNMC-HTQYQ-CPQ99-66QFC |
Windows 10 Education | NW6C2-QMPVW-D7KKK-3GKT6-VCFB2 |
Windows 10 Education N | 2WH4N-8QGBV-H22JP-CT43Q-MDWWJ |
Windows 10 Enterprise | NPPR9-FWDCX-D2C8J-H872K-2YT43 |
Windows 10 Enterprise N | DPH2V-TTNVB-4X9Q3-TJR4H-KHJW4 |
Windows 10 Enterprise G | YYVX9-NTFWV-6MDM3-9PT4T-4M68B |
Windows 10 Enterprise G N | 44RPN-FTY23-9VTTB-MP9BX-T84FV |
Windows 10 LTSC/LTSB versions
What Is Windows Kms
Windows 10 LTSC 2019
Operating system edition | KMS Client Setup Key |
---|---|
Windows 10 Enterprise LTSC 2019 | M7XTQ-FN8P6-TTKYV-9D4CC-J462D |
Windows 10 Enterprise N LTSC 2019 | 92NFX-8DJQP-P6BBQ-THF9C-7CG2H |
Windows 10 LTSB 2016
Operating system edition | KMS Client Setup Key |
---|---|
Windows 10 Enterprise LTSB 2016 | DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ |
Windows 10 Enterprise N LTSB 2016 | QFFDN-GRT3P-VKWWX-X7T3R-8B639 |
Windows 10 LTSB 2015
Operating system edition | KMS Client Setup Key |
---|---|
Windows 10 Enterprise 2015 LTSB | WNMTR-4C88C-JK8YV-HQ7T2-76DF9 |
Windows 10 Enterprise 2015 LTSB N | 2F77B-TNFGY-69QQF-B8YKP-D69TJ |
Earlier versions of Windows Server
Windows Server 2012 R2
Operating system edition | KMS Client Setup Key |
---|---|
Windows Server 2012 R2 Server 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
Operating system edition | KMS Client Setup Key |
---|---|
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 Server 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 2008 R2
Operating system edition | KMS Client Setup Key |
---|---|
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 Server 2008
Operating system edition | KMS Client Setup Key |
---|---|
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
Windows 2008 Kms Client Key
Windows 8.1
Operating system edition | KMS Client Setup 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 Kms Client Activation Key
Windows 8
Operating system edition | KMS Client Setup Key |
---|---|
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
Operating system edition | KMS Client Setup Key |
---|---|
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 Kms Server
See also
Windows 2016 Kms Client Key
• Plan for Volume Activation