FW: pushing out iTunes update, SUS?

[CasperSally]

Looks like we may have to jump from 9.2 to 10.1.

Is SUS the best way to do this? We've never used SUS in the past. I'm mostly concerned with bandwidth of all machines trying to pull updates wirelessly (I know you can limit bandwidth used per machine, but the quantity of machines checking in makes me nervous). I realize you can also use multiple servers.

Can anyone provide some info on suggested bandwidth settings, how many servers per X machines you use, etc?

Thanks!

[stevewood]

If it were me and I had bandwidth concerns I would add iTunes to my
JSS and use policies to push out. That way I could control which
machines got he update at certain times.

For example, I might break my user base by building and scope a policy
to each building. If I had 5 buildings then I would have 5 policies
that might become active on different days. Make sense?

Steve

Sent from my iPhone

[Bukira]

That's what I do, we don't bother with SUS

Criss Myers

[tlarkin]

I have 1 xserve per a building for Casper, which also runs SUS. I have it set up to cascade from one parent server to all children server and then use self service to allow users to trigger updates and force a reboot.

You can always download the PKG manually from apple and have Casper deploy it that way. Just keep in mind that things like iTunes also need the newest versions of Safari and Quicktime a lot of the times as well.

I used to just drop updates in manually, but that got convoluted and was a pain. Now the SUS does it all.

-Tom