Getting Started with App Auto-Patch Version 3.x and Jamf Pro

1. Download the latest App-Auto-Patch-via-Dialog.zsh script to your computer. The latest version can be found here: https://github.com/App-Auto-Patch/App-Auto-Patch/blob/main/App-Auto-Patch-via-Dialog.zsh

• If you'd like to use Terminal to download a copy and save it to your Downloads, open the Terminal application and paste the following command:

curl -o ~/Downloads/App-Auto-Patch-via-Dialog.zsh https://raw.githubusercontent.com/App-Auto-Patch/App-Auto-Patch/main/App-Auto-Patch-via-Dialog.zsh

2. Upload the script to Jamf Pro. Since the script can be configured via MDM Config Profile or Command-Line interface, it's not necessary to name the parameters.

3. Create a Configuration Profile to configure settings using the preference domain xyz.techitout.appAutoPatch. You can find an example configuration profile with all available options here: Managed Configuration Profile Example

You can find a list comparing the 2.x and 3.x options for migrating here: AAP 3.0 Migration Options

To assist with creating a configuration profile, there are manifest files available for both third-party profile creators and Jamf schema:

App-Auto-Patch 3.0 Manifest : Can be used with ProfileCreator or iMazing Profile Editor. We are working on having this added to the ProfileManifests repository so it's automatically available in these applications.

App-Auto-Patch 3.0 Jamf JSON Schema

You can add this schema to Jamf by creating a new coniguration profile -> Application & Custom Settings -> External Applications -> Add -> Custom Schema -> Add schema -> copy/pasta the JSON or upload the JSON file -> Click Save.

Then you will have all of the options available to configure

4. Once you have your script stored in Jamf Pro and your configuration profile created to configure settings, create a policy to deploy/install App-Auto-Patch.

Since App-Auto-Patch 3.0 installs itself locally, you only need to deploy the script from Jamf Pro once. In this example, we set the Trigger to Recurring Check-In and Execution Frequency to Once per computer

5. The Jamf Pro policy will need to have the App Auto-Patch script added to the Script payload. You don't need to include any parameters, however, you can add any of the command-line triggers that will be used when App Auto-Patch runs.

6. Once the policy is deployed, the script will install itself locally to the /Library/Management/AppAutoPatch folder and start running with your configured settings.