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.


0 Comments   [ + ] Show comments

Answers (1)

Posted by: dchristian 12 years ago
Red Belt

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.

Don't be a Stranger!

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

Sign up! or login


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