Skip to main content

​
Overview

Deploy Unbound with a Jamf script and a policy set to run daily. Choose one installer.

Binary runtime

Recommended for Mac fleets.

Python installer

Use on Macs older than macOS 13.

​
Where your API key comes from

Both installers start on the Configure page in Unbound. Select My org (MDM), open the macOS tab and copy the install command. It carries your admin API key, which covers the whole fleet, and your organization’s URLs. You paste the command into the Jamf policy, and the script reads those values from it. The command also tells you which page to follow:

​
Verify

Jamf

Computers → Policies → Unbound daily onboard → Logs shows the run as Completed.

Device

Python installer: /Library/Application Support/Unbound/last-success.txt updates daily. Binary runtime: sudo launchctl print system/ai.getunbound.discovery shows the discovery service, and pkgutil --pkg-info ai.getunbound.runtime shows the installed version.

Unbound

Devices appear on Settings → Devices, and show a recent Last Sync on AI Tools Discovery.
To run a policy on one Mac now:
The Mac must be in scope. The policy ID is the number after id= in the policy’s URL. To run it again the same day, open the policy’s Logs and select Flush.

​
Report status in Jamf

Add an Extension Attribute to see the last successful run in inventory. Python installer only: the binary runtime does not write this file. For the binary runtime, use the package receipt ai.getunbound.runtime in a Smart Group. Go to Settings → Computer Management → Extension Attributes → New. Set Data Type to String and Input Type to Script:

Tamper Resistance

Best practices for keeping Unbound active on every device with managed settings.