Multiple Version Approvals for Software Packages

Objective

To explain how Automox manual patch policies handle version precedence and automatic upgrades when an earlier version of a software package is approved, but newer versions subsequently become available.

Overview

In Automox manual patch policies, administrators manually select and approve specific software package versions for deployment across target devices. Understanding how version approval rules evaluate newer releases ensures consistent patch behavior and predictable application states across your environment.

Package Version Approval Behavior

When managing software packages (such as Google Chrome, Mozilla Firefox, or Adobe Acrobat Reader) with multiple available release versions, approval behavior operates as follows:

  • Initial Approval: Approving a specific earlier version of a package authorizes the Automox Agent to deploy that version during the next scheduled policy run.

  • Newer Version Releases: If a newer version of an already-approved software title is subsequently released to the repository or Automox software catalog:

    • The policy evaluates the software title as approved for update.

    • When the patch policy next executes, the latest available version of the software package will be installed, overriding the previously targeted legacy version.

⚠️ Key Takeaway: Manual approval authorizes updating the target application. Approving an older version does not permanently lock or pin endpoints to that legacy version if newer updates for the same package become available within the repository.

Best Practices for Version Control

If your organization requires strict version control or needs to prevent applications from automatically updating to the latest release:

  1. Use Targeted Worklets for Version Pinning: If you must enforce a specific legacy software version across your fleet, deploy a custom Worklet to install and lock the application at that exact version number.

  2. Review Package Targeting: Routinely inspect the Package Targeting section of your manual patch policies to review newly detected software package releases prior to policy execution cycles.

Was this article helpful?
0 out of 0 found this helpful