Can't image Late 2105 iMac's.

Are you using 10.11 taken from the iMac? They've got their own custom build.

@davidacland I wan't aware it was a forked build. If I manually boot into Macintosh HD, the JAMF Helper kicks in and everything works smoothly.

I'll recreate the OS using the 2015 iMac.

@davidacland

I just checked the build numbers and they're all exactly the same. "Operating System Build:15B42". Even the installer from the MAS.

Edit: Recreated the installer. Same issue. I'll probably make a support ticket.

Reset the PRAM on the system after imaging, if that corrects the issue, you'll need to reset the Startup Disk to the internal volume at the end of your imaging process, to override the last used startup setting.

If you isolate out the setting to just the Simple Finder, does it still cause Finder to crash?

The Late 2015 iMacs shipped with a system-specific build, but merged back with OS X 10.11.1.

OS X 10.11 15A284 September 30, 2015
OS X 10.11.1 15B42 October 21, 2015

Late 2015 27" iMac shipped with (first batches) OS X 10.11 (15A4310)
Late 2015 21.5" iMac shipped with OS X 10.11 (15A2301)

One would hope that 15B42 would be working on all...

Hi all,

Simple Finder not being disabled is an issue I have open with Apple as per this.

I'll probably add some logic to alert about simple finder & 10.11 NBI's for now.

Thanks @bentoms

@htse This worked.. I think. I'll make a new 10.11 Netboot image and report back. Surprised I had to do it for a brand-new iMac. There's a first for everything.

Hi All,

I have a pre-release of AutoCasperNBI 1.3.1 available: here.

This has a warning like the below when enabling Simple Finder for a 10.11 NBI or trying to build a 10.11 NBI with Simple Finder enabled:

@htse

I keep having to reset my PRAM every other Netboot. I wonder if it's the netboot image or the OS is the issue.

I'll report back.

@bentoms

Try AutoCasperNBI 1.3.1, worked without a problem.

excellent, now that you know that resetting the PRAM worked, you'll need follow through and reset the startup disk or reset the PRAM at the end of your imaging. You can either use the nvram -c to clear PRAM from a script or use systemsetup -setstartupdisk.

The Mac remembers the last device it started up from, this is expected behaviour, so it doesn't rescan for startup devices.

@htse So far "nvram -c" looks promising. Thanks once again!

@Abdiaziz thanks for the feedback here & on GitHub.

@htse have you tried with Casper NetInstall Creator?

The reason I ask, is that might use the recovery boot.efi which has SIP disabled. So... If that works, I know what I need to add to AutoCasperNBI. :)

@htse

After more testing, I'm back to square one. Reboot loops everywhere. It doesn't matter if the script is set for before, after or reboot.

#!/bin/bash

nvram -c

Selecting a startup disk gives me the error "Not a system folder"

sudo systemsetup -setstartupdisk /Volumes/"Macintosh HD"

Question,
Is it a prestage image?

Gabe Shackney
Princeton Public Schools

@gshackney

It is not a pre-stage image.

This is only happening with Late 2015 iMac's. I've tried multiple 2013 and 2015 iMac's and none of the 2013's are having this issue.

I'm going to upgrade our Netboot server to El Capitan.

@htse

Thanks for all the help!

This is what I'm using now. Set to "After" so it runs after applying the OS.

#!/bin/bash
nvram -c
sudo systemsetup -setstartupdisk /Volumes/"Macintosh HD"/System/Library/CoreServices