There was a Device that was not Rebooted by a Patch Policy
The Patch Policy contains the configuration "Automatically Reboot after a Patch Policy runs" setting to "true". However, with Automox, a Reboot will only occur if the Reboot is necessary from the Package Manifest. This means that if the Installation (InstallUpdate) that occurred contained items that would require a reboot in order to finish it's installation, Automox will then reboot the device if the Patch Policy has an "Automatically Reboot after Patch Policy run" setting configured to "true".
A policy was run on a device, but the resulting device was not rebooted by the patch policy.
- The first step is to identify the Installation Activity that should have resulted in a device Reboot. The easiest method to do this is to head to Report > Activity Log:
- Then, after clicking "View", find the Device that was supposed to reboot, if it appears in the Activity Log. for this example we'll be using one of our internal devices:
- Visibly, there is some information about what was installed, but it may be easier to expand the log window (press the downward "carrot" symbol on the right side)
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"
- Next, we can keep these items in mind, and search for all packages installed on the device using API. Here is the newbie guide, in case a reference is needed!
- Here is the link on how to make the getSoftwarePackages call for an individual device. Once the API call has been made, we can search in the Body for the Software Packages using their name, and then look for the "requires_reboot" variable which should contain a "true" or "false" boolean. In this instance, we'll look for "2022-04 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64 (KB5012157)"
- If the "requires_reboot" variable is "false" for all of the packages included with the Installation, then no reboot would have been issued.
- If the software included in the policy has not yet been patched, you can check the "Requires Reboot" field on the Device Details page to see if the policy that was updated needed a reboot: