Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Bandwidht control

Created: 26 Aug 2011 | 1 comment
jenstf's picture
4 Agree
0 Disagree
+4 4 Votes
Login to vote

When deploying clients to upgrade from SEP 11 to 12.1 last night I noticed that even 80 client deployments (aprox 180MB install file per client) used much of our bandwidht.

There is a possability to set the deploy time windows e.g from 1AM to 5AM. But it looked like all deployments where done from 1AM.
There is also possible to distribute it over x days.

What I want is the oppurtunity to set a bandwidht limit when deploying clients, so that it doesn't steal all the bandwidht.
Or that when I say that the upgrade schedule should be 00:00 to 06:00, the updates are distributed all over the schedule, not mass distributed when the schedule starts

Comments 1 CommentJump to latest comment

deepak.vasudevan's picture

I second your suggestion. For a bigger geographically distributed networks spread across a WAN between timezones the entire pipe would get locked only for this. 

In my opinion, the security should be a seamless background task never obtrusive and never intrusive.

0
Login to vote