Jamf Pro Patch Management
Overview
Jamf Pro patches Apple devices two ways. Managed software updates push macOS and iOS/iPadOS versions through MDM update plans. Patch management titles track third-party apps (Chrome, Zoom, Office) and report which version each Mac runs. Policies deliver the packages. MSPs need a patch posture number for each client, plus a short list of devices to chase.
Anti-triggers
- Encryption, check-in, or managed state: use
jamf-device-compliance.
- Windows patching: this plugin only covers Jamf-managed Apple devices.
Key Concepts
| Thing |
Tool |
Notes |
| Deployable OS versions |
jamf_list_available_os_updates |
What Jamf can push today, macOS and iOS/iPadOS |
| Device OS version |
jamf_search_computers / jamf_search_mobile_devices |
OPERATING_SYSTEM is in the computer search default sections |
| OS update plans |
jamf_list_software_update_plans |
Scheduled updates and their status. Filter e.g. device.deviceId=="42". |
| Third-party titles |
jamf_list_patch_titles |
Each id is a patch software title configuration |
| Per-title report |
jamf_get_patch_report |
Which computers run which version. Filter e.g. version!="120.0". |
| Delivery policies |
jamf_list_policies, jamf_get_policy |
Scope, packages, scripts, Self Service settings |
Common Workflows
OS patch posture for one client
jamf_list_available_os_updates to get the newest deployable macOS and iOS versions.
jamf_search_computers with sections: ["GENERAL", "OPERATING_SYSTEM"], paging with pageSize: 200 until you have totalCount records. Add a site filter if the tenant is shared.
- Group by
operatingSystem.version: current, one minor behind, older minors, previous major, unsupported.
- Repeat for mobile devices with
jamf_search_mobile_devices (GENERAL holds the OS version).
jamf_list_software_update_plans to show which behind devices already have an update scheduled, and which plans failed.
Report the percentage on the latest minor of each major in use, then list devices two or more minors behind.
Third-party app currency
jamf_list_patch_titles, pick the titles the client cares about.
jamf_get_patch_report for each, with filter: 'version!="<latest>"' to get only outdated Macs.
- If many Macs are behind,
jamf_list_policies with contains: "<app name>" and jamf_get_policy to check the patch policy's scope and whether it is enabled.
Scheduling an OS update (write)
jamf_schedule_os_update creates a managed software update plan for up to 50 devices of one type.
| Arg |
Values |
deviceType |
computer or mobile_device |
deviceIds |
Up to 50 ids |
updateAction |
DOWNLOAD_ONLY, DOWNLOAD_INSTALL_ALLOW_DEFERRAL (needs maxDeferrals), DOWNLOAD_INSTALL_SCHEDULE (needs forceInstallLocalDateTime, device-local, e.g. 2026-11-14T22:00:00) |
versionType |
LATEST_MINOR, LATEST_MAJOR, LATEST_ANY, SPECIFIC_VERSION (needs specificVersion from jamf_list_available_os_updates) |
Immediate forced install and forced restart are not offered. Before calling, confirm with the user: the device list, the action, the target version, and the user-facing impact (deferral count or install time). Prefer LATEST_MINOR with deferrals for routine patching. Major upgrades should go through the client's change process.
After scheduling, check jamf_list_software_update_plans for the new plans' status.
Keeping a patch target group
jamf_create_smart_computer_group (write) with a criterion like {"name": "Operating System Version", "searchType": "less than", "value": "15.6"} gives the client's admins a live view in Jamf, and policies can scope to it.
Gatekeeping
- Posture review is entirely read tier.
jamf_schedule_os_update and jamf_create_smart_computer_group are write tier.
- No patching tool is admin tier.
jamf_remove_computers_from_static_group, which stops policies applying to the removed Macs, is write tier like the other group changes.
Gotchas
- Large fleets: request only
GENERAL and OPERATING_SYSTEM sections. Each response is capped, and APPLICATIONS alone can blow the cap.
jamf_list_available_os_updates lists what Jamf can deploy, not what Apple has released in total. A version missing there cannot be scheduled.
- Update plans for devices that are offline stay pending. A device with a stale check-in (see
jamf-device-compliance) will not patch until it reconnects.
jamf_list_policies returns at most limit names (default 100). Check totalMatched before saying no patch policy exists.
1---2name: jamf-pro-patch-management3description: >4 OS and third-party patch posture in Jamf Pro: which macOS and iOS versions5 Jamf can deploy, measuring OS version spread from inventory, managed6 software update plans and their status, patch management titles and per-title7 patch reports, the policies that deliver patches, and scheduling OS updates8 without forcing restarts.9when_to_use: >-10 When answering how current a client's Macs, iPhones, or iPads are, finding11 devices behind on macOS/iOS or on an app like Chrome or Zoom, or scheduling12 an OS update. Use when: macos updates, ios updates, os version report, jamf13 patch report, outdated apps mac, jamf patch management, schedule os update,14 software update plan.15metadata:16 source: https://skillmd.com/skills/wyre-ai/jamf-pro-patch-management17---1819# Jamf Pro Patch Management2021## Overview2223Jamf Pro patches Apple devices two ways. **Managed software updates** push macOS and iOS/iPadOS versions through MDM update plans. **Patch management titles** track third-party apps (Chrome, Zoom, Office) and report which version each Mac runs. Policies deliver the packages. MSPs need a patch posture number for each client, plus a short list of devices to chase.2425## Anti-triggers2627- **Encryption, check-in, or managed state**: use `jamf-device-compliance`.28- **Windows patching**: this plugin only covers Jamf-managed Apple devices.2930## Key Concepts3132| Thing | Tool | Notes |33|-------|------|-------|34| Deployable OS versions | `jamf_list_available_os_updates` | What Jamf can push today, macOS and iOS/iPadOS |35| Device OS version | `jamf_search_computers` / `jamf_search_mobile_devices` | `OPERATING_SYSTEM` is in the computer search default sections |36| OS update plans | `jamf_list_software_update_plans` | Scheduled updates and their status. Filter e.g. `device.deviceId=="42"`. |37| Third-party titles | `jamf_list_patch_titles` | Each id is a patch software title configuration |38| Per-title report | `jamf_get_patch_report` | Which computers run which version. Filter e.g. `version!="120.0"`. |39| Delivery policies | `jamf_list_policies`, `jamf_get_policy` | Scope, packages, scripts, Self Service settings |4041## Common Workflows4243### OS patch posture for one client44451. `jamf_list_available_os_updates` to get the newest deployable macOS and iOS versions.462. `jamf_search_computers` with `sections: ["GENERAL", "OPERATING_SYSTEM"]`, paging with `pageSize: 200` until you have `totalCount` records. Add a site filter if the tenant is shared.473. Group by `operatingSystem.version`: current, one minor behind, older minors, previous major, unsupported.484. Repeat for mobile devices with `jamf_search_mobile_devices` (`GENERAL` holds the OS version).495. `jamf_list_software_update_plans` to show which behind devices already have an update scheduled, and which plans failed.5051Report the percentage on the latest minor of each major in use, then list devices two or more minors behind.5253### Third-party app currency54551. `jamf_list_patch_titles`, pick the titles the client cares about.562. `jamf_get_patch_report` for each, with `filter: 'version!="<latest>"'` to get only outdated Macs.573. If many Macs are behind, `jamf_list_policies` with `contains: "<app name>"` and `jamf_get_policy` to check the patch policy's scope and whether it is enabled.5859### Scheduling an OS update (write)6061`jamf_schedule_os_update` creates a managed software update plan for up to 50 devices of one type.6263| Arg | Values |64|-----|--------|65| `deviceType` | `computer` or `mobile_device` |66| `deviceIds` | Up to 50 ids |67| `updateAction` | `DOWNLOAD_ONLY`, `DOWNLOAD_INSTALL_ALLOW_DEFERRAL` (needs `maxDeferrals`), `DOWNLOAD_INSTALL_SCHEDULE` (needs `forceInstallLocalDateTime`, device-local, e.g. `2026-11-14T22:00:00`) |68| `versionType` | `LATEST_MINOR`, `LATEST_MAJOR`, `LATEST_ANY`, `SPECIFIC_VERSION` (needs `specificVersion` from `jamf_list_available_os_updates`) |6970Immediate forced install and forced restart are not offered. Before calling, confirm with the user: the device list, the action, the target version, and the user-facing impact (deferral count or install time). Prefer `LATEST_MINOR` with deferrals for routine patching. Major upgrades should go through the client's change process.7172After scheduling, check `jamf_list_software_update_plans` for the new plans' status.7374### Keeping a patch target group7576`jamf_create_smart_computer_group` (write) with a criterion like `{"name": "Operating System Version", "searchType": "less than", "value": "15.6"}` gives the client's admins a live view in Jamf, and policies can scope to it.7778## Gatekeeping7980- Posture review is entirely **read** tier.81- `jamf_schedule_os_update` and `jamf_create_smart_computer_group` are **write** tier.82- No patching tool is admin tier. `jamf_remove_computers_from_static_group`, which stops policies applying to the removed Macs, is **write** tier like the other group changes.8384## Gotchas8586- Large fleets: request only `GENERAL` and `OPERATING_SYSTEM` sections. Each response is capped, and `APPLICATIONS` alone can blow the cap.87- `jamf_list_available_os_updates` lists what Jamf can deploy, not what Apple has released in total. A version missing there cannot be scheduled.88- Update plans for devices that are offline stay pending. A device with a stale check-in (see `jamf-device-compliance`) will not patch until it reconnects.89- `jamf_list_policies` returns at most `limit` names (default 100). Check `totalMatched` before saying no patch policy exists.