Patch Deployment Settings
We are evaluating patch management solutions that offer us a robust method of deploying, managing, and reporting on OS and application patches across approximately 170 WAN sites. Your current "Patch Deployment Settings" lack some features we are looking for and we wanted to identify those requirements and have you tell us if there are any plans to deploy these features in the future.
1. Bandwidth throttling.
We have numerous, older, slower, 56k Frame Relay sites that when we attempt to push patches with our legacy system, it completely utilizes the WAN network pipe and we effectively "break" that site. We need a patching solution that we can have flexible configuration options for how "fast" software/updates/patches are pulled/pushed. We need to be able to do the following.
Limit bandwidth per individual installation, "Push patch <abc> to device <123> at 15kbps".
Configure "site bandwidth" settings for remote IP subnets so that regardless of individual installation actions, any scheduled updates, that no software/updates/patches are pulled/pushed over a certain Kbps limit. "No traffic >25k for site <#001>".
We need to be able to "trickle" patches out slower pipes in some cases. Having per-site and per-deployment bandwidth options removes the need to configure how many machines from a remote site can receive updates at one time, that the updates are randomly scheduled, etc.
Pushing a single (1Mb) patch to 10 machines simultaneously over a 56k Frame Relay circuit will completely eat up all user bandwidth for quite some time. If we had the configuration option for "this site" so that when it receives updates, the server only pushes them at 5kbps, we minimize the operational risks.
Is there any possibility that per site, minimally, bandwidth restrictions on patch/updates/software deployments can be added as a feature>
ChrisSchear
1. Bandwidth throttling.
We have numerous, older, slower, 56k Frame Relay sites that when we attempt to push patches with our legacy system, it completely utilizes the WAN network pipe and we effectively "break" that site. We need a patching solution that we can have flexible configuration options for how "fast" software/updates/patches are pulled/pushed. We need to be able to do the following.
Limit bandwidth per individual installation, "Push patch <abc> to device <123> at 15kbps".
Configure "site bandwidth" settings for remote IP subnets so that regardless of individual installation actions, any scheduled updates, that no software/updates/patches are pulled/pushed over a certain Kbps limit. "No traffic >25k for site <#001>".
We need to be able to "trickle" patches out slower pipes in some cases. Having per-site and per-deployment bandwidth options removes the need to configure how many machines from a remote site can receive updates at one time, that the updates are randomly scheduled, etc.
Pushing a single (1Mb) patch to 10 machines simultaneously over a 56k Frame Relay circuit will completely eat up all user bandwidth for quite some time. If we had the configuration option for "this site" so that when it receives updates, the server only pushes them at 5kbps, we minimize the operational risks.
Is there any possibility that per site, minimally, bandwidth restrictions on patch/updates/software deployments can be added as a feature>
ChrisSchear