KMS Activation for Windows Server 2016



AskPFEPlat is in the process of a transformation to the new Core Infrastructure and Security TechCommunity, and will be moving by the end of March 2019 to our new home at (hosted at Please bear with us while we are still under construction!

We will continue bringing you the same great content, from the same great contributors, on our new platform. Until then, you can access our new content on either as you do today, or at our new site Please feel free to update your bookmarks accordingly!

Why are we doing this? Simple really; we are looking to expand our team internally in order to provide you even more great content, as well as take on a more proactive role in the future with our readers (more to come on that later)! Since our team encompasses many more roles than Premier Field Engineers these days, we felt it was also time we reflected that initial expansion.

If you have never visited the TechCommunity site, it can be found at On the TechCommunity site, you will find numerous technical communities across many topics, which include discussion areas, along with blog content.

NOTE: In addition to the AskPFEPlat-to-Core Infrastructure and Security transformation, Premier Field Engineers from all technology areas will be working together to expand the TechCommunity site even further, joining together in the technology agnostic Premier Field Engineering TechCommunity (along with Core Infrastructure and Security), which can be found at!

As always, thank you for continuing to read the Core Infrastructure and Security (AskPFEPlat) blog, and we look forward to providing you more great content well into the future!


Hi everyone.  Graeme Bray here with a quick article around KMS and Server 2016.  KMS and Server 2016 you say?  Shouldn’t I be using Active Directory Based Activation?  Yes, you should, but in case you are not, let’s go over the pre-requisites to activate Windows Server 2016 via KMS.

********* UPDATE (5/5/17)*****************

The requirements have been updated below to remove and add a required update.  There was a supersedence change that makes 3058168 superseded by the July 2016 Update Rollup.  Additionally, there is often an error saying that the update is not applicable to your machine.  To fix this issue, you need to install the latest Servicing Stack Update (SSU) for 2012 or 2012 R2.  Their KB’s and links are below:

Windows Server 2012 R2 / KB3173424

Windows Server 2012 / KB3173426


First, lets review the pre-requisite updates that must be installed.

If your KMS host is running Windows Server 2012, you need two updates:

* (NOTE: This has been superseded by the July 2016 Update Rollup)

o Direct Download: (NOTE: This has been superseded by the July 2016 Update Rollup)


o Direct Download:

If your KMS host is running Windows Server 2012 R2, you need two updates:

* (NOTE: This has been superseded by the July 2016 Update Rollup)

o Direct Download: (NOTE: This has been superseded by the July 2016 Update Rollup)


o Direct Download:

If your KMS host is running Windows Server 2008 R2:

* There is no update to allow Windows Server 2008 R2 to activate Windows Server 2016.  Windows Server 2008 R2 is in extended support.  During this phase, we only release security updates and do not release updates that add additional functionality.

Lets review what these updates add:

* The first update allows the activation of Windows 10 from Windows 8, 8.1, and Windows Server 2012 R2 based systems.

* The second is an update rollup that allows KMS to activate Windows 10 1607 long-term servicing branch (LTSB) systems and Windows Server 2016 clients.

KMS License Key

After that, all you need to do is add your KMS License Key from the Volume License site.

But wait, how do I find my KMS License Key?!  Have no fear, there is a KB article (and detailed steps) for you!

Retrieve KMS License Key from the VLSC for Windows Server 2016.

To resolve this problem, follow these steps:

1. Log on to the Volume Licensing Service Center (VLSC).

2. Click License.

3. Click Relationship Summary.

4. Click License ID of your current Active License.

5. After the page loads, click Product Keys.

6. In the list of keys, locate Windows Srv 2016 DataCtr/Std KMS

7. Install this key on the KMS host.

Client Licensing

After your KMS host is activated, use the Client Setup Keys to activate your shiny new Windows Server 2016 hosts.

What is a client setup key you ask?  A CSVLK is the key that is installed, by default, on your Volume License media that you pulled down day 1.  If you are using volume license media, no key change is required.

If you are converting an install from Retail, MSDN, etc, you will want to use the client setup key to convert to a Volume License key to allow activation.

Active Directory Based Activation

Graeme, this sure seems like a lot of work to get KMS working for Windows Server 2016.  Is there a better way to do this?

The recommendation at this point is to leave your existing KMS system alone.  Whether it is running on Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2, continue to service the machine via security and quality updates.  Allow your KMS system to activate down-level operating systems and Office installs (Windows 7, Windows Server 2008/2008 R2, and Office 2010).  Utilize Active Directory Based Activation (ADBA) for all new clients (Windows 8, 8.1, Windows Server 2012, 2012 R2, 2016, Windows 10, Office 2013, and Office 2016).

Active Directory Based Activation provides several key benefits:

1. Activation is near instantaneous when a system is brought online.  As soon as the system talks to Active Directory, the system is activated.

2. One less server to maintain and update.  Once all downlevel (2008 R2 & prior) systems are migrated, you can remove your KMS host.

3. AD-Based activation is forest wide.  KMS hosts require additional configuration to support multiple domains.

Have more questions?

Q: Where can I get even more details around KMS and AD Based Activation?

A: Refer to these other posts by one of my colleagues, Charity Shelbourne.

Q: Can Microsoft help me with this process?

A: Absolutely!  Reach out to your TAM and you can engage Premier Field Engineering for assistance.

Thanks for reading!

Graeme “Keeping KMS easy” Bray