1.5 –2 hours is way, way, too long for just a 4GB base image even if you are going across a fast-Ethernet network. Normally our offices can image in about 40 minutes- less if they are on a 1 gig network.
Question: is your distribution point also your netboot server? If it is, that can slow imaging down significantly.
You might also try compiling your builds- this can save a huge amount of time.
What is doing the routing for this NetBoot service? How far apart (logically, physically) are these two networks?
Do you have asr scan the config/image for multicast? If so, how did you create and scan the image?
How fast are your pings from the target network to the NetBoot server?
Cheers, - Douglas Worley
Sent from my Tricorder.
OK after spending my day trying to figure out the netboot, our network group sniffing the network, it appears that we are unicasting the image. there are some multicast packets, but they done't appear to be the preferred delivery mechanism. I have read on multicast images and it appears that requires client side command line stuff. If we are wanting to use CasperImaging suite to deliver the base.dmg image we are providing, can we deliver that multicast.
I just did an asr scanimage --source <path/to/base.dmg> (I left off the --nostream because that sets the image up for unicast if I am reading correctly) and am waiting on the netboot results. Am I lost here or headed in teh right direction?
The man page for asr is confusing. It used to be actually wrong. :)
When scanning an image in Disk Utility, it adds the --nostream option which optimizes it for unicast deployment. The assumption is that if you are using a GUI app, you want unicast.
The default in the CLI using asr is to not put the --nostream option, which optimizes it for multicast deployment. The assumptions here is that if are using the CLI you are a power user, and likely want multicast.
The good news is that ASR will restore even if the image is scanned with the incorrect method, just so long as it is scanned. The news that your image is taking forever and throwing up multicast packets is in line with my labs of this use case.
Try making a copy of the image, and scan that with the --nostream option. See if that makes any difference.
Best of luck! - Douglas
Try restarting the NetBoot service?
Is there any pattern in the network traffic? Like, does the traffic show up only when pushing an image, or when sitting idle while NetBoot screen?
Did you use the Resource Kit to create the .nbi? Try making a new JAMF netboot set, see if that makes any difference.
I followed the netboot instructions from the "Casper Netboot Automator
Action.pdf" and I can't get it to work..
When I start system image util, I have 2 x Install Mac OS X Lion options
and 2 x Mac OS X Lion options...
Today I also had 1x of the ESD options...
It follow steps for configure options (Configure automatic root login,
launch casper imaging, and preference file) but when I try the netboot
it just launches a clean install complete with choose your regions...
Lead System Engineer, DEI & Mobility
3333 Beverly Rd. B2-338B
Hoffman Estates, IL 60179
Team Lead DEI: Matt Beiriger
<mailto:mbeirig at searshc.com;jwojda at searshc.com?subject=John%20Wojda%20Fe
Team Lead Mobility: Chris
<mailto:cstaana at searshc.com;jwojda at searshc.com?subject=John%20Wojda%20Fe
Mac Tip/Tricks/Self Service & Support
"Any time you choose to be inflexible in your approach to an
unpredictable project you are already building failure into your plan"