volume license serializer for office 2016 for mac kace

VOLUME LICENSE SERIALIZER FOR OFFICE 2016 FOR MAC KACE INSTALL
VOLUME LICENSE SERIALIZER FOR OFFICE 2016 FOR MAC KACE UPDATE
VOLUME LICENSE SERIALIZER FOR OFFICE 2016 FOR MAC KACE FULL

VOLUME LICENSE SERIALIZER FOR OFFICE 2016 FOR MAC KACE FULL

The full suite package is available via the following FWLinks, its available via a CDN so choose the closest location to you for the fastest download. Where to get the latest full installer package? Word is that Microsoft are working on Delta updates that will be much much smaller, but until then this might be a workable solution.

VOLUME LICENSE SERIALIZER FOR OFFICE 2016 FOR MAC KACE UPDATE

Thats much more manageable for remote sites with slow links, or even labs with lots of machines.Īny new updates to the apps would simply mean downloading the full suite package again, approx 1.3GB and pushing that to clients, still 10 times more than office 2011 combo updaters however, but much smaller than pushing each 2016 app update to the client. We would only need to push about 1.3Gb to the client to have a fully up to date office 2016 installation.

VOLUME LICENSE SERIALIZER FOR OFFICE 2016 FOR MAC KACE INSTALL

So we could just download the latest suite package which is about 1.3GB, then install that on our client machines, install the special licensing package on top to licence the suite and we’re done. Microsoft offer the latest version of the suite in a package that contains all the apps and is SKU-less, meaning no licensing (It can be licenced as 0365 or VL) Well we only need the full VL installer for its special licensing package that generates the volume licence plist (/Library/Preferences/2.plist) That means we are pushing about 5gb to the client just to install office. Let Munki apply each app update ~800Mb times 5 apps (Word, Excel, PowerPoint, OneNote, Outlook).

Install the full Office 2016 VL installer (1.3GB).So now if we applied our same methodology of deploying Office 2011 to Office 2016 we would end up with something like this: It also means that the Office 2016 updates that Microsoft offer for each app are huge, approx 800Mb per app. That results in each app being rather large as you can see here. This means that our Office 2016 installer package is only about 1.3Gb, the installer then just copies the same files into each app bundle at install time via a postinstall script.

Previously in Office 2011, the apps could get this content from a shared location such as /Library/Application Support However what this means is that any shared content the apps use such as frameworks, fonts, and proofing tools all need to be contained within each application bundle. However, in Office 2016, Microsoft has sandboxed their applications, which is the right thing do™.

Let Munki apply the latest combo updater it has (14.5.8) and around 120MbĪnd we’re done. Pretty easy and painless and about 1.1Gb of data to send to the client.

Install the full volume licence installer from the VLSC site which was version 14.3.0 and around 1Gb.

In my organisation I deploy software with Munki, previously with Office 2011, it was pretty easy to deploy and get a fully up to date install of Office 2011

Volume license serializer for office 2016 for mac kace