Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

About Custom Severity - (Maybe a fool question)

Created: 25 Jun 2012 | 1 comment
Goltrek's picture

 

Hi, I'm very newbie with Patch Management, but I was read a lot of info (even the: Symantec Mangement Platform 7.1 - Installation and Setup of Patch Management Solution Outline).
 
So, I'm not sure if I have a wrong idea about Custom Severity; but as I see it, with Custom Severity feature I can to refine what patches applies to my platform and which one don't.
 
The short history is that I don't know how to link the Custom Severity with my patch policies, in order to be able to stablish that critical patches be installed every week without user interaction and important or other severities be installed on other schedule.

 

 

Comments 1 CommentJump to latest comment

JSpur's picture

Microsoft publishes a patch that is critical to Windows XP but only Moderate to Windows 7. Your environment doesn't run Windows XP but does run Windows 7. You can then assign a custom severity code to that particular bulletin that tells you that it’s not critical but it is Moderate. So when you run reports for your environment you see your custom severity code and know that this is not something you have to deploy ASAP.  

Beyond that, patch does not distinguish between Critical and everything else when it comes to scheduling. What you enable is what gets installed based on the defined schedule and applicability. You should have only one Software Update Policy assigned to any given computer.

If anyone else has input on this, please feel free to add or correct my statement.