The change is the new second pkg: “MicrosoftOffice2016VLSerializer.pkg” What’s that about? Well, for a while now it’s been fairly common practice to deploy the Office license to Macs outside of the Office installers or updates. This came about as on occasion an Office Update or Installer would delete the file. I am trying to update to the latest version of Office (1500). Whenever I try to update it, through Microsoft Autoupdate, it downloads but it gets stuck on the verification process.

• Microsoft Office For Mac 2016
• Download Office 2016 Updates Manually
• Update History Office Mac

Soon Microsoft are to release an update to the Office 2016 Volume License installer on VLSC.

This update is 15.17 & is the first that has a few changes that may affect the way you deploy Office 2016.

Microsoft Office For Mac 2016

These changes are going to be later enforced in 15.20 & onwards. Below are some details on the changes, some of the why & how via the power of the MacAdmins.org Slack & the awesome @pbowden that some of us have had a sneak peek.

Contents

• 1 What’s Changing?

When you download the .iso from VLSC you’ll notice two packages within it:

The change is the new second pkg: “Microsoft_Office_2016_VL_Serializer.pkg”

What’s that about?

Well, for a while now it’s been fairly common practice to deploy the Office license to Macs outside of the Office installers or updates.

This came about as on occasion an Office Update or Installer would delete the file.

However, whilst the deletion itself was a bug, the ability to use the license.plist across Macs was also a bug.

What is it & should I use it?

With Office 2016, Microsoft are moving to a device based serialisation method. Which means that deploying the plist /Library/Preferences/com.microsoft.office.licensingv2.plist will no longer work.

This device based serialisation is based around the generating a license on the Mac that is to be running Office 2016.

So if you employ monolithic imaging or deploy Office 2016 via a Composer snap shot etc, the serialisation will not work. (Please don’t deploy Office 2016 via a Composer snap shot, use the pkg).

Also, if you install Office 2016 whilst booted to another volume (as in when installing via a NetBoot or NetInstall volume or something like Target Mode Imaging), again the serialisation will not work.

To install Office 2016 from another volume & have the serialisation work, cache it locally on the Mac being imaged & install on first boot or if using Casper Imaging check “Install on boot drive after Imaging” for the PKG from within Casper Admin.

However, to enable Office 2016 to be correctly licensed in the multitude of deployment scenarios that we mac admins employ, @pbowden & his team have created the “Microsoft_Office_2016_VL_Serializer.pkg”

Running this will correctly serialise the Office 2016 suite, & should be run from the Mac that’s running the suite. So again, can be added post imaging & then the suite will be correctly serialised.

To be clear, this will only affect you if using the Volume Licensed version of Office 2016 & not the Office365 version.

What happens if I carry on copying the licensing.plist?

For now, not much.

15.17 is the first release with the “Microsoft_Office_2016_VL_Serializer.pkg”, from 15.20 (scheduled for Q1 2016) you will have to use the correct license.

How did people find this out?

Well a little over a month ago a gentleman with the nick @pbowden hopped into the #microsoft-office channel on the MacAdmins.org Slack, this was awesome as @pbowden is a: Software engineer for Office for Mac/iOS at Microsoft, a fellow Brit & nice guy.

It’s been a great few weeks with the community sharing feedback with @pbowden & some of us being able to test pre-release installers for Office.

I hope this warning has been as helpful to you, as it was when @pbowden shared it with us.

Microsoft releases security and quality updates for the Click-To-Run (C2R) version of Office 2016 and for Office 2019, which is exclusively C2R. These updates are released approximately once a month, usually on the second Tuesday of the month.

If you'd like to verify that you're up to date, check your Office version number and manually update Office if necessary. To check your version of Office, do the following:

1. Open any Office application, such as Word or Excel.
2. Choose File > Account.
3. Under Product Information, note the version number under the About section.

If the version number matches the most current version, you're up to date. If not, you can manually update to get the latest version of Office. To update Office, follow these steps.

The following tables provide the update history for the volume licensed version of Office 2019, as well as the retail versions of Office 2016 C2R and Office 2019, with the most recent release date listed first.

New versions contain all the updates contained in previous versions.

Note

• Starting on August 11, 2020, the security updates (CVE articles) for Office 2016 and 2019 are listed on the security update page, instead of this page. 
• Office 2016 and 2019 are supported under the Fixed Lifecycle Policy. Only the most recent volume licensed and retail releases listed below are supported.

Volume licensed versions of Office 2019

The following information applies to volume licensed versions of Office 2019, such as Office Professional Plus 2019, purchased through a volume licensing agreement.

Retail versions of Office 2016 C2R and Office 2019

Download Office 2016 Updates Manually

The following information applies to retail versions of Office 2016 C2R and Office 2019, which share the same release dates and version numbers.

Update History Office Mac