Incremental Upgrade Scenarios for Jamf Pro 10.0.0 or Later
The following table lists the incremental upgrade paths required for upgrading to Jamf Pro 10.0.0 or later.
Upgrading from version | Incremental upgrade path | Notes |
---|---|---|
10.38.x | N/A | Jamf Pro 10.34.1 and 10.34.2 resolve a security vulnerability. It is strongly recommended that you upgrade to 10.34.2 or later as soon as possible. For more information, see Jamf Nation. Jamf Pro 10.34.0 includes a database schema change which requires MySQL 5.7.13 or later. Upgrades to Jamf Pro 10.34.0 or later will fail if you have an older version of MySQL installed; you must first upgrade to 5.7.13 or later (MySQL 8.0 is recommended). For instructions, see the Upgrading to MySQL 8.0 article. Due to a Memecached configuration error that prevents Tomcat from starting in clustered environments, you must do the following when upgrading from Jamf Pro 10.32.x or earlier to Jamf Pro 10.33.x or later:
|
10.29.x |
| 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.28.x |
| Upgrading from 10.28.x or earlier requires an incremental upgrade to 10.29.x before upgrading to 10.30.0 or later due to a database change that may cause upgrades to fail. Jamf Pro 10.27.0 includes a database performance enhancement which requires MySQL 5.7.8 or later. Upgrades to Jamf Pro 10.27.0 or later will fail if you have an older version of MySQL installed; you must first upgrade to MySQL 5.7.8 or later (MySQL 8.0 is recommended). For instructions, see the Upgrading to MySQL 8.0 article. In Jamf Pro 10.26.0, a new column was added to the |
10.24.x |
| Upgrading from 10.24.x or earlier requires an incremental upgrade to 10.25.0 before upgrading to 10.26.0 or later due to a database change that causes upgrades to fail. As a result of PI-008830 and PI-008818, some MDM commands fail to send in environments that have been upgraded to 10.24.1. It is recommended that you upgrade to Jamf Pro 10.24.2 or later to resolve these product issues. Jamf Pro 10.20.0 resolves a third-party security vulnerability that affects on-premise customers running Jamf Pro 10.19.0 or earlier. For more information, see Update: Apache Tomcat Vulnerability. Jamf Pro 10.16.0 or later requires MySQL 5.7.8 or later. If you have an incompatible version of MySQL installed and are upgrading to Jamf Pro 10.16.0 or later, you should upgrade to MySQL 8.0. For instructions, see the Upgrading to MySQL 8.0 article. Jamf Pro 10.15.1 resolves a security vulnerability that affects Jamf Pro 9.4–10.15.0. For more information, see Jamf Pro 10.15.1 FAQ. |
10.13.x |
| It is required that you upgrade to Jamf Pro 10.14.0 before upgrading to Jamf Pro 10.15.1 or later. You must migrate to Java 11 before upgrading to Jamf Pro 10.14.0 or later. See the Migrating to Java 11 article for more information.
|
10.10.1 |
| Upgrading from 10.10.1 or earlier requires an incremental upgrade before upgrading to 10.14.0 or later due to a database index change in 10.14.0 that causes upgrades to fail. |
10.9.x |
|
The following incremental upgrade is required only if you use the Jamf Infrastructure Manager to host the LDAP Proxy: Due to a security enhancement, when upgrading from Jamf Pro 10.9.x or earlier to Jamf Pro 10.11.0 or later, you must first do the following:
After you have met these two requirements, you can upgrade to Jamf Pro 10.11.0 or later. |
10.6.x |
| |
9.97.x or earlier |
|
Additional Information
For information on best practices for evaluating and preparing for an upgrade, see the Preparing to Upgrade Jamf Pro article.