Best Suggestion/Practices for setting up/configuring KACE for Deploying Patches to Servers
So our environment has about 50 or so windows servers from 2008 on up to 2019.
Here is what we would like to do, and not sure if it is doable:
- Best method for configuring patching for the servers that will cover most/all patches whilst keeping deployment time down to a suitable level (3hours)?
- Detect, and deploy so it automatically reboots, and installs patches until it is completely finished.
Would it be better if we made vendor specific patch labels, such as only MS Patches that are critical/important and run those on a regular basis, or some other method?
Looking for some suggestions and Ideas and really appreciate the feedback.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
kbot_cache
4 years ago
Hey Omorganx,
This response can get really long so i'll just post some quick bullet points that I think are important.
- Have replication shares for any geo location receiving patches for quicker jobs
- configure smart labels within the patch catalog for various patching scenarios
- Create patch jobs using the smart labels
That's all there is to it in a nut shell, lmk if you need some more detail.
