Home

Overview

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.

Requirements

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

• A working & tested Munki setup.
• A working & tested Jamf Pro instance is also needed.

Client Setup

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

This is covered in the following:

• Munki Preferences
• jamJAR Preferences

Jamf Pro Setup

• Script
• Policy
• Extension Attribute

How it Works

• Step-by-Step

Stupid jamJAR Tricks

• Install Cached Packages
• Performing an Erase and Install of Mojave with jamJAR
• Install applicable Apple Software Updates for Apple Software
• Possible conflicts between Jamf's Restricted Software and macOS installations