Repository navigation
Script
This page details jamJAR's script, which can found here.
v3.0 of the policy script will not work with jamJAR < 3.0, due to the way the script interacts with jamJAR.
With 3.0+, Each title in a comma-separated parameter is passed individually to the binary:
/usr/local/munki/jamJAR --add-to-installs <title> [--force] [--verbose]
/usr/local/munki/jamJAR --remove-from-installs <title> [--force] [--verbose]
/usr/local/munki/jamJAR --add-to-uninstalls <title> [--force] [--verbose]
/usr/local/munki/jamJAR --remove-from-uninstalls <title> [--force] [--verbose]
jamJAR's script has several parameters, for assignment when called via a Jamf Pro policy, these are detailed below.
Parameters $4, $5, $6 & $7 need to have the ItemName for one or more items within the Munki repo (i.e. GoogleChrome).
You can supply one or more ItemNames into the parameters $4 - $7 below separated by commas.
ex. GoogleChrome,Firefox,Slack
Parameters $8 and $9 are optional.
| Parameter | Description |
|---|---|
$4 |
Add to installs (comma-separated) |
$5 |
Remove from installs (comma-separated) |
$6 |
Add to uninstalls (comma-separated) |
$7 |
Remove from uninstalls (comma-separated) |
$8 |
Force mode — set any value to force immediate install/uninstall. The "ENGAGE" keyword is no longer required; any non-empty string enables force mode. |
$9 |
Verbose mode — set any value to enable verbose logging to /var/log/jamJAR.log. |
The character length of parameters supplied in Jamf scripts is currently limited to 255. Anything beyond this length is cutoff. There are several feature requests on Jamfnation to expand this, so if this is something you want to see definitely give them an upvote.
If the $4 parameter is defined, this item is added to the LocalOnlyManifest's managed_installs array.
This will result in jamJAR instructing Munki to install the App (if not already installed), and to continuing patching it using updates in the Munki repo (if already installed).
If the $5 parameter is defined, this item is removed from the LocalOnlyManifest's managed_installs array.
If the $6 parameter is defined, this item is added to the LocalOnlyManifest's managed_uninstalls array.
This will result in jamJAR instructing Munki to uninstall the App using the method specified in the pkginfo file (if already installed), or to will do nothing (if not installed).
If the $7 parameter is defined, this item is removed from the LocalOnlyManifest's managed_uninstalls array.
If any value is passed to $8, then force the immediate install/uninstall of the action passed to $4 or $6.
If any value is passed to $9 then enable verbose logging to /var/log/jamJAR.log is enabled.
The script uses tail -f /var/log/jamJAR.log during each call so binary output is surfaced
in the Jamf Pro policy log in real time.