Skip to main content

On-Demand macOS Updates from the Device Page

Updated yesterday

Swif now lets admins push a one-off macOS update to any single Mac directly from its Device Details page—no policy editing required. Use it when you need to patch a VIP’s laptop, ship the latest beta to a developer, or close a zero-day faster than your standard ring-based policy.


What you’ll see

UI area

What it shows

Updates tab (new)

A live feed of every macOS update Apple has advertised to that Mac ▷ OS name, version, “Allows Install Later”, release date and current status (New, Downloaded, Failed, Installed).

Manage ▸ Update OS

A wizard that lets you pick the install action and an optional target version for an immediate update.


Step-by-step

  1. Open Device Details → choose the Mac you want to patch.

  2. Click the Updates tab to confirm the versions Apple is offering.

  3. Pick Manage ▸ Update OS.

  4. Select an Install Action:

Option

Behaviour

When to use

Download & install (default)

Downloads immediately, installs at next opportunity (user can defer once).

Routine patches.

Download only

Caches the update; user triggers install later.

Low-bandwidth sites, staged roll-outs.

Notify user

macOS Software Update banner only. No auto download.

Informational / last-chance reminder before enforcing via policy.

Download, install & allow deferral

Installs, but user may click Later up to your Max Deferral count (set in Software Update Policy).

User-centric orgs needing “nudge” rather than force.

Download, install & restart

Forces a reboot once install finishes (supervised Macs only).

Urgent security fixes, kiosks.

5. (Optional) Pick a Target Version from the drop-down. If left blank, macOS takes the newest eligible build.

6. Click Continue to queue the command.


What happens under the hood

Phase

Detail

Queueing

The command enters the high-priority “MDM” queue. Device Lock/Wipe still outrank it, but it jumps ahead of inventory collection or low-risk policies.

Delivery

Swif uses Apple Push Notification service (APNs) to wake the Mac; fallback polling occurs every 30 min.

Timeouts

If the command is sent but macOS hasn’t replied within 15 minutes, it retries automatically. If the Mac is offline, the command will stay in queue for 30 days.

Status updates

A full command trail appears in the Commands tab.

Policy coexistence

Per-device actions do not override your fleet-wide Software Update at Night or regular Software Update policy; they simply run once. If a conflict arises, whichever action reaches the device first wins.


Requirements & limitations

  • macOS 11 (Big Sur) or later, enrolled with Swif MDM & APNs reachable.

  • “Download, install & restart” and deferral enforcement require supervised Macs (ABM/ASM ADE or User-Approved MDM + macOS 15 Sequoia).

  • Declarative Device Management (DDM) features—e.g., Software Update at Night—use Apple’s new scheduling keys and may supersede ad-hoc actions if both target the same patch.


Best practices

  • Test first on a pilot Mac to verify driver or app compatibility.

  • Combine with a macOS Software Update at Night policy for low-touch fleet hygiene, reserving ad-hoc pushes for emergencies.

  • Encourage users to keep lids open and power connected overnight; updates that miss the window will install at next launch.

Need to force a reboot right now? Choose Download, install & restart—Swif will download the build, install, and trigger a reboot as soon as the Mac confirms the payload. As always, you can audit every step in the Commands tab via Swif’s webhook events.

Did this answer your question?