Video Screencast Help
Search Video Help Close Back
to help

What happened to Custom Severity in Patch reports?

Created: 11 Mar 2013 | Updated: 12 Mar 2013 | 1 comment
KSchroeder's picture
0 0 Votes
Login to vote

Hello all,

I'm sure one of you has already solved this...but I'm stuck.  We used "Custom Severity" extensively in 6.x to filter out non-required updates (Timzone fixes, Junk Email, misc Hotfixes) so as to not skew our compliance numbers.  While Custom Severity still exists in 7.1, none of the out-of-box reports seem to utilize it.  I thought it might be as simple as cloning those reports, adding a parameter for _CustomSeverity (as the 6.2 reports had) and moving along, but the Stored Procedures in 7.1 don't have Custom Severity listed.  Before I try to tie together the results from

exec spPMCore_CustomSeverityNames

I thought I would see if anyone else had already done this.  Anyone?

Operating Systems:

Comments 1 CommentJump to latest comment

Roman Vassiljev's picture

Hi KSchroeder,

You are right, in 6.x it was possible to filter Compliance report by selected Custom Severity. I believe you still may do it in 7.1 using ‘Group by’ field or ‘Search’.
Please see attached screenshots.

Thanks,
Roman

GroupByCustomSeverity.jpg SearchCustomSeverity.jpg
+1
Login to vote