Skip to main content
The Ops Playbook

Kandji Managed OS vs Jamf Pro Blueprints: Comparing macOS Update Enforcement

How does Kandji Managed OS compare to Jamf Pro blueprints for macOS updates? Map deadlines, deferrals and statuses, then pilot DDM enforcement before macOS 27.

Kandji Managed OS vs Jamf Pro Blueprints: Comparing macOS Update Enforcement
KBY Technologies12 min readTier L115 min

This playbook covers

Share

Kandji Managed OS (on macOS 14 and later) and Jamf Pro blueprints both send the Mac a declarative device management (DDM) declaration holding a target version and a deadline, and macOS then handles the notifications and the enforced install in the device’s local time. The difference is in how you express the policy. Kandji puts the minimum version, the deadline and Rapid Security Response enforcement in one Managed OS Library Item, and its Software Update Library Item deferrals are ignored by Managed OS. Jamf Pro splits the job across two blueprint components: Software Updates enforces a version and deadline, and Software Update Settings controls deferrals, automatic installs and Background Security Improvements. The key constraint: Apple removed software update commands and the legacy update settings in macOS 27, so on macOS 27 Jamf Pro enforcement belongs in blueprints. Rebuild it there and pilot it on a small group first.

#Current Method: How Kandji Managed OS Enforces macOS Updates

In Kandji, you add a Managed OS Library Item for a macOS major version and assign it to an Assignment Map or Classic Blueprint. The same version can be added several times with different labels to give groups different deadlines. Under Upgrades you choose one of three Version Enforcement options:

  • Do Not Manage, which leaves updates alone and cannot be combined with Continuously Enforce for upgrades.
  • Automatically Enforce New Updates, with a time frame after Apple releases an update.
  • Manually Enforce Minimum Version, with a minimum version and an Enforcement Deadline. Macs already above the minimum are not updated.

Both enforcing options set a floor; a Mac below it gets the latest macOS version Kandji has approved, not the floor itself. Since 29 November 2023 Kandji has used DDM for Managed OS on macOS Sonoma and later, and the operating system then controls notifications and enforcement. Users cannot defer past the deadline an hour at a time as they could with the older Kandji Agent flow, and enforcement always uses the Mac’s local time zone. The separate Enforcement Time Zone setting applies only to upgrades from macOS 13 and earlier.

A deferral of 1 to 90 days in the Software Update or Restrictions Library Item sets the ceiling of what users are offered. Managed OS ignores those deferrals for the updates it enforces, and it is not compatible with blocking the Software Update settings pane.

Kandji itself is deprecated, and Kandji’s documentation asks customers to complete the move to Iru by 1 December 2026. If you are still deciding whether to stay or move, our guide to the Kandji to Iru deadline and the option of migrating Macs to Jamf Pro covers that choice.

#Improved Workflow: Map Each Managed OS Setting to a Jamf Pro Blueprint Component

Jamf Pro offers two routes. Managed software updates, under Computers then Software Updates, sends update plans to groups; only its Download and schedule to install action uses DDM, and Jamf now notes that Apple removed software update commands in macOS 27. Blueprints are the route Jamf recommends for macOS 27, and they are what this workflow uses. Jamf’s blueprint guide also says the Software Updates and Software Update Settings components replace the update settings in the Software Update and Restrictions configuration profile payloads. Macs on earlier versions still honour those legacy settings, so a mixed fleet keeps the old profiles scoped to earlier versions and uses the blueprint components for macOS 27 and later.

Kandji Managed OS settings and their closest Jamf Pro blueprint equivalents
Kandji settingJamf Pro equivalentDifference to plan for
Manually Enforce Minimum Version with an Enforcement DeadlineSoftware Updates component, Specific OS version and timeJamf sends one unconditional declaration, and every scoped Mac must install that exact version by the deadline. It does not move when Apple ships a newer release, so you reconfigure the blueprint for each new target.
Automatically Enforce New Updates with a time frameSoftware Updates component, Latest OS version with a number of enforcement daysJamf generates one declaration per available version. Each deadline is the date Apple posted that version plus your days. Ignore major versions keeps Macs within their current major release.
Upgrades: Continuously Enforce or Install on-demand from Self ServiceLatest OS version with Ignore major versions selected or deselectedDeselecting Ignore major versions moves Macs to new major releases on the same enforcement schedule. The component documents no on-demand Self Service equivalent.
Software Update or Restrictions Library Item deferralsSoftware Update Settings component, DeferralsDeferrals run from 1 to 90 days, with separate macOS periods for major, minor and non-OS updates. A Software Updates declaration overrides them and makes the update visible at once.
Rapid Security Response enforcementSoftware Update Settings component, Background Security ImprovementsBackground Security Improvements is the renamed Rapid Security Response setting. Specifying an OS version also installs that version’s Background Security Improvements.
Library Item status: Downloading, Cached, Installing, Pass, ErrorBlueprint deployment status through the Jamf Pro API: Success, Pending, FailedWith Latest OS version, each Mac reports one status entry per declaration, so several entries per Mac are normal.

So: a Software Update Settings blueprint for the ceiling, a Software Updates blueprint for the floor, both scoped to smart groups that keep pilot and production apart. Limit blueprint editing and deployment to the team that owns patching. For a broader comparison, see our playbook on evaluating Jamf Pro against Kandji on a real Mac pilot.

#Implementation: Pilot DDM Update Enforcement in Jamf Pro

Use a pilot smart group of a few Macs whose users have agreed to take part.

  1. Confirm eligibility. Jamf says Macs below the component’s minimum OS version receive no declaration, do not show as failed and are skipped silently. Check each pilot Mac’s macOS version in inventory before deploying. Jamf’s managed software updates documentation requires a Bootstrap Token escrowed with Jamf Pro for unattended installs on Apple silicon, and for declared updates Apple says the Mac uses a bootstrap token if one is available or prompts the user for credentials. Stop if any pilot Mac is below the minimum or lacks an escrowed Bootstrap Token you expected.
  2. Record the current state. Before changing anything, record which Software Update and Restrictions configuration profiles, blueprints and managed software update plans are scoped to the pilot Macs, with their settings. This is the rollback reference. Do not enable managed software updates for the first time as part of this pilot: Jamf warns that enabling it starts a record cleanup that clears software update commands previously deployed from Jamf Pro and disables mass action software update commands.
  3. Build the ceiling. Create a blueprint with a Software Update Settings component. Set only what you need: Deferrals for major and minor macOS updates, the Install actions (Allowed, Always or Never) and Background Security Improvements. Remember that these settings override equivalent settings in existing profiles rather than merging with them. Click Save, then Deploy to the pilot group only.
  4. Build the floor. Create a blueprint with a Software Updates component and choose Specific OS version and time for the first pilot. A fixed version makes the evidence unambiguous. Set the deadline several days out so users see the notifications before enforcement; Kandji recommends at least five days for a first enforcement, and the same reasoning applies here. Click Save, then Deploy to the pilot group.
  5. Collect device evidence. On a pilot Mac, open System Settings, General, Device Management, open the MDM profile and check its Device Declarations. Apple documents that, once an update is declared, the Mac downloads and prepares it and shows the deadline in System Settings and in a notification. Stop if the declaration is missing after the Mac has checked in.
  6. Collect server evidence. Use the Jamf Pro API to view the blueprint’s deployment status. Success means every scoped declaration has reported in; Pending means at least one has not; Failed means at least one declaration reports valid: invalid. Stop on any valid: invalid and investigate before widening scope.
  7. Move to rolling enforcement. After the pilot Macs reach the target version, change the component to Latest OS version, set your enforcement days and decide whether to select Ignore major versions. Deploy to the pilot group again and repeat steps 5 and 6 before adding production groups.
Serious concentrated engineer in hardhat and formally suit sitting at table with blueprints while working on laptop against gray background
Photo by Andrea Piacquadio on Pexels

#Guardrails

  • Keep scope narrow. A Software Updates declaration takes precedence over Software Update Settings deferrals, so a misplaced blueprint exposes updates on every Mac it reaches.
  • Plan for the deadline itself. Apple documents that, at the local enforcement time, macOS force quits all open apps, regardless of unsaved documents, and restarts if necessary.
  • Expect notifications to get louder. Do Not Disturb is ignored in the 24 hours before enforcement. If Notification preference for updates scheduled by declarations is set to Disable, users see a notification only 60 minutes before the install is required.
  • Avoid the managed software updates action Download, install, and restart on user Macs. Jamf warns it can cause data loss because the Mac restarts without warning when the command completes.
  • Deadlines use each Mac’s local time zone in both products; pick a time that suits every region.
  • In a mixed fleet, scope legacy Software Update and Restrictions profiles to Macs below macOS 27 and the blueprint components to macOS 27 and later, as Jamf advises.

#Validation

  1. Every pilot Mac shows the Software Updates declaration under Device Declarations in its MDM profile.
  2. The blueprint’s deployment status shows Success for each pilot Mac, with no valid: invalid entries.
  3. Users report seeing the deadline in System Settings and in notifications before the enforcement date.
  4. Each pilot Mac’s inventory shows the target version after the deadline.
  5. With Latest OS version, entries showing valid: unknown with Error.ActivationFailed and Info.Predicate are treated as expected: Jamf explains that the declaration’s condition was false for that Mac, for example because it was already on a newer version.

#Common Mistakes

  • Starting with rolling enforcement. Kandji warns that a two-week automatic window, when Apple has shipped nothing in the last two weeks, makes every out-of-date Mac update straight away. Jamf calculates Latest OS version deadlines from Apple’s posting date in the same way, so expect a version posted longer ago than your enforcement window to have a deadline that has already passed. Start with Specific OS version and time.
  • Expecting deferrals to hold back an enforced update. In both products, the enforcing declaration wins over deferrals.
  • Treating every non-success entry as a failure. Several status entries per Mac and valid: unknown entries are normal with Latest OS version. Only valid: invalid needs investigation.
  • Assuming new group members inherit a scheduled plan. For managed software updates, Jamf says a Download and schedule to install plan applies only to computers in the group at deployment time; adding a Mac to the smart group later does not apply it.
  • Missing silently skipped Macs. Ineligible Macs never appear as failed, so compare the pilot group’s membership with the status entries returned.
Top view of an architecture workspace with a laptop, blueprints, and notes.
Photo by Antoni Shkraba on Pexels

#Recovery

If the pilot goes wrong before the deadline, edit the Software Updates component to a later deadline or remove the pilot group from the blueprint, then Deploy. Confirm on a pilot Mac, under Device Declarations, that the declaration has changed or gone. If it has not changed after the Mac checks in, stop and escalate to Jamf support rather than stacking more changes. Restore any legacy profiles you recorded in step 2 only for Macs below macOS 27, where they still apply.

For plans sent through managed software updates, Jamf documents one way to revoke a Download and schedule to install declaration: turn the Use new feature switch off and back on. That affects the whole feature, not one plan.

If a Mac misses its deadline because it was offline, short of battery or low on free space, Apple says the Mac detects that it has not reached the declared state, resumes the process when it is back online, shows a past-due notification and attempts the install within the next hour. Verify recovery from inventory and deployment status.

#Measurable Outcome

Measure what Jamf Pro shows, not estimates:

  • The share of pilot Macs on the target version by the deadline, from inventory.
  • The number of declarations reporting valid: invalid, which should be zero before you widen scope.
  • The number of Macs still Pending a set time after deployment, and the reason for each.
  • The number of pilot Macs silently skipped as ineligible.

Review these weekly during the pilot and after each Apple release once Latest OS version is live.

#Kandji to Jamf Pro Update Enforcement Checklist

  • Kandji Managed OS settings, labels and deferral values recorded for each Blueprint or Assignment Map node.
  • Pilot smart group created, with every Mac at or above the component’s minimum OS version.
  • Bootstrap Token escrow confirmed for Apple silicon pilot Macs.
  • Existing Software Update and Restrictions profiles, blueprints and plans scoped to the pilot recorded as the rollback reference.
  • Software Update Settings blueprint deployed to the pilot only.
  • Software Updates blueprint deployed with Specific OS version and time and a deadline several days out.
  • Declaration seen under Device Declarations on a pilot Mac, and Success in the deployment status.
  • Legacy profiles scoped only to Macs below macOS 27.

The next safe decision is whether to switch the pilot to Latest OS version, and whether to select Ignore major versions. Make it only when every eligible pilot Mac reached the target version with no valid: invalid entries, and keep your recorded profiles as the rollback boundary.

About this page

Credited to

Dates

Published

Sources

This page lists no external sources.

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Kandji Managed OS vs Jamf Pro Blueprints: Comparing macOS Update Enforcement. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Discover more

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Operate smarter, with fewer recurring tickets.

Receive new operational playbooks, incident-prevention guidance, automation scripts and recovery runbooks.