May 2025 Release Notes

May 30, 2025

Updated:

We updated Agent Firewall Allowlisting Rules to add command-storage-cdn.prod.automox.com to the allowlist.
We added more clarity around the timing of end-user notifications to End-User Notifications.

Bugfixes:

We fixed an issue where policies were not consistently triggering a restart sequence upon successful completion of the policy.
We fixed an issue where installed software was not being displayed for some devices.
We fixed an issue where Search All Logs on the Activity Log page was returning zero results.

Added:

Added more information about the release process for Automox Agent. See Agent Release Process: Beta + General Availability for details.

Updates:

Updated Setting a Patching Schedule - You can select a custom schedule, which now allows you to select the occurrence of days instead of weeks. In addition, you can select a schedule specifically for Patch Tuesday, which can be configured with a delay.
Developer Portal: Updated the configuration objects for Create a new policy and Update a policy to allow for setting is_patch_tuesday and patch_tuesday_offset when creating or updating policies using the API.

Bugfixes:

We added RunAtLoad to the Agent plist file on macOS, to fix an issue where macOS devices were not reconnecting to Automox after waking from sleep.
We updated links to cve.mitre.org to reflect the domain change to cve.org.

Added:

Updated:

We updated the Analytics documentation to include the new Patch Impact and Performance board.
We updated the Secrets Management documentation and updated images.
We updated the Agent 2.2.24 Release Notes for clarity, and included a screenshot of the end-user notification received when the system is offline.
We consolidated the documentation regarding rolling back Windows patches into How to Roll Back an Installed Patch on Devices, and removed a redundant article.
Third-Party Software Support - We have removed Tableau Reader from Third-Party Patching Support, as updates now require a website account to download.

Bugfixes:

We fixed an issue wherein toggling Automatic Agent Upgrades in the console would apply the change to the next selected organization.
We fixed an issue where clicking on a saved query in Device Query would cause the error "An unexpected error occurred. Please try again. If the issue persists, contact support." to be displayed.
We fixed an issue with third-party software support, where MS ODBC Driver 17 for SQL Server and MS ODBC Driver 18 for SQL Server were a version behind.

Added:

Updated:

Updated Agent 2.2.24 Release Notes to reflect that this version is now in General Availability (GA).
Updated Install and Configure Automox Agent for Apple Silicon Devices to reflect that we now use the native macOS prompt to configure the secure token, enhancing security.
Updated Agent Firewall Allowlisting Rules to include recommendations for Analytics.
Updated End-User Notifications to reflect that you can now use custom messages in tray notifications.
Third-Party Software Support: We fixed detection and patching for GoTo Opener and GoTo Connect, and removed references to GoToMeeting, which is not currently supported.

Added:

Custom Roles is being rolled out to General Availability. See Roles and Permissions Management to learn more.
Agent Configurations is now GA. See Managing Agent Configurations to learn more.
Agent 2.2.24 is now in Beta. See Agent 2.2.24 Release Notes to learn more.

Updated:

Third-party support: VMware Horizon Client 8 has been rebranded as Omnissa Horizon Client 8.
We've updated our Automox Agent Update Policy regarding deferred upgrades, as customers now have the ability to control that via Agent Settings. See Managing Agent Configurations for details.
We fixed a broken link in Agent 1.42 Release Notes.
We updated the OCSF Class Events documentation on our Developer Portal to show Agent Configuration events, under Web Resource Activity Events, for Audit Trail API.

Bugfixes:

We fixed an issue where agents were showing as disconnected while the logs showed successful check-ins.
We fixed an issue where device logs were causing the Device page to have a longer load time.