We use Box as an enterprise file sharing & collaboration solution, with Active Directory Federation Services (ADFS) as our Identity Provider (IdP).
However, there are some limitations with this setup which are not particularly detailed anywhere, just omitted.
Below are some of the limitations I’ve found.
Soon Microsoft are to release an update to the Office 2016 Volume License installer on VLSC.
This update is 15.17 & is the first that has a few changes that may affect the way you deploy Office 2016.
These changes are going to be later enforced in 15.20 & onwards. Below are some details on the changes, some of the why & how via the power of the MacAdmins.org Slack & the awesome @pbowden that some of us have had a sneak peek.
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.
Earlier today the above popped up on some 10.9 Macs, iOS devices & even Android devices. Clicking “Cancel” would only stop the pop up for a few minutes & it would re-appear.
On the MacAdmins Slack a few mentioned seeing this, so the immediate thoughts of “OMG what has happened to my wireless” subsided.
The below is to try explain the use of the Enabled/Disabled Identifiers arrays in the NBImageInfo.plist on OSX Server.
This is to try & better explain their use.
NBI’s that are generated via SIU have a NBImageInfo.plist which is populated from the SupportedModelProperties array in /System/Library/CoreServices/PlatformSupport.plist.
NOTE: Casper Imaging 9.65 addresses this & as such the workaround is no longer needed.
As blogged before, a part of our Casper Imaging workflow involves partitioning the “Macintosh HD” for use with FSTAB.
Unfortunately, we have discovered an issue with Casper Imaging & Yosemite shipped Macs as these Macs come with CoreStorage enabled “Macintosh HD”. This has been logged with JAMF as D-008217 & this post will be updated once resolved.
To get around this defect, I’ve written a little AppleScript app called “CoreStorage Revert” that you can get via a PKG from here. (NOTE: This is for CoreStorage volumes & not Fusion drives).
The PKG is meant to be added to an AutoCasperNBI created NBI, as it removes the com.AutoCasperNBI.CasperImaging.plist as “CoreStorage Revert” launches Casper Imaging itself.
For more details on the app, the why & some rambling findings, see below.