Important Notices
Support Discontinued for Hosting Jamf Pro Server on macOS
Support for hosting the Jamf Pro server on macOS has been discontinued, and the Jamf Pro installer for Mac is no longer available to download.
If you want to migrate your Jamf Pro server from macOS to Jamf Cloud, contact Jamf Customer Success. If you want to keep your Jamf Pro server on premise, see the "Jamf Pro Server Environment" section of the System Requirements for supported platforms. For more information, see the Migrating to Another Server article.
The administrator applications that were previously included in the Jamf Pro installer for Mac—Composer, Jamf Admin, Jamf Remote, and Recon—are now available as a separate download on Jamf Account named "Jamf Pro Apps".
New Recommended Versions of MySQL
Starting with Jamf Pro 10.37.0, MySQL 8.0.28 is the recommended version. MySQL 8.0.28 addressed important security vulnerabilities. For more information, see the following webpage: Oracle Critical Patch Update Advisory - January 2022.
If you are using MySQL 8.0.27 or earlier, see the following MySQL documentation to upgrade: Upgrading MySQL.
If you are using the MySQL 5 series, the recommended version is now MySQL 5.7.37. If you want to upgrade to MySQL 8.0 (recommended), see the instructions in the following article: Upgrading to MySQL 8.0.
Computer Scripts with Duplicate Names
When upgrading to Jamf Pro 10.37.0, computer scripts with duplicated names in your environment will be renamed in the Jamf Pro database. Duplicate script names will be renamed in the following format:
ScriptName _renamed_UUID
Notice History by Release
| Starting with version... | Change or Consideration | Description |
|---|---|---|
10.36.0 | New recommended versions of MySQL | MySQL 8.0.27 is the recommended version for use with Jamf Pro 10.36.0. If you are using the MySQL 5 series, the recommended version is now MySQL 5.7.36. |
10.36.0 | Additional privileges required for Jamf Recon and Jamf Remote | Jamf Pro administrators will need to grant the following privileges to their Jamf Recon and Jamf Remote users for these applications to work properly:
|
10.33.0 | Memcached change required for clustered environments | A Memcached configuration error prevents Tomcat from starting in clustered environments when upgrading to Jamf Pro 10.33.0 or later. To start Tomcat and complete the Jamf Pro upgrade, you must navigate to path/to/jss/tomcat/webapps/ROOT/WEB-INF/classes/dal/memcached.properties and add memcached.directory.timeToLiveSeconds=86400 to the memcached.properties file. |
10.33.0 | Increased startup time when upgrading | Duplicated rows stored in the computer inventory applications database table will be removed during the initial server startup when upgrading to Jamf Pro 10.33.0. This one-time extended startup could take anywhere from a few additional minutes to several additional hours, depending on the size of your applications table and the hardware used in your environment. It is important that you do not stop the startup process. If you have questions or experience any issues during startup, contact Jamf Support. |
10.30.0 | Incremental upgrade required | Direct upgrades from Jamf Pro 10.28.x or earlier to Jamf Pro 10.30.0 or later may fail. An incremental upgrade to 10.29.x is now required for upgrades from 10.28.0 or earlier to Jamf Pro 10.30.0 or later. |
10.30.0 | Rename Apple TV devices | If your environment was impacted by [PI-008988], changes in Jamf Pro 10.30.0 may require the Apple TV devices in your environment to be renamed after you upgrade to 10.30.0 or later. You can manually edit the device's inventory information and enforce the device name. For more information see Mobile Device Inventory Information in the Jamf Pro Administrator's Guide. Alternatively, you can re-enroll devices with Jamf Pro using a PreStage enrollment that enforces device names. For more information, see Mobile Device PreStage Enrollments in the Jamf Pro Administrator's Guide. |
10.29.0 | Incremental upgrade required | Upgrading from 10.29.x or earlier requires an incremental upgrade to 10.30.x before upgrading to 10.31.0 or later due to a database change that may cause upgrades to fail. |
10.29.0 | Clear failed | If your environment was impacted by [PI-009279], you must clear all failed |