Skip to content

App Auto-Patch 3.1.0 beta3

Pre-release
Pre-release

Choose a tag to compare

View all tags
@TechTrekkie TechTrekkie released this 26 Mar 18:42
3.1.0-beta3
e26f921
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

App Auto-Patch 3.1.0-beta3

Version 3.1.0 of App Auto-Patch is here!
Please review the wiki for all information about how to use 3.1.0
The Getting Started page will have steps and tips for testing and debugging

New features/Specific Changes in 3.1.0-beta3

  • Days Deadlines - allows you to specify the maximum number of days the user can defer after the Patching Start Date. You can set multiple days deadlines with one of each type; focus, and hard.

  • WorkflowInstallNowPatchingStatusAction - Added MDM keys and triggers for determining what happens with the Patching Completion Status when using the --workflow-install-now option

  • Moved the Defer button next to the Continue button to position it underneath the deferral menu drop-down

  • Adjusted logic to use deferral_timer_workflow_relaunch_minutes after AAP completes the installation workflow

  • Fixed logic for workflow_disable_relaunch_option to disable relaunch after successful patching completion if set to TRUE

  • Added exit_error function to handle startup validation errors

  • Fixed an issue where --workflow-install-now was not displaying the discovery workflow when InteractiveMode < 2

  • Added the ability to pull from a custom Installomator fork. It must include all Installomator contents, including fragments

  • Added logic to check for a successful App Auto Patch installation.

  • Fixed logic for InteractiveMode to use default if no option is set via MDM or command line

  • Fixed logic for DaysUntilReset to use default if no option is set via mdm or command line

Major Features of Version 3.0.0

  • AAP 3.0 is designed to be MDM agnostic. While it still works great with Jamf Pro, setup and configuration have moved away from using Jamf Pro parameters.

  • AAP 3.0 uses a background agent (LaunchDaemon) which allows AAP to work independently of a mobile device management (MDM) service. (In other words, you can take advantage of AAP with or without an MDM service.)

  • AAP 3.0 performs an automatic installation of all required items and dependencies. Just run the script for it to install itself, and it can be triggered via sudo appautopatch or automatically with built in Relaunch functionality

  • AAP 3.0 is configurable using interactive command line or managed configuration profiles.

  • You can find a mapping of 2.x variables to 3.0.4 configuration and command line options from the following TSV file: Migration Options

  • Profile Manfiests to assist with building a configuration profile can be found in the Resources folder: Profile Manifests

  • An example configuration profile and a profile & plist containing All available options can be found in the resources: Example Configurations

Full Changelog: 3.1.0-beta2...3.1.0-beta3

Assets 2
Loading