Agent 39 Release Notes

  • 2 June 2022
  • 6 replies
  • 489 views

Userlevel 2
Badge

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.


6 replies

Hi Automox,

We have seen all our Linux devices as disconnected after they upgraded to the newest .39 agent.

I can’t find any change in how the agent itself functions and the servers list the service as unrecognized.
Re-installing the agent does not seem to fix the issue.

Have I missed something obvious?

Hi Automox,

We have seen all our Linux devices as disconnected after they upgraded to the newest .39 agent.

I can’t find any change in how the agent itself functions and the servers list the service as unrecognized.
Re-installing the agent does not seem to fix the issue.

Have I missed something obvious?

Using the curl command yielded the same unrecognized service.

Installing the agent manually and setting the key works.

Userlevel 1
Badge

Hi Automox,

We have seen all our Linux devices as disconnected after they upgraded to the newest .39 agent.

I can’t find any change in how the agent itself functions and the servers list the service as unrecognized.
Re-installing the agent does not seem to fix the issue.

Have I missed something obvious?

Using the curl command yielded the same unrecognized service.

Installing the agent manually and setting the key works.

Hi Steven,

Our Support team is curious if you are running the new systemd version?  You can verify via systemctl status amagent .  If you see this in the output, then you are likely not on the latest version and would need to uninstall/reinstall (via the curl install if possible).

   Loaded: loaded (/etc/rc.d/init.d/amagent; generated)

You would see something like this if the systemd version is installed:

   Loaded: loaded (/etc/systemd/system/amagent.service; enabled; vendor preset: disabled)
Badge

Is it possible please for the release notes to also be updated here?

Release Notes | Automox Knowledge Base

Userlevel 1
Badge

Is it possible please for the release notes to also be updated here?

Release Notes | Automox Knowledge Base

Hi @ParkerDan , ever since Automox migrated to the ZenDesk platform for our ticketing system we have been building a new Knowledge Base repository in our new Customer Portal. We left the old repository online for convenience until everything has been migrated.

You can find release notes now through the Customer Portal:
https://help.automox.com/hc/en-us/articles/7936927791124-Finding-Release-Information

 

Agent 39:
https://help.automox.com/hc/en-us/articles/7731193309076-Agent-39-Release-Notes

 

Cheers!

Badge

Can we get a note for release 40?

Reply