Munki Versions Save

Managed software installation for macOS —

v6.0.1

1 year ago

This is the official release of Munki 6.0.1, a bug-fix release of the Munki tools.

Bug fix

This release addresses a serious issue with client certs on macOS Ventura. See https://github.com/munki/munki/issues/1163 and https://github.com/munki/munki/pull/1162 for details. Thank you to @rrenstrom for the fix.

Features new in Munki 6

See the release notes for the Munki 6.0 release for details on the features new in Munki 6.

Documentation

Current documentation here: https://github.com/munki/munki/wiki/Munki-6-Information

Build info

The GUI apps and the Python framework were built under Xcode 13.4.1 on macOS 12.6. Other versions of Xcode have not been tested and may cause different results.

Package versioning

  • metapackage version: 6.0.1.4523
  • munki core tools version: 6.0.1.4523
  • LaunchAgents/LaunchDaemons version: 3.0.3265
  • Apps package version: 6.0.0.4520
  • Python package version: 3.9.13.4518

Attachment info

munkitools-6.0.1.4523.pkg is a package that should install without requiring a restart unless upgrading from an extremely old Munki tools (like one of the 3.x releases or earlier). It should be suitable for most initial deployment scenarios, including those driven by DEP/ADE. It does not include a component to trigger "bootstrapping" or any other automatic run of the tools after installation.

v6.0.0

1 year ago

This is the official release of Munki 6.0, a release adding new features to the Munki tools.

This is the exact same build as Munki 6.0 Release Candidate 1. There have been no changes since that release.

New features

  • Munki 6 adds a feature to stage a macOS installer application and have Managed Software Center launch it for a user, temporarily giving the user admin rights if needed. This enables Munki to assist with an upgrade of macOS on Apple silicon, but this feature can be used on Intel Macs as well.
  • munkiimport and makepkginfo now support a new --installer-type option, which can be used with disk images containing macOS installers to indicate whether you want to build a startosinstall item, a stage_os_installer item, or even a copy_from_dmg item (which would copy the installer to /Applications, and do nothing else).

Documentation

Current documentation here: https://github.com/munki/munki/wiki/Munki-6-Information

Getting started with staged macOS installers

  • Use munkiimport --installer-type stage_os_installer /path/to/dmg/containing/Install\ macOS\ Foo.app or munkiimport --installer-type stage_os_installer /path/to/Install\ macOS\ Foo.app to generate a pkginfo supporting this new install mechanism (and import the installer). Optionally use --arch arm64 to limit this to Apple silicon.
  • Add the newly created item to a manifest for a testing machine.
  • Test!

Other changes in Munki 6.0

Build info

The GUI apps and the Python framework were built under Xcode 13.4.1 on macOS 12.6. Other versions of Xcode have not been tested and may cause different results.

Package versioning

  • metapackage version: 6.0.0.4520
  • munki core tools version: 6.0.0.4501
  • LaunchAgents/LaunchDaemons version: 3.0.3265
  • Apps package version: 6.0.0.4520
  • Python package version: 3.9.13.4518

Attachment info

munkitools-6.0.0.4520.pkg is a package that should install without requiring a restart unless upgrading from an extremely old Munki tools (like one of the 3.x releases or earlier). It should be suitable for most initial deployment scenarios, including those driven by DEP/ADE. It does not include a component to trigger "bootstrapping" or any other automatic run of the tools after installation.

v6.0.0b3

1 year ago

This is a beta release of Munki 6, a release adding new features to the Munki tools.

New features

  • Munki 6 adds a feature to stage a macOS installer application and have Managed Software Center launch it for a user, temporarily giving the user admin rights if needed. This enables Munki to assist with an upgrade of macOS on Apple silicon, but this feature can be used on Intel Macs as well.
  • munkiimport and makepkginfo now support a new --installer-type option, which can be used with disk images containing macOS installers to indicate whether you want to build a startosinstall item, a stage_os_installer item, or even a copy_from_dmg item (which would copy the installer to /Applications, and do nothing else).

Documentation

Work-in-progress documentation here: https://github.com/munki/munki/wiki/Munki-6-Information

Getting started with staged macOS installers

  • Use munkiimport --installer-type stage_os_installer /path/to/dmg/containing/Install\ macOS\ Foo.app or munkiimport --installer-type stage_os_installer /path/to/Install\ macOS\ Foo.app to generate a pkginfo supporting this new install mechanism (and import the installer). Optionally use --arch arm64 to limit this to Apple silicon.
  • Add the newly created item to a manifest for a testing machine.
  • Test!

Other changes in Munki 6.0

Changes from Beta 2:

  • Changes from Beta 2 are here: https://github.com/munki/munki/compare/v6.0.0b2..v6.0.0b3
    • Some highlights:
      • When Munki calls /usr/sbin/softwareupdate --list, the process is terminated if it has no output for five minutes.
      • munkiimport and makepkginfo's --arch option now errors if the option value is not one of 'i386', 'x86_64', 'arm64'
      • A fix for an issue where a user launching a macOS installer and then quitting it without installing would reset the tracking of how long the update had been available for install
      • UI/UX improvements when using a stage_os_installer item as an optional_install:
        • If the macOS installer is already available in the /Applications folder, you can still choose the item for install (previously it appeared as already installed)
        • MSC app will show the "_staged" display name and description if the optional_install stage_os_installer item is staged, but not yet installed
        • Improved behavior when there's a staged os update and pending Apple updates

Build info

The GUI apps and the Python framework were built under Xcode 13.4.1 on macOS 12.5.1. Other versions of Xcode have not been tested and may cause different results.

Package versioning

  • metapackage version: 6.0.0.4501
  • munki core tools version: 6.0.0.4501
  • LaunchAgents/LaunchDaemons version: 3.0.3265
  • Apps package version: 6.0.0.4499
  • Python package version: 3.9.13.4481

Attachment info

munkitools-6.0.0.4501.pkg is a package that should install without requiring a restart unless upgrading from an extremely old Munki tools (like one of the 3.x releases or earlier). It should be suitable for most initial deployment scenarios, including those driven by DEP/ADE. It does not include a component to trigger "bootstrapping" or any other automatic run of the tools after installation.

v6.0.0b1

1 year ago

This is a beta release of Munki 6, a release adding new features to the Munki tools.

New features

  • Munki 6 adds a feature to stage a macOS installer and have Managed Software Center launch it for a user, temporarily giving the user admin rights if needed. This allows Munki to upgrade macOS on Apple silicon, but the feature can be used on Intel Macs as well.
  • munkiimport and makepkginfo now support a new --installer-type option, which can be used with disk images containing macOS installers to indicate whether you want to build a startosinstall item, a stage_os_installer item, or even a copy_from_dmg item (which would copy the installer to /Applications, and do nothing else).

Documentation

Much new documentation needs to be written.

Getting started with staged macOS installers

  • Use munkiimport --installer-type stage_os_installer <path/to/dmg/containing/Install\ macOS\ Foo.app to generate a pkginfo supporting this new install mechanism. Optionally use --arch arm64 to limit this to Apple silicon.
  • Add the newly created item to a manifest for a testing machine.
  • Test!

Other changes

Build info

The GUI apps and the Python framework were built under Xcode 13.4.1 on macOS 12.5.1. Other versions of Xcode have not been tested and may cause different results.

Package versioning

  • metapackage version: 6.0.0.4481
  • munki core tools version: 6.0.0.4481
  • LaunchAgents/LaunchDaemons version: 3.0.3265
  • Apps package version: 6.0.0.4474
  • Python package version: 3.9.13.4481

Attachment info

munkitools-6.0.0.4481.pkg is a package that should install without requiring a restart unless upgrading from an extremely old Munki tools (like one of the 3.x releases or earlier). It should be suitable for most initial deployment scenarios, including those driven by DEP/ADE. It does not include a component to trigger "bootstrapping" or any other automatic run of the tools after installation.

v5.7.3

1 year ago

This is the official release of Munki 5.7.3, a bug-fix release of the Munki tools.

Known issues

  • Munki cannot yet do major OS upgrades on Apple silicon Macs.

Bug fixes

Notification Center changes

Please see the release notes for the Munki 5.7 release (https://github.com/munki/munki/releases/tag/v5.7.0) for important information on changes in Notification Center notifications, and things an admin might need to do to react to these changes.

Other changes

A complete list of changes from the 5.7.2 release is here: https://github.com/munki/munki/compare/v5.7.2...v5.7.3

Build info

The GUI apps and the Python framework were built under Xcode 13.4.1 on macOS 12.5. Other versions of Xcode have not been tested and may cause different results.

Package versioning

  • metapackage version: 5.7.3.4444
  • munki core tools version: 5.7.3.4443
  • LaunchAgents/LaunchDaemons version: 3.0.3265
  • Apps package version: 5.7.2.4439
  • Python package version: 3.9.13.4444

Attachment info

munkitools-5.7.3.4444.pkg is a package that should install without requiring a restart unless upgrading from an extremely old Munki tools (like one of the 3.x releases or earlier). It should be suitable for most initial deployment scenarios, including those driven by DEP/ADE. It does not include a component to trigger "bootstrapping" or any other automatic run of the tools after installation.

v5.7.2

1 year ago

This is the official release of Munki 5.7.2, a bug-fix release of the Munki tools.

Known issues

  • Munki cannot yet do major OS upgrades on Apple silicon Macs.

Bug fixes

Notification Center changes

Please see the release notes for the Munki 5.7 release (https://github.com/munki/munki/releases/tag/v5.7.0) for important information on changes in Notification Center notifications, and things an admin might need to do to react to these changes.

Other changes

A complete list of changes is here: https://github.com/munki/munki/compare/v5.7.1...v5.7.2

Build info

The GUI apps and the Python framework were built under Xcode 13.4.1 on macOS 12.4. Earlier (and later!) versions of Xcode have not been tested and may or may not have issues.

Package versioning

  • metapackage version: 5.7.2.4439
  • munki core tools version: 5.7.2.4438
  • LaunchAgents/LaunchDaemons version: 3.0.3265
  • Apps package version: 5.7.2.4439
  • Python package version: 3.9.13.4424

Attachment info

munkitools-5.7.2.4439.pkg is a package that should install without requiring a restart unless upgrading from an extremely old Munki tools (like one of the 3.x releases or earlier). It should be suitable for most initial deployment scenarios, including those driven by DEP/ADE. It does not include a component to trigger "bootstrapping" or any other automatic run of the tools after installation.

v5.7.1

1 year ago

This is the official release of Munki 5.7.1, a bug-fix release of the Munki tools.

Known issues

  • Munki cannot yet do major OS upgrades on Apple silicon Macs.
  • Managed Software Center has a visual issue under Catalina and earlier: a thin separator line appears between the "title bar" and "content" areas of the window. (This is not an issue new to this release. I am not actively working on this issue; this would be an excellent opportunity for someone to contribute a fix.)

Bug fixes

Notification Center changes

Please see the release notes for the Munki 5.7 release (https://github.com/munki/munki/releases/tag/v5.7.0) for important information on changes in Notification Center notifications, and things an admin might need to do to react to these changes.

Other changes

A complete list of changes is here: https://github.com/munki/munki/compare/v5.7.0...v5.7.1

Build info

The GUI apps and the Python framework were built under Xcode 13.3.1 on macOS 12.4. Earlier versions of Xcode have not been tested and may or may not have issues.

Package versioning

  • metapackage version: 5.7.1.4434
  • munki core tools version: 5.7.1.4434
  • LaunchAgents/LaunchDaemons version: 3.0.3265
  • Apps package version: 5.6.0.4429
  • Python package version: 3.9.13.4424

Attachment info

munkitools-5.7.1.4434.pkg is a package that should install without requiring a restart unless upgrading from an extremely old Munki tools (like one of the 3.x releases or earlier). It should be suitable for most initial deployment scenarios, including those driven by DEP/ADE.

v5.7.0

1 year ago

This is the official release of Munki 5.7, a feature-add and bug-fix release of the Munki tools.

This release is the exact same build as 5.7 Release Candidate 3.

Known issues

  • Munki cannot yet do major OS upgrades on Apple silicon Macs.
  • Managed Software Center has a visual issue under Catalina and earlier: a thin separator line appears between the "title bar" and "content" areas of the window. (This is not an issue new to this release. I am not actively working on this issue; this would be an excellent opportunity for someone to contribute a fix.)

Bug fixes

  • A fix for an issue where clicking on a Notification Center notification would not reliably launch Managed Software Center.app in some configurations. This change may require some additional admin effort -- see "Notification Center changes" below for details
  • A fix for over-aggressive cleanup of the download cache which sometimes removed partial (incomplete) downloads, causing resuming partial downloads to fail and forcing it to start over from zero on a subsequent attempt. https://github.com/munki/munki/commit/450294be76688f84f859404ad4e5d325228be370
  • An attempt to improve the behavior around Apple updates on Apple silicon for those updates that do not require a restart (IOW, to actually show them in the MSC UI) https://github.com/munki/munki/commit/f6c618a243e015f3c680321992cde25e9815b027
  • A fix for an issue where an "aggressive/obnoxious" notification triggered when there was another application in full screen mode might result in all interaction being blocked. See https://github.com/munki/munki/issues/1108 for more details on the issue.

Changes

  • PyObjC version has been bumped to 8.5
  • Included Python version is now 3.9.13
  • This version has a more "lightweight" PyObjC install than did Munki 5.6.x and earlier. If you are using munki-python with your own scripts, you should test them thoroughly against this release, and consider using a non-Munki python for your non-Munki uses.
  • A new option (-A) to make_munki_mpkg.sh build and include a component package that triggers a managedsoftwareupdate --auto run immediately after install. This is intended for use with a DEP/ADE-style enrollment where the user creates their account in the Setup Assistant. Once the Setup Assistant exits, the user is automatically logged into their newly-created account, skipping any chance for Munki to bootstrap at the loginwindow. Using this option will cause Munki to do an automatic run in the background immediately. Test this option thoroughly in your environment to make sure it works for your needs.
  • Removed the -m option to make_munki_mpkg.sh: the package generated should work in both DEP/ADM install scenarios and other installation scenarios.

Notification Center changes

  • Notification Center notifications are posted by the munki-notifier.app, which is a helper app included inside the Managed Software Center application. Prior to Munki 5.7, it used a "clever" but unsupported technique to "spoof" the bundle identifier of Managed Software Center.app (com.googlecode.munki.ManagedSoftwareCenter). This technique caused Notification Center to display MSC.app's icon in the notifications, and to attempt to launch MSC.app (instead of munki-notifier) when a notification was clicked on.
  • For reasons not entirely understood yet (though I have some theories), this spoofing technique failed in some configurations, with usernotifyd complaining that it could not "...find appropriate application to launch for com.googlecode.munki.ManagedSoftwareCenter..." and therefore failing to launch MSC.app.
  • This issue seemed to affect Apple silicon Macs 100% of the time. I suspect it has to do with the fact that all code must be signed on Apple silicon (by default Munki's code is "ad-hoc" signed on Apple silicon), and that the signature of the real MSC.app does not match the signature of munki-notifier. This might explain the failure for some people even on Intel -- perhaps they were signing the GUI apps.
  • The problem can be avoided by abandoning the bundle identifier "spoofing" technique and letting a click on a notification just (re-)launch munki-notifier, which in turn can launch MSC.app. We can make munki-notifier look like MSC.app when posting notifications by giving it the same icon as MSC.app and using localized display names to cause it to display the same name as MSC.app. From a user's point-of-view, it still looks like the notifications are coming from MSC.app. But from Notification Center's perspective, the notifications are coming from munki-notifier, which has a bundle identifier of com.googlecode.munki.munki-notifier.
  • Machines that ran releases of Munki prior to 5.7 will now likely have two entries for "Managed Software Center" in the Notification Center preferences pane. One would be the "old" one for the com.googlecode.munki.ManagedSoftwareCenter bundle identifier; the other will be the new one for munki-notifier's actual com.googlecode.munki.munki-notifier bundle identifier.
  • Administrator task: If you are currently installing a configuration profile to ensure Managed Software Center notifications are being allowed/delivered, you'll need to update that profile (or add a new one) to allow notifications from munki-notifier (bundle identifier com.googlecode.munki.munki-notifier). If you do not install a profile, your users (running Catalina and above) will get a new notification asking if they want to allow "Managed Software Center" to send them notifications. Assume that many will say no.
  • Administrator task: If you "re-brand" Managed Software Center, you'll need to make changes to the munki-notifier app as well, since it now shares an icon and localized display names with Managed Software Center. Tools like munki-rebrand (https://github.com/ox-it/munki-rebrand) will need to be updated. (It appears that munki-rebrand has been updated.)

Other changes

A complete list of changes is here: https://github.com/munki/munki/compare/v5.6.4...v5.7.0

Build info

The GUI apps and the Python framework were built under Xcode 13.3.1 on macOS 12.3.1. Earlier versions of Xcode have not been tested and may or may not have issues.

Package versioning

  • metapackage version: 5.7.0.4429
  • munki core tools version: 5.7.0.4428
  • LaunchAgents/LaunchDaemons version: 3.0.3265
  • Apps package version: 5.6.0.4429
  • Python package version: 3.9.13.4424

Attachment info

munkitools-5.7.0.4429.pkg is a package that should install without requiring a restart unless upgrading from an extremely old Munki tools (like one of the 3.x releases or earlier). It should be suitable for most initial deployment scenarios, including those driven by DEP/ADE.

v5.7.0RC3

1 year ago

This is a release candidate of Munki 5.7, a feature-add and bug-fix release of the Munki tools.

Known issues

  • Munki cannot yet do major OS upgrades on Apple silicon Macs.
  • Managed Software Center has a visual issue under Catalina and earlier: a thin separator line appears between the "title bar" and "content" areas of the window. (This is not an issue new to this release. I am not actively working on this issue; this would be an excellent opportunity for someone to contribute a fix.)

Bug fixes

  • [New in RC3] A fix for a logic error in displaying Apple updates in Managed Software Center introduced in RC2. https://github.com/munki/munki/commit/9dbc161dc6f9b9d4f0fb75ba875a5d307b6c7f7f
  • [New in RC2] A fix for over-aggressive cleanup of the download cache which sometimes removed partial (incomplete) downloads, causing resuming partial downloads to fail and forcing it to start over from zero on a subsequent attempt. https://github.com/munki/munki/commit/450294be76688f84f859404ad4e5d325228be370
  • [New in RC2] An attempt to improve the behavior around Apple updates on Apple silicon for those updates that do not require a restart (IOW, to actually show them in the MSC UI) https://github.com/munki/munki/commit/f6c618a243e015f3c680321992cde25e9815b027
  • A fix for an issue where clicking on a Notification Center notification would not reliably launch Managed Software Center.app in some configurations. This change may require some additional admin effort -- see "Notification Center changes" below for details
  • A fix for an issue where an "aggressive/obnoxious" notification triggered when there was another application in full screen mode might result in all interaction being blocked. See https://github.com/munki/munki/issues/1108 for more details on the issue.
  • This version includes a fix for a crashing issue when using client certs on macOS Mojave (and probably earlier) that occurred in 5.7 beta 2 (and probably beta 1)
  • This version includes a fix for a "Segmentation fault" issue in 5.7 Beta 1 on macOS 10.14 and earlier
  • Included Python version has been changed to 3.9.13 (down from 3.10.4 in earlier betas) to address an upgrade issue detailed here: https://github.com/munki/munki/issues/1136

Changes

  • PyObjC version has been bumped to 8.5
  • Included Python version is now 3.9.13
  • This version has a more "lightweight" PyObjC install than did Munki 5.6.x and earlier. If you are using munki-python with your own scripts, you should test them thoroughly against this release candidate, and consider using a non-Munki python for your non-Munki uses.
  • A new option (-A) to make_munki_mpkg.sh trigger a managedsoftwareupdate --auto run immediately after install. This is intended for use with a DEP/ADE-style enrollment where the user creates their account in the Setup Assistant. Once the Setup Assistant exits, the user is automatically logged into their newly-created account, skipping any chance for Munki to bootstrap at the loginwindow. Using this option will cause Munki to do an automatic run in the background immediately. Use with care.
  • Removed the -m option to make_munki_mpkg.sh: the package generated should work in both DEP/ADM install scenarios and other installation scenarios.

Notification Center changes

  • Notification Center notifications are posted by the munki-notifier.app, which is a helper app included inside the Managed Software Center application. Prior to Munki 5.7, it used a "clever" but unsupported technique to "spoof" the bundle identifier of Managed Software Center.app (com.googlecode.munki.ManagedSoftwareCenter). This technique caused Notification Center to display MSC.app's icon in the notifications, and to attempt to launch MSC.app (instead of munki-notifier) when a notification was clicked on.
  • For reasons not entirely understood yet (though I have some theories), this spoofing technique failed in some configurations, with usernotifyd complaining that it could not "...find appropriate application to launch for com.googlecode.munki.ManagedSoftwareCenter..." and therefore failing to launch MSC.app.
  • This issue seemed to affect Apple silicon Macs 100% of the time. I suspect it has to do with the fact that all code must be signed on Apple silicon (by default Munki's code is "ad-hoc" signed on Apple silicon), and that the signature of the real MSC.app does not match the signature of munki-notifier. This might explain the failure for some people even on Intel -- perhaps they were signing the GUI apps.
  • The problem can be avoided by abandoning the bundle identifier "spoofing" technique and letting a click on a notification just (re-)launch munki-notifier, which in turn can launch MSC.app. We can make munki-notifier look like MSC.app when posting notifications by giving it the same icon as MSC.app and using localized display names to cause it to display the same name as MSC.app. From a user's point-of-view, it still looks like the notifications are coming from MSC.app. But from Notification Center's perspective, the notifications are coming from munki-notifier, which has a bundle identifier of com.googlecode.munki.munki-notifier.
  • Machines that ran releases of Munki prior to 5.7 will now likely have two entries for "Managed Software Center" in the Notification Center preferences pane. One would be the "old" one for the com.googlecode.munki.ManagedSoftwareCenter bundle identifier; the other will be the new one for munki-notifier's actual com.googlecode.munki.munki-notifier bundle identifier.
  • Administrator task: If you are currently installing a configuration profile to ensure Managed Software Center notifications are being allowed/delivered, you'll need to update that profile (or add a new one) to allow notifications from munki-notifier (bundle identifier com.googlecode.munki.munki-notifier). If you do not install a profile, your users (running Catalina and above) will get a new notification asking if they want to allow "Managed Software Center" to send them notifications. Assume that many will say no.
  • Administrator task: If you "re-brand" Managed Software Center, you'll need to make changes to the munki-notifier app as well, since it now shares an icon and localized display names with Managed Software Center. Tools like munki-rebrand (https://github.com/ox-it/munki-rebrand) will need to be updated. (It appears that munki-rebrand has been updated.)

Other changes

A complete list of changes is here: https://github.com/munki/munki/compare/v5.6.4...v5.7.0RC3

Build info

The GUI apps and the Python framework were built under Xcode 13.3.1 on macOS 12.3.1. Earlier versions of Xcode have not been tested and may or may not have issues.

Package versioning

  • metapackage version: 5.7.0.4429
  • munki core tools version: 5.7.0.4428
  • LaunchAgents/LaunchDaemons version: 3.0.3265
  • Apps package version: 5.6.0.4429
  • Python package version: 3.9.13.4424

Attachment info

munkitools-5.7.0.4429.pkg is a package that should install without requiring a restart unless upgrading from an extremely old Munki tools (like one of the 3.x releases or earlier). It should be suitable for most initial deployment scenarios, including those driven by DEP/ADE.

v5.7.0b2

2 years ago

This is a beta release of Munki 5.7, a feature-add and bug-fix release of the Munki tools.

Known issues

  • Munki cannot yet upgrade Apple silicon Macs to macOS Monterey.
  • Managed Software Center has a visual issue under Catalina and earlier: a thin separator line appears between the "title bar" and "content" areas of the window. (This is not an issue new to this release).

Changes and fixes:

  • This beta includes a fix for a "Segmentation fault" issue in Beta 1 on macOS 10.14 (and possibly earlier -- please test!)
  • Included Python version has been bumped to 3.10.4
  • PyObjC version has been bumped to 8.5 (up from 8.2 in Beta 1)
  • A new option (-A) to make_munki_mpkg.sh trigger a managedsoftwareupdate --auto run immediately after install. This is intended for use with a DEP/ADE-style enrollment where the user creates their account in the Setup Assistant. Once the Setup Assistant exits, the user is automatically logged into their newly-created account, skipping any chance for Munki to bootstrap at the loginwindow. Using this option will cause Munki to do an automatic run in the background immediately. Use with care.
  • Removed the -m option to make_munki_mpkg.sh: the package generated should work in both DEP/ADM install scenarios and other installation scenarios.
  • A fix for an issue where clicking on a Notification Center notification would not reliably launch Managed Software Center.app in some configurations. This change may require some additional admin effort -- see "Notification Center changes" below for details
  • A fix for an issue where an "aggressive/obnoxious" notification triggered when there was another application in full screen mode might result in all interaction being blocked. See https://github.com/munki/munki/issues/1108 for more details on the issue.

Notification Center changes

  • Notification Center notifications are posted by the munki-notifiy.app, which is a helper app included inside the Managed Software Center application. Prior to Munki 5.7, it used a "clever" but unsupported technique to "spoof" the bundle identifier of Managed Software Center.app (com.googlecode.munki.ManagedSoftwareCenter). This technique caused Notification Center to display MSC.app's icon in the notifications, and to attempt to launch MSC.app (instead of munki-notifier) when a notification was clicked on.
  • For reasons not entirely understood yet (though I have some theories), this spoofing technique failed in some configurations, with usernotifyd complaining that it could not "...find appropriate application to launch for com.googlecode.munki.ManagedSoftwareCenter..." and therefore failing to launch MSC.app.
  • This issue seemed to affect Apple silicon Macs 100% of the time. I suspect it has to do with the fact that all code must be signed on Apple silicon (by default Munki's code is "ad-hoc" signed on Apple silicon), and that the signature of the real MSC.app does not match the signature of munki-notifier. This might explain the failure for some people even on Intel -- perhaps they were signing the GUI apps.
  • The problem can be avoided by abandoning the bundle identifier "spoofing" technique and letting a click on a notification just (re-)launch munki-notifier, which in turn can launch MSC.app. We can make munki-notifier look like MSC.app when posting notifications by giving it the same icon as MSC.app and using localized display names to cause it to display the same name as MSC.app. From a user's point-of-view, it still looks like the notifications are coming from MSC.app. But from Notification Center's perspective, the notifications are coming from munki-notifier, which has a bundle identifier of com.googlecode.munki.munki-notifier.
  • Machines that ran releases of Munki prior to 5.7 will now likely have two entries for "Managed Software Center" in the Notification Center preferences pane. One would be the "old" one for the com.googlecode.munki.ManagedSoftwareCenter bundle identifier; the other will be the new one for munki-notifier's actual com.googlecode.munki.munki-notifier bundle identifier.
  • Administrator task: If you are currently installing a configuration profile to ensure Managed Software Center notifications are being allowed/delivered, you'll need to update that profile (or add a new one) to allow notifications from munki-notifier (bundle identifier com.googlecode.munki.munki-notifier). If you do not install a profile, your users (running Catalina and above) will get a new notification asking if they want to allow "Managed Software Center" to send them notifications. Assume that many will say no.
  • Administrator task: If you "re-brand" Managed Software Center, you'll need to make changes to the munki-notifier app as well, since it now shares an icon and localized display names with Managed Software Center. Tools like munki-rebrand (https://github.com/ox-it/munki-rebrand) will need to be updated.

Other changes

A complete list of changes is here: https://github.com/munki/munki/compare/v5.6.4...v5.7.0b2

Build info

The apps and the Python framework were built under Xcode 13.2.1. There have been issues reported with building the Python framework with Xcode 13.3 and 13.3.1.

Package versioning

  • metapackage version: 5.7.0.4418
  • munki core tools version: 5.7.0.4408
  • LaunchAgents/LaunchDaemons version: 3.0.3265
  • Apps package version: 5.6.0.4411
  • Python package version: 3.10.4.4418

Attachment info

munkitools-5.7.0.4418.pkg is a package that should install without requiring a restart unless upgrading from an extremely old Munki tools (like one of the 3.x releases or earlier).