Network devices messed up after imaging

[sidhu_navdeep]

Hi Folks,

Recently I faced a peculiar issue when we imaged an old Macbook Pro (Mid 2009) using reference image which was captured using latest Macbook Pro model (Late 2013).

Image got installed fine but it messed up all network devices. For e.g. LAN card is showing as Wi-Fi under Network. It is also showing thunderbolt port in Network devices however physically there is no thunderbolt port available at old Mac.

I'm using Casper 9.22 version. Did anyone faced this issue & what could be the solution of this annoying problem? If anybody needs further information then please let me know.

Thanks in anticipation!

[bryce_carlson · Accepted solution]

You may want to look into using a vanilla never booted DMG when imaging. It can really cut down on issues with multiple models of Macs in an environment. It works great when there is a uniform build of OS X (like there is now with 10.9.2 Mavericks.) The project AutoDMG will help you make the never booted DMG. https://github.com/MagerValp/AutoDMG

Also, here is a nice step by step on it:
http://coolestguidesontheplanet.com/using-autodmg-create-clean-osx-10-9-mavericks-boot-image/

I have also posted some video walkthroughs on this:
http://www.youtube.com/playlist?list=PLeYyIvkU2s_Pjy_Mb4YoU09IZaJCuBirg

[sidhu_navdeep]

Many thanks for your response Bryce. I really appreciate it. I've gone through these links & will give it a shot to get a never booted DMG using AutoDMG app. I'll keep you posted....Thanks again

[bryce_carlson]

Not a problem.

Another side note on the Retina MacBook Pros since you mentioned that you use them (just so that my prior post is not misleading). I have had the best luck imaging those with a thin image standard. Or Apple rep basically told me that going forward Apple Engineering would prefer that new Mac use the OS that they are shipped with to cut down on text/driver issues.

In my testing the Retina MacBook Pros do not react well the an AutoDMG never booted disk image that was made on a non-retina system. For every other Mac we have in our environment the never booted disk image works flawlessly. It is just the Retina systems that act up. Not sure why, but our Apple rep is getting us an answer.

[sidhu_navdeep]

oops...I already captured never booted disk image using non-retina system via AutoDMG app. Since I'm very new to the Mac & Casper world, I don't know much about thin image standard. How does this work?

Moreover we always going to image the new Macs (irrespective of shipped OS) because there are so many other apps/standards which we want to apply on new Macs during imaging..so I'm bit worried that vanilla image may work on legacy Macs but it won't work on new Macs...so how can I image the new Macs (which comes with Retina display)?

[sidhu_navdeep]

or what will happen if I create never booted image by installing AutoDMG app on a Retina MacBook Pro? Will this work on both types of Macs?

[bryce_carlson]

And that image that you captured should work for all non-retina Macs. Honestly, the concept behind it says that it should also work on Retina Macs, but I had issues with rare but consistent kernel panics and lock ups when I used it.

Thin imaging is the iOSification of Mac deployment.
Here is a JAMF Nation post on the topic: https://jamfnation.jamfsoftware.com/discussion.html?id=10491
Thin imaging works just the same as any other deployment with the exception of two things. I will walk you through our deployment processes to paint a better picture.

Thin Imaging:
1. Get pallet of Macs from Apple
2. Unbox Macs
3. Asset Tag Macs
4. NetBoot (Like PXE Boot on PCs)
5. Run Casper Imaging (Do not erase the Mac HD that the Mac came with, and run a configuration without an OS)
6. Shutdown Mac
7. Deploy to staff member

Imaging with never booted disk image:
1. Get pallet of Macs from Apple
2. Unbox Macs
3. Asset Tag Macs
4. NetBoot (Like PXE Boot on PCs)
5. Run Casper Imaging (Erase the Mac HD that the Mac came with, and run a configuration that contains the DMG created from AutoDMG as the first item)
6. Shutdown Mac
7. Deploy to staff member

As far as your vintage Macs question goes. You could always make another config in Casper Admin that does contain an OS either captured from a Mac, or created from AutoDMG.

[bryce_carlson]

I have never made a AutoDMG image from a MacBook Pro.... It is worth a try. I just have not had the time to look at the mechanics of why that behavior exists, or tested it (since all MacBook Pros with Retina are out in the field after bing thin imaged).

[bryce_carlson]

Attached is screen shots of my two configs I referenced to give you a better idea of what I am talking about.
external image link
external image link

[bryce_carlson]

The link did not work quite right. Here is the raw link.
http://imgur.com/wMuB181
http://imgur.com/XSA0TpW

[sidhu_navdeep]

Thanks again for all the detailed information & details...I completely understood the process & appreciate for sharing the screen dumps to make it simpler!

I'm going to install AutoDMG on new Mac (with Retina display) & will capture the never booted DMG & then will try to image new Mac by erasing the Mac HD to see whether this will work or not. If it works then we can have a uniform approach for all Macs..If it does not work then I'll jump to thin imaging which you explained. I'll keep you posted.

Cheers!

[sidhu_navdeep]

Hi Bryce,
I just want to thank you for your tremendous support to resolve this issue. I successfully imaged legacy Macs using never booted DMG (10.9.3) & network devices remain intact after imaging. I also managed to image new Macs with retina display without any problems using this approach. So all looks good. Thanks again mate..cheers!