Relution Signet Customer Hub

Software Update

With Relution 26.1.0, the new Apple configuration Software Update has been introduced for devices running iOS 18 or later. This configuration can be used alongside the existing System Updates configuration. It replaces, among other things, the Update Deferral restrictions and the update behavior from the legacy System Updates configuration, which is marked as deprecated in Relution.

To ensure updates across the entire device fleet, both Software Update and System Updates can be configured in parallel and deployed to all iOS devices.

General

Beta Program Enrollment

  • Allowed
  • Always Off

Software Update Notifications

  • Show all notifications
  • Updates shown to the user:
    • All
    • Latest
    • Oldest

Automatic Software Update Actions

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 Updates

  • User Choice
  • Always Off
  • Always On

Deferral of OS Updates

  • Number of days: Number of days to postpone a major or minor operating system update on the device

Rapid Response for Security Updates

  • Allows the user to install security improvements in the background
  • Enables the user to roll back security updates in the background

Managed Software Updates

New in 26.4

The 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 described above: those 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
    • Latest major version — the device is raised to the most recent available major version.
    • Latest minor version — updates happen within the installed major version.
    • Minimum specific version — a concrete version is set as the minimum level.
  • Details page URL — optional link that iOS shows to users in the update announcement.

Enforcement

  • Enforcement schedule
    • Relative to release date — the deadline results from Days after release and Time of day. 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.

Triggering Updates

There are two ways to perform iOS updates:

Policy Configuration The System Updates policy can be used to define the time window for system updates.

Device Action Through actions in the device inventory, devices can be updated immediately to the latest available version.

For iOS devices to successfully perform an update, the following conditions must be met:

  • Devices must be sufficiently charged or connected to a power source.
  • Devices must be unlocked; otherwise, users must enter their device passcode.
  • The installed update will always be the latest publicly available iOS version.
  • Supported iOS devices check for updates independently of this policy configuration once per day.
  • This configuration overrides any restrictions on deferring updates.
  • No users should be signed in on shared devices.