However if you don’t use Munki as the source for original Office installs maintaining just the updates there could be much easier.Įither option will allow you to control when clients are offered specific update versions and stagger the rollouts across your fleet in groups. Trying to maintain the logic for both full installers and delta updaters in the repo will bring additional complexity as well.
The downside, in my opinion, is the increased size of serving the full installers to clients for each update or separately importing both the full installers and delta updaters Microsoft makes available into your repo. The primary benefits of utilizing Munki are only having to maintain a single server for all software updates and the ability to force the installation of updates with a force_install_after_date key. The downside is that end users can defer the updates indefinitely. Combined with an MAU Caching Server there can be great savings in bandwidth in addition to controlling which updates are available to clients. This will be a dramatic reduction in size once it arrives in MAU version 4. Microsoft is also working on “Ultra-Thin” updates that will reduce the download size to under 20 MB for each update. MAU can easily take advantage of delta updates going back several versions. The primary benefit of utilizing Microsoft AutoUpdate is the reduced size, and thus greater speed, of updates. As long as your fleet is patched in a timely manner it doesn’t matter which approach you take or system you utilize. I’ll start by saying there is no right or wrong way to go about this. Read on if you are interested in how I’m keeping Office up-to-date and providing for new installs. I’ve shared my setup severals times on the MacAdmins Slack, most recently in a direct message, so I wanted to provide more details here. However I’ve found that a hybrid approach using both works best for us. Most MacAdmins take an either/or approach to managing updates for Microsoft Office on macOS, utilizing either Microsoft AutoUpdate (MAU) or Munki.
0 kommentar(er)
