Patch Management 7.1 SP 2, TECH167291, Reboot Status Data Class
We are currently experiencing issues with our Patch Management Solution 7.1 SP 2. I have a ticket with support but they don’t seem to have an answer for me. I have applied TECH167291 per support. Which is supposed to fix the issue.
History: I called support regarding Windows Compliance by Computer and Reboot Status Reports were not accurate. Compliance numbers were off, computers needing to be rebooted (not all of them actually needed to be rebooted), some systems if they were rebooted they didn’t update in the compliance report or the reboot status report even though the updates were installed and the system was rebooted.
I’ve done some research and found prior to applying TECH167291, that there are some key tables which are not functioning correctly. The following tables will execute if I take there script and execute it in a query but if I try to view the table normally through SQL Management Studio, I am unable to view the table getting a timout execution error. If I run the script through a query it will take 9-12 minutes to finish. Thus the stored procedure calling it is not allowing enough time for these to update.
The tables include:
Another table which does not have correct information in it is the Evt_Reboot table which is the key table in reporting when a system has been rebooted. There are several systems (50-60) which do not have any reboot history showing NULL instead. After researching these systems in resource manager, I found that these systems are missing the data class reboot which is required for Patch to report when a system has been rebooted.
I have applied the TECH167291 as recommended to fix the issue regarding compliance inaccuracy but now, since the fix bypasses reboot required and keys off of actual installs the reboot status report is blank, and the compliance by windows report shows there are no pending reboots.
We need to have all reports function as they should. Any ideas on how I can get the data class applied back to the systems missing it? Or any way to generate a reboot status report maybe some other way? I need to get this fixed as soon as possible, and support is not SQL efficient enough to help repair the tables at the current level I’m at.