On Friday, Apple released an update titled “Incompatible Kernel Extension Configuration Data: Version 3.28.1”
This update was an exclude list of bad Kernel Extension’s for 10.11 & included an Apple Kernel Extension.
Below is some more information on this & a possible way to detect affected Macs via the JSS.
When trying to bring 10.11 support to AutoCasperNBI & AutoImagrNBI I stumbled across an odd issue.
On the flight to JNUC2015 I loaded up my 10.11 GM VM & figured it out.
Incredulous, I double checked this with James Ridsdale, Darren Wallace & David Acland. All of whom were located near me on the flight & all had their various MacBooks out running Keynote, Terminal &/or were running VM’s (spot the IT Crowd).
Below is what I found, steps to reproduce & a link to the bug on Open Radar.
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.
At Apple’s recent event, the release date for the next release of OS X (El Capitan) was “leaked” in the above shown email.
Not only is this release going to be the most magical since the last one, it’s main focus seems to be on performance & security. The latter of which will affect us admins, especially System Integrity Protection (read: SIP).
This post will try to explain one way SIP may affect you, & possibly how to prepare.