-
Notifications
You must be signed in to change notification settings - Fork 0
Alternate Workflows
These options offer alternate workflow behaviors that can be especially helpfull when using super to deploy non-system updates or temporary super workflows.
Make super perform a system restart even if there are no restart-required macOS updates or upgrades.
Command option example:
--workflow-restart-without-updates
Command option disable example:
--workflow-restart-without-updates-off
Configuration profile example:
<key>WorkflowRestartWithoutUpdates</key>
<true/>
DO NOT USE this option if you want to perform macOS updates or upgrades. This option is literally designed for the case when you do not want to perform a macOS update but you still want to enforce a system restart.
This option can also be used along with the --install-jamf-policy-triggers and --workflow-disable-update-check options to specify a workflow that will only install Jamf Pro Policies and then forcibly restart the computer.
Disable the super workflow from checking for, downloading, or installing any Apple software updates or upgrades, even if they are available.
Command option example:
--workflow-disable-update-check
Command option disable example:
--workflow-disable-update-check-off
Configuration profile example:
<key>WorkflowDisableUpdateCheck</key>
<true/>
DO NOT USE this option if you want to perform macOS updates or upgrades. This option is literally designed for the case when you do not want to perform any Apple software updates.
This option is most commonly used for a workflow where you only want to install the super items without actually starting a macOS update or upgrade workflow. This option can also be used along with the --install-jamf-policy-triggers and/or --workflow-restart-without-updates options.
Obviously, the --workflow-disable-update-check option can not be used along with the --workflow-only-download options.
Lastly, you can use the --workflow-disable-update-check option along with the --reset-super and --auth-delete-all options to fully disable any active or deferred super workflows. With this combination of options, all local super settings and credentials are deleted and any existing super processes are killed.
Disable the automatic relaunch of super after the current workflow successfully completes.
Command option example:
--workflow-disable-relaunch
Command option disable example:
--workflow-disable-relaunch-off
Configuration profile example:
<key>WorkflowDisableRelaunch</key>
<true/>
As a default, if the super workflow completes (for example, when macOS is already on the latest version that is available and/or allowed), super automatically relaunches every 360 minutes (6 hours) to check for the availability of new macOS software. Additionally, every time super starts up it also checks for settings deployed via configuration profile.
While the --workflow-disable-relaunch option disables this behavior, you can also adjust the timing of the automatic relaunch via the --deferral-timer-workflow-relaunch option.
Reset all local super settings after the current workflow successfully completes.
Command option example:
--workflow-reset-super-after-completion
This option can only be enabled or deployed via command line. It's useful for specifying an alternate temporary super workflow that's only active until succesfull completion. For example, combining this option with the --install-macos-major-upgrades option allows super to perform a macOS major upgrade and then return to the default behavior of only targeting macOS minor updates.
Further, you can combine this option with the --workflow-install-now option to allow for a temporary user-initiated mac OS upgrade workflow that, again, after completion will return super back to a default workflow.
Keep in mind that managed settings deployed via configuration profile always remain active and will override any command line options. As such, it's best to keep "always configured" super options deployed via configuration profiles and "temporary" super options deployment via command line.