Microsoft Office

Configuring KMS Server for MS Office 2019/2016 Volume Activation

By December 23, 2019 No Comments

In this article we’ll deal with the peculiarities of MS Office 2019 and Office 2016 volume activation on a corporate KMS server. It is supposed that you already have the deployed KMS server on Windows Server 2012 R2 / 2019 or other Windows versions.

Corporate customers can activate Office products inside the corporate network by using the local KMS server without connecting to Microsoft activation servers in the Internet.

System Requirements for the MS Office 2019/2016 KMS Server

A KMS server for Office can run on the following Windows OS versions:

  • KMS server for Office 2016 – requires OS not older than Windows Server 2008 R2 or Windows 7 SP 1 with the KB2757817 installed (yes, you can deploy a KMS server even on a desktop Windows edition );
  • KMS server for Office 2019 – requires OS version not lower than Windows Server 2012 or Windows 8.1.

Two types of enterprise volume activation are supported:

  • Activation on a dedicated KMS server;
  • Activation through the domain – ADBA (Active Directory-Based Activation), requires the domain functional level at least Windows Server 2012.

Updating KMS Server to Support Office 2019/2016 Volume Activation

First of all, you have to find and copy a KMS Host key for Office 2019 or 2016 in your personal section on Microsoft Volume Licensing Service Center (VLSC) website.

Microsoft Volume Licensing Service Center (VLSC) website

The next step is to download and install on the KMS server the following extension package – Microsoft Office Volume License Pack. This small package (about 400 Kb) contains the files necessary for the KMS server to be able to receive and process activation requests from MS Office clients. Depending on the version of Office that you plan to use, you must download and install the correct version of the Volume License Pack:

download office 2019 volume license pack

Run the file volumelicensepack you have downloaded on your KMS as an administrator.

Install Microsoft Office 2016 Volume License Pack

During installation the Volume Activation Tools window appears, where you have to select the activation type (KMS or ADBA). Both options are described below.

If you are going to use the standard KMS activation, select Key Management Service, specify the FQDN name of your KMS server and the KMS Host Key you got earlier.

Then select the activation method: online or by phone. In the first case you will have to temporary provide your KMS server with the direct Internet access.

kms host activate online

After your KMS server is activated on Microsoft, the current KMS server configuration is displayed. In the Product Key Management list, the entry Name: Office 16, VOLUME_KMS_channel (or Office 19, VOLUME_KMSCLIENT channel) with the licensing status Licensed should appear.
Note. In Windows Firewall, in order to connect to port TCP 1688 on the server an additional rule should be enabled. If necessary, this rule must be enabled manually using the command:

Enable-NetFirewallRule -Name SPPSVC-In-TCP

Close the Volume Activation wizard, and Software Protection service will be restarted.

Office 16, VOLUME_KMS_channel

You can get information about the installed KMS key for your version of Office as follows:

For Office 2019 – cscript slmgr.vbs /dlv 70512334-47B4-44DB-A233-BE5EA33B914C

For Office 2016 – cscript slmgr.vbs /dlv 98ebfe73-2084-4c97-932c-c0cd1643bea7

If your KMS server for Office 2019 is successfully configured, something like this will appear:

Name: Office 19, OfficeKMSHostVL_KMS_Host edition
Description: Office 19, VOLUME_KMS channel
Activation ID: 70512334-47B4-44DB-A233-BE5EA33B914C
License Status: Licensed

Tip. If the automatic activation from Volume Activation Tools was completed with an error, then you need to try to activate the KMS server manually. To do this, restart the Software Protection service:

net stop sppsvc && net start sppsvc/code>

restart KMS - Software Protection service

and run the command:

slmgr /ato 98ebfe73-2084-4c97-932c-c0cd1643bea7 (for Office 2016)

or

slmgr.vbs /ato 70512334-47B4-44DB-A233-BE5EA33B914C (for Office 2019)

Office 2019/2016 Activation Using Active Directory (ADBA)

If you are going to use ADBA for the automatic activation of Office 2019/2016 on the computers in the AD domain, select Active Directory-Based Activation as a volume activation method in Volume Activation Tools. This activation method works only for Windows 10/ 8.1 and Windows Server 2019 / 2016 / 2012 / 2012 R2.

ms office 2016 adba activation

Then you have to enter the same KMS Host key (CSVLK) and specify its name (optional).

install kms host key for ms office 2016

Now you only have to activate your KMS key.

office 2016 kms host

A warning that a new object will be created in the AD forest appears. Therefore, to properly install the KMS server for ADBA activation, you will need Enterprise Admin privileges.

office 2016 vat: adding ADBA object to the domain forest

In this case, additional entries will appear in the domain configuration branch CN=Activation Objects,CN=Microsoft SPP,CN=Services,CN=Configuration.

CN=Activation Objects,CN=Microsoft SPP,CN=Services,CN=Configuration

Close the VAT window, and press ENTER in the update tool console. The information about the installed KMS key can be obtained using SKU-ID (displayed in the final step of the KMS server installation):

slmgr.vbs /dlv 98ebfe73-2084-4c97-932c-c0cd1643bea7 – for Office 2016

slmgr.vbs /dlv 70512334-47B4-44DB-A233-BE5EA33B914C – for Office 2019

Now this KMS server is ready to activate clients with Office 2019/2016 joined to the Active Directory domain.

Configuring MS Office 2019/2016 clients for Activation on the KMS Server

You need to install a special corporate edition of Office 2016 on the users’ computers (you can download it from the personal section of the Microsoft VLSC licensing site). In this version, a special KMS (GVLK) key is preinstalled (however, you can change the product key for a usual Office version installed with the retail, MAK or OEM key).Starting with Office 2019, Microsoft uses Click-to-Run (C2R) technology instead of traditional MSI packages to install enterprise products. Unlike previous versions, you can’t download Office 2019 products from your personal account on the Volume Licensing Service Center website. To deploy Office 2019 products (including Visio and Project), you must use the Office Deployment Tool (ODT). In addition, you can install Office 2019 only on Windows 10 devices.

If you have a valid DNS record for the KMS server in the domain (you can find a KMS server in a domain with the command: nslookup -type=srv _vlmcs._tcp.contoso.com), and you installed the corporate edition of MS Office (Volume License), then a copy of Office should activate automatically after installation on a computer in the AD domain.

To immediately activate the Office on the client computer, run these commands one by one (in the elevated command prompt):

CD \Program Files\Microsoft Office\Office16
Note. For a 32-bit Office version installed on a Windows x64 version, another command is used:

CD \Program Files (x86)\Microsoft Office\Office16

You can specify the KMS server manually:

cscript ospp.vbs /sethst:kms01.contoso.com

You can also specify the name or IP address of the KMS server through the following REG_SZ registry parameter KeyManagementServiceName in the HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform\ (you can deploy this registry key in the domain using GPO).

If the KMS server is running on a non-standard port (not on 1688), you can change the port on the client like this:

cscript ospp.vbs /setprt:1689

Or through the registry: parameter KeyManagementServicePort in the HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform.

Activate your Office product copy of on the KMS server:

cscript ospp.vbs /act

cscript ospp.vbs - activating office2016 on KMS from cmd

The presence of the following lines indicates that your copy of Office 2016 has been successfully activated:

License Name: Office 16, Office16ProPlusVL_KMS_client edition
License description: Office 16, VOLUME_KMSCLIENT channel
<Product activation successful>

With the help of the following command, you can get information about the client activation history on the KMS server (you are searching for entries with the Event ID: 12288):

cscript ospp.vbs /dhistorykms

To allow performing Office activation for the non-admin users, run the command:

cscript ospp.vbs /puserops

If you want to allow KMS activation only under administrator account, run:

cscript ospp.vbs /duserops

If Office 2019/2016 activation errors occur, more detailed information about the errors can be obtained using the command:

cscript ospp.vbs /ddescr:0xC004F042

where 0xC004F042 is your activation error code.

If you need to activate Office 2019/2016 on a remote computer, use the following format command:

cscript OSPP.VBS <Options> remotePCname [username] [password]Note. To delay Office activation for 30 days (up to 5 times), you can use the tool  ospprearm.exe.

You can check the current Office 2019/2016/365 activation status using the command:

cscript ospp.vbs /dstatusall

Note. In order the KMS server to start activating clients, it has to receive at least 5 product activation requests from the clients (activation threshold). If there are not enough requests, you will see an error on the clients:

LICENSE STATUS:  ---OOB_GRACE---
ERROR CODE: 0x4004F00C
ERROR DESCRIPTION: The Software Licensing Service reported that the application is running within the valid grace period.

The detailed information can be found in the KMS section of the event log (look for the Event ID 12290).

GVLK Keys for Microsoft Office 2019 and 2016

All corporate Office 2016/2019 versions are installed with Generic Volume License Keys (GVLK). These keys are public and accessible to everyone on the Microsoft TechNet. Due to them, all Office product versions are automatically activated if there is the KMS server in the domain network. So,  in most cases, it is not required to specify the GVLK key for Office.

A complete list of official public GVLK keys for MS Office 2016 and 2019 can be found here: https://technet.microsoft.com/en-us/library/dn385360(v=office.16).aspx.

Product nameGVLK key for KMS activation
Office Professional Plus 2019NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
Office Standard 20196NWWJ-YQWMR-QKGCB-6TMB3-9D9HK
Project Professional 2019B4NPR-3FKK7-T2MBV-FRQ4W-PKD2B
Project Standard 2019C4F7P-NCP8C-6CQPT-MQHV9-JXD2M
Visio Professional 20199BGNQ-K37YR-RQHF2-38RQ3-7VCBB
Visio Standard 20197TQNQ-K3YQQ-3PFH7-CCPPM-X4VQ2
Access 20199N9PT-27V4Y-VJ2PD-YXFMF-YTFQT
Excel 2019TMJWT-YYNMB-3BKTF-644FC-RVXBD
Outlook 20197HD7K-N4PVK-BHBCQ-YWQRW-XW4VK
PowerPoint 2019RRNCX-C64HY-W2MM7-MCH9G-TJHMQ
Publisher 2019G2KWX-3NW6P-PY93R-JXK2T-C9Y9V
Skype for Business 2019NCJ33-JHBBY-HTK98-MYCV8-HMKHJ
Word 2019PBX3G-NWMT6-Q7XBW-PYJGG-WXD33
Office Professional Plus 2016XQNVK-8JYDB-WJ9W3-YJ8YR-WFG99
Office Standard 2016JNRGM-WHDWX-FJJG3-K47QV-DRTFM
Project Professional 2016YG9NW-3K39V-2T3HJ-93F3Q-G83KT
Project Standard 2016GNFHQ-F6YQM-KQDGJ-327XX-KQBVC
Visio Professional 2016PD3PC-RHNGV-FXJ29-8JK7D-RJRJK
Visio Standard 20167WHWN-4T7MP-G96JF-G33KR-W8GF4
Access 2016GNH9Y-D2J4T-FJHGG-QRVH7-QPFDW
Excel 20169C2PK-NWTVB-JMPW8-BFT28-7FTBF
OneNote 2016DR92N-9HTF2-97XKM-XW2WJ-XW3J6
Outlook 2016R69KK-NTPKF-7M3Q4-QYBHW-6MT9B
PowerPoint 2016J7MQP-HNJ4Y-WJ7YM-PFYGF-BY6C6
Publisher 2016F47MM-N3XJP-TQXJ9-BP99D-8K837
Skype for Business 2016869NQ-FJ69K-466HW-QYCP2-DDBV6
Word 2016WXY84-JN2Q9-RBCCQ-3Q3J3-3PFJ6

If necessary, you can change the Office product key to a GVLK as follows:

cscript ospp.vbs /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

KMS Activation Error “vmw.exe has stopped working” on Windows Server 2016

If you are trying to install a KMS server for Office 2019/2016 on the Windows Server 2016, keep in mind that it has a number of problems with the launch of the Volume Activated Services Tool. When you try to activate an Office 2019/2016 KMS server through the Volume Activated Services GUI, you can receive an error:

Vmw.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.
Vmw.exe has stopped working then activate Office 2016 KMS server

I’ve mentioned before that VAMT currently supports only operating systems up to Windows 8.1. And when installing the KMS server role on Windows Server 2016 or Windows 10, the executable file Vmw.exe crashes.

As a workaround, you need to activate the KMS server from the command prompt after installing volumelicensepack. Install the KMS Host key (which you got with VLSC) with the command:

slmgr -ipk <Office_2016_2019_KMS_Host_Key>

install kms host key for office 2016

Then activate the KMS server itself (you need direct Internet access):

slmgr.vbs /ato 98ebfe73-2084-4c97-932c-c0cd1643bea7

For Office 2019, use the SKU ID – 70512334-47B4-44DB-A233-BE5EA33B914C.

activating office16kmsostv_kms_host_editionl

Now your KMS server based on Windows Server 2016 is activated and can be used to activate clients.

Leave a Reply