Jamf Pro
Sync Macs, iPhones and iPads, and Jamf Pro's policies and configuration profiles, into each client's documentation.
Connect Jamf Pro and each client's Apple devices are documented automatically: model, serial number, macOS or iOS version, user, IP and MAC address, and warranty. Its policies and configuration profiles come across too, as 🍏 MDM Policy flexible assets, so anyone can see how a client's Macs are set up without signing in to Jamf.
Knowpoint only reads from Jamf Pro. Nothing is changed there.
What's synced
| From Jamf Pro | Becomes |
|---|---|
| The instance, or each Site | An organization |
| Computers | Assets (Workstation, or Server for a Mac server), with a From Jamf Pro card |
| Mobile devices | Assets (Other), with the same card |
| Policies | 🍏 MDM Policies: the packages and scripts each runs, when it runs, what it's scoped to and any exclusions, and whether it's in Self Service |
| macOS and mobile configuration profiles | 🍏 MDM Policies: what each profile configures, and what it's scoped to |
A policy that's turned off in Jamf is synced with the status Disabled. Up to 500 policies and profiles are read per sync; the rest come on the next one.
Set it up
- In Jamf Pro, go to Settings → System → API roles and clients.
- Under API Roles, add a role with these privileges: Read Computers, Read Mobile Devices, Read Sites, Read Policies, Read macOS Configuration Profiles and Read Mobile Device Configuration Profiles.
- Under API Clients, add a client with that role, turn it on, and generate a client secret. Copy the client ID and secret.
- In Knowpoint, go to Admin → Integrations → Jamf Pro, enter the Jamf Pro address (like
https://yourclient.jamfcloud.com), the client ID and the secret, and choose Test connection.
One Jamf Pro per client, or Sites
Most MSPs have a Jamf Pro instance for each client, because Apple ties push certificates and Apple Business Manager to one organization. Connect each instance as its own integration, choose This Jamf Pro is one client, and give the client's name (or match it to the client afterwards with Match companies).
If one Jamf Pro is shared between clients with Sites, choose Each Site is a client. Each Site becomes an organization, and devices, policies and profiles go to the client of their Site. Anything that isn't in a Site is left out.
Good to know
- Device details from Jamf follow the device details order when another tool, such as your RMM or PSA, documents the same Mac.
- Matching works as it does for every integration: by serial number first, so a Mac that's also in your RMM is one asset, not two.