Home

Overview

jamJAR is a project that has two modes:

Standard Mode

In standard mode, jamJAR combines Jamf Pro & Munki. Leveraging policies from Jamf Pro & the LocalOnlyManifest option from Munki.

In this mode, 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 from the LocalOnlyManifest.
• Sends a notification that the item has been installed.
• Sends a notification that installs are pending & advises a logout.
• Updates the clients inventory on Jamf Pro, & the optional jamJAR extension attribute.

Munki Mode (experimental, testers needed & PR's wanted!)

In Munki mode, only the jamJAR postflight is needed. The postflight will not modify the clients manifest, but notifications will be sent if the criteria for sending notifications has been met.

Requirements

To start using jamJAR, the following requirements must be met:

• A working & tested Munki setup.
• When used in the Standard mode, a working & tested Jamf Pro instance is also needed.
• When used in Munki mode, a notification application like terminal-notifier

Setup

With the above Requirements met, we can now look at setting up things client side.

This is covered in the following:

• Munki Setup
• jamJAR Setup