It has been 5 years since AutoCasperNBI was released, with AutoImagrNBI coming soon afterwards.
However, 5 years is a long time in the world of Apple. And as such, much has changed when it comes to deploying macOS.
NetBoot & Imaging are no longer viable methods for modern macOS deployment, especially when we look at booting off of a network volume to block copy an OS.
As such, today I am ceasing development on both projects & setting their respective GitHub repos as read-only.
In a future episode of the
Mac Admins Podcast I go into more detail about the history of how these apps came to be, & I’ll be at JNUC2019 next week raising a glass to both apps.
I have just updated both AutoCasperNBI & AutoImagrNBI to version 1.5.2.
The apps are now notarized, as per the forthcoming changes mentioned
Also, both projects Xcode settings have been updated & Sparkle bumped to the latest release 1.21.3 too.
Tonight brings a small update to both AutoCasperNBI & AutoImagrNBI, which is support for setting a custom Desktop image on Mojave.
Oh, & I correctly signed AutoCasperNBI this release (I hope).
Today I have released my seemingly annual pre-JNUC post-new macOS updates to both AutoCasperNBI & AutoImagrNBI, these are likely to be the last major updates to the apps & quite possibly the last updates to the apps ever.
Below is why I have updated the apps, & why this is likely to be their last update.
Another year, another macOS release & another update to AutoCasperNBI & AutoImagrNBI.
Details of the updates can be found below, as well as the sadness.
Earlier today, I released AutoCasperNBI & AutoImagrNBI 1.3.4. Both of these are now Sierra compatible as well as signed.
For more information about the changes to these apps, see below.
issue was opened recently for AutoCasperNBI, where 10.11.2 NBI’s generated for not accessible over ARD or VNC.
Some digging revealed this this only affected NBI’s with the
“Reduce Image Size” option selected.
NBI’s for 10.7.x – 10.11.1 work fine over ARD or VNC with that option selected, so some investigation was needed. Below is the investigative work, but you can also skip straight to
So it’s been a busy few months, whilst I’ve generally been
falling apart I’ve also been busy with various projects I own or am involved in & a side project to those has had a massive update.
As such, I felt it was a good time to quickly post an update on the goings on. Details below.
Update 25/10/15: The post has been updated with my findings & explains the additions in AutoCasperNBI & AutoImagrNBI where applicable.
On Wednesday Apple unleashed the 11th iteration of OS X, El Capitan.
This release has had a number of under the hood changes that have affected
AutoCasperNBI & AutoImagrNBI, some like csrutil have been detailed here. The two main issues can be found in greater detail below.
Now, don’t fret, these changes are not insurmountable. They just mean that neither
AutoCasperNBI nor AutoImagrNBI will have 10.11 releases available for a few weeks.
This should be fine as there’s no urgency for 10.11 NBIs as, at the time of writing, all current Macs can boot to 10.10.
Imagr may be the new kid on the Mac imaging block, but for those of us using the Casper Suite it can offer an alternative imaging method with little extra effort.
The post expands upon the above, explaining the niche use cases for Imagr for those of us using the Casper Suite