/build/static/layout/Breadcrumb_cap_w.png

Best Practice patching

I am setting up the patching schedules for our server environment. 

Is it best to create a schedule for each severity of patching? (Critical, Important, Low .. etc..)

If so, I am considering creating a detect schedule to include all severity. Then create a deploy schedule one each severity.

schedule detect - critical, important, moderate, low, recommended

schedule deploy - critical

schedule deploy - important

schedule deploy - moderate

schedule deploy - low

schedule deploy - recommended


The schedules would be to detect the on Thursday after patch Tuesday then deploy Friday after patch Tuesday.

I'm creating a test environment for the initial patching then pushing to production after a week.


0 Comments   [ + ] Show comments

Answers (1)

Posted by: Hobbsy 1 month ago
Red Belt
0

If you are planning on patching at that granular level you may not have time to patch all patches and you will increase server downtime by doing it this way. 

Good luck automating your patching based on Patch Tuesday too, Quest have been deaf to our requests to make this possible for the last few years, but if you want to know how it is possible you are welcome to get in touch.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ