Windows and Office 2016 KMS

You can combine both the Windows and Office 2016 Key Management Service (KMS) roles onto the same server. An ideal host would be a Domain Controller running Server Core, which is something I've done in the past and won't impact on the DC roles. For larger environments, you can dedicate a VM. 

To start, ensure your build is fully patched. Download and run the Microsoft Office 2016 Volume License Pack installer with the default options:


Create two firewall rules via PowerShell to permit tcp:1688 for KMS client communications and optionally permitting ICMP ping requests:

New-NetFirewallRule -DisplayName "KMS" -Direction Inbound -LocalPort 1688 -Protocol TCP -Action Allow
Set-NetFirewallRule -DisplayName "File and Printer Sharing (Echo Request – ICMPv4-In)" -enabled True
Import and activate the Windows KMS key:


slmgr /ato 

Import and activate the Office 2016 KMS key:


slmgr /ato 98EBFE73-2084-4C97-932C-C0CD1643BEA7

Test the activation by manually pointing a client to the new KMS:

slmgr /skms

slmgr /ato

Note: The KMS requires a minimum of five product activation requests before it will begin activating clients.

To monitor activations on the KMS for Windows:

slmgr /dlv

For Office 2016:

slmgr /dlv 98EBFE73-2084-4C97-932C-C0CD1643BEA7 (Display Office 2016 KMS activation status)

If you are replacing an existing KMS, update the srv _vlmcs._tcp SRV DNS record or create another for multiple KMS'; set the successors SRV record a higher priority/weight for it to receive requests as a priority over the other.