See below on how to block this upgrade with Jamf Pro.
Last night, Jamf released Jamf Pro 10.13.1 & 10.15.1. These were released due to PI-007507.
This PI is noted as a “critical security vulnerability” which “does not pose a risk to private data or managed devices. It does have the potential to impact the integrity and availability of your web server” but “impacts versions of Jamf Pro 9.4 and later”
Below details these changes, & overcoming this issue.
With Jamf Pro 10.6.0, Jamf changed the default storage engine from MyISAM to InnoDB.
Jamf also released a tool to convert the tables with the release of 10.7.0.
However, as the Jamf supplied tools are not available currently available as a standalone download for those of us that do manual installations & as we host our datajar.mobi instances on Kubernetes… we went the manual route.
Below is how we performed these conversions.
On day 3 of JNUC 2017, I gave my third & final talk of the conference: “Securely Managing Identities Across Mac and G Suite with JumpCloud”
This talk should show just how easy it is to get started with JumpCloud. Along with an overview of how at dataJAR we’re leveraging JumpCloud to integrate G Suite within our Jamf|MSP platform (datajar.mobi), as well as bridging authentication across various other cloud systems & bring 2FA to our Macs.