If you’ve installed your Volume licensed Microsoft Office copy with MAK key and now want to activate it using corporate KMS server—this article will show you the way on how to do it.
The Differences Between MAK and KMS Keys
First of all, you need to understand how the MAK Office activation differs from KMS. Microsoft offers two types of activation of its products to corporate customers under the Volume License program—MAK (Multiple Activation Key) and KMS (Key Management Service).
- MAK – this is the key to activate the Office through contacting Microsoft. Activation can be done automatically via the Internet or by phone. MAK is similar to a regular Windows retail key, which is sold in stores. One MAK key can activate several Offices copies in the organization. The limit depends on the type of company license agreement (Open, Select, Enterprise Agreement, and so on);
- KMS – the key is used only to activate the KMS server, and on all the computers that have installed the same public GVLK key. 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. After installing such a GVLK key, clients automatically discover the KMS server in the domain and are activated on it.
Using OSPP.VBS Script to Manage Office Product Key
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. The location of the ospp.vbs file depends on the version of Office and Windows type (32 or 64 bit; see table below).
|Office Version||Windows bitness||Path to OSPP.VBS|
|Office 2010||32-bit||C:\Program Files\Microsoft Office\Office14|
|Office 2010||64-bit||C:\Program Files (x86)\Microsoft Office\Office14|
|Office 2013||32-bit||C:\Program Files\Microsoft Office\Office15|
|Office 2013||64-bit||C:\Program Files (x86)\Microsoft Office\Office15|
|Office 2016/Office 2019||32-bit||C:\Program Files\Microsoft Office\Office16|
|Office 2016/Office 2019||64-bit||C:\Program Files (x86)\Microsoft Office\Office16|
To change the MAK key of installed MS Office copy to KMS, you need to perform the following actions:
- Run the elevated cmd and navigate to Office installation folder (in this example we are using the x86 Office 2016 version on the Windows10 x64 desktop);
Cd “C:\Program Files (x86)\Microsoft Office\Office16”
Tip1. To run the ospp.vbs script, you must specify the script server cscript executable each time.
Tip2. In order 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
You can verify that the installed Office copy is activated with the KMS key. Run the command cscript OSPP.VBS /dstatus and verify that the following lines are listed:
LICENSE NAME: Office 16, Office116PROPLusVL_MAK edition LICENSE DESCRIPTION: Office 16, RETAIL (MAK) channel
- To change the current Office product key, you need to use the following command:
cscript OSPP.VBS /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
XXXXX must be replaced with the corresponding GVLK product key from the table below. In this example for Office 2016 Pro Plus, the command to change the KMS key looks like this:
cscript OSPP.VBS /inpkey:XQNVK-8JYDB-WJ9W3-YJ8YR-WFG99
- To immediately activate a copy of Office on the KMS server, run the following command:
cscript OSPP.VBS /act
The <Product activation successful> line indicates that the KMS server activated this copy of Office.
Note. For successful Office KMS activation, the port 1688 (by default) shouldn’t be blocked between the client and the KMS server. 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
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
The current status of activation of MS Office can be obtained with the command:
cscript OSPP.VBS /dstatus
As 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).
Note. Please note that the activation status is not displayed anywhere in the graphical interface of the Office apps.
In case there is no SRV entry in domain DNS that allows clients to find the KMS server, the address and port of the KMS server can be set manually:
cscript OSPP.VBS /sethst:KMSRV1.theitbros.com cscript OSPP.VBS /setprt:1688
You can also try to find the address and port of the KMS server published in DNS using the nslookup tool (it is useful in corporate networks without KMS autodiscovery enabled). To find the KMS SRV Record in the theitbros.com domain, run the command:
nslookup -type=srv _vlmcs._tcp.theitbros.com
In the future, you can switch back to the KMS Autodiscover mode of the KMS server through DNS:
cscript OSPP.VBS /remhst
The OSPP.VBS script also allows you to control the Office activation on a remote computer over the network, the format of the command is:
cscript OSPP.VBS <Arguments> RemoteComputerName [username] [password]
KMS (GVLK) Keys for MS Office
This table contains the list of Generic Volume License Key for different Office versions:
|MS Office edition||KMS Setup Key (GVLK keys)|
|Office 2019 Professional Plus||NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP|
|Office 2019 Standard||6NWWJ-YQWMR-QKGCB-6TMB3-9D9HK|
|Office 2016 Professional Plus||XQNVK-8JYDB-WJ9W3-YJ8YR-WFG99|
|Office 2016 Standard||JNRGM-WHDWX-FJJG3-K47QV-DRTFM|
|Office 2013 Professional Plus||YC7DK-G2NP3-2QQC3-J6H88-GVGXT|
|Office 2013 Standard||KBKQT-2NMXY-JJWGP-M62JB-92CD4|
|Office 2010 Professional Plus||VYBBJ-TRJPB-QFQRF-QFT4D-H3GVB|
|Office 2010 Standard||V7QKV-4XVVR-XYV4D-F7DFM-8R6BM|
- RDP Error: Remote Desktop Can’t Find the Computer - September 17, 2020
- How to Seize FSMO Roles From Dead Domain Controller? - September 16, 2020
- Active Directory Schema Update - September 11, 2020