- #Jamf pro 10.27 release notes full version#
- #Jamf pro 10.27 release notes Patch#
- #Jamf pro 10.27 release notes upgrade#
- #Jamf pro 10.27 release notes tv#
#Jamf pro 10.27 release notes Patch#
Over the coming weeks and months, you can expect to see even more titles added to the Jamf Pro patch feed. We will provide guidance alongside a future Jamf Pro release for any necessary migration steps that may occur to help all customers move off of the deprecated versions of these titles prior to any end of support.
We recommend that any customer adding a new title select the non-deprecated variants to minimize any future migration steps.
#Jamf pro 10.27 release notes full version#
This deprecation label may cause an alarming round of email alerts for customers subscribing to title changes - don't panic! All deprecated titles will continue to receive full version updates for the foreseeable future in parallel with the newly released titles, so no existing patch workflows should be impacted. This is especially valuable for customers who aren’t always adopting the very latest version of an app or series.Īs was noted in the Jamf Pro 10.27 release notes, some of the existing titles have been marked as deprecated following this first round of upgrades.
#Jamf pro 10.27 release notes upgrade#
A "Jamf Pro Startup Suspended" message will be displayed if an upgrade is attempted.Today, we launched enhanced versions of many of our existing patch management titles with more granular breakdowns and definitions to make app reporting and patch workflows more flexible. 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).Īn 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. Jamf Pro 10.27.0 includes a database performance enhancement which requires MySQL 5.7.8 or later. As a result, all inbound connections to Jamf Pro negotiate via newer versions of TLS to prevent any TLS 1.1 communication. TLS Changes for Jamf Cloud and Patch ManagementĬonnections over TLS 1.1 have been disabled for environments hosted in Jamf Cloud. For more information, see Remote Commands for Computers in the Jamf Pro Administrator's Guide. If your environment was impacted by, you must clear all failed InstallApplication MDM commands that display the INCOMPATIBILITY_REASON_MINIMUM_OS_VERSION error. For more information, see Mobile Device PreStage Enrollments in the Jamf Pro Administrator's Guide.Ĭlear failed InstallApplicationMDM commands For more information see Mobile Device Inventory Information in the Jamf Pro Administrator's Guide.Īlternatively, you can re-enroll devices with Jamf Pro using a PreStage enrollment that enforces device names. You can manually edit the device's inventory information and enforce the device name.
#Jamf pro 10.27 release notes tv#
If your environment was impacted by, 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.
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. If you have questions or experience any issues during startup, contact Jamf Support.ĭirect upgrades from Jamf Pro 10.28.x or earlier to Jamf Pro 10.30.0 or later may fail. It is important that you do not stop the startup process. 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. To start Tomcat and complete the Jamf Pro upgrade, you must navigate to path/to/jss/tomcat/webapps/ROOT/WEB-INF/classes/dal/memcached.properties and add =86400 to the memcached.properties file.ĭuplicated 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. Memcached change required for clustered environmentsĪ Memcached configuration error prevents Tomcat from starting in clustered environments when upgrading to Jamf Pro 10.33.0 or later.
0 kommentar(er)
