You may have to expand on what you mean by 'does not work fine.' It's common for the temperature to go up when working with something that is using a lot of your CPU% or a lot of memory.

Microsoft Office 2016 for Mac: (installed 2017-12-12) Microsoft Office 2016 Volume License Serializer: (installed 2017-12-12) Microsoft AutoUpdate: (installed 2017-12-13) Microsoft OneNote for Mac: (installed 2017-12-13). Note: This method didn't actually work for me, but based on everything I've read, it should work, so I'm still presenting it as a possibility. Just get the MicrosoftOffice2016VLSerializer.pkg (which can import directly into Munki) from the.iso and distribute that out (with the above preinstall script). The install packages from the CDN do not include the serializer which is why the standalone serializer download is required. I see both the 2016 and 2019 serializers as shown above. You may need to call the VLSC and ask if you don't see it.

Download Etrecheckand post the results on here, so we can see what you are working with. It may be something where you want to install more RAM, or it could be how you're using it. Are you using it on your lap with a blanket under it, on a pillow, things like that will make these models heat up.

Dec 29, 2017 11:44 AM

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.

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.

Office For Mac Serializer

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.

Office 2016 Mac Serializer Not Working Windows 10

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