-
Notifications
You must be signed in to change notification settings - Fork 82
Alternate Workflows
The default super workflow only attempts to install macOS upDATES if they are available. However, there are several alternate workflows options that allow you to leverage the deferral and deadline features of super to install other items.
Instead of having super automatically select the beginning date and time of the super workflow (aka. day zero), this option sets a specific date and time as day zero.
Command option example:
--workflow-zero-date-manual=2024-09-30:12:00
Command option disable example:
--workflow-zero-date-manual=X
Configuration Profile Example:
<key>WorkflowZeroDateManual</key>
<string>2024-09-30:12:00</string>
At a minimum, you must always specify "year-month-day". Hours are represented by a 24-hour clock, and any non-specified hours or minutes are rounded to "00".
This option is largely used for testing days-based deadline workflows, but it can also be used in production to set potentially more consistent day zero behavior. Note that you need to manually update this value every time you want to set a new workflow day zero.
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 --workflow-jamf-policy-triggers and/or --workflow-restart-without-updates options to take advantage of dialogs, notifications, deferrals, and deadline workflows provided by super. Obviously, the --workflow-disable-update-check option 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 update workflows. With this combination of options, the super workflow deletes any local super settings, kills any existing super processes, deletes any saved credentials, and deletes the super LaunchDaemon.
Disable the automatic relaunch of the super workflow when no macOS updates or upgrades are available and/or allowed.
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 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.
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.
Make the super workflow run one or more Jamf Pro Policy Triggers that are comma separated with no spaces.
Command option example:
--workflow-jamf-policy-triggers=Trigger1,Trigger2,Trigger3
Command option disable example:
--workflow-jamf-policy-triggers=X
Configuration profile example:
<key>WorkflowJamfPolicyTriggers</key>
<string>Trigger1,Trigger2,Trigger3</string>
With this option enabled the super workflow runs the Jamf Pro Policy Triggers first, immediately followed by the macOS update or upgrade. As a default behavior, Jamf Pro Policies only run if the system also needs to restart for Apple software updates.
Alternately, this option can be used along with the --workflow-disable-update-check option so even when there are no macOS updates available you can still take advantage of dialogs, notifications, deferrals, and deadlines provided by super. However, the super workflow does not automatically restart the computer when the --workflow-disable-update-check option is enabled. This is by design as it's assumed that one of the specified Jamf Pro Policies is going to restart the computer.
Therefore, if you want super to only run your Jamf Pro Policies and to also force a restart then you must specify both the --workflow-disable-update-check and --workflow-restart-without-updates options along with your Jamf Pro Policy Triggers.
When deploying super using the command line, if any Policy Trigger names contains any special characters or spaces then you should surround the text with single ' quotes. However, when deploying super using a Jamf Pro Policy with Script Parameters do not use single quotes.
Make the super workflow 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 --workflow-disable-update-check and --workflow-jamf-policy-triggers options to take advantage of dialogs, notifications, deferrals, and deadline workflows provided by super.