OT: Nested SUS's?

We daisy chain SUS in most environments. Master pulls down updates from the WAN, then the replicas all point to the Master for its updates. I one global company, we had problems getting the Hong Kong SUS to sync to the master in London. The pipe, latency, etc., so we set up the Hong Kong SUS to pull from the internet. Didn't have problems with US/UK/FR SUS replication. I would assume you can use Casper to point each region's Macs to the local SUS (whether it's a Master or Replica)...we use WGM (MCX) to control that.
"Toms, Ben (Grey Communications Group - IT)" <Ben.Toms at grey.com> wrote:

Apple recently posted a KB with instructions on how to set things up. I would talk with your network folks first to make sure you won't run into any latency/bottleneck issues.

http://support.apple.com/kb/HT3765

I remember back when I first researched this, there was no KB:

http://lists.apple.com/archives/macos-x-server/2008/Apr/msg00401.html

PS, I don't think this is OT at all...

Don

I may be incorrect, but I'm now going through the ACSA certifications...

I think that if you do the "nesting" that you still have to enable the updates on each sus server. The updates are downloaded and enabled on the master; then the additional servers synchronize using swupd_syncd. After this synchronization you have to enable the updates on the secondary servers.

Perfect don!

Thank you.

I was looking for nesting, replicating or multiple Sus on apples kb. NOT cascading!

Doh!

Again thanks to you & craig....

Regards,

Ben.

Each SUS is handled independently. And you can specify multiple SUS's in the
JSS and then point a computer or a group of computers in the JSS to a
specific SUS in multiple ways, like network segments, etc...

Craig E

Thanks for the speedy reply.

We'll use NW segments to point mac's to local SUS's.

But I was hoping we could point all our SUS's to one master SUS that we enable updates on. Rather than having to enable for each sus seperately.

Regards,

Ben.