Throughout the Automox console, status messages are heavily relied on to indicate the current operating state of devices, policies, and agents. While these status messages are intended to be simple indicators of state, the underlying meaning of each one is not always clear. To provide more details, the definition of each status message is outlined here.
You will see a number of different states for your devices in the Automox platform. To convey this information, every device is assigned a status that indicates exactly how Automox is interacting with the device at any given time.
Devices with an Initializing status have successfully connected to Automox, but have not yet completed their first system scan.
System scans are typically performed once every 24 hours for each device—or on demand, if desired. The Scanning status indicates that a system scan has been queued on a device, but has not yet completed.
Whenever a new patch is being installed on a device, its status shows Updating until the installation is complete.
If, for some reason, a patch needs to be rolled back, its status changes to Uninstalling until the uninstallation process is finished.
Rolling back patches is inherently risky and can cause operating system or application failures. We highly recommend testing rollbacks before applying them to critical systems. The device will reboot in order to roll back the patch.
When a reboot command has been issued from Automox to a given device, its status is set to Rebooting until the reboot process has finished.
The Needs Attention status indicates that one or more policies on a selected device are marked as Non-Compliant. Manual intervention may be required to fix a device in a Needs Attention state.
Devices with a status of Compliant have no queued commands and no scheduled updates.
Whenever a policy assigned to a device is pending remediation, the device will have a status of Pending Update.
During the course of a system scan, Automox will query the device's operating system to determine if a reboot is required. If so, the device's status will be set to Reboot Required, indicating that the device may require a reboot. Rebooting may happen automatically the next time a policy with automatic rebooting enabled is run.
In addition to the Device Status, policies assigned to the device will also have their own assigned statuses as well. These policy statuses indicate the current state of a given policy's evaluation and remediation steps.
Policies with a status of Non-Compliant have failed remediation. While the definition of "remediation" can differ depending on the policy type, this generally means that the policy has failed to successfully install new patches and manual intervention may be required.
During a system scan, each policy is evaluated to determine whether or not remediation is required on a given device. If so, its status will be set to Pending Remediation until remediation happens during the patch scheduled defined on the policy itself.
Policies with a status of Compliant have no scheduled updates or failed remediations.
A device's connection status is used to indicate whether or not the Automox agent installed on the device is communicating with the Automox API. While this status isn't a firm indication that something is wrong with the device, it can be used to determine how up-to-date the device's information is.
If the Automox agent installed on a device hasn't checked into the Automox API within the last two minutes, the device's connection status is set to Disconnected.
A Connected connection status indicates that the agent has checked in with the Automox API within the last two minutes.