However, we *do* support you moving that plist around volumes on the *same* machine (e.g. Manually copying one of those generated plists and copying it to other machines is absolutely not supported and akin to playing with fire. The role of the Microsoft Office Setup Assistant app is to collect various machine identifiers (including hardware serial number and boot disk hashes) and encodes them into /Library/Preferences/.ist …this is how we tether the license to the machine. just because it might work if you hacked some packages together and tried it once or twice on your machine, it doesn’t mean to say that it’ll *stay* working after you deploy. The licensing code is fairly complex and uses various internal triggers to ‘wake up’ at various times to check that all is well. It’s that same reason why I typically don’t like folks shoe-horning the updater package on a new machine – as the licensing package is not in the updater, and you could end up in a mess with licensing. There are code dependencies between Office15_all_volume_licensing.pkg and Office15_all_licensing.pkg, which is why I’d prefer you to deploy the SKU-less build first as it contains Office15_all_licensing.pkg.

pkg just in case there are things we need to do in the postinstall script. pkg, but I’d prefer that you install using the.

Technically, you can just run the Microsoft Office Setup Assistant.app that’s inside the.

It’s completely supportable to download and install the latest SKU-less build from those FWLinks like, and simply run the Office15_all_volume_licensing.pkg to license the build for VL. While I recommend joining the macadmin Slack instance to participate in these conversations, it may not be feasible for everyone Therefore I’m posting this information externally for everyone’s benefit. Below is information provided by who is a software engineer for Office for Mac/iOS at Microsoft, in the MacAdmins Slack instance ( on Twitter) regarding the supported way to license Office 2016 with a volume license.

Macadmins slack