Jamf - Xurrent App Installation & Configuration Guide

The Jamf integration enables Xurrent to synchronize device information from Jamf Pro into Xurrent Configuration Items (CIs).

The integration can synchronize:

• Computers
• Mobile devices

You can configure which device types are synchronized and control how devices that are no longer present in Jamf Pro are handled.

Prerequisites

Before installing and configuring the Jamf integration, make sure you have:

• Access to a Jamf Pro environment.
• Permission to create an API Client in Jamf Pro.
• The Jamf Pro URL.
• A Client ID.
• A Client secret.
• An API Client in Jamf Pro with the following privileges:
  • Read Computers
  • Read Mobile Devices
  • Read Sites
• All three Jamf Pro privileges are required for the integration to work correctly. The Read Sites privilege is required even if only one device type is being synchronized. Without Read Sites, synchronization fails with a 403 error that does not explicitly identify the missing privilege.
• Access to Xurrent with permission to install and configure App Instances.

Installing the Jamf App

1. Sign in to Xurrent.
2. Open the App Store.
3. Search for Jamf.
4. Open the Jamf app.
5. Select Install or create an App Instance.
6. Enter a name for the App Instance.
7. Configure the required Jamf Pro connection details.
8. Save the App Instance.

After installation, the Jamf App Instance is available for configuration.

Configure the Jamf App Instance

Open the Jamf App Instance and configure the following settings.

Jamf Pro URL

Enter the URL of your Jamf Pro environment.

Example:

https://your-company.jamfcloud.com

Use the URL of your own Jamf Pro environment.

Client ID

Enter the Client ID generated for the Jamf Pro API Client.

Client secret

Enter the Client secret generated for the Jamf Pro API Client.

Keep this value confidential.

Device Synchronization

The Jamf integration provides separate options for synchronizing computers and mobile devices.

Sync computers

Enable this option to synchronize computers from Jamf Pro to Xurrent.

When enabled, the integration retrieves computer information from Jamf Pro and creates or updates the corresponding Configuration Items in Xurrent.

Required Jamf permission: Read Computers

Sync mobile devices

Enable this option to synchronize mobile devices from Jamf Pro to Xurrent.

When enabled, the integration retrieves mobile device information from Jamf Pro and creates or updates the corresponding Configuration Items in Xurrent.

Required Jamf permission: Read Mobile Devices

You can enable either option or both, depending on your requirements.

Exclude personal devices

Enable this option if personal devices should not be synchronized from Jamf Pro.

When enabled, devices identified as personal devices by Jamf Pro are excluded from the synchronization.

Full resync

Use Full resync when you want the integration to perform a complete synchronization rather than relying only on incremental changes.

A full resynchronization can be useful after:

• Initial configuration
• Changes to synchronization settings
• Data corrections
• Troubleshooting

Because a full resynchronization may process a large number of devices, use it when required.

Stale Devices

The Jamf integration provides settings to control how devices that are no longer actively reporting to Jamf Pro are handled.

Stale after days

Specify the number of days after which a device is considered stale.

For example, if this value is set to 30, a device that has not been updated within the defined period can be treated as stale.

Stale status

Select the status that should be assigned to a CI when the corresponding Jamf device becomes stale.

Available statuses include:

• Lost or stolen
• In stock
• Reserved
• Standby for continuity
• Lent out
• In production
• Archived
• To be removed
• Removed

Choose the status that matches your organization's CI lifecycle process.

Save the Configuration

After entering the required configuration:

1. Review the Jamf Pro URL.
2. Verify the Client ID.
3. Verify the Client secret.
4. Select whether to synchronize computers.
5. Select whether to synchronize mobile devices.
6. Configure whether personal devices should be excluded.
7. Configure the stale-device settings.
8. Save the App Instance.

Run the Synchronization

After the App Instance has been configured, run the synchronization.

The execution summary provides information about the synchronization, including:

• Last Run Started At
• Execution Status
• Last Run Completed At
• Execution Output
• Total Computers found
• Total Mobile Devices found
• Total Configuration Items updated/created
• Total Errors
• Missing OS CIs

‍

‍

Execution summary

The Execution Summary provides a complete overview of the latest integration run, including synchronization results, errors, and missing configuration items.
Note: This integration runs automatically once per day.

Execution Status: Shows the results of the most recent execution, including the current status and, in case of failures, the reason for failure.
Example:

• Status: Completed

Execution Output:
Displays the results of the most recent execution, including timestamps, statuses, and any error messages. Example:

• Sync window: From the beginning to Sep 16, 2026 09:29:23 UTC‍
• Total Computers found: 111‍
• Total Mobile Devices found: 105‍
• Total Configuration Items (Updated/Created): 216‍
• Total Errors: 0

Errors:

• Lists any errors that occurred during the last execution.

Missing OS Configuration Items:

• Shows OS configuration items detected on devices that are not yet present in Xurrent.

Verify the synchronization

After the run completes, review the execution output.

A successful synchronization should show:

• The expected number of computers found.
• The expected number of mobile devices found.
• The number of CIs created or updated.
• No unexpected errors.

The actual numbers will depend on the devices available in your Jamf Pro environment.

‍

Troubleshooting

Authentication fails

If the App Instance cannot authenticate with Jamf Pro:

1. Verify the Jamf Pro URL.
2. Verify the Client ID.
3. Verify the Client secret.
4. Confirm that the API Client is active in Jamf Pro.
5. Verify that the API Client has the required permissions.
6. Confirm that the Jamf Pro environment is reachable.

No computers are synchronized

If no computers are found:

1. Verify that Sync computers is enabled.
2. Confirm that computers are present in Jamf Pro.
3. Verify that the API Client has the Read Computers permission.
4. Run a full resynchronization if appropriate.
5. Review the execution output for errors.

No mobile devices are synchronized

If no mobile devices are found:

1. Verify that Sync mobile devices is enabled.
2. Confirm that mobile devices are present in Jamf Pro.
3. Verify that the API Client has the Read Mobile Devices permission.
4. Run a full resynchronization if appropriate.
5. Review the execution output for errors.

Personal devices are missing

If personal devices are not appearing in Xurrent:

1. Check whether Exclude personal devices is enabled.
2. Verify how the devices are classified in Jamf Pro.
3. Disable the exclusion option if personal devices should also be synchronized.

Devices are marked as stale

If a CI is being treated as stale:

1. Review the Stale after days value.
2. Verify the device's last update information in Jamf Pro.
3. Check the configured Stale status.
4. Adjust the stale threshold if required.

Security and Compliance

The Jamf integration uses credentials to access the Jamf Pro API.

Follow these practices:

• Use a dedicated API Client for the Xurrent integration.
• Grant only the required read permissions.
• Protect the Client secret.
• Do not share credentials through tickets, email, screenshots, or documentation.
• Rotate credentials according to your organization's security policies.
• Disable or revoke unused API Clients.

‍