(Please don’t deploy Office 2016 via a Composer snap shot, use the pkg).Īlso, 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. So if you employ monolithic imaging or deploy Office 2016 via a Composer snap shot etc, the serialisation will not work. This device based serialisation is based around the generating a license on the Mac that is to be running Office 2016. Which means that deploying the plist /Library/Preferences/2.plist will no longer work. With Office 2016, Microsoft are moving to a device based serialisation method. However, whilst the deletion itself was a bug, the ability to use the ist across Macs was also a bug. This came about as on occasion an Office Update or Installer would delete the file. 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.
The change is the new second pkg: “Microsoft_Office_2016_VL_Serializer.pkg” What’s that about?
iso from VLSC you’ll notice two packages within it:
1.3 What happens if I carry on copying the ist?.
