Objective
To explain why an Automox patch policy may report a status of Successful even though no software or updates were actually installed on the endpoint, and how to verify device compliance.
Problem / Symptoms
The Automox Activity Log displays a Successful status for a patch policy execution.
No new updates or software installations appear in the device's installation history.
Agent log files (
amagent.log) contain messages such as:Couldn't find update for [ID], skipping. Nothing left to do.
Root Cause
When Automox executes a patch policy, it queries the local Operating System Update Manager (e.g., Windows Update Agent, apt/yum for Linux, or softwareupdate for macOS) to apply designated patches.
If the OS update manager determines that the requested updates are already installed or are no longer applicable to the endpoint's current build, it reports back to the Automox Agent that the process completed cleanly without errors. Consequently, Automox marks the policy execution task as Successful, as the device is in a compliant state.
Analyzing Log Files
When inspecting agent log entries for a policy run, key log outputs confirm that the local update engine completed its evaluation without errors:
| Log Identifier | Meaning |
"response":["0"] | Exit code 0—indicates the update execution completed with no engine errors. |
Couldn't find update for [ID], skipping. | The specific KB or package ID is not required or applicable for this endpoint's OS build. |
Nothing left to do. | Confirms the update engine finished scanning and applying all applicable updates. |
Example Log Entry (amagent.log)
{"args":"\"[Update IDs]\"","response":"[\"0\",\"Installing MS updates: ...\\r\\nCouldn't find update for [ID], skipping.\\r\\nNothing left to do\",null]"}Verification Steps
To confirm whether an endpoint is already fully updated or requires further action:
1.Check Local OS Update History:
Verify whether the targeted patches were previously installed on the endpoint:
- Windows: Navigate to Settings > Update & Security > View update history (or run
Get-HotFixin PowerShell). - macOS: Inspect
/var/log/install.logor runsoftwareupdate --historyin Terminal. - Linux: Check the package manager history log (e.g.,
/var/log/dpkg.logfor Debian/Ubuntu or/var/log/dnf.logfor RHEL).
2.Re-Scan Device in Automox Console:
In the Automox console, navigate to the Devices page, locate the endpoint, and select Scan Device to force an immediate software inventory refresh.
3.Verify Device Compliance Status:
Check the Device Details page to ensure no pending patches remain in the Needs Patching list.
Escalation Requirements
If you suspect an endpoint is missing patches that should apply to its OS build:
Collect the local agent log files:
Windows:
C:\ProgramData\amagent\amagent.logmacOS / Linux:
/var/log/automox/amagent.log
Submit a ticket to Automox Support including the Device Name, Device ID, and attached log files for analysis.