Repository navigation
Home
jamJAR combines Jamf Pro & Munki. Leveraging policies from Jamf Pro & the LocalOnlyManifest option from Munki.
Jamf Pro updates items in a Mac Clients jamJAR LocalOnlyManifest & then runs Munki. After every Munki run, the jamJAR postflight then processes the ManagedInstallReport.plist found within the Managed Installs directory &, (based on conditions explained later), either:
- Removes the item(s) from the LocalOnlyManifest.
- Sends a notification that the item(s) have been installed.
- Sends a notification that installs are pending & advises a logout.
- If an install occurs, updates the clients inventory on Jamf Pro, & the optional jamJAR extension attribute.
With jamJAR 3.0, jamJAR is now a compiled Swift binary (/usr/local/munki/jamJAR) rather than a Python/shell postflight script. The postflight script is now a thin bash shim that calls the binary. A LaunchAgent runs pending-notification processing at user login (Notifier only).
To start using jamJAR, the following requirements must be met:
- A working & tested Munki 5.1+ setup.
- A working & tested Jamf Pro instance is also needed.
jamJAR < 3.0 required Munki's python (/usr/local/munki/munki-python), but jamJAR 3.0+ removes that requirement as it's written in Swift.
With the above Requirements met, we can now look at setting up things client side.
This is covered in the following: