Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

SUPER aka S.U.P.E.R.M.A.N. is a script for fully-automating macOS updates. It uses IBM Notifier 3.x (which it auto-installs) to provide customizable popup notices like Nudge, and automates the macOS update procedure similar to using Nudge with NudgeHelper.
 

 
 
SUPER has some advantages over Nudge+NudgeHelper - for instance, the user never sees the macOS Updates dialog, and by default it is configured so that once they've entered their password for updating one time, they won't have to enter it again.    It also downloads and prepares updates before prompting the user.
 
It has some disadvantages as well - for instance, it's not possible to have SUPER only prompt if macOS is not a specific minor version, unlike Nudge.  If a new minor version of macOS is released, SUPER will detect it and prompt for updates.

SUPER can be configured with different types of deadlines for installing updates:

...

When it first prompts it will look like this:
 

 
(If the deadline is close, the "Defer" time will be the time until the deadline, otherwise it will be the number of minutes configured in the "Default Deferral Timer" option)
 
 
If you click on Restart, on an Apple Silicon Mac you'll get the user auth dialog:
 
Image RemovedImage Added


 
NOTE: the password will get saved in the user's keychain - next time the Mac needs updates, the user will not be prompted!
 
 
IF you enter the wrong password twice it will abort, and you'll get the error dialog:
 

 
 
Once you've entered your password (or immediately on an Intel Mac) you'll see the restart message:
 
Image RemovedImage Added


Full details on using & configuring SUPER are in the SUPER wiki at https://github.com/Macjutsu/super/wiki

...

NOTE: for all of the examples below, "ENGR - " versions exist in UT Jamf in the ENGR site.  I am working on templates and a script to make it easy for EPM to clone them to There are also templates that EPM can clone into your site.

For testing SUPER you will need several configuration profiles in your site (where "SITE" below should be your sitename, e.g ENGR, MECH, COFA, etc).  
 

...

 
Create a policy to remove both Nudge & NudgeHelper from your target systems:
 
SITE - Remove Nudge & NudgeHelper - SUPER macos targets

  • Scope this to your SITE - SUPER macos update targets group
  • Add script "GLOBAL - Nudge - Uninstall" with parameter uninstall_nudgehelper = true
  • Add a custom trigger SITE-remove-nudge-for-super 

...

  1. Add your SITE - SUPER macos update targets group to your SITE - Exceptions - Nudge group - to ensure they don't also run Nudge.
    • If you don't have such a group, ask EPM to create it - OR, set the Exception - Nudge EA for each computer.
  2. Set your SITE - Remove Nudge & NudgeHelper policy - SUPER macos targets policy to Enabled, Ongoing (do not set Recurring Check-in)
  3. Set your SITE - Add SUPER Accessory Files policy to Enabled, Ongoing (do not set Recurring Check-in)
  4. Set your SITE - Run SUPER for macOS updates policies to Enabled, Recurring Check-in, Run Once Per Week
  5. Set your SITE - Switch to SUPER for MacOS Updates policy to Enabled, Recurring Check-in, Run Once Per Computer
  6. Run "sudo jamf policy" on the Mac to kick things off or just wait for the policies to run.

...


The Configuration Profile for SUPER has a schema loaded to make it easy to adjust settings:
 
Image RemovedImage Added
 
 
You will need to Add Properties if you want to try a count-deferral or date-deferral instead of a number-of-days-deferral.
 
This schema should be complete, I have extended it from the one available in the SUPER gitbutgithub, but if you find anything missing let me know.  Hopefully it will be available in the github soon - I added an issue with the schema file attached.
 
It's also possible to turn off updates, or set a "Zero Date" for the # days, if you want it to happen sooner, or want to put off updates for a long time.
 
That may be important, e.g in the case of updates that turn out to break things. Because of that possibility it will be best to create separate config profiles for each major MacOS version, like we do with Nudge - so we can turn off the particular version's upgrades if needed.

...