Could someone explain me the differences between the report called: "Computer Requering Restart" that is located under Patch Management Menu:
and the ones that check the table Inv_AeX_AC_Client_Status.
Im asking because in the first one, filtering by "All Site Servers" Im getting that only 1 Task Server is pending of reboot but using the one published by @Igor Perevozchikov here I am getting 64 results (using the same filter) I am getting 66 Task Servers pending to be rebooted.
In any case Im appliying a policy that reboots Task Servers when it is needed using an schedule, but Im realizing that almost all site servers are being rebooted even when the reports are saying that no reboot is pending.
Thanks for your help.
Hello Pablo Llorente!1. "Restart status" patch management solution report works using stored procedure spPMCore_RebootStatusReportThis stored procedure checks this SQL table "Inv_Software_Update_Distribution_Status" to check there "DistributionStatus" column for value 65536 which is set by event from "Software Update Agent" if there are installed patch update(s) which require rebootOnce computer will be rebooted, then "Software Update Agent" will check that patch is installed, reboot is done and then removes this pending reboot state2. This custom report https://community.broadcom.com/symantecenterprise/viewdocument/report-to-see-current-pending-rebo?CommunityKey=ef59d715-7ea1-41c6-97f3-dd1bcc10d0c3&tab=librarydocuments is based on "Inv_AeX_AC_Client_Status" sql table and if "MachineState" column = 1 (means that there is a pending reboot state in Operating System and not caused exactly by event from "Software Update agent" after patch update(s) installation, but probably there are other reasons of pending reboots, like computer domain join, computer name rename, WUA installed updates with pending reboot state) this information is checked by Symantec Management Agent in current Operating system registry.You can try powershell script to check pending reboot state