Important Notices

Apache Log File Upgrades in the Jamf Pro Server

The Jamf Pro server includes a logging framework upgrade. The Apache log file included in the Jamf Pro installers is automatically upgraded from to log4j2.xml when you upgrade to Jamf Pro 10.31.0 or later.

The file will be backed up to the following locations:
  • Linux: /usr/local/jss/backups

  • Windows: C:\Program Files\JSS\Backups

  • macOS: /Library/JSS/Backups


If you customized the file, you must edit the log4j2.xml file and reapply your customizations after you upgrade to Jamf Pro 10.31.0.

In addition, if you have a customized process for manually installing Jamf Pro, you must modify your process accordingly. For example, If your Jamf Pro server is hosted on Windows and you manually upgrade Jamf Pro, this change impacts the upgrade process.

For more information about Apache Log4j 2, see the following Apache documentation: Apache Log4j 2.

In-House Apps Reporting Incorrect Version in Jamf Pro Server and Self Service

Starting with Jamf Pro 10.31.0, your environment may be impacted by [PI-009768]. Previously, In-House apps read CFBundleVersion to fill in version data, which resulted in Jamf Pro pulling in an internal version that could represent a released version or an unreleased version of the In-House apps. In-House apps now read CFBundleShortVersionString to fill in version data. Jamf Pro will now automatically pull in the public released version. If you see an undesired version in Self Service, you will need to re-upload your apps or manually update your version field for consistency across In-House apps usage.

Notice History by Release

Starting with version...Change or ConsiderationDescription


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.