Important Notices

Notice History by Release

Starting with version...Change or ConsiderationDescription


Memcached change required for clustered environments

A Memcached configuration error prevents Tomcat from starting in clustered environments when upgrading to Jamf Pro 10.33.0 or later. To start Tomcat and complete the Jamf Pro upgrade, you must navigate to path/to/jss/tomcat/webapps/ROOT/WEB-INF/classes/dal/ and add to the file.
10.33.0Increased startup time when upgradingDuplicated rows stored in the computer inventory applications database table will be removed during the initial server startup when upgrading to Jamf Pro 10.33.0. This one-time extended startup could take anywhere from a few additional minutes to several additional hours, depending on the size of your applications table and the hardware used in your environment. It is important that you do not stop the startup process. If you have questions or experience any issues during startup, contact Jamf Support.


Incremental upgrade required

Direct upgrades from Jamf Pro 10.28.x or earlier to Jamf Pro 10.30.0 or later may fail. An incremental upgrade to 10.29.x is now required for upgrades from 10.28.0 or earlier to Jamf Pro 10.30.0 or later.


Rename Apple TV devices

If your environment was impacted by [PI-008988], changes in Jamf Pro 10.30.0 may require the Apple TV devices in your environment to be renamed after you upgrade to 10.30.0 or later.

You can manually edit the device's inventory information and enforce the device name. For more information see Mobile Device Inventory Information in the Jamf Pro Administrator's Guide.

Alternatively, you can re-enroll devices with Jamf Pro using a PreStage enrollment that enforces device names. For more information, see Mobile Device PreStage Enrollments in the Jamf Pro Administrator's Guide.


Clear failed InstallApplicationMDM commands

If your environment was impacted by [PI-009279], you must clear all failed InstallApplication MDM commands that display the INCOMPATIBILITY_REASON_MINIMUM_OS_VERSION error. You can do this using a mass action. For more information, see Remote Commands for Computers in the Jamf Pro Administrator's Guide.


TLS Changes for Jamf Cloud and Patch Management

Connections over TLS 1.1 have been disabled for environments hosted in Jamf Cloud. As a result, all inbound connections to Jamf Pro negotiate via newer versions of TLS to prevent any TLS 1.1 communication.


MySQL 5.7.8 or later required

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


Incremental upgrade required

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.