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.

​
Get your API key

Open Configure and copy the key from the API Access panel. Both installers take it as Jamf Parameter 4.
Jamf reserves $1 to $3. Custom parameters start at Parameter 4.

​
Verify

Jamf

The policy shows Completed in Policies → Logs.

Device

/Library/Application Support/Unbound/last-success.txt updates daily.

Unbound

Devices appear with a recent last-seen time.
To run a policy on one Mac now:
The Mac must be in scope. To run it again the same day, flush the policy log under Policies → your policy → Logs → Flush.

​
Report status in Jamf

Add an Extension Attribute to see the last successful run in inventory. Works with either installer. 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.