You'd need to create new NetBoot sets from the OS on the new MacBook Airs since they have a special build of OS X 10.10.2.

I've chosen to use a "no-imaging" approach for these for now, where I boot into the Recovery HD, attach a USB drive and install some bootstrapping packages.

Once 10.10.3 ships I'll build a new (hopefully "universal") NetBoot set.

@RossDrummond The new models come with their own "forked" build of OSX.

1. So you'll need to grab a copy of Composer (i'd recommend 9.7)
2. Boot an new untouched MacBook Air into Target Disk Mode
3. Create an OS.dmg of it via Composer.
4. Create an NBI via AutoCasperNBI
5. Upload the new NBI to your NetBoot Server.
6. Upload the OS.dmg created at 3 to Casper Admin.
7. Netboot & image

@gregneagle @bentoms

Thanks guys, I created a new image via AutoDMG from the latest installed of 10.10 from the AppStore but i'll try this route. Do you know what's changed in these models that they've forked?

I owe you a reply as well @bentoms Using your new AutoCasperNBI works a treat!

But don't worry, you're not alone.

One does not know about fork builds until they survive their first new round of hardware.

@RossDrummond On the Airs it was new processors and the new Thunderbolt 2 port. On the 13" MacBook Retinas, along with the Thunderbolt 2 port and processor bump, they also got the new Force touchpad. Processor bumps don't always fork the OS but at least the Thunderbolt and touchpads did.

@RossDrummond

It's almost always the logic board hardware that has changed, causing a need for new kernel drivers. Since the logic boards were not in production when 10.10.2 was released, a new build of 10.10.2 had to be built that included the new kernel drivers. This is the way Apple has always operated, and I highly doubt it will change.

This discussion has some ideas on how to grab the InstallESD.dmg file from that MacBook Air, in case you do not want to use the Composer method that @bentoms mentioned abve:

Early 2015 macs - can not download "Install OS X Yosemite"

It's all coming back to me now @adamcodega @stevewood! Those grey discs in the paper bag, going through them all trying to find the right installer!

Thanks for your responses, a momentary brain fart, totally forgot they do that!

Ross.

@bentoms

I just got one of these MBA's A1466 7,2 hit my environment. I am currently using one of your Netboot configs built late last year. By using the steps below and the rest of the process, am I going to have to have two NBI's on my network(and possibly three when I start seeing the new Macbook)? What are other's plans.

Having to rebuild a NBI every time Apple tweaks hardware really bites. Wish there was another, more hardware agnostic way.

/randy

Posted: 4/2/15 at 8:55 AM by bentoms

@RossDrummond The new models come with their own "forked" build of OSX.

So you'll need to grab a copy of Composer (i'd recommend 9.7)
Boot an new untouched MacBook Air into Target Disk Mode
Create an OS.dmg of it via Composer.
Create an NBI via AutoCasperNBI
Upload the new NBI to your NetBoot Server.
Upload the OS.dmg created at 3 to Casper Admin.
Netboot & image

@Diddel you should be able to boot everything prior to the MBA if you build an NBI using the build of 10.10.2 that is specific to that MBA. However, you can also wait for 10.10.3 to drop, which is rumored to happen today. With that update, fingers crossed, you should be able to boot the new MBA, the new MacBook, and the new MacBook Pro.

That would allow you to have one NBI set to boot everything, until Apple releases new hardware, then it is rinse and repeat the process.

@stevewood

Thanks for the heads up on 10.10.3. I have been on vacation for the past 2+ weeks and I just came back to all this. I did not take technology with me on the road other than a phone so I have been out of the loop on 10.10.3.

I will hold out for the update and then update the NBI and cross the fingers.

/randy

@Diddel you should be able to boot everything prior to the MBA if you build an NBI using the build of 10.10.2 that is specific to that MBA. However, you can also wait for 10.10.3 to drop, which is rumored to happen today. With that update, fingers crossed, you should be able to boot the new MBA, the new MacBook, and the new MacBook Pro.

That would allow you to have one NBI set to boot everything, until Apple releases new hardware, then it is rinse and repeat the process.

Well speak of the devil. 10.10.3 just dropped.

Thanks everyone, I was having difficulties with the Early 2015 MBA's as well. After updating to 10.10.3 and creating a new NBI i can now image these.

Anyone else running into an issue with AutoCasperNBI not being able to recognize 10.10.3?

@obannonl what steps did you follow to create a new NBI for 10.10.3?

@rbecerra The method I used was I took a brand new MBA Updated the OS to 10.10.3
Enable root user and turn on auto logon to root user
Reboot(System should then auto logon as root user)
Configured how I wanted the NBI to look(Casper Imaging on the dock and auto Launch, background color, etc)
Reboot into Target disk mode and connect(Thunderbolt Cable) to system running same OS(10.10.3)
Use Disk Utility to create image file(DMG)) from the target disk
Use System Image Utility to create NetBoot image from the DMG just created
Copy Netboot Image to server

I haven't tried using the AutoCasperNBI tool so I don't know the time difference, but my method takes me about an hour to complete.

I'm having an issue with my NBI which was created with AutoCasperNBI on a 2015 MBA with 10.10.3 installed. I can get into the NBI and run Casper Imaging but it fails to install the OS every time (actually fails to install any OS I have). It just skips over it like it can't mount the distribution point or something. The error log doesn't show any issue with it mounting the DP. The error I get is:

Error: The package "Base_10.10.3-14D131.hfs.dmg" does not exist in "/Volumes/CasperShare/Packages/"

Here is what I can't figure out if I throw my old NBI back on the server and boot into it I can image the computer just fine with the 10.10.3 OS.

@stutz That seems like Casper Imaging cannot find the OS.dmg.

Do you have multiple DP's, have they been replicated?

@rbecerra How was the 10.10.3 OS.dmg created & what version of AutoCasperNBI?

AutoDMG created OS.dmg's should work fine for AutoCasperNBI release version.

If captured an OS.dmg using composer & didn't select recovery HD (a composer 9.7 feature), then you'll need to try the pre-release.

No I just have the one DP.

Casper Imaging can find the DP on the old NBI but not the new one is what it appears. I tried re-creating the NBI on a different computer and the same issue occurs.

@obannonl on my rMBP 2013, NBI's take under 20 minutes.

@stutz Different versions of Casper Imaging?

Nope same one v9.62.

@stutz what OS was old NBI? Can you try a newer Casper Imaging on the new NBI?

The OS was 10.10.2. I'll give v9.7 a shot and see if I get anything different.

@stutz 9.65 imaging might be a better bet. There seems to be issues with 9.7 imaging & recovery partition for some.

You won't be able to image OS X 10.10.2 or later unless you're at 9.65 at a minimum (due to a defect in the OS version detection in Casper Imaging 9.63 and earlier. We don't talk about 9.64). As @bentoms said, 9.7 may have some issues with deploying the Recovery partition in some situations, but 9.65 is pretty tried-and-true.