
- Microsoft windows kms client keys 64 Bit#
- Microsoft windows kms client keys pro#
- Microsoft windows kms client keys software#
- Microsoft windows kms client keys license#
Please note that the activation status is not displayed anywhere in the graphical interface of the Office apps. The current status of MS Office activation can be obtained with the command: cscript OSPP.VBS /dstatusĪs you can see, the result of the command shows that this copy of Office is activated on the KMS server (Office 16, VOLUME_KMSCLIENT channel), and 180 days left until the end of activation (every 7 days the client will automatically renew the activation for another 180 days). On the KMS server, the command must allow incoming traffic on port TCP 1688: New-NetFirewallRule -DisplayName "KMS_IN" -Direction Inbound -LocalPort 1688 -Protocol TCP -Action Allow To allow outgoing traffic on the client, use the following PowerShell command: New-NetFirewallRule -DisplayName "KMS_OUT" -Direction Outbound -RemotePort 1688 -Protocol TCP -Action Allow

For successful Office KMS activation, the port 1688 (by default) shouldn’t be blocked between the client, and the KMS server. The line indicates that the KMS server activated this copy of Office.
Microsoft windows kms client keys pro#
In this example for Office 2016 Pro Plus, the command to change the KMS key looks like this: XXXXX must be replaced with the corresponding GVLK product key from the table on Microsoft website. To change the current Office product key, you need to use the following command: cscript OSPP.VBS /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX.
Microsoft windows kms client keys license#
LICENSE DESCRIPTION: Office 16, RETAIL (MAK) channel Run the command cscript OSPP.VBS /dstatus and verify the following lines are listed: LICENSE NAME: Office 16, Office116PROPLusVL_MAK edition You can verify that the installed Office copy is activated with the KMS key. In order to not to go into the Office directory with the ospp.vbs utility each time, you can add the path to it to the PATH environment variable: set path=%path% C:\Program Files (x86)\Microsoft Office\Office16. To run the ospp.vbs script, you must specify the script server cscript executable each time.
Microsoft windows kms client keys 64 Bit#
The location of the ospp.vbs file depends on the version of Office and Windows type (32 or 64 bit see a table below).Ĭ:\Program Files\Microsoft Office\Office14Ĭ:\Program Files (x86)\Microsoft Office\Office14Ĭ:\Program Files\Microsoft Office\Office15Ĭ:\Program Files (x86)\Microsoft Office\Office15Ĭ:\Program Files\Microsoft Office\Office16Ĭ:\Program Files (x86)\Microsoft Office\Office16
Microsoft windows kms client keys software#
To manage the activation of all versions of Microsoft Office (starting from Office 2007) it distro includes a special vbs script- OSPP.VBS (Office Software Protection Platform), which is located in the directory with the MS Office installed. Using OSPP.VBS Script to Manage Office Product Key After installing such a GVLK key, clients automatically discover the KMS server in the domain and are activated on it. GVLK is a Microsoft public key unique to each Office/Windows edition, which is used by all corporate customers to activate volume license Office copies on the local KMS server or using the Active Directory Based activation.

First of all, you need to understand how the MAK Office activation differs from KMS.
