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.
Volume License Serializer not working in Catalina I did a clean install of Catalina on a computer at work, ran the 16.16.12 installer for Office 2016 and the Volume License Serializer. Office is not activated and asks for a key. Office 2016 for Mac is a version of Office that’s available as a one-time purchase from a retail store or through a volume licensing agreement. It will be supported with security updates and bug fixes, as needed, until October 13, 2020. The minimum supported macOS for Office 2016 for Mac is 10.10 (Yosemite). Upgrade to Office 2019 for Mac: If you're a volume licensed customer, you can upgrade to Office 2019 for Mac without uninstalling Office 2016 for Mac. First, you need to download the 2019 version of the Volume License (VL) Serializer from the Volume Licensing Service Center (VLSC).
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.
Troubleshoot and fix the things that block co-authoring from working in Office, SharePoint online, SharePoint Server, and OneDrive. Word 2019 for Mac Word 2016 PowerPoint 2016 Office for business Word 2013 PowerPoint 2013 Word 2010 PowerPoint 2010 PowerPoint 2016 for Mac Word 2016 for Mac SharePoint Server 2016 Skype for Business SharePoint. Found a way to install Office 2016. I have the ISO file which I renamed to Office2016.iso. When you mount you will see this info MicrosoftOffice2016VolumeInstaller.pkg So the command is as follows.
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”
Office 2016 Mac Serializer Not Working Windows 10
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.
Office For Mac Serializer
Office 2016 Mac Serializer Not Working Without
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.