Agent 36 Release Notes

  • 14 February 2022
  • 3 replies

Userlevel 2

Hello Automox community! My name is Eric Huber and I’m the new Agent Product Manager here at Automox. I am excited to announce that Agent 36 is now available to download in the Automox Console! This release is for Mac devices only


Here’s what’s new:

  • New: Enhanced patching capabilities for all supported macOS operating systems (Intel & Apple Silicon). To reiterate, the below operating systems are supported:

    • macOS 10.15 “Catalina” (Intel)

    • macOS 11.x “Big Sur” (Intel & Apple Silicon)

    • macOS 12.x “Monterey” (Intel & Apple Silicon)

  • Change: The commands to enable the Automox Service Account for patching Apple Silicon devices have changed. IMPORTANT: the old flags will no longer work on Agent 36. Please review our updated documentation here.

    • New Flags
      --automox-service-account <enable|disable>

      --automox-user-prompt <enable|disable>

  • Change: The user prompt will appear immediately for entering a password after running the --automox-user-prompt enable command rather than waiting for a device scan

  • Fix: A user could be prompted twice for a password after enabling the service account

  • Fix: Reboot commands could appear stuck on macOS devices

  • Fix: macOS Monterey could not be patched on Intel devices

  • Fix: Mac devices reboot without notification on macOS updates

  • Fix: Mac devices do not reboot and log out users after macOS updates

  • Fix: The Automox Service Account password would rotate after every command causing subsequent commands to fail

  • Fix: A user prompt for granting secure token access could appear twice in some conditions

  • Security: General security improvements and enhancements.

  • Known Issue: When enabling the Automox Service Account user prompt via an SSH session, the user password prompt will close when the SSH session terminates or times out, but the user prompt process still runs. 

    • Workaround: Do not enable the Automox Service Account via an SSH session. Use a worklet or MDM tool instead

    • Status: Will be fixed in a future release

  • Known Issue: If an administrator manually creates the Automox Service Account and then uses the --automox-user-prompt enable command to assign a secure token to that service account, secure token access is not granted. 

    • Workaround: Do not manually create a service account. Let the Automox agent create the service account by following the instructions here

    • Status: Will be addressed in a future release


Automatic upgrades to Agent 36 are disabled for all Organizations until Wednesday, February 16th.

3 replies


thanks so much for this. We were hit hard by this the last couple of months. Lets hope this improves our posture

Userlevel 2

thanks so much for this. We were hit hard by this the last couple of months. Lets hope this improves our posture

It’s our pleasure! Please do let us know if this addresses some of the issues you’ve been facing :)

Thanks, Eric! And was certainly an issue we needed to address, @lamador - and we are. I mean, we went & found @EricH-Automox after all. :metal: