Your best bet is to create distributed repositories on the other end of these T1's, then in the Agent policy, have those machines only update from those repositories.
out of 13 locations we have repositories at 5 locations. So, do i have any other options?
I would try to put repositories at the other 8 locations. I would also increase the ASCI to at least a few hours to decrease bandwidth.
putting more repositories is not an option of mine.
"I would also increase the ASCI to at least a few hours to decrease bandwidth" - where is this option?
1 of 1 people found this helpful
ASCI (Agent-to-Server Communication Interval) is set within the McAfee Agent Policy. You can just keep increasing it until you find the right setting for you.
To fascilitate updates to remote sites over slower pipes as there is no BITS-like mechanism in ePO; I disabled global updating and set up an update task to kick off at a specific time local to the machine and used the randomization value within the task to spread out when machines would kick off the task.
This solution gives two levels of throttling: timezone and randomization.
NOTE: This is with ePO 3.6.1, hopefully you can extrapolate to ePO 4.0 easily.
Its been awhile, sorry for the delay. I did what you said and i will see how it works out. As of right now i have a very small test group and it should not mess with bandwidth. However, I will have to look into doing the same thing with all of my tasks. The guy i work with though thinks that you can make it work with a select number of computers at a time. Any idea what he may be talking about. Push out updates to 4 machines, when done push out to another 4 machines and so on.