Agent 39 Release Notes

Release Overview

Agent 1.0.39 is a minor release that addresses multiple issues.This release is for all supported Windows, Mac and Linux operating systems.
 

Changes / New Features

• Increased password complexity for Automox Service Account
  Note: see below for additional details.
   

Bug Fixes

• The amagent directory is not removed after agent uninstall on Windows
• Multiple agent processes causing high CPU usage
• Notifications user responses are lost on agent restart
• Agent service disconnects when Linux devices sleep or STOMP connection is severed and does not reconnect
• Windows Agent build for version 1.0.38 shows version 1.0.37 on executable file properties
   

Automox Service Account Change Details

• Enabled by default for agent versions 1.0.39+

Password Complexity Rules

• Minimum password Length: 32

• Password must contain at least one letter and one number

• New for Agent 1.0.39: Password cannot contain repeating, ascending, and descending character sequences

• New for Agent 1.0.39: Minimum number of complex characters: 4

  • Valid characters:

    .'!@#$^&*_-+=`|(){}[]:;/<>,?/

In-Place Upgrades from Previous Agent Releases

• For devices that do not already have an Automox service account, this change takes effect immediately.

• For devices that already have an Automox service account in a bad state, the additional password complexity requirements take effect after remediation. See below for options to remediate the account:

Remediation options for devices with an Automox service account in a bad state

1. Option 1 - Automated Remediation

   1. Make sure the automox-service-account feature is enabled on the device.

   2. Wait for or manually trigger a scan.

   3. The agent will delete and recreate the account. This newly created account will have the complex password requirements enabled.

   4. This new account will still need to be securetoken enabled.

2. Option 2 - Manual Intervention

   • As an alternative to Option 1, the Automox service account can be manually deleted by the user.

   • On the next device scan, an Automox service account will be recreated automatically. This newly created account will have the complex password requirements enabled.

   • This new account will still need to be securetoken enabled.

Note: option #1 may fail on macOS Monterey devices because Automox might not be able to delete the service account without terminal having full disk access on the device. The workaround is to use option #2.

We provides a 100% CloudNative IT Endpoint operations platform for modern organizations. As a comprehensive EndPointManagement Platform, it has advanced SoftwareManagement for PatchManagement, Adding, Removing, and Updating Software, Changing and Configure Settings along with PolicyManagement on any device or operating system located anywhere in the world and at any time. With the push of a button, ITAdministartors can fix CriticalVulnerabilities faster, slash cost and complexity, and win back hours in the day.If you want to know more kindly Click here