Software update settings
With Relution 26.1.0, the new Apple configuration Software update settings has been introduced for devices running iOS 18 or later. It controls the update behavior of the devices: beta program, notifications, automatic download and installation, and the deferral of updates. It thereby replaces, among other things, deferring updates via the restrictions (Force delayed software updates).
The legacy System updates configuration is marked as deprecated in Relution. Its successor is the Managed Software Updates configuration (see below). To enforce a target version across the entire device fleet, Software update settings and Managed Software Updates are combined. For supervised devices running a version earlier than iOS 17, which do not support Managed Software Updates, System updates can still be assigned for a transitional period. If both configurations are assigned to a device that supports declarative software updates, Managed Software Updates takes precedence.
Configuration
The configuration is available in policies for iOS, tvOS and visionOS; the portal marks it there with iOS 18+, tvOS 18.4+ and visionOS 26+ respectively. The macOS variant with its own fields is described in the article Software Update (macOS) →. One configuration of this type is possible per policy. Devices that do not support the configuration (for example, before iOS 18) do not receive it. Which settings the form shows depends on the platform of the policy (see Platforms).
In the portal, the Software update settings configuration is divided into the following sections.
General
Show all software update enforcement notifications
- Enable / Disable (default: enabled)
If the switch is disabled, the device only shows the notifications triggered one hour before the enforcement deadline and the restart countdown notification.
Updates shown to the user
- All — the device shows all available update versions.
- Newest — the device only shows the newest (highest) version.
- Oldest — the device only shows the oldest (lowest) version.
The selection applies when several updates are available at the same time. No option is preselected; without a selection, Relution does not send a value and the device keeps its default behavior.
Beta program enrollment (only in supervised mode)
- Allowed (default) — the user can enroll in any beta programs associated with their signed-in Apple Account.
- Always Off — the device is not allowed to enroll in beta programs and is removed from any beta programs it is already enrolled in.
Automatic Software Update actions
On iOS, these settings only take effect on devices in supervised mode. User choice is preset for all three settings.
Automatically download available OS Updates
- User choice
- Always Off
- Always On
Automatically install available OS Updates
- User choice
- Always Off
- Always On
Automatically install available security update
- User choice
- Always Off
- Always On
The options work the same way for all three settings:
| Option | Effect |
|---|---|
| User choice | The user turns the function on or off in the device settings. |
| Always Off | The function is turned off; the user cannot turn it on. |
| Always On | The function is turned on; the user cannot turn it off. |
The two installation settings only take effect if automatic downloads are enabled on the device.
Deferral of OS Updates
On iOS, this setting only takes effect on devices in supervised mode.
- Delay in days: Number of days by which a major or minor operating system update is deferred on the device. Allowed values are 1 to 90 days.
A new update only appears on the device once this number of days has passed since its release. The field is empty initially; without a value, Relution does not send a deferral.
Rapid Security Response
On iOS, these settings only take effect on devices in supervised mode. Apple now refers to the former Rapid Security Responses as Background Security Improvements; the section title still uses the former term.
- Allow background security improvements to the user: If the switch is disabled, the device does not offer background security improvements to the user for installation.
- Allow rollbacks of background security improvement to the user: If the switch is disabled, the device does not offer the user the option to remove an installed security improvement again.
Both switches are enabled by default.
Platforms
The form shows the settings described above in iOS policies. In policies for tvOS and visionOS, individual settings are missing:
- tvOS: The form only contains Show all software update enforcement notifications, Automatically install available OS Updates and Delay in days.
- visionOS: Beta program enrollment and the Rapid Security Response section are missing.
The Automatic Software Update actions and Deferral of OS Updates sections are also marked Supervised in tvOS and visionOS policies.
Example: Deferred but automatic updates
On supervised iOS devices, new operating system versions should only appear after two weeks and then be installed without user interaction; beta versions are excluded.
- Beta program enrollment:
Always Off - Automatically download available OS Updates:
Always On - Automatically install available OS Updates:
Always On - Automatically install available security update:
Always On - Delay in days:
14
New operating system updates only appear on the devices 14 days after their release and are then downloaded and installed automatically. Users can neither turn off the automatic updates nor enroll in beta programs.
Managed Software Updates
New in 26.4The Managed Software Updates configuration enforces operating system updates, targeting a specific version by a deadline. It is the successor to the deprecated System updates configuration and complements the Software update settings configuration described above: those settings control the update behaviour (automatic download, deferral, notifications), while Managed Software Updates defines bindingly which version has to be installed by when.
It requires iOS 17 or later in supervised mode. The configuration is also available for tvOS 18.4 and later and visionOS 26 and later.
Target version
- Version to enforce (default: Latest minor version)
- Latest minor version — updates happen within the installed major version.
- Latest major version — the device is raised to the most recent available major version.
- Minimum specific version — a concrete version is set as the minimum level. It is selected in the mandatory Version field from the list of available operating system versions.
Enforcement
- Enforcement schedule (default: Relative to release date)
- Relative to release date — the deadline results from Days after release (mandatory, 0 or more) and Time of day (preset to 00:00). The same rule then applies automatically to every future version.
- Specific date and time — the Deadline is set as a fixed point in time.
- Grace period after enrollment — optional. Postpones the deadline until this many days after a device was enrolled, so that freshly enrolled devices are not forced to update immediately. It applies to both enforcement schedules and only ever extends a deadline, never shortens it. Leaving the field empty disables the function.
An enforcement is only sent if the device reports available updates. If there is no suitable update for a device, e.g. no newer minor version, no enforcement is sent. A deadline that has already passed is still sent to the device; the update is then enforced at the next restart.
Details
- Details page URL — optional link that iOS shows to users in the update announcement.
Triggering Updates
There are two ways to perform iOS updates:
Policy Configuration The Managed Software Updates configuration defines the target version and deadline (see above). The deprecated System updates configuration (only in supervised mode) still defines weekdays (Repeats on) and a Start time for scheduled updates. The latest available update is installed, optionally limited by Max. version to update to.
Device Action The Install Update device action in the device inventory installs one of the versions available for the device immediately. In addition, the action defines how the update is performed: Download and install updates, Only download updates, don’t install or Only install already downloaded updates.
For iOS devices to successfully perform an update, the following applies:
- Devices must be sufficiently charged or connected to a power source.
- Devices must be unlocked; otherwise, users must enter their device passcode.
- Supported iOS devices check for updates once per day, independently of the System updates configuration.
- The System updates configuration overrides any restrictions on deferring updates.
- No users should be signed in on shared devices.