You are here:
Discover Devices from Jamf Pro
Discover Mac computers and mobile devices managed in Jamf Pro, and synchronize key inventory data into CMDB. Keep computer and mobile configuration items accurate and current by aligning CMDB records with Jamf Pro device data. Use Jamf discovery to support reliable asset tracking and IT service workflows that depend on trusted device information.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with Agentforce IT Service that have Discovery enabled. |
Use Jamf Pro as a trusted data source to create and update configuration items (CI) in CMDB. You get a reliable, current view of the Apple endpoints across your organization. Discovery keeps CMDB aligned with changes made in Jamf Pro, so that CIs stay accurate between scans without manual effort.
What you Discover
Jamf discovery populates these types of configuration items:
| Configuration item | Description |
|---|---|
| Mac Host | Mac computers managed by Jamf Pro, such as MacBook, iMac, and Mac mini. |
| Mobile Devices | Apple mobile devices managed by Jamf Pro, such as iPhone and iPad. |
| Installed Software | The applications installed on discovered computers and mobile devices. |
How Jamf Discovery Works
Jamf discovery runs on Salesforce Flow using externally triggered flows. When you enable a target, Salesforce connects to Jamf Pro through a registered integration connection that authenticates with OAuth. Enabling the target activates the flows, and activation triggers discovery to run. For more information about externally triggered flows, see Externally Triggered Flows.
Each target uses two flows, because Jamf Pro serves computers and mobile devices from different endpoints:
- A Compute flow discovers Mac computers and their installed software.
- A Mobile flow discovers mobile devices and their installed software.
Each flow creates its own scan job, so every Jamf target produces two scan jobs, one for computers and one for mobile devices. You can monitor each run and review any errors on the Scan Jobs page. A scan job shows a summary by device type and a detailed list of new and updated CIs.
Before your first scan, you can review how Jamf attributes map to CMDB fields on the Field Mapping page. The page shows the default mappings that are ready-to-use. To capture more Jamf data, you customize the mappings in the flow. For more information, see Considerations for Mapping Jamf Fields to CMDB.
How Jamf Uses External Triggers to Sync Data
The externally triggered flows run on the schedule that you set. The first run brings every managed device into CMDB. Each later run syncs only the devices that checked in to Jamf Pro since the previous run. This keeps each run efficient as the number of managed devices grows.
On each run, CMDB updates the records that already exist and creates new records for devices it hasn't seen before. To detect what changed, discovery relies on the device check-in time reported by Jamf Pro. Jamf Pro reports computers and mobile devices from separate endpoints. Each flow uses the check-in field for its device type:
| Device type | Check-in field |
|---|---|
| Mac computers | Last Contact Time (general.lastContactTime) |
| Mobile devices | Last Inventory Update (lastInventoryUpdateDate) |
CMDB stores this time as Last Discovered On and uses it to select which devices to sync.
How Devices are Classified
Jamf Pro manages Apple devices only, so classification stays simple. During discovery, CMDB assigns each device to one of these CI types:
- Mac Host, for Mac computers.
- Mobile Device, for iPhone, iPad, and other Apple mobile devices.
How Devices are Identified
To keep records accurate and avoid duplicates, CMDB uses identification rules to match Jamf data to existing configuration items. To identify a device, CMDB uses:
- the serial number for Mac computers.
- the IMEI number for mobile devices, or the Serial Number when no IMEI is available.
For more information, see Identification Rules in CMDB.
How Discovery Data is Tracked
CMDB tags every CI discovered through Jamf with the source Jamf, and updates the discovery details on each run, such as when the device was first and last discovered. Since a device can be discovered by more than one source over time, you can always see how Jamf last confirmed a device.
The CI History tab on the CI record page, records every discovery change, with Jamf listed as the source. History entries include new devices, changed attributes, and software that was added or removed.
- Create a Discovery Target for Jamf Pro
Create a Jamf Pro discovery target to bring managed Apple device data into CMDB. Keep endpoint Configuration Items (CIs) accurate and up to date. Configure the integration connection, review field mappings, and run discovery using Salesforce Flow. Populate CMDB with managed Mac computer and mobile device data, and support IT operations that rely on accurate CI data. - Considerations for Mapping Jamf Fields to CMDB
Learn how Jamf device data maps to CMDB fields. See which fields identify devices and how CMDB formats certain values. Use these considerations to interpret discovered data correctly and to decide when to customize the mappings. - Customize Field Mappings for Jamf Discovery
Customize the Jamf field mappings to capture Jamf data that isn't mapped by default. Map additional Jamf attributes to CMDB fields to keep discovered device data aligned with your organization's needs.
