What's Changed

Changes and Considerations for This Release

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

MySQL 5.7.8 or Later Required for Jamf Pro 10.27.0 or Later

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 Knowledge Base article.

Incremental Upgrade Required from Jamf Pro 10.24.0 or Earlier to Jamf Pro 10.27.0 or Later

An incremental upgrade to Jamf Pro 10.25.0 is now required for upgrades from 10.24.x or earlier to Jamf Pro 10.27.0 or later due to a database change in Jamf Pro 10.26.0 that causes upgrades to fail. 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.

Upcoming TLS Changes for Jamf Cloud and Patch Management

In early 2021, connections over TLS 1.1 will be disabled for environments hosted in Jamf Cloud. As a result, all inbound connections to Jamf Pro will negotiate via newer versions of TLS to prevent any TLS 1.1 communication. To ensure continued connectivity to Jamf Cloud services, please verify the following:

Jamf Cloud

Ensure the following sub-domain is able to communicate with your network:

*.services.jamfcloud.com

If you use the Jamf Cloud Distribution Service (JCDS) as a cloud distribution point, your firewall may need to be updated to allow for connection to the updated addresses based on your hosted data region.

For more information about connections to Jamf Cloud, see the Permitting Inbound/Outbound Traffic with Jamf Cloud Knowledge Base article.

Patch Management

If you are using patch definitions from Jamf for patch management in Jamf Pro, your firewall may need to be adjusted to allow communication with the addresses for patch definitions:

  • patch.services.jamfcloud.com

  • jamf-patch.jamfcloud.com

For more information about Jamf Pro server connections for patch management, see the Network Ports Used by Jamf Pro Knowledge Base article.

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.25.0

Incremental upgrade required

An incremental upgrade is 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.

10.25.0

Increased startup time when upgrading

Prerequisite: To ensure the increased startup time change described below does not cause issues in your environment, first verify that the innodb_buffer_pool_size is set to the recommended value. The recommended InnoDB buffer pool size is around 50 to 70% of the total system memory for dedicated database servers. However, if the Jamf Pro database server is also hosting Tomcat, calculate this value to be 50 to 70% of the remaining system memory, after accounting for how much is already allocated to the Tomcat service, the operating system, and any other running services on the server. For example, a server running both Tomcat and MySQL with 16 GB of RAM total has 8 GB allocated to the Tomcat service and 4 GB has been set aside for the system and other processes. 4 GB remains from the original total, so the calculation would be to allocate anywhere from 2 to 3 GB to the InnoDB buffer pool size setting.

Increased startup time: Duplicated columns stored in the mobile_device_installed_applications database table will be moved during the initial server startup when upgrading. This one-time extended startup could take anywhere from a few additional minutes to several additional hours, depending on the size of your mobile_device_installed_applications table 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.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

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