Now I am starting to ponder if an update to a newer OS version could be something. While it was not the latest version back then, it sounded like the most suited for this 3-years-old machine. Two years ago I decided to bite the bullet and pulled the trigger on an update to El Capitan. It came with Mavericks installed, which I thought was a very good system indeed. You'll have to wait until 10.9.1.Since 2013 I own a 13' rMBP (2.8 i7, 16GB, 512GB SSD).Īpart from the battery, which I will have replaced at an Apple Store within the next months (the capacity dropped to about 65% by now, after over 1100 cycles), I am still very happy with its functionality and performance. I don't think you're going to get a working netboot image of 10.9 for all the new models and the older ones. In the case of imaging, we're leaving the current OS on (i.e., the 'special' build) and just applying the rest of our setup via policies/Casper Remote. The few Late 2013 machines we picked up, we're just not netbooting them. Us now, for example, we have an App Store 10.9 netboot image for all models but Late 2013. I really don't think it's worth the headache of managing netboot images and forked OSes. Us IT folk then wait for the next update which levels everything out.īest practice, imho, is not creating a production netboot image until a model-spanning build number is out. Generally, these days, all new models ship with a model-specific build number that can't be used with any other model. When 10.8.5 was released, it had only one build number for all models. Nor could older machines boot to an image of the MacBook Air's 'special' 10.8.4.

This summer the MacBook Airs came out with a special build of 10.8.4, so they couldn't netboot to our 10.8.4 netboot image.

I'm not surprised older models don't boot to the image from the new model.

Late 2013 imac latest os