A remediation might require a full system reboot in order for the patch or update to take effect. Occasionally, a remediation might even require a second reboot.
As a Windows administrator, to determine if an advisory or minion requires a reboot as part of a remediation, first run an assessment.
Note: Rebooting as part of remediaton only applies to Windows minions.
Then to determine whether a reboot is needed:
For | Refer to |
---|---|
Advisory | On the Advisories tab of the policy dashboard, check the Install Behavior column for the advisory's status:
|
Minion | On the Minions tab of the policy dashboard, check the Needs Reboot column for the minion's status:
|
If you detemine your system or minion needs a reboot follow these steps:
Procedure
Results
After initiating a reboot, the minion might take several minutes to reboot and come back online.
To check whether the minion is back online after a reboot, refresh the Minions tab in the Vulnerability workspace and check the minion’s presence. See Minion presence for more information.
What to do next
After rebooting a minion as part of a remediation, you must run another assessment to verify the remediation was successful.