Getting Started with App Auto-Patch Version 2.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/robjschroeder/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. Make any modifications to this script to fit your organizational needs.

• Some modifications to consider include:

-- scriptLog
-- debugMode
-- deferralTimer (if using deferrals)
-- unattendedExit
-- Support Team Details

3. Upload the script to Jamf Pro, you can make use of the Jamf Pro Script parameters. The current parameter labels are as follows:

   • Parameter 4: Interactive Mode [ 0 (Completely Silent) | 1 (Silent Discovery, Interactive Patching) | 2 (Full Interactive) (default) ]
   • Parameter 5: A space-separated list of Installomator labels to ignore (i.e., "microsoft* googlechrome* jamfconnect zoom* 1password* firefox* swiftdialog")
   • Parameter 6: A space-separated list of required Installomator labels (i.e., "firefoxpkg_intl")
   • Parameter 7: A space-separated list of optional Installomator labels (i.e., "renew") ** Does not support wildcards **
   • Parameter 8: A space-separated list of options to override default Installomator options (i.e., BLOCKING_PROCESS_ACTION=prompt_user NOTIFY=silent LOGO=appstore)
   • Parameter 9: Number of times a user is allowed to defer before being forced to install updates. A value of "Disabled" will not display the deferral prompt. [ integer | Disabled (default) ]

4. Once you have your script stored in Jamf Pro, create a policy.

5. The Jamf Pro policy will need to have the App Auto-Patch script added to the Script payload. Fill the script parameters to make sure you get the desired result of the script.

• Optionally, you can make the script available in Self Service for end-users to run on their own time.

6. Once you have the policy set up as you'd like, feel free to test it out.