Pushing Software Best Practice
I'm trying to get a feel for what people are doing to push software to numerous machines (200+). For instance - you want to send an upgrade or patch to 200+ machines. How are people accomplishing this in a matter that doesn't slow the network or the KACE appliance to a crawl? If you are breaking the computers down into groups do you find that the push still goes out in a timely matter.
Reason for question - we are trying to minimize downtime when we eventually have to push out a monthly software update.
Thanks.
Reason for question - we are trying to minimize downtime when we eventually have to push out a monthly software update.
Thanks.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
dchristian
14 years ago
Cgoodwin,
Besides breaking the computers into groups, you may want to alter the deployment window of your managed installation.
This way you will only deploy your software during off hours.
Besides breaking the computers into groups, you may want to alter the deployment window of your managed installation.
This way you will only deploy your software during off hours.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
