Navigate / search

Windows 10 / Office 2016 – KMS Activation

 

Required Windows Server Updates

The following update is required for Windows 10 activation:

The following update is required for Office 2016 activation:

Windows 10 / Server 2016 requires at least a KMS server based on Windows Server 2012. Activation via Windows Server 2008 R2 is not possible!


Activation by Command Line

Step 1

Type the following command to integrate your volume license key to the KMS server.

If the key isn’t accepted by the server you will receive the error 0xC004F015.

For Windows 10 LTSB 1607 the Licence key “Windows Server 2016 Datacenter” is valid.

Step 2

Display the installation ID that is necessary for telephone activation.

Step 3

Activate your KMS key by calling Microsoft hotline for product actiavtion and enter your “Instllation ID” by telephone. You will receive a “Confirmation ID” that must be entered by the following command.

If the activation ID isn’t accepted you will receive the error 0xC004F04D. Retry the phone activation in most cases you just entered a wrong installation ID. Sometimes the hotline is telling you a wrong “Confirmation ID” or answers you in languages you have never heard about. I had that problems several times… Your only chane is to open a MS ticket to solve the problem. I’ve tried to solve problems like these with the activiation hotline but most of the guys are not familiar with the Windows activation.

You are done with the Windows 10 /  Server 2016 Key integration.

slmgr.vbs /dli

Step 4 – Office 2016

Type the following command to integrate your volume license key to the KMS server.

If the key isn’t accepted by the server you will receive the error 0xC004F015.

Step 5 – Office 2016

Display the installation ID that is necessary for telephone activation. You have to add “98EBFE73-2084-4C97-932C-C0CD1643BEA7” to receive the Office 2016 installation id otherwise you will receive the installation ID for Windows Server 2016 / Windows 10.

Step 6 – Office 2016

Activate your KMS key by calling Microsoft hotline for product actiavtion and enter your “Instllation ID” by telephone. You will receive a “Confirmation ID” that must be entered by the following command. You have to add ” 98EBFE73-2084-4C97-932C-C0CD1643BEA7” for Office 2016 activation otherwise you’ll try to activate Windows Server 2016 / Windows 10 with an Office “Confirmation ID”.

You are done with the Office 2016 Key integration.

slmgr.vbs /dli 98EBFE73-2084-4C97-932C-C0CD1643BEA7


Configure DNS

When the KMS configuration part is done you have to tell your Windows clients where to find the KMS host system. Therefore I recommend to set up a “SRV Resource Record” in your DNS as it is explained in detail at MS Technet: https://technet.microsoft.com/en-us/library/ff793405.aspx

There are also ways to configure a static entry in your Windows 10  OS deployment or Office 2016 deployment. But when your environment receives a change for example the hostname of your KMS or you have to replace your KMS server by another one you will get in trouble fixing all that static links. I’ve seen a lot of customers setting up static links to the KMS server which was easy to configure for the project first, but for the operations team it was a mess.

In most companies the DNS record will be created by the “Network Team”. So how can we ensure that these guys have done their work? Just type the following command on any Windows 10 client that is member of your domain.

Result

As you can see in this example there are two KMS servers available.


Common Errors

busy Error 0xC004F015

If you receive the error 0xC004F015 your entered key is invalid and can not be used by the KMS server. Check if all neccessarry updates were installed!

busy Error 0xc004f038

This error occures when not enough clients are registered at the KMS server yet. The KMS Server will start activating clients successfull when he receives 20 requests from different machines. (Office 2016 – 5 requests)

Check your “Current count” status:

  • Windows 10 / Server 2016 –  slmgr.vbs /dli
  • Office 2016 –  slmgr.vbs /dli 98EBFE73-2084-4C97-932C-C0CD1643BEA7

Leave a comment

name*

email* (not published)

website

This site uses Akismet to reduce spam. Learn how your comment data is processed.