Sep 24, 2018  To deploy Microsoft Office 2019 for Mac with a Volume License. The VL Serializer must be installed on each Mac that you want to set up with a Volume License; If desired, the VL Serializer can be installed prior to downloading and installing the Office 2019 applications. Office Professional Plus 2016 64 Bit English (9803 downloads) Office.

This document shows how to convert Microsoft Office 2013 or Microsoft Office 2016 to and from KMS activation and MAK activation, as well as help determine which activation type is currently in use. These activations are available for faculty and staff using departmental machines. Please note that only Office Pro Plus can use KMS or MAK activation. Other editions are not compatible.

These instructions only apply to machines running Windows Vista, 7, 8.1, or 10. Machines running macOS do not use KMS or MAK activation. Instead, the Microsoft Volume License Serializer is run on a machine to create its own unique license file. This serializer can be found on the Campus Software Library under the section for Microsoft software.

See [Windows] Volume Activation 2.0 at UW-Madison for the full details of MAK and KMS activation at UW Madison.

Contents:

Converting Microsoft Office 2013 or 2016 from KMS to MAK Activation

1. If you are affiliated with the University, email help@doit.wisc.edu to request the University's Office 2013 or Office 2016 MAK activation key, otherwise use the product key which came with your copy of Office.
2. Launch Microsoft Word 2013 or Microsoft Word 2016
   • Click the File tab.
   • Click Account.
3. Click Change Product Key under Product Information.


4. Enter the MAK activation key from the help@doit.wisc.edu email in the field provided.


5. After you enter a good key, you will get the green check mark and the Continue button will change to an Install button


6. Click Install.
   • An additional alert may appear in the taskbar. If so, click it and select Yes.


7. Exit Microsoft Word.
8. Launch Word.
   • Click the File tab
   • Click Account.
   Under Product Information, Word should report that it is activated.

Converting Microsoft Office 2013 or 2016 from MAK to KMS Activation

1. Launch a command window with elevated privileges
   • Type cmd in the Search bar to locate the command window.
   • Right-click on cmd or Command Prompt and click Run as administrator from the context menu
   • Click Yes at the User Account Control prompt to open the command window with elevated privileges.
2. In the command prompt window, type the following command that corresponds to your version of Office:
   • Office 2013:
     • CD 'Program FilesMicrosoft OfficeOffice15'
     • Note: If this is the 32-bit version of Office installed onto a machine running the 64-bit version of Windows, use the following command instead:
       • CD 'Program Files (x86)Microsoft OfficeOffice15'
   • Office 2016:
     • CD 'Program FilesMicrosoft OfficeOffice16'
     • Note: If this is the 32-bit version of Office installed onto a machine running the 64-bit version of Windows, use the following command instead:
       • CD 'Program Files (x86)Microsoft OfficeOffice16'
3. Press Enter.


4. Type the following command that corresponds to your version of Office:
   • Office 2013:
     • cscript ospp.vbs /inpkey:YC7DK-G2NP3-2QQC3-J6H88-GVGXT
   • Office 2016:
     • cscript ospp.vbs /inpkey:XQNVK-8JYDB-WJ9W3-YJ8YR-WFG99
5. Press Enter.


6. Type the following command:
   • cscript ospp.vbs /sethst:ms-kms-1.services.wisc.edu
7. Press Enter.


8. Type the following command:
   • cscript ospp.vbs /act
9. Press Enter.


10. Close the command prompt window.

Determining Microsoft Office 2013 or 2016 Activation type

1. Launch a command window with elevated privileges
   • Type cmd in the Search bar to locate the command window.
   • Right-click on cmd or Command Prompt and click Run as administrator from the context menu
   • Click Yes at the User Account Control prompt to open the command window with elevated privileges.
2. In the command prompt window, type the following command that corresponds to your version of Office:
   • Office 2013:
     • CD 'Program FilesMicrosoft OfficeOffice15'
     • Note: If this is the 32-bit version of Office installed onto a machine running the 64-bit version of Windows, use the following command instead:
       • CD 'Program Files (x86)Microsoft OfficeOffice15'
   • Office 2016:
     • CD 'Program FilesMicrosoft OfficeOffice16'
     • Note: If this is the 32-bit version of Office installed onto a machine running the 64-bit version of Windows, use the following command instead:
       • CD 'Program Files (x86)Microsoft OfficeOffice16'
3. Press Enter.
4. Type the following command:
   • cscript ospp.vbs /dstatus
5. Press Enter.
6. Check your version:
   • If Office is KMS activated, you will see 'KMS_Client edition' in the LICENSE NAME field.
   
   
   • If Office is MAK activated, you will see 'MAK edition' in the LICENSE NAME field.
   
   
7. Close the Command Prompt window

Some background:

In my organisation I deploy software with Munki, previously with Office 2011, it was pretty easy to deploy and get a fully up to date install of Office 2011

• Install the full volume licence installer from the VLSC site which was version 14.3.0 and around 1Gb
• Let Munki apply the latest combo updater it has (14.5.8) and around 120Mb

And we’re done. Pretty easy and painless and about 1.1Gb of data to send to the client.

However, in Office 2016, Microsoft has sandboxed their applications, which is the right thing do™. However what this means is that any shared content the apps use such as frameworks, fonts, and proofing tools all need to be contained within each application bundle. Previously in Office 2011, the apps could get this content from a shared location such as /Library/Application Support

This means that our Office 2016 installer package is only about 1.3Gb, the installer then just copies the same files into each app bundle at install time via a postinstall script. That results in each app being rather large as you can see here.

It also means that the Office 2016 updates that Microsoft offer for each app are huge, approx 800Mb per app.

So now if we applied our same methodology of deploying Office 2011 to Office 2016 we would end up with something like this:

• Install the full Office 2016 VL installer (1.3GB)
• Let Munki apply each app update ~800Mb times 5 apps (Word, Excel, PowerPoint, OneNote, Outlook)

That means we are pushing about 5gb to the client just to install office. Thats insane.

Solution?

Well we only need the full VL installer for its special licensing package that generates the volume licence plist (/Library/Preferences/com.microsoft.office.licensingV2.plist)

Microsoft offer the latest version of the suite in a package that contains all the apps and is SKU-less, meaning no licensing (It can be licenced as 0365 or VL)

So we could just download the latest suite package which is about 1.3GB, then install that on our client machines, install the special licensing package on top to licence the suite and we’re done. We would only need to push about 1.3Gb to the client to have a fully up to date office 2016 installation. Thats much more manageable for remote sites with slow links, or even labs with lots of machines.

Any new updates to the apps would simply mean downloading the full suite package again, approx 1.3GB and pushing that to clients, still 10 times more than office 2011 combo updaters however, but much smaller than pushing each 2016 app update to the client.

Word is that Microsoft are working on Delta updates that will be much much smaller, but until then this might be a workable solution.

Where to get the latest full installer package?

The full suite package is available via the following FWLinks, its available via a CDN so choose the closest location to you for the fastest download.

Dublin:
Office 2016 for Mac suite: http://go.microsoft.com/fwlink/?LinkID= 532572

Puerto Rico:
Office 2016 for Mac suite: http://go.microsoft.com/fwlink/?LinkID=525133

Singapore:
Office 2016 for Mac suite: http://go.microsoft.com/fwlink/?LinkID= 532577

Wait what? How do I get that special licensing package though?Maxwell render for mac.

If you open the VL installer package that you got from the Microsoft VLSC site with something like Pacifist, you will see the package we are talking about

This package “Office15_all_volume_licensing.pkg” is the one we are after.

To extract just this package we need to expand the Volume_Installer.pkg and then flatten the volume_licencing.pkg

So bust open the terminal and use these commands:

Unpack the installer package into a new directory on our desktop. Note: this new directory should not already exist, the pkgutil command will create it

Now lets flatten the licensing package and save it on our desktop

So now we have standalone serialised package that can be deployed to any machine and it will generate the volume licence plist that office 2016 looks for.

Why not just package up and deploy the com.microsoft.office.licensingV2 plist?

In the past, a lot of people, myself included, would often just create a package of a pre-created license plist from one machine and then deploy that package to multiple machines. That was enough for Office to pickup the correct licensing and everything seemed good in the world.

However the official word from Microsoft is that this is bad ju-ju and we should stop doing this as it is unsupported and may break your Office install. Instead run the serializer package on every machine that requires it.

Microsoft plans to make the serialiser package available as a standalone package on the VLSC ISO, so this extracting and flattening process will soon be redundant. Until then this might help you out.