Install Kms Host Office 2016 Product
Oct 19, 2016 It will install the Office key files into the KMS store, and activate it (for Office 2010) or try to do so (for Office 2013+, if you face the vmw.exe bug too). 4) Repeat 1-3 for Office 2013, it will owerwrite kmshost.vbs. Then install Office 2016 key files as usual, installer will. All volume editions of Office 2016 client products are pre-installed with a Generic Volume License Key (GVLK) key, which supports automatic activation for both KMS and Active Directory-Based Activation, so you will not need to install a product key. This download contains an executable file that will extract and install KMS host license files.
So we're running a Windows 2008R2 server as our KMS server.
I've installed the Microsoft Office 2016 Volume License Pack from here
I've inputted my kms key , that for some reason I had to call MS to get?
Now on my workstation I initially upgraded my Office 2013 to 2016, since then i've also uninstalled everything and reinstalled and it will not automatically activate?
So on my machine I run cscript ospp.vbs /act and receive the following error
---Exiting-----------------------------
I've even tried forcing activation through VAMT and receive a error:
The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information
and when i look in event viewer i see:
Error operating on product: Application Name: Office . Exception System.Runtime.InteropServices.COMException (0xC004F074) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options) at Microsoft.Licensing.VolumeActivation.WmiConnection.ExecuteMethod(String queryString, String actionValue, Dictionary`2 wmiParameter) at Microsoft.Licensing.VolumeActivation.SoftwareLicensingProvider.ActivateProduct(Product product) at Microsoft.Licensing.VolumeActivation.SoftwareLicensingProvider.VolumeActivate(Product product) at Microsoft.Licensing.VolumeActivation.VolumeActivationWorker.OnDoWork(Product product) at Microsoft.Licensing.VolumeActivation.WmiProviderWorker.Work()
Not sure if i missing something? if anyone knows how a can resolve this i would be greatly appreciated.
Thanks
Applies to:Volume licensed versions of Office 2019 and Office 2016, including Project and Visio
All volume licensed versions of Office, including Project and Visio, have a Generic Volume License Key (GVLK) preinstalled. GVLKs support both Key Management Service (KMS) and Active Directory-based activation. On the KMS host computer configured to support volume activation of Office, you install and enable only one KMS host key to activate all volume licensed versions of Office.
If the KMS host computer is available and properly configured, activation of Office occurs transparently to the user. Office is activated the first time it runs, provided that there have been at least four previous activation requests to the KMS host computer. This is because the KMS host computer requires at least five requests before it begins activating clients.
You don't have to do anything else to enable activation of Office by KMS. KMS clients can locate a KMS host computer automatically by querying DNS for service (SRV) resource records (RRs) that publish the KMS service. For more information, see How DNS is used to find a KMS host computer.
If the network environment does not use SRV RRs, you can manually assign a KMS client to use a specific KMS host computer by configuring the HKEY_LOCAL_MACHINESoftwareMicrosoftOfficeSoftwareProtectionPlatform registry key on the KMS client. The KMS host computer name is specified by KeyManagementServiceName (REG_SZ), and the port is specified by KeyManagementServicePort (REG_SZ). The default port is 1688. These registry keys can also be set through by using ospp.vbs script. For more information about the ospp.vbs script, see Tools to manage volume activation of Office.
Configure KMS host caching
You can configure whether or not the last used KMS host computer is saved to the cache on the KMS client. If the KMS host computer is not cached, the KMS client will query DNS every time that activation is attempted. This means that the priority and weight parameters set for KMS host computers will be honored. If the KMS host computer is cached, the KMS client won't query DNS and instead will attempt to contact the cached KMS host computer that last resulted in successful activation.
To configure KMS host caching, you can use the opss.vbs script. For more information about the ospp.vbs script, see Tools to manage volume activation of Office.
To configure KMS host caching, open an elevated command prompt on the KMS client computer and go to the Program FilesMicrosoft OfficeOffice16 folder. If you installed the 32-bit version of Office on a 64-bit operating system, go to the Program Files (x86)Microsoft OfficeOffice16 folder.
To disable KMS host caching, type the following command, and then press ENTER:
To enable KMS host caching, type the following command, and then press ENTER:
Check the license status of Office
The following table describes the license state of the Office with respect to activation.
| License state | Description |
|---|---|
| Licensed | By default, the KMS client requests activation with the KMS host computer one time every seven days. (The number of days is configurable.) This design allows the maximum possible time for the client to be in the licensed state. After the client is successfully activated, it remains in the licensed state for 180 days. When in the licensed state, users do not see any notification dialog boxes prompting them to activate the client. After 180 days, the activation attempt process resumes. If activation is continually successful, the whole activation experience is transparent to the user. |
| Out-of-tolerance | If activation does not occur during the 180-day period, Office goes into the out-of-tolerance state for 30 days. Users then see notifications that request activation. |
| Unlicensed notification | If activation does not occur during the out-of-tolerance state, Office goes into the unlicensed notification state. Users then see notifications that request activation and a red title bar. |
Kms Install Office 2016 Key
You use the ospp.vbs script with the /dstatusall option to check the license state for all Office clients. Use the /dstatus option to check the status of the local client. For more information about using the ospp.vbs script, see Tools to manage volume activation of Office.