Activate windows 10 with kms server

KMS client setup keys

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.

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 host running in your deployment. If you haven’t already configured a KMS host, see Deploy KMS Activation for steps to set one up.

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.

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 lookout for an update to support using those as KMS hosts for Windows 10 clients.

Windows Server Semi-Annual Channel versions

Windows Server, version 1909, version 1903, and 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 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.

Источник статьи: http://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys

Activate using Key Management Service

  • Windows 10
  • Windows 8.1
  • Windows 8
  • Windows 7
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2

Looking for retail activation?

There are three possible scenarios for volume activation of WindowsВ 10 or Windows ServerВ 2012В R2 by using a Key Management Service (KMS) host:

  • Host KMS on a computer running WindowsВ 10
  • Host KMS on a computer running Windows ServerВ 2012В R2
  • Host KMS on a computer running an earlier version of Windows

Key Management Service in WindowsВ 10

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, such as WindowsВ 8.1 or WindowsВ 7. Clients locate the KMS server by using resource records in DNS, so some configuration of DNS may be required. This scenario can be beneficial if your organization uses volume activation for clients and MAK-based activation for a smaller number of servers. To enable KMS functionality, a KMS key is installed on a KMS host; then, the host is activated over the Internet or by phone using Microsoft activation services.

Configure KMS in Windows 10

To activate, use the slmgr.vbs command. Open an elevated command prompt and run one of the following commands:

  • To install the KMS key, type slmgr.vbs /ipk .
  • To activate online, type slmgr.vbs /ato .
  • To activate by telephone, follow these steps:
    1. Run slmgr.vbs /dti and confirm the installation ID.
    2. Call Microsoft Licensing Activation Centers worldwide telephone numbers and follow the voice prompts to enter the installation ID that you obtained in step 1 on your telephone.
    3. Follow the voice prompts and write down the responded 48-digit confirmation ID for OS activation.
    4. Run slmgr.vbs /atp \ .

For more information, see the information for WindowsВ 7 in Deploy KMS Activation.

Key Management Service in Windows ServerВ 2012В R2

Installing a KMS host key on a computer running Windows Server allows you to activate computers running Windows ServerВ 2012В R2, Windows ServerВ 2008В R2, Windows ServerВ 2008, Windows 10, WindowsВ 8.1, WindowsВ 7, and Windows Vista.

You cannot install a client KMS key into the KMS in Windows Server.

This scenario is commonly used in larger organizations that do not find the overhead of using a server a burden.

If you receive error 0xC004F015 when trying to activate WindowsВ 10 Enterprise, see KB 3086418.

Configure KMS in Windows ServerВ 2012В R2

Sign in to a computer running Windows Server 2012 R2 with an account that has local administrative credentials.

Add the Volume Activation Services role, as shown in Figure 4.

Figure 4. Adding the Volume Activation Services role in Server Manager

When the role installation is complete, click the link to launch the Volume Activation Tools (Figure 5).

Figure 5. Launching the Volume Activation Tools

Select the Key Management Service (KMS) option, and specify the computer that will act as the KMS host (Figure 6). This can be the same computer on which you installed the role or another computer. For example, it can be a client computer running Windows 10.

Figure 6. Configuring the computer as a KMS host

Install your KMS host key by typing it in the text box, and then click Commit (Figure 7).

Figure 7. Installing your KMS host key

If asked to confirm replacement of an existing key, click Yes.

After the product key is installed, you must activate it. Click Next (Figure 8).

Figure 8. Activating the software

The KMS key can be activated online or by phone. See Figure 9.

Figure 9. Choosing to activate online

Now that the KMS host is configured, it will begin to listen for activation requests. However, it will not activate clients successfully until the activation threshold is met.

Verifying the configuration of Key Management Service

You can verify KMS volume activation from the KMS host server or from the client computer. KMS volume activation requires a minimum threshold ofВ 25 computers before activation requests will be processed. The verification process described here will increment the activation count each time a client computer contacts the KMS host, but unless the activation threshold is reached, the verification will take the form of an error message rather than a confirmation message.

If you configured Active Directory-based activation before configuring KMS activation, you must use a client computer that will not first try to activate itself by using Active Directory-based activation. You could use a workgroup computer that is not joined to a domain or a computer running WindowsВ 7 or Windows ServerВ 2008В R2.

To verify that KMS volume activation works, complete the following steps:

On the KMS host, open the event log and confirm that DNS publishing is successful.

On a client computer, open a Command Prompt window, type Slmgr.vbs /ato, and then press ENTER.

The /ato command causes the operating system to attempt activation by using whichever key has been installed in the operating system. The response should show the license state and detailed Windows version information.

On a client computer or the KMS host, open an elevated Command Prompt window, type Slmgr.vbs /dlv, and then press ENTER.

The /dlv command displays the detailed licensing information. The response should return an error that states that the KMS activation count is too low. This confirms that KMS is functioning correctly, even though the client has not been activated.

For more information about the use and syntax of slmgr.vbs, see Slmgr.vbs Options.

Key Management Service in earlier versions of Windows

If you have already established a KMS infrastructure in your organization for an earlier version of Windows, you may want to continue using that infrastructure to activate computers running WindowsВ 10 or Windows ServerВ 2012В R2. Your existing KMS host must be running Windows 7 or later. To upgrade your KMS host, complete the following steps:

Источник статьи: http://docs.microsoft.com/en-us/windows/deployment/volume-activation/activate-using-key-management-service-vamt