Saturating the network with updates

rob_potvin
Contributor III
Contributor III

When 200+ clients try to pull 100MB from the Casper server it seems to saturate the network. Other then limit the scope is there a way to limit the amount of bandwidth used when downloading updates?

I just sent out the iWork 9.1 Update and took down the network, the network engineer is pissed and asked what I could do. I don't' have the answer, so any help would help me out

Thanks guys

8 REPLIES 8

talkingmoose
Moderator
Moderator

It's really up to you how you want to do it. Determine how many machines can cache files at one time without choking your network and set that as your maximum number. Then use static groups, smart groups, IP address ranges or something else that lets you divide up your machine count. Set different policies to push to a different group of machines at different times of day and verify at the end of each time period that your machines have cached the files.

When all your machines have cached the files then set one policy to tell them all to install. Keep in mind that you only want to install this type of update when no one is using the computer. Set your policy to verify if someone is logged in and run it only if no one is logged in or at Login, Logout or Startup.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

talkingmoose
Moderator
Moderator

This isn't necessarily a Casper-specific issue. It can happen with any
On 10/18/11 3:44 AM, "Rob Potvin" <bisjamf at bis-school.com> wrote:
deployment system.

Just don't do everything at once but rather stage or stagger times. If you
need to make sure folks have the updates at the same time then cache the
updates to the machines at staged or staggered times ahead of time and
then have Casper install cached packages at a specific time.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

Matt
Valued Contributor

Do staged deployments. Its actually better to do deployments in stages anyways. Do maybe 25 at a time.

rob_potvin
Contributor III
Contributor III

Thanks guys, how do you stagger? Groups? Hardware? Version? What is your logic behind it?

Thanks

nessts
Valued Contributor II

one way is to cache the packages on the every 30 check, then install the package at a later time.
or you make groups of computers to push to at different times.
--
Todd Ness
Technology Consultant/Non-Windows Services
Americas Regional Delivery Engineering
HP Enterprise Services

Matt
Valued Contributor

I do groups. I have a pilot group of 25 users that pilots all deployments, then I make a smart group to target users who don't have it and to install at a certain period, usually at login or logout.

donmontalvo
Esteemed Contributor III

Are you using AFP or HTTP? Curious, not that I know if it makes a difference.

Don

--
https://donmontalvo.com

Not applicable

On my case http takes longer to deploy a package that AFP so I decided to use AFP. I limited the bandwidth on the switch level.
Cheers

Carmelo Lopez Portilla

ITS EMBL Heidelberg
Tel. +49 (0) 6221 387 8444
Fax +49 (0) 6221 387 8517
email: lopez at embl.de