The Patch Management Solution for Windows Compliance Reports are showing clients needing a reboot when they have been rebooted, or they display inaccurate data concerning the client's compliance.
Software Update Cycle data is captured as an 'Event' for Patch Management. If the event is missed due to client tasks being backed up or stale, then the 'Event' is lost. If the Event is lost, the Patch Reports are not able to provide accurate 'IsInstalled=TRUE' or 'Reboot Required' data.
Utilizing scripting to execute the Software Update Cycle does not trigger the event, so the process does not gather the event data. This is not supported, for it is utilizing other solutions (Software Delivery or Task Jobs) to execute the Patch functions. Ensure that the process is completely owned by Patch Management.
Additionally, this can be caused by a myriad of things:
Review the following to see if the issue is present:
1. Check the Client's Registry to see if a reboot is required
2. Check the Client's Resource Manager
Once deemed this is the issue in the environment, wait for the Software Update Cycle to execute on the client(s) once more to resolve this temporary problem. However, if unable to wait for another Software Update Cycle / Reboot Event; review the work around section if needed.
Advisory: This has been resolved in Patch Management 8.x by enabling the 'Send additional status events for Software Update policies (Aex SWD Status)' on the Windows Patch Remediation Settings (Settings > All Settings > Software > Patch Management > Windows Settings)
Note: This process is not real-time and is dependent upon scheduled tasks to execute. The results should be present within a day at the most, but as early as 4 hours following, for the setting will request the missing event from the Clients following 'Update Configuration' to get this policy's change, the run of the Windows System Assessment Scan, and return inventory to the SMP Server to be processed to the database.
Work Around: run the attached sql files to update the views in the Symantec_CMDB database; vPMCore_SWDEventExecutionSuccessByComputer and vPMCore_SWDEventExecutionSuccessByComputer2
Workaround Addition 1: Import the attached custom report: Listed Missing Reboot Events
Workaround Addition 2: View the attached 'Custom RebootRequired Inventory_Dataclass_Report.zip' file; walks through the process to create a custom Inventory Job (gather reboot data without event), custom DataClass (store inventory in database) and custom Report (view data in Console).
Additional Info: Uninstalling / Reinstalling the Altiris Agent will not resolve this issue, for the Patch Inventory is held in the Symantec_CMDB database and will not be affected.