Client Management Suite

I am intestrested in excluding the "Unclassified" patches from the report "Windows Compliance by Computer".  It is being used behind the scenes for compliance and percentage calculations and also when you drill down for Not Installed patches.  Has anyone done this before?

Thanks,

Dale

Dale,

I haven't tried modifying any of the CMS 7.x reports (finally got my 7.1 test box set up this week!) but if they are anything like the reports from Patch 6.2...I suggest putting on your SQL hat or calling a pro.  In 6.x at least most of the reports were generated by DB stored procedures that shouldn't be modified (though you can copy the code out of them into a report, or another custom stored procedure of your own).  What may work is to execute the results of the built-in reports to a temp table, then run a select against that to filter out those which are Unclassified...but that won't help much for compliance drill-downs and global percentages.

As I get more into 7.1 and figure out the inner workings, I'll post back if I come up with something.  Does Custom Severity still exist in 7.1?  Would that help you, to flag those Unclassified patches as your own custom classification, like "excluded" or "not approved" or something?

Thanks for the reply Kyle. Custom Severity still exists but there is no way to filter on it in the "Windows Compliance by Computer" report.  It might be SQL or IT Analytics once we get that configured.

You will need to clone the stored procedure, clone the report, modify the cloned report to point to the cloned stored procedure, then modify the stored procedure as necessary (updating the query if you add or remove variables/parameters).

Thanks for the reply Mike.  I think I'll have to talk to my DBA on getting access to the SP on the SQL Server box.  How can you find out what the SP is for the "Windows Compliance by Computer" report and once you clone it how do you point it to your new cloned report to the new SP?

It will appear in the SQL area of the cloned report as an exec, e.g. exec sp_WindowsPMCoreCompliancebyBulletin (that's imaginary).

You point the clone to the new SP by modifying this portion of the SQL to include the new SP name.

Well I thought I would post the 2 stored procedures I used.  As mentioned above I cloned the two reports, created two custom stored procedures and pointed the cloned reports to the new stored procedures. The hard part was figuring out the database schema.  Hope others find this useful.

Attachment(s)

spDY_PMWindows_ComplianceByComputer.txt   12 KB 1 version

spDY_PMWindows_ComplianceByUpdate.txt   17 KB 1 version