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).   

0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



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
Answered 08/11/2015 by: ronco
Second Degree Brown Belt

Please log in to comment
Nine Simple (but Critical) Tips for Effective Patch Management
This paper reviews nine simple tips that can make patch management simpler, more effective and less expensive.