Skip to main content
Jamf Nation, hosted by Jamf, is a knowledgeable community of Apple-focused admins and Jamf users. Join us in person at the ninth annual Jamf Nation User Conference (JNUC) this November for three days of learning, laughter and IT love.

Incremental Upgrade Scenarios for Jamf Pro 10.0.0 or Later

Overview

When upgrading to the latest release of Jamf Pro, incremental upgrades are required in the following scenarios.

Example: If you are currently running 10.8.0 and want to upgrade to 10.14.0, you must upgrade to 10.10.x and then to 10.13.0 before upgrading to 10.14.0.

Upgrading from version Incremental upgrades required Notes
10.10.1 or earlier 10.13.0
10.9.x or earlier 10.10.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:
1. Perform an incremental upgrade to Jamf Pro 10.10.x.
2. Re-enroll your Jamf Infrastructure Manager if it hosts the LDAP proxy.
After you have met these two requirements, you can upgrade to Jamf Pro 10.11.0 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 Knowledge Base article for instructions.

10.6.2 or earlier 10.8.0
9.97.x or earlier 10.0.0 and 10.8.0

Additional Information

For information on best practices for evaluating and preparing for an upgrade, see the Preparing to Upgrade Jamf Pro Knowledge Base article.

Like Comment
Order by:
SOLVED Posted: by dpratl

Why is this not mentioned anymore?

Is this only needed when I use the Jamf Infrastructure Manager to host the LDAP Proxy?
And if it is connected with the Jamf Infrastructure Manager, why do I need a change of the database tables for it?
Sorry if this question is silly.

Thanks
BR
Daniel

Like
SOLVED Posted: by srobert

Hi Daniel,
not a silly question I too had the same question. Although we don't use LDAP Proxy, the conversion is needed. You are absolutely correct they should mention database conversion to InnoDB is required for 10.11.1. we are also in the process of upgrading from 10.9 to 10.11.1 in our test environment and confirmed with our Jamf Buddy that the conversion is needed b4.

hope that helps
-Shanaz

Like
SOLVED Posted: by dpratl

Hi @srobert,

Thank you very much for the information.

Happy Easter

BR
Daniel

Like
SOLVED Posted: by TamiK

This article has been updated with a notice that the InnoDB storage engine for MySQL is required starting with Jamf Pro 10.10.0.

Like
SOLVED Posted: by grahamrpugh

Since the Tomcat requirements have changed and we can no longer use the version RHEL provides in RHEL 7, we should get some instructions on how to manually upgrade from Tomcat 7 (RHEL latest approved version) directly to Tomcat 8.5.4x. (we cannot use the Linux installer as we are a multi-instance shop).

For example:

  • What do we need to change in server.xml?
  • Any other files need changing?
  • Can we do it at the same time as upgrading, e.g. shut down tomcat, upgrade tomcat, put the new ROOT.war in place in each instance and restart tomcat?
Like
SOLVED Posted: by TamiK

This article has been updated with a requirement for users upgrading from Jamf Pro 10.10.1 or earlier to perform an incremental upgrade to 10.13.0 before upgrading to Jamf Pro 10.14.0 or later.

Like
SOLVED Posted: by TamiK

This article has been updated to add an example of a common upgrade scenario.

Like