Incremental Upgrade Scenarios for Jamf Pro 10.0.0 or Later

10.40.x
10.39.x
10.38.x
10.37.x
10.36.x
10.35.x
10.34.x
10.33.x
10.32.x
10.31.x
10.30.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.

10.29.x

1. Upgrade to 10.30.x.

2. Upgrade to 10.31.x or later.

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
10.27.x
10.26.x
10.25.x

1. Upgrade to 10.29.x.

2. Upgrade to 10.30.x or later.

3. Upgrade to 10.31.x or later.

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 encryption_key database table. This introduced an error in the JAMFSoftwareServer.log file during Jamf Pro's initial startup after upgrading from an earlier version. Jamf Pro 10.26.0–10.29.0 will run fine despite the log error, and no incremental upgrade is required. This error was resolved in Jamf Pro 10.30.0.

10.24.x
10.23.x
10.22.x
10.21.x
10.20.x
10.19.x
10.18.x
10.17.x
10.16.x
10.15.x
10.14.x

1. Upgrade to 10.25.0.

2. Upgrade to 10.29.x.

3. Upgrade to 10.30.x or later.

4. Upgrade to 10.31.x or later.

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
10.12.x
10.11.x

1. Migrate to Java 11.

2. Upgrade to 10.14.0.

3. Upgrade to 10.15.1 or later.

4. Upgrade to 10.25.0.

5. Upgrade to 10.29.x.

6. Upgrade to 10.30.x or later.

7. Upgrade to 10.31.x or later.

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.

Important notice for upgrading from Jamf Pro 10.13.0 or earlier to 10.14.0 or later:

Java 11 is not compatible with Jamf Pro 10.13.0 or earlier. Please wait until you are ready to upgrade to Jamf Pro 10.14.0 or later before migrating to Java 11 on your Jamf Pro server.

10.10.1
10.10.0

1. Upgrade to 10.13.0.

2. Migrate to Java 11.

3. Upgrade to 10.14.0.

4. Upgrade to 10.15.1 or later.

5. Upgrade to 10.25.0.

6. Upgrade to 10.29.x.

7. Upgrade to 10.30.x or later.

8. Upgrade to 10.31.x or later.

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
10.8.x
10.7.x

1. If your database is using the MyISAM storage engine, convert it to InnoDB.

2. If using Jamf Infrastructure Manager to host the LDAP Proxy, upgrade to 10.10.x. If not, proceed to step 3.

3. Upgrade to 10.13.0.

4. Migrate to Java 11.

5. Upgrade to 10.14.0.

6. Upgrade to 10.15.1 or later.

7. Upgrade to 10.25.0.

8. Upgrade to 10.29.x.

9. Upgrade to 10.30.x or later.

10. Upgrade to 10.31.x or later.

Important notice for upgrading from Jamf Pro 10.9.x or earlier to 10.10.0 or later:

The InnoDB storage engine for MySQL is required starting with Jamf Pro 10.10.0. If you have not converted your MySQL database tables from MyISAM to InnoDB, see the Converting the MySQL Database Storage Engine from MyISAM to InnoDB Using the Jamf Pro Server Tools Command-Line Interface article for instructions.

The following incremental upgrade is required only if you use the Jamf Infrastructure Manager to host the LDAP Proxy:

After you have met these two requirements, you can upgrade to Jamf Pro 10.11.0 or later.

10.6.x
10.5.x
10.4.x
10.3.x
10.2.x
10.1.x
10.0.x
9.101.x
9.100.x
9.99.x
9.98.x

1. Upgrade to 10.8.0.

2. Convert your database to InnoDB.

3. If using Jamf Infrastructure Manager to host the LDAP Proxy, upgrade to 10.10.x. If not, proceed to step 4.

4. Upgrade to 10.13.0.

5. Migrate to Java 11.

6. Upgrade to 10.14.0.

7. Upgrade to 10.15.1 or later.

8. Upgrade to 10.25.0.

9. Upgrade to 10.29.x.

10. Upgrade to 10.30.x or later.

11. Upgrade to 10.31.x or later.

9.97.x or earlier

1. Upgrade to 10.0.0.

2. Upgrade to 10.8.0.

3. Convert your database to InnoDB.

4. If using Jamf Infrastructure Manager to host the LDAP Proxy, upgrade to 10.10.x. If not, proceed to step 5.

5. Upgrade to 10.13.0.

6. Migrate to Java 11.

7. Upgrade to 10.14.0.

8. Upgrade to 10.15.1 or later.

9. Upgrade to 10.25.0.

10. Upgrade to 10.29.x.

11. Upgrade to 10.30.x or later.

12. Upgrade to 10.31.x or later.