/build/static/layout/Breadcrumb_cap_w.png

Another patching best practice question.

I have the following criteria i'm trying to design for:
1.  Patch approximately 2000 servers (2003,2008,2012) - 2003 have extended support
2.  Servers spread out over 7 sites.
3.  Patch monthly 
4.  OS patches and updates only (no application patching, no service packs)
5.  Will always reboot after patching
6.  Most servers are patch, reboot, forget.
7.  Some servers require pre or post processing (shut down/ start services, etc)

-Assuming i use replication shares, how do I target servers to patch from a particular replication share?
-What would be best practice in how i create patch packages and assigning them to servers?
-What is the best way to patch servers with Kace when servers need pre or post patching?
-What is the easiest way to maintain the servers within each patch group?  (add or remove servers as new servers are built, pulled from group temporarily).   

thanks

0 Comments   [ + ] Show comments

Answers (1)

Posted by: ronco 5 years ago
Third Degree Brown Belt
0
rotherpj,

These and all other Patching-related questions are answered in the recent Patching Week Series KKEs.  You can also come to one of our Open Forum KKEs to discuss the various scenarios.

Ron Colson
KACE Koach

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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