-
Notifications
You must be signed in to change notification settings - Fork 347
Munki and Office 2016
Here is very in-depth information that may supersede some of the information below:
https://clburlison.com/demystify-office2016/ (Published 04 Jan 2016)
Microsoft had significant issues early in their release process for 2016, but have been responsive and addressed many of the common ones. This page may change to reflect updates in the future.
With Office 2016, Microsoft has made significant changes to how Office is packaged and deployed. The individual apps are now sandboxed and can be deployed individually. Additionally, there are now 2 ways you can purchase/license Office 2016:
- Traditional Volume-licensed model
- Office 365 Subscription
As done previously, Office 2016 is available as a traditional volume-licensed installer. This is downloadable as an ISO image from Microsoft's Volume-license portal. The volume-license installer is suitable for deployment via Munki as of version 15.13.4 without changes, otherwise you'd need to use a custom ChoiceChangesXML to exclude the specific volume licensing package from it. Some are also excluding the Microsoft AutoUpdate installer so there isn't a first-launch prompt asking to also launch the associated daemon, since Munki will be handling those updates.
Some have found that they prefer to install AND update Office 2016 via Munki by using AutoPkg and the collection of Office 2016 recipes available in the main autopkg recipes repo subdirectory. These recipes package and import the individual Office apps by pulling the "updates" directly from Microsoft. (As of 15.19.1 'deltas' are also available, but there are 'internal' tracks that Microsoft would like you to test by manually running MAU - more info here:.) Minus some shared fonts that could be left out for languages you may not need, the only component definitely needed from the volume-license installer was your actual volume license file (which would be present at /Library/Preferences/com.microsoft.office.licensingV2.plist
). As of the 15.17.1 version of the volume license, the download includes a package that can serialize a disk, which should be used instead of other methods, and works with either the SKU-Less or 'Standalone' installer versions. The Office 2016 recipes are:
- MSExcel2016.munki
- MSWord2016.munki
- MSPowerpoint2016.munki
- MSOneNote2016.munki
- MSOutlook2016.munki
If the Office updates (detailed above) are deployed to a system without installing the licensing file, the first Office 2016 app opened will prompt the user to log in to Office 365. Each additional app launched may prompt the end user to access the credentials in the keychain set by the first licensed app, but in any case Munki has no additional work to perform.
Additionally, SKU-less versions of the suite (which can be used with either flavor of licensing), can be found (along with other helpful info) at macadmins.software
- Getting Started
- Overview
- Discussion Group
- Demonstration Setup
- Glossary
- Frequently Asked Questions
- Contributing to Munki
- Release Notes
- Introduction
- Managed Software Center in Munki 5.2
- Manual Apple Updates
- force_install_after_date for Apple Updates
- Additional update encouragement
- Aggressive update notifications
- AggressiveUpdateNotificationDays preference
- Additional Munki 5 changes
- Configuration profile notes
- Major macOS upgrade notes
- Upgrading to Munki 5
- Introduction
- Munki Links
- Product Icons
- Screenshots In Product Descriptions
- Client Customization
- Custom Help Content
- Featured Items
- Update Notifications:
- Introduction
- iconimporter
- makepkginfo
- munkiimport
- managedsoftwareupdate
- makecatalogs
- manifestutil
- repoclean
- Preferences
- Default Repo Detection
- Default Manifest Resolution
- Managed Preferences Support In Munki
- Apple Software Updates With Munki
- Pkginfo Files
- Supported Pkginfo Keys
- Pre And Postinstall Scripts
- Munki And AutoRemove
- Blocking Applications
- ChoiceChangesXML
- CopyFromDMG
- nopkg items
- How Munki Decides What Needs To Be Installed
- Default Installs
- Removal of Unused Software
- Upgrading macOS:
- Apple Updates:
- Securing the Munki repo
- Preflight And Postflight Scripts
- Report Broken Client
- MSC Logging
- Munki With Git
- Bootstrapping With Munki
- License Seat Tracking
- LaunchD Jobs and Changing When Munki Runs
- Web Request Middleware
- Repo Plugins
- Downgrading Software
- Downgrading Munki tools
- Authorized Restarts
- Allowing Untrusted Packages
- About Munki's Embedded Python
- Customizing Python for Munki
- Configuration Profile Emulation
- PPPC Privacy permissions
- AutoPkg
- Repackaging
- Creating Disk Images
- Stupid Munki Tricks
- Troubleshooting
- Professional Support
- Known Issues and Workarounds
- Building Munki packages
- Munki packages and restarts
- Signing Munki
- Removing Munki
- More Links And Tools
- Munki Configuration Script
- Who's Using Munki
- Munki 3 Information
- Munki 4 Information
- macOS Monterey Info
- Pkginfo For Apple Software Updates
- Managing Configuration Profiles
- Microsoft Office
- Adobe Products
- Upgrading macOS: