Imaging the Newest Airs and Retina MBPs

the answer i got straight from Apple is that you probably have to have a separate image for these machines until at least 10.7.5 if not 10.8 probably.

I had to talk to Apple, ran into this with the last gen MBP when I used the Air as the base image. think it is a bug in X.7.X

I had to delete sudo rm -r /Library/Preferences/SystemConfiguration
and
re add each "hardware port" with networksetup

Not sure if this is helpful, but I do this on my base image - I don't re add each hardware port.

sudo defaults delete /Library/Preferences/SystemConfiguration/preferences NetworkServices

sudo defaults delete /Library/Preferences/SystemConfiguration/preferences CurrentSet

sudo defaults delete /Library/Preferences/SystemConfiguration/preferences Sets

sudo chmod 644 /Library/Preferences/SystemConfiguration/preferences.plist

sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

PS - c'mon 10.7.5!

Using a golden image from one specialized hardware to a newer specialized hardware (that only has driver support in its own custom build) is guaranteed to cause problems.

Issues with network adapters and hardware-specific configs is one the main reasons people have been moving away from manual "golden master" images.

I don't use Casper, but doesn't it have a "compiled imaging" feature that's functionally equivalent to InstaDMG or Apple's System Image Utility?

@caspersally Unfortunately (yet) another 10.7.5 seed was released last week.

[color=red]I loathe Apple this week.[/color]

Don

I've built a 10.8 netboot image, so all new hardware can be handled. Then I'd use a hardware specific build (if 10.7 or for a reimage) or a thin build (new hardware) to lay down the software and settings we use.