What's Changed

Updated 12 November 2020

The “System Requirements Changes” section has been added.

Changes and Considerations for This Release

Review the following information before upgrading to prepare for changes that may impact your environment.

Incremental Upgrade Required from Jamf Pro 10.13.0 or Earlier to Jamf Pro 10.25.0 or Later

An incremental upgrade is now required for upgrades from 10.13.0 or earlier to Jamf Pro 10.25.0 or later. A "Jamf Pro Startup Suspended" message will be displayed if an upgrade is attempted. For more information, see the Incremental Upgrade Scenarios for Jamf Pro 10.0.0 or Later Knowledge Base article.

System Requirements Changes

See Jamf Pro System Requirements for a complete list of current requirements.

Computer and Mobile Device Management

macOS 11.0.x has been added as Recommended compatibility.

Change History

Depending on the version you are upgrading from, changes made to Jamf Pro since your last upgrade could impact your current environment setup or workflows.

The following table provides a historical list of key changes and additions to Jamf Pro, and the versions in which they were implemented.

Starting
with version...

Change or
Consideration

Description

10.23.0

Added support for Ubuntu Server 20.04 LTS

Ubuntu Server 20.04 LTS was added to the Recommended compatibility level. Ubuntu Server 18.04 LTS was moved to the Minimum Supported compatibility level.

10.22.0

Increased startup time when upgrading

A database schema change will be made to update which tables groups are stored in. This one-time change could cause an increase in startup time, depending on the amount of smart and static groups and the hardware used in your environment. To prevent database issues that could require restoring from a backup, it is important that you do not stop Tomcat or downgrade. If you have questions or experience any issues during this process, contact Jamf Support.

10.21.0

Configurable session-timeout value

User session management was updated to support clustered sessions. As a result, Jamf Pro sessions no longer respect the session-timeout value in web.xml and, by default, will timeout after 1800 seconds (30 minutes). The session-timeout value is now configurable in the session.properties configuration file as a "number of seconds value", for example session.maxInactiveIntervalInSeconds=1800

10.19.0

Increased startup time when upgrading

A database schema change will be made to add a new id column to the extension_attribute_values and mobile_device_extension_attribute_values tables when upgrading to Jamf Pro 10.19.0 or later. Internal testing suggests that this one-time change may take roughly 20 extra minutes per 15 million rows in these two tables combined, depending on the hardware used in your environment. To prevent database issues that could require restoring from a backup, it is important that you do not stop Tomcat or downgrade. If you have questions or experience any issues during this process, contact Jamf Support.

Copyright     Privacy Policy     Terms of Use     Security
© copyright 2002-2020 Jamf. All rights reserved.