Deploy Studio RC20 MultiCasting on OS X 10.4.11 xserver

After finally finishing the Master image it came in at 72GB! Takes about 3 hours to image one machine and 6 hours for two. So I thought I'd give Multicasting another go (I tried it a couple of years ago with lots of lost packets!). Also just heard they refitted the server room so maybe this'll help.

It was set up a few months back when we had DHCP problems caused by upgrading DeployStudio to RC20. You get the option to set up Multicasting when you set up DeployStudio Server. Here's my post

So taking a new iMac 24" and an old white 21" iMac I thought I'd set up Multicasting. First in DeployStudio admin I clicked the image and clicked the Multicast button at the bottom (looks like the Airport icon)

Airport Icon at bottom denotes MultiCasting

This now shows it's multicasting in the Activity section.

I've set up a workflow to restore an image to a volume, and in this set up some Multicast options.

Setting up Multicast options in a workflow

So far I have tried:

• Attempt 1
• Stream Rate 6MB/s
• Clients Disk Speed 120MB/s (I wasn't sure about the older 21" iMac so I slowed it from 200MB/s)
• Start Trigger 2 client
• Result:
• Stream Rate 5MB/s
• Disk Rate changes from 5MB/s to 15MB/s

I've been writing this as the process is going, and just noticed at 12:48 that some errors occurred. I noticed that this happened around the time that I loaded DeployStudio Admin on my machine, so I think this might have caused a slight interruption on the server (and it is 7 years old now). I do remember that I once remote'd into a machine whilst imaging which interrupted it. So the process is a little delicate. I shall wait to see if it has effected the process or whether it can cope with a few byte missing here and there?

After waiting until the 100% marker (which took 3 hours) it seemed to have stopped with no more errors, although it didn't quite finish. It said something about "starting" but just stopped there. I waited for another hour with no more progress so decided to reboot. Upon reboot the startup disk was not set, and the came up with the white screen with a question mark!

My initial conclusion was that the process had failed, but in hindsight I think that maybe the computers were waiting the data that was lost to be broadcast again, but this might be me clutching at straws. I shall look into it at the end of August. For now we'll just have the old method to use.