Patch Policy Did Not Reboot Device
If a device is not rebooted as expected after a patch policy runs, it could be due to Automox’s specific reboot behavior.
Understanding Reboot Behavior
Automox only reboots devices if required by the Package Manifest of the installed updates. Even when the policy setting "Automatically Reboot After a Patch Policy Runs" is enabled, a reboot occurs only if the update explicitly requires one.
Symptoms
- A patch policy completes, but the target device does not reboot automatically.
Troubleshooting Steps
Method 1: Check the Software page for Required Reboot Status
- Navigate to the Software page to view the status on the Required Reboot column.
Method 2: Device Details Page
- Navigate to the Device Details page in the Automox Console.
- Review the Requires Reboot field to check whether pending updates necessitate a reboot.
Method 3: API
Step 1: Identify the Installation Activity
- Navigate to Reports > Activity Log in the Automox Console.
- Locate the device that was expected to reboot.
- Review the installed patches, such as:
Installed patches:
- "2022-04 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64 (KB5012157)"
- "Security Intelligence Update for Microsoft Defender Antivirus - KB2267602"
- Note down the installed packages for the next step.
Step 2: Check the "requires_reboot" Variable
Use the Automox API to check the requires_reboot value:
- Refer to the API Guide for instructions on making the getSoftwarePackages call.
- After retrieving the list, search for the installed package (e.g., KB5012157).
- Confirm whether the requires_reboot field is set to true or false.
- If all packages show "requires_reboot": false, no reboot will occur.
Example Response:
{
"packageName": "KB5012157",
"requires_reboot": false
}
Additional Notes
- If issues persist, contact Automox Support with:
- Device Name/ID
- Logs from the affected device