Script

Introduction

This page details jamJAR's script, which can found here.

Parameters

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).

As of 1.2, you can supply one or more ItemNames into the parameters $4 - $7 below separated by commas and a space.

ex. GoogleChrome, Firefox, Slack

Parameter Length

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.

$4 (Add to installs)

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).

$5 (Remove from installs)

If the $5 parameter is defined, this item is removed from the LocalOnlyManifest's managed_installs array.

$6 (Add to uninstalls)

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).

$7 (Remove from uninstalls)

If the $7 parameter is defined, this item is removed from the LocalOnlyManifest's managed_uninstalls array.

$8 (Yolo Mode)

$8 if set to ENGAGE, the jamJAR script runs Munki using 1st the managedsoftwareupdate --checkonly then managedsoftwareupdate --installonly options.

Affectively forcing the installation/uninstallation of the defined items & any pending items.