Agent 2.7.26 Release Notes

Agent 2.7.26 is a major release focusing on policy execution improvements and Tray updates. It contains the following features, improvements, and fixes:

Additions

Policy Execution Improvements - Notification Consolidation

Automox is changing how overlapping policies run on a device and how the Agent Tray reports them to your end users.

The problem this solves:

A policy with an active end user notification blocks every other scheduled notification-enabled policy on that endpoint until the notification is resolved. The Tray can display only one policy at a time, so the notification lists the packages for that policy alone.

That creates a gap between what your end users see and what actually happens:

  • When someone selects Install Updates, or when the deadline is reached, the policies queued behind the notification remediate as well. Their packages were never shown in the Tray.
  • A restart notification can be held back while an earlier policy is still pending, so a restart can arrive without the warning your end user expected.
  • End users have no way to see the full set of updates that a single click will apply.

What’s changing:

  • Platform: Updates to the logic that schedules and runs policies. These changes are behind the scenes, with nothing to reconfigure in the console.
  • Agent and Tray: The Agent gets matching policy logic, along with visible changes to the Tray:
    • The Tray becomes dynamic. When multiple notification-enabled policies are active on the same device, it displays the packages and actions from all of them together instead of one at a time.
    • The package and version list reflects every active policy, so end users see the complete set before they act.
    • The Tray displays the nearest deadline across all active policies.
    • Install Updates applies the patch activity for every active policy at once, matching what the Tray shows.
    • The Agent consolidates device restarts. Instead of patch, restart, patch, restart across two policies, it patches both and restarts once.
    • Together, these changes remove duplicate and repeated actions, so patching interrupts your end users less often.

Key things to know:

  • Notification consolidation converges policy actions such as patching and restarts when policies overlap on an endpoint.
  • The Tray shows the package and version list from every overlapping policy, not just the first one.
  • The Tray shows the nearest deadline across overlapping policies.
  • Install Updates runs the patch activity for all overlapping policies.
  • The Agent combines restart commands to minimize restarts when working through overlapping policies.

How you get it:

  • This Agent release - v2.7 and later.
  • The Platform pairs the new scheduling logic with endpoints running Agent version and beyond.
  • Devices on earlier Agent versions keep the logic they use today, so you can roll the new version out on your own schedule.

Additional Information

Do Not Disturb (DND)

The Tray will continue to honor Do Not Disturb (DND) policy settings with the following updates.

  • When notifications merge for policies that all honor DND, DND will continue to be enforced and behave as it does today.
  • When one or more Bypass DND notifications merge with an existing Honor DND notification, bypassing DND will be prioritized and all additional notifications will bypass DND until the given Bypass DND policy is resolved.

Install and Restart Messages

The Tray will prioritize Install and Restart messages in the following order.

  • When Install + Restart notifications merge, the Tray will prioritize and display the Restart Message associated with the nearest policy driving the restart.
  • When multiple Install notifications merge, the Tray will display the Install Message from the policy with the nearest deadline.

Custom Install and Restart messages are still supported.

  • Should notifications with Default + Custom messages merge, the Tray will prioritize and display the Custom Message over the Default, honoring the prioritization logic outlined above.

Improvements

  • Agent Tray UI: Several improvements have been made to the Agent Tray, providing a cleaner User Interface (UI), and improving accessibility.
    • About the changes:
      • The width of the Tray has been increased to 365px.
      • All text within Banners has been increased to use 14px medium font.
      • Text related to Restart messages has been to use 14px bold font.
      • All other strings and messages have been increased to use 14px font.
      • The information architecture has been improved to highlight the content within call-to-action banners.

Bugfixes

  • macOS - Tray opens in middle of screen when multiple monitors are in use: Resolved an issue where the Agent Tray would be displayed in an incorrect location when it was opened in a secondary monitor.
  • Windows - Agent Service not being Removed from Endpoint when Device is Removed from the Console: Resolved an issue where the Agent Service was not being removed properly after a Device / Server was deleted from the Automox Console. Before the fix, the Agent was properly uninstalling and removing its binaries, but the Windows Service was remaining present.
  • macOS - Service Account Auto-Created Erroneously: Identified and addressed a defect where the Agent’s Health Check would automatically create the service account when the GetSystemDetail script ran during a Scan. This was identified while researching reports of CLI parsing errors when users were attempting to disable the Automox Service Account from the Command Line.
  • Windows - Agent Upgrade Failure Doesn’t Report to Platform: Addressed a race condition where a failed Agent upgrade log report was not being generated and sent to the Platform.

Security Improvements

  • Strengthened restrictions on credential templating used by device commands, limiting which commands can reference stored credentials and narrowing what can be substituted. This reduces the risk of custom scripts accessing sensitive device or service-account credentials.
  • This release has been rebuilt with an updated version of Go. This release is rebuilt with Go [1.26.10 / 1.27.3], which addresses CVE-2026-111943. The updated Go version no longer trusts eight intermediate certificate authority (CA) certificates from eMudhra whose private keys were found to be weak. eMudhra has revoked these certificates.
Note: Devices running Windows Server 2012 will instead receive agent v2.7.27, which is built using Go 1.26.10, due to lacking support for Server 2012 in Go version 1.27.3.