Add Oct 19, 2016 Windows Server 2016 Volume Activation Tips (KMS host key) was. How to: Setup and configure a Microsoft Key Management Service (KMS). Vlmcsd is a fully Microsoft compatible KMS server that provides activation. Use Word 2016 to open documents created in earlier versions of. Volume license editions of Office 2016. This download contains an executable file that will extract and install KMS host. Microsoft Office Compatibility. Office 2016 kms host key will only work with Office 2016. Installing and configuring KMS server.
Windows Server 2016 KMS – Office 2016 & Server16/Win10 KMS Recently, we found that Server 2016 standard was having issues using the volume activation tools that are built in. Instead of using the VAT role, we elected to build our KMS server through command line. In this tutorial, I will walk you through the steps necessary to complete your new KMS install using Server 2016 Standard. We are installing a KMS server for Server 2016, Windows 10, and Office 2016 Pro Plus clients. (Other versions also activate as it is backwards compatible.) Note: We are using VMware Hypervisor 6.5 (Free), and our KMS server is running as a VM using Windows Server 2016 Standard (with desktop experience). Screen capture images can be browsed here.
Create a Windows Server 2016 Server (any edition). Set the timezone, name (and join) your server with your Active Directory. Enable Remote Desktop and set a static IP address (optional).
Check for, and install, all windows updates. Reboot the server. Install the Volume Activation Services Role through the server manager. Click next through the entire process leaving the defaults. (This GUI is what crashes for us, which is why we are using command line.). Reboot the server once the installation completes. Visit the Microsoft Volume Licensing Center and obtain your KMS keys for Office 2016 and Server 2016.
Keep these for future reference. While on the volume site, download “Office Professional Plus 2016 Key Management Service Host”. It will be an ISO file. Extract the ISO to C: kms or an appropriate location.
Use an elevated command prompt for all of the following steps. Install the Office 2016 KMS Host pack (What we extracted to C: kms). cd c: kms. cscript kmshost.vbs. After the VAT popup appears, close VAT and hit enter twice to return to a standard command line. Install the KMS keys for Windows and Office, one at a time, waiting for the confirmation that the key has been installed prior to continuing to the next.
slmgr.vbs -ipk. slmgr.vbs -ipk. Export the licensing information. This is for two reasons. First, to make sure both keys have been inserted correctly, and to obtain the activation ID.
cd c: windows system32. cscript slmgr.vbs -dlv all C: kms export.txt. cscript must be used to export the information into a txt file. Open the recently created export.txt file, and scroll to the licensed products. Copy the Activation ID‘s for both products and keep for the next step. NOTE: The Activation ID and Application ID are NOT the same, so make sure you obtain the correct ID. The easiest way to find the correct product is to locate the Installation ID.
![Office Office](http://www.queensu.ca/its/sites/webpublish.queensu.ca.itswww/files/images/software/msoffice/outlook/Office%202011%20(Mac)/office2011-install-two.png)
It will only be present on the two products that we have installed a key on (even though we will not be using the Installation ID.). Activate your product keys. Do each command one at a time, waiting for the confirmation before moving to the next.
slmgr.vbs -ato. slmgr.vbs -ato.
Confirm that your products are activated and licensed. cscript slmgr.vbs -dlv all C: kms export2.txt. Confirm that the two products identified before have “licensed” as their licensing status. Now your server is licensing clients. There are thresholds that will determine when activation starts.
Windows Server will activate after a count of 5. Windows 10 will activate after a count of 25. Office 2016 will activate after a count of 5. Additional Information about KMS: A Server 2016 KMS key will activate all server editions up to 2016. It will also activate all Windows Client editions up to Windows 10 including 7, 8 and 8.1. The Office 2016 Professional Plus key will activate both Pro Plus and Standard Office 2016 installations.
Post navigation.
. Dedicated KMS server;. Activation through the domain – ADBA (Active Directory-Based Activation), requires the domain functional level at least Windows Server 2012. Installing the KMS server to activate Office 2016 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.
On the next step download the KMS extension package — Microsoft Office 2016 Volume License Pack. Run the file you have downloaded (office2016volumelicensepack4285-1000en-usx86.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 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. 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 and run the command: slmgr /ato 98ebfe73-2084-4c97-932c-c0cd1643bea7/code Office 2016 Activation Using Active Directory (ADBA) 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 activation method works only for Windows 8.1, Windows Server 2016 / 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 your KMS key. A warning that a new object will be created in the AD forest appears.
![Install Kms Host Office 2016 Compatibility Install Kms Host Office 2016 Compatibility](/uploads/1/2/5/4/125405038/214528887.jpg)
Therefore, to properly install the KMS server for ADBA activation, you will need Enterprise Admin privileges. In this case, additional entries will appear in the domain configuration branch 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 Now this KMS server is ready to activate clients with Office 2016 joined to the Active Directory domain. Configuring MS Office 2016 clients for activation on the KMS server On the users’ computers, you need to install a special corporate edition of MS Office 2016 product (you can download it from the personal cabinet of the Microsoft volume licensing site – VLSC).
In this editions, a special GVLK key is preinstalled and after installation of such MS Office 2016 copy, it automatically tries to find the KMS server in the domain through a special DNS record (however, you can change the key from the usual Office version installed with the retail, MAK or OEM key). To immediately activate the Office on the client computer, run these commands one by one (in the command prompt with the administrator privileges): CD Program Files Microsoft Office Office16. In order the KMS server to start activating clients, it has to receive at least 5 product activation requests from the clients (activation threshold). The information can be found in the KMS section of the event log (look for the Event ID 12290). GVLK for Microsoft Office 2016 All corporate Office 2016 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 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. Do I have to have Office 2016 installed on the computer that is running the KMS? When I run the cscript, it says everything is fine, and it opens the Volume Licensing Tool, but the tool doesn’t give me the option to choose a product, and although it accepts the Office key, I don’t see any change in the products being managed. This is a 2012 r2 server that is working fine for activating Windows 7 work stations. I have been told that I can be running the KMS activation for Office on the same server as for Windows, but is that not correct? It’s a file server and secondary domain controller, so naturally I don’t have Office installed.