Skip to main content
The Ops Playbook

Kandji vs Jamf Pro for Automated Device Enrollment: PreStages and ADE Library Items Compared

How does Kandji compare to Jamf for Mac Automated Device Enrollment? Map PreStages to the Iru ADE Library Item, Blueprint Routing and Setup Assistant settings.

Kandji vs Jamf Pro for Automated Device Enrollment: PreStages and ADE Library Items Compared
KBY Technologies11 min readTier L115 min

This playbook covers

Share

Kandji (now Iru Endpoint) and Jamf Pro both build on Apple’s Automated Device Enrollment (ADE), so a Mac assigned to either service in Apple Business or Apple School Manager is enrolled and supervised during Setup Assistant. The difference is where each product keeps the enrollment settings and how a Mac is routed to them. Jamf Pro keeps Setup Assistant, account, minimum macOS, enrollment package and enrollment profile settings in a PreStage enrollment that belongs to one ADE instance and is scoped to serial numbers. Iru keeps the same kind of settings in an Automated Device Enrollment Library Item attached to a Blueprint, and routes waiting devices by Blueprint assignment or by Blueprint Routing rules that are evaluated once, at enrollment. The key constraint is the same in both: these settings act only while a Mac is in Setup Assistant, and Iru states that changes apply only to devices that enrol after you save. Compare them on a pilot Mac, never on the production scope.

#Current Method: Comparing MDMs From Feature Lists Instead of the Enrollment Path

Most Kandji and Jamf evaluations compare dashboards, app catalogues and patching. Enrollment gets less attention, yet a wrong ADE setting only shows itself on a Mac going through Setup Assistant, so mistakes are slow to find and expensive to repeat.

The dependencies are the same for both products and sit outside either console:

  • An Apple Business or Apple School Manager organisation that owns the Macs.
  • A device management service in Apple Business, created from the MDM’s public key (.pem), which issues the service token (.p7m) the MDM uploads.
  • Device assignment: Apple Business must assign a Mac to a device management service before Setup Assistant shows the enrollment pane for that service.
  • Internet access during Setup Assistant, which both vendors require. Iru also requires Apple Push Notification service before ADE.

A side-by-side scorecard is useful, and the KBY guide to piloting both MDMs on real Macs and scoring them covers the wider evaluation. This playbook covers only the enrollment path.

#Improved Workflow: Map Each ADE Control Across Both Products

The table reflects Jamf Pro documentation 11.34.0 and Iru Endpoint documentation as published in November 2026. Iru moved its apps from Kandji to Iru branding on 8 April 2026, so older screenshots and links may still say Kandji.

Where Automated Device Enrollment settings live in Jamf Pro and Kandji (Iru Endpoint)
ADE controlJamf ProKandji (Iru Endpoint)
Token connectionSettings > Global > Automated Device Enrollment > New, then Upload Server Token File. Each token creates one ADE instance; repeat for more instances. A token is valid for one year after upload.Account Menu Button > Integrations > Apple > Set up Automated Device Enrollment. The page shows one token; additional tokens are added with the Iru Endpoint API.
Where settings liveA PreStage enrollment tied to one ADE instance, edited as payloads (General, Account Settings, Configuration profiles, Enrollment packages and others).An Automated Device Enrollment Library Item with universal settings and per-platform sections, assigned to a Blueprint or to Blueprint Routing.
How a Mac is routedPreStage Scope tab: selected serial numbers, or Automatically assign new devices.The Blueprint chosen for a device awaiting enrollment, a default ADE Blueprint, or Blueprint Routing rules evaluated top to bottom at enrollment.
Setup AssistantSkip chosen screens, or Automatically advance through Setup Assistant (macOS 11 or later) with language and region.Skip chosen screens, or automatically advance; region and language for auto-advance require Ethernet.
Local accountsAccount Settings payload: managed local administrator, primary account as Administrator, Standard or Skip, pre-fill and lock.Primary account type, Provision local administrator account, Hide Account, and Make auto admin the MDM enabled user.
User authenticationEnrollment customization with a Single Sign-On Authentication PreStage Pane (requires SAML SSO in Jamf Pro).Require authentication in the ADE Library Item, using Custom SAML, Google Workspace Native or Microsoft Entra ID Native.
Work before the desktopEnrollment configuration profiles and signed distribution packages installed before Setup Assistant completes.Install Library Items during Setup Assistant, with an automatic release after 15 minutes by default (1 to 120), then Liftoff after enrollment.
Minimum OS at enrollmentMinimum required macOS version (macOS 14.4 or later): No enforcement by default, latest options or a specific version.Require minimum OS version: Version must be greater than or equal to, and Update to.

The trade-off: Jamf Pro routing is explicit, so a serial sits in exactly the PreStage you scoped it to. Iru routing can be rule-based, so a tag set before the Mac arrives can choose its Blueprint, and the Blueprint Routing Activity tab records which rule matched. Explicit scope is easier to audit; rules scale better, but you only learn the destination when the Mac enrols.

Roles: assigning devices needs an Apple Business role allowed to assign devices to device management services, reading Jamf PreStages needs an API client with Read Computer PreStage Enrollments, and Blueprint Routing needs an Iru tenant administrator.

#Implementation: Run One Pilot Mac Through Each Product

Use one or two Macs per product that are new or already erased. Leave production PreStages, Blueprints and default assignments untouched.

  1. Back up the Jamf Pro PreStage configuration. Create an API role with only the Read Computer PreStage Enrollments privilege and an API client that uses it. Request a token, put the access_token value from the response in TOKEN (it expires after the client’s configured lifetime), then save every computer PreStage and the scope of the one you will compare against. These calls only read; with --fail, curl exits non-zero on an HTTP error, so stop there.
    1curl --request POST --url "$JAMF_URL/api/v1/oauth/token" \
    2  --header 'content-type: application/x-www-form-urlencoded' \
    3  --data-urlencode 'grant_type=client_credentials' \
    4  --data-urlencode "client_id=$CLIENT_ID" \
    5  --data-urlencode "client_secret=$CLIENT_SECRET"
    6
    7curl --fail --request GET --url "$JAMF_URL/api/v3/computer-prestages?page=0&page-size=100&sort=id%3Adesc" \
    8  --header 'accept: application/json' --header "Authorization: Bearer $TOKEN" > prestages-before.json
    9
    10curl --fail --request GET --url "$JAMF_URL/api/v2/computer-prestages/$PRESTAGE_ID/scope" \
    11  --header 'accept: application/json' --header "Authorization: Bearer $TOKEN" > scope-before.json
  2. Record and set the Apple Business assignment. In Apple Business, note the device management service the device list shows for each pilot serial. Then assign each pilot Mac to the Jamf Pro or Iru service it will test. Precondition: the Mac is not in use. Rollback: assign it back to the recorded service. A default device assignment applies only to devices added afterwards; existing devices must be assigned by hand.
  3. Build the Jamf Pro pilot PreStage. In Jamf Pro, click Computers > PreStage enrollments > New. Name it (for example Mac-Pilot-ADE), choose the ADE instance, and leave Automatically assign new devices cleared so new purchases do not land in the pilot. Choose the Setup Assistant screens to skip, configure Account Settings, set Minimum required macOS version, and add only essential enrollment packages. On the Scope tab, select only the pilot serials and click Save. If a pilot serial already sits in another PreStage, remove it from that scope first, then add it here. Stop if the serial does not appear on the Scope tab after a few minutes; Jamf Pro syncs with Apple every two minutes.
  4. Build the Iru pilot configuration. Create an Automated Device Enrollment Library Item and assign it to a pilot Blueprint. In the Mac section, configure the Setup Assistant screens, Primary account type, Provision local administrator account and, if you need it, Require minimum OS version. Turn on Install Library Items during Setup Assistant only for items that must exist before the desktop, and keep the default 15-minute release. Then go to Enrollment > Automated Device Enrollment, filter by Awaiting Enrollment, and assign the pilot serial to the pilot Blueprint. Rollback: reassign the serial to its original Blueprint.
  5. Enrol and time each Mac. Record the time from power-on to a usable desktop, the panes shown and every manual touch.
Laptop displaying code with reflection, perfect for tech and programming themes.
Photo by Christina Morillo on Pexels

#Guardrails

  • Keep the MDM profile non-removable in production. Jamf lists Make MDM profile mandatory and Prevent users from removing MDM profile among its commonly recommended General settings; Iru makes the profile non-removable by default and recommends against Allow MDM Profile Removal in production.
  • Never disconnect Iru ADE to renew a token; use Renew Token. In Jamf Pro, upload the new token to the existing instance and do not delete an expired instance first.
  • In Jamf Pro, never use the same username for the user-initiated enrollment administrator and the PreStage administrator; accounts may not be created correctly and the LAPS password will not be retrievable in the Jamf Pro API.
  • Leave the extra administrator non-MDM-enabled unless it is the real user; both vendors warn otherwise the user’s account cannot receive user-level profiles.
  • On Jamf Cloud, do not configure the PreStage Certificates payload; Jamf manages the SSL certificate.
  • Treat erasing a Mac to re-run Setup Assistant as a destructive step outside this playbook: use your organisation’s wipe procedure, with the user’s data backed up first.

#Validation

  • Jamf Pro scope: the pilot serial is listed on the pilot PreStage Scope tab, and a fresh call to /api/v2/computer-prestages/$PRESTAGE_ID/scope lists it under assignments as serialNumber.
  • Iru routing: the serial shows the pilot Blueprint under Awaiting Enrollment, and the ADE Library Item column names your pilot Library Item rather than None. With Blueprint Routing, the Activity tab shows the matched rule set, its position and label.
  • On the Mac: Setup Assistant shows only the panes you left in. On Iru, items in the Setup Assistant list run behind a Configuring Mac screen with no progress indicator. If the Mac is below the minimum, Iru shows a Software Update pane with a 60-second countdown, and Jamf Pro prompts the user to update before Setup Assistant continues.
  • After enrollment: accounts match your settings; a Jamf Pro auto-advanced Mac defaults to Pacific Time unless language and region are set.

#Common Mistakes

  • Cloning a Jamf Pro PreStage and expecting the scope to follow. The clone does not include the original scope.
  • Expecting Iru changes to reach enrolled Macs. Enrollment-time settings apply only to devices that enrol after you save. Changes to Require minimum OS version take effect without resyncing ADE settings to Apple.
  • Loading Setup Assistant with work. Jamf warns that too many enrollment profiles or packages can cause unexpected enrollment issues, and that payload variables in enrollment profiles are not replaced. Iru notes that each Library Item added to the Setup Assistant list increases time spent there.
  • Picking a specific macOS version in Jamf Pro for macOS 14 Macs. Jamf documents that an incompatible selection makes updates fail in Setup Assistant on macOS 14; choose a latest option instead. A specific version that Apple no longer lists is skipped.
  • Pre-filling accounts alongside Iru Passport. Turn off Prefill initial account creation details and Lock pre-filled account creation details; they conflict with Passport and can cause Setup Assistant errors.
  • Interactive installers in Liftoff. Iru warns that Custom Apps or Custom Scripts waiting on user input can be hidden and make Liftoff hang until the agent check-in times out. For the apps that follow, see Kandji Auto Apps compared with Jamf Pro App Installers.
A programmer working on code with a laptop and monitor setup in an office.
Photo by Jakub Zerdzicki on Pexels

#Recovery

  1. A Mac stuck on Configuring in Iru. Open the device record and select Release hold, which sends Apple’s DeviceConfigured command. Select Check status to confirm the banner clears. Items that had not finished continue through the Blueprint afterwards.
  2. A Mac in the wrong Jamf Pro PreStage. Remove it from that scope and add it to the correct PreStage. If a pilot change leaked into a production PreStage, compare the console against prestages-before.json and set each changed field back in the interface.
  3. An expired or replaced token. In Jamf Pro, download a new token from Apple Business or Apple School Manager and upload it to the existing instance. In Iru, select Renew Token; if ADE was disconnected by mistake, set it up again with a new token from the same device management service.
  4. A Mac assigned to the wrong service. Reassign it in Apple Business. Unassigning does not remove an enrolled Mac from management, but an unassigned Mac must be reassigned before it will be offered ADE again.

Verify recovery by repeating the validation checks above on the affected serial. If you are weighing a move between the two products rather than a pilot, the Kandji to Iru upgrade or Jamf Pro migration decision sets out that choice.

#Measurable Outcome

Judge the products on figures from your own pilot:

  • Minutes from power-on to a usable desktop for each pilot Mac, per product.
  • Setup Assistant panes shown and manual touches needed per Mac.
  • Days left on each service token, checked monthly; a Jamf token is valid for one year after upload.

Repeat the pilot after each major macOS release and whenever you change accounts, authentication or the minimum OS setting.

#Kandji and Jamf Pro ADE Pilot Checklist

  • PreStage JSON and scope saved with a read-only API client.
  • Original Apple Business assignment recorded for every pilot serial.
  • Jamf pilot PreStage scoped to pilot serials only, with automatic assignment cleared.
  • Iru ADE Library Item on a pilot Blueprint, Setup Assistant list kept short, 15-minute release kept.
  • MDM profile removal blocked, distinct administrator usernames, MDM-enabled extra admin off.
  • Times, panes and touches recorded for each Mac; token expiry dates noted.
  • Pilot serials returned to their recorded service and Blueprint when the pilot ends.

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 vs Jamf Pro for Automated Device Enrollment: PreStages and ADE Library Items Compared. 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.