Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
This is the official release of Munki 3.1, a feature update to the Munki tools.
This is the same build as Release Candidate 5.
Read more about Munki 3 here: https://github.com/munki/munki/wiki/Munki-3-Information
Major changes in the 3.1 release:
New bootstrapping tools and behaviors:
managedsoftwareupdatehas two new options:
managedsoftwareupdate --set-bootstrap-modecreates the needed /Users/Shared/.com.googlecode.munki.checkandinstallatstartup file, and also turns off FileVault auto login (this is the automatic login to the account of the user who unlocks the FV2-encrpyted disk at boot), by setting the com.apple.loginwindow DisableFDEAutoLogin preference to True.
managedsoftwareupdate --clear-bootstrap-moderemoves the /Users/Shared/.com.googlecode.munki.checkandinstallatstartup file and resets the com.apple.loginwindow DisableFDEAutoLogin preference to its previous value.
- When performing a macOS upgrade (using an Install macOS.app/startosinstall), Munki uses these new mechanisms in order to effectively re-bootstrap after an OS upgrade. See 99d902b
Managed Software Center.app
- Choosing "Reload page" from the Navigate menu now also triggers an update check.
- Managed Software Center.app can now optionally show optional installs and updates that apply to macOS versions higher than the currently installed version. This can help motivate macOS upgrades, as users can see that in order to be able to get the latest version of Keynote, they must first upgrade to 10.12.x, for example. This optional behavior is enabled by setting the ManagedInstalls preference
- "Problem" updates are now displayed on the Updates page of Managed Software Center.app; these are updates that cannot be installed for some reason (the most common one being insufficient disk space) that a user might be able to remedy.
- Faster launching of Managed Software Center.app.
Faster launching of MunkiStatus.app.
startosinstallOS upgrade pkginfo items can now contain an additional array of strings, which are added as additional options to the
startosinstallbinary. For example:
<key>additional_startosinstall_options</key> <array> <string>--converttoapfs</string> <string>NO</string> </array>
managedsoftwareupdatehas a new
--show-configoption, which will print Munki's configuration. This can be helpful when troubleshooting the potentially confusing interaction between different preference levels and managed preferences.
makecatalogsnow stores icon hashes in a separate file (
icons/_icon_hashes.plist) instead of in the catalogs. This enables the client to skip attempted downloads of icons if they are not listed in icons/_icon_hashes.plist, as well as only re-downloading icons if the hashes change.
Munki now prevents idle sleep during the check/download phase if the machine is on AC power.
makecatalogsoption to skip checking for installer item existence; useful if pkgs are stored elsewhere. Thanks to Yoann Gini: 04b3364
Updated localizations for Danish, Dutch, Finnish, French, German, Italian, Japanese, Norwegian, Russian, and Spanish. Thanks to all who contributed to these.
Bug fixes and other changes since the 3.0.3 release:
Fix for mounting fileshares in 10.13 in the command-line admin tools: e13c21e
Add the (presumed) default softwareupdate CatalogURL for High Sierra: e1ccdae
Bug fix for installed_state logic that caused some items to be displayed as 'installed' when they should have shown as 'Update available': 89e2faf
Fix to purge the cached softwareupdate catalog after a macOS upgrade: b6567fc
osinstallermodule to handle some
startosinstalloutput changes for High Sierra: e3e44a4
munkiimport: Don't print a warning about failure to read catalogs/all for a brand-new, empty repo: c45b5e8
• Fix for a bug where installing a
nopkg item that did not require a restart cleared the restart flag set by earlier items that did require a restart: eb17f85
If Managed Software Center.app is open while the munki tools are upgraded to 3.1, you may see some display "ugliness" in the Updates view. This issue goes away with a relaunch of Managed Software Center.app. See #806
makecatalogsin Munki 3.1 generates and stores icon hashes differently than earlier releases of Munki. If you use a 3.1+ version of
makecatalogsbut still have a lot of pre-3.1 Munki clients, you'll see a large number of attempts to download icons from those clients. If this is an issue you wish to avoid, use a pre-3.1 version of
makecatalogsuntil the majority of your fleet is upgraded to Munki 3.1 or later.