Due to the release of the final RTM version of Microsoft Office 2016, corporate clients can migrate to a new Office platform. In this article we’ll deal with the peculiarities of MS Office 2016 activation on a corporate KMS server (FAQ about Key Management Service). It is supposed that we already have the deployed KMS activation server running Windows Server 2012 R2 or other Windows versions (see the list of the supported operating systems below).
By using the KMS server, corporate clients can activate Office products inside the corporate network without connecting to Microsoft activation servers in the Internet. Earlier we have already considered the peculiarities of MS Office 2013 activation in the corporate environment, and the main principles and approaches to Office 2016 activation on a KMS server stayed unchanged.
A KMS server for Office 2016 can run on the following OS versions:
- Windows 7 (KB2757817 installation required)
- Windows 8.1
- Windows Server 2008 R2 (KB2757817 installation required)
- Windows Server 2012 / Windows Server 2012 R2
- Windows 10
2 activation types are supported:
- A common one, using KMS server
- Active Directory-Based Activation, with the AD schema version Windows Server 2012 or higher
First of all you have to find and copy a KMS Host key for Office 2016 in your personal section on Microsoft Volume Licensing Service Center (VLSC) website.
In the next step download the KMS extension package — Microsoft Office 2016 Volume License Pack (https://www.microsoft.com/en-us/download/details.aspx?id=49164). Run the file you have downloaded (office2016volumelicensepack_4285-1000_en-us_x86.exe) on your KMS server with administrator privileges.
During installation the Volume Activation Tools window appears, where you have to select the activation type (KMS or ADBA). Both variants are considered below.
KMS Activation of Office 2016
If you are going to use the common 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 grant your KMS server the direct Internet access.
After your KMS server is activated on Microsoft websites, the current KMS server configuration is displayed. In the product list, the entry Name: Office 16, VOLUME_KMS_channel with the licensing status Licensed will appear.
Exit the wizard, and Software Protection service will be restarted.
Office 2016 Activation Using Active Directory
If you are going to use Active Directory-Based Activation for the automatic activation of Office 2016 on the computers in the AD domain, select Active Directory-Based Activation as a volume activation method in Volume Activation Tools. This method of activation will work in Windows 8.1, Windows Server 2012 / 2012 R2 and Windows 10.
Then you have to enter the same KMS Host key (CSVLK) and specify its name (optional).
Now you only have to activate this KMS key.
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 activation):
slmgr.vbs /dlv 98ebfe73-2084-4c97-932c-c0cd1643bea7
KMS server is ready to activate clients.
How to Configure MS Office 2016 Clients to Be Activated on the KMS Server
To immediately activate the new Office version on the client computer, run these commands one by one (in the command prompt with the administrator privileges):
CD \Program Files\Microsoft Office\Office16
Specify the name of the KMS server:
cscript ospp.vbs /sethst:kms01.woshub.com
Activate the product:
cscript ospp.vbs /act
The current activation status can be obtained using the command:
cscript ospp.vbs /dstatusall
GVLK for Microsoft Office 2016
All corporate Office 2016 versions are installed with public Generic Volume License Keys (GVLK). Due to them, all product versions are automatically activated if there is the KMS server in the network. So, as a rule, you don’t need to enter your GVLK.
If necessary, a product key can be changed as follows:
cscript ospp.vbs /inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx