About Managed OS for macOS
Managed OS for macOS deploys and enforces macOS updates across your fleet of Mac computers via Declarative Device Management (DDM). You can offer major macOS upgrades on-demand from Self Service or have them enforced automatically. When you configure Managed OS, Iru declares the required macOS version and deadline; macOS handles download, caching, notifications, and installation. Iru handles:Update detection
Download and caching
User notification
Automatic installation
Compliance monitoring
Adding Managed OS for macOS to your Library
Add the Library Item for the macOS release you want to manage, such as macOS 26 Tahoe or macOS 27 Golden Gate. To add it to your Iru Endpoint Library, follow the steps outlined in the Library Overview article. When you select Add Library Item, choose that release.Adding multiple Managed OS Library Items
When using Iru Endpoint, you can add the same Managed OS version to your Library multiple times. This is helpful when configuring different settings for various Blueprints or creating distinct update settings for nodes in an Assignment Map. To differentiate between these copies, you can use labels. See Library Item Labels in Library Overview for steps.Configuring Managed OS for macOS
General
Use General to name this Library Item and assign it to Blueprints.Add Label
Assign to Blueprints
Upgrades
Use Upgrades to configure how and when devices install this major version of macOS. Devices that upgrade receive the latest minor version available for that major version.Choose an upgrade method
- Upgrade automatically forces the device to upgrade either immediately after Library Item assignment or on a specified date and time.
- Upgrade on demand from Self Service lets users upgrade through Self Service or Software Update with no enforced deadline. You can make additional copies of the Library Item to use different settings for different Blueprints.
Choose when to enforce the upgrade
Make the upgrade available in Self Service

Choose a Self Service category

Customize the Self Service item

Updates
Use Updates to configure minor-version enforcement for devices already running this major version of macOS.Choose a Version Enforcement option
- Do not manage updates does not manage macOS updates. You cannot select it when Upgrade automatically is selected because Upgrades also controls the upgrade schedule.
- Enforce a specific version enforces the exact macOS version and deadline you specify.
- Rolling enforcement automatically calculates the minimum required version based on when Apple released each update.
- Manually enforce a minimum version enforces the minimum version and deadline you specify.

Configure Rolling enforcement
- Select Within (1 day, 2 days, 1 week, 2 weeks, 3 weeks, 1 month, 2 months, or 3 months) of release and at a time for enforcement.
- Optionally, set Delay enforcement by to a number of days (up to 90). This delays when Iru sends the target-version declaration without changing the enforcement date. Use it to temporarily hold back the newest available version while still using Rolling enforcement.
- Optionally, to hide the new version from users for the same period, set a matching deferral in a Software Update Library Item. If Delay enforcement by is shorter than that deferral, Managed OS still overrides the deferral once its declaration is sent.

Review the enforcement timeline
Configure a minimum version
- Choose the Minimum version, Enforcement deadline, and Enforcement time. Updates are not enforced on a Mac already running a version later than the specified minimum.
- Optionally select the Enable phased rollout checkbox, then enter the number of hours in the Rollout window field (24–168). See Configure a phased rollout for details.

Configure a specific version
- Choose the Specific version, Enforcement deadline, and Enforcement time. This option enforces the exact macOS version instead of treating it as a minimum.
- Optionally, select Enable phased rollout. See Configure a phased rollout for details.
- To enforce an Apple beta build, select This is a beta version, choose a Seed Token synced from Apple to Iru, then enter the beta version and build. Iru applies two declarations to the device in order: Software Update Settings (to enroll the device in the beta program), then Software Update Enforcement (to the specified version). For example, to test a beta upgrade to the next major macOS release, use a macOS Tahoe Managed OS Library Item, select a macOS Golden Gate seed token, and enter the target major version (such as
27.0) and the current AppleSeed beta build. - If you use Managed OS for beta enrollment and version enforcement, set Beta program enrollment in any Software Update Library Item on the same Blueprint to Not configured. For opt-in beta enrollment or enrollment without a required version, see Testing Apple Beta Releases.

Configure a phased rollout
Optionally select the Enable phased rollout checkbox, then enter the number of hours in the Rollout window field (24–168).- For Rolling enforcement, when Apple releases a new version, declaration issuance starts after any Delay enforcement by period ends, or immediately if no delay is set.
- For Manually enforce a minimum version, declaration issuance is staggered from Library Item save when you first create the item, or when you change OS version settings or the enforcement date or time, and again when Apple releases a new version.
- For Enforce a specific version, declaration issuance is staggered from Library Item save when you first create the item, or when you change OS version settings or the enforcement date or time.
Enforcement timeline
Timeline preview shows when versions are delayed, targeted, required, and past due, based on your enforcement settings. Each version appears on its own row. Months and days run across the top, and markers show events such as a release and the target version. Hover the pointer over any item in the timeline for more details about that item. The legend includes Delayed, Target version, Minimum required version, and Update past due. Hover the pointer over the information icon next to Timeline preview to see the full legend.- Delayed: The version has been released by Apple, but initial declarations are withheld from devices until the delay configured in this Library Item expires.
- Target version: The version available for install. Devices that update are taken to this version. Devices running this version or the minimum required version are in Pass status.
- Minimum required version: The minimum version a device can be running to be in Pass status.
- Update past due: Devices still on this version are forced to update to the new version. If a device is not updated after an extended time, check it manually. An operating system issue can prevent the update from installing.
Background Security Improvements Enforcement
Configure Background Security Improvements Enforcement
- None: Background Security Improvements will not be enforced.
- Automatically enforce: Choose the enforcement timeframe and local time for enforcement.
Set Background Security Improvements Enforcement Timeframe
Configure Background Security Improvements Enforcement Time
Save the configuration