Skip to main content
Question

Late 2010 & 2010 not imaging via Capser Imaging although the Base build is (13B3116)

  • February 6, 2014
  • 3 replies
  • 29 views
K
Forum|alt.badge.img+3

Hi Guys

I am running into issues when trying to image a late 2010 or 2011 macbook pro (Non Retina).

We created a mavericks 10.9.1 netboot image (13B3116) which boots into every other mac we’ve tested so far.

See below:

Macbook Retina 13 Late 2013
Macbook Retina 15 Late 2013
Macbook Retina 13 2012
Macbook Retina 15 2015
Macbook Air 2012
Macbook Pro 15 2009 (Non Retina)

When I attempt to netboot using a late 2010 or 2011 macbook pro (Non Retina) the netboot does not load and I receive infamous stop sign. Therefore I created another Mavericks 10.9.1 netboot image based off the late 2011 (Non retina) macbook pro (13B42). I was able to netboot into the mavericks 10.9.1 netboot (13B42) successfully, however when I try to image the machine via casper imaging the process fails.

Our base image is currently mavericks 10.9.1 (13B3116) and we are able to image the above mentioned machines via casper imaging.

The mavericks 10.9.1 (13B3116) base image also works on the 2010 and 2011 macbook pro’s (non retina) if you image the machine via disk utility.

Does anyone have any suggestions on how I can fix this?

Thanks,

Kenny

    3 replies

    B
    Forum|alt.badge.img+9
    • bajones
    • Contributor
    • February 6, 2014

    Can you do a verbose boot (command+v) on the machine that is booting to the stop sign? This could shed some light on the reason it won't boot. I'm guessing it has something to do with the PlatformSupport plist file.

    When you say the imaging process fails, what exactly are you seeing? Any error messages or odd behavior?

    P
    Forum|alt.badge.img+11
    • pblake
    • Contributor
    • February 6, 2014

    I have found a lot of machines cannot run 10.9.1 until it receives a firmware update. I suggest dropping a 10.7 or 10.8 build and seeing if there is a firmware update.

    C
    Forum|alt.badge.img+10
    • clrlmiller
    • Contributor
    • February 12, 2014

    Apple forked the 10.9.1 build numbers for the Later systems vs. Older systems. This is your most likely culprit. The latest build for the older Macs is 10.9.1-13B42, while the later systems are using 10.9.1-13B3116. I might recommend creating another baseline OS image built on 13B42 for the older systems. We're hoping the build(s) will be unified as one by the time 10.9.2 is released.

    If you've an Apple Developer Account you can download a pre-release of 10.9.2 on which to create a single NetBoot Image. Legally, you CANNOT deploy it onto client systems, but this wouldn't be a deployment, just a means to boot all of your systems for Imaging, then lay down 1 of 2 configurations that beside the baseline OS build are identical.

    Terms & ConditionsCookie settingsAccessibility statement