2023-12-14
Highlights
- New option to save the user's password for future automatic macOS updates and upgrades. Literally, "Save Password" but for automatic macOS updates and upgrades.
- New display customization options including unmovable dialogs and hide background mode courtesy of IBM Notifier 3.x.
- New macOS installer workflows are now handled by
mist-cliintegration, thus removing allpythondependencies. - New LaunchDaemon architecture significantly improves automatic launch and deferment reliability for all
superworkflows. - New default "always on" behavior automatically checks for Apple software updates on a regular basis.
- Support for Jamf Pro 10.48+ (Beta) Managed Software Updates.
- Support for Jamf Pro 10.49+ API Roles and Clients.
- Please check out the updated
superWiki for more details!
Compatibility Notes
super4.x requires macOS 11 or newer (all code supporting macOS 10.x has been removed).- All
super4.x code has been refactored for style, clarity, and uniformity. As such nearly every single option name has been changed. - Most
super3.0 command line options and managed preferences are not compatible withsuper4.x - Previously saved
super3.0 Apple silicon authentication credentials are automatically migrated the first timesuper4.x runs. - It is safe to mix
superversion 3.0 and 4.x managed preferences (except for the DisplaySilently key) in a single configuration profile. However each version only recognizes the managed preference keys that are compatible for that version. - Refer to this spreadsheet (tab separated values) for migrating
super3.0 command line options to version 4.x. - Refer to this spreadsheet (tab separated values) for migrating
super3.0 managed preferences to version 4.x. - Updated Jamf Pro Extension Attribute scripts now supports both
superversions 3.0 and 4.x. - Updated example MDM configuration profiles for
superv4.x. super4.0.3 SHA-256: 2c7411a4bfa84a63e20955d18d6c6ba19933b2cf35b04f91bbcac98c666e335c
Known Issues
- The Jamf Pro (Beta) Managed Software Updates workflow is not compatible with the
--install-macos-major-version-targetoption. Until this issue is resolved you can revert your Jamf Pro service back to the current macOS software update workflow.