These are the most frequently asked questions about the 'Needs Attention' status in the Automox console.
Finding Devices that Need Attention
- Use the Device Troubleshooting section of the Dashboard: Automox Console Dashboard
- Use the filters on the Devices page: Filtering and Searching on the Devices Page
- Use the Needs Attention Report: Automox and Reporting Your Environment
Status Explanation
-
Needs Reboot - The device has patches that require a restart before the installation can complete.
- A trigger on the OS indicates that a reboot is still required.
- Note: As of version 2.3, the Automox agent detects user-initiated reboots for patch policies.
-
Failed Update Attempts - A recent patch policy failed to run.
- Use the Activity Log report to review patching errors for the device.
- Manual intervention might be required.
-
Disconnected for 30+ days - The Automox agent has not communicated with the console in 30+ days.
- If the computer is online, troubleshooting may be required: Device Status Shows Disconnected
- It is not possible to take any patching actions until these devices are connected again.
-
Not Compatible - A required component of the Automox agent is misconfigured.
- Missing Secure Token on Silicon macOS M-series devices: Secure Token Troubleshooting Guide
- Unable to connect to the Update Source (Windows Update, Apple Update).
- Low Disk Space - A minimum of 3GB of free space is required.
- Use the Device Logs section of the Device Details to review failing agent scan commands.
- Additional details may be found on the Device Details page: Compatibility Checklist
Incorrect Status
The device's status will only change when the computer is online and communicating with the Automox console.
If the Automox agent is offline, or the agent scans are failing, some of the statuses may not clear or change.
- Use the Device Logs section of the Device Details to review failing agent scan commands.