![]() This release includes functionality that strengthen Jamf’s integrations and continues to support organizations in their movement from on-premises Active Directory to a more modern and secure infrastructure in the cloud. Additionally, this release includes on a stronger integration with Jamf Protect so admins can stay in Jamf Pro to do other Jamf things such as deploy a Jamf Protect package and plans. We’ve listened to feedback and are confident that 10.27 responds to those workflow improvements requests. ![]() If you have questions or experience any issues during this process, contact Jamf Support.Jamf Pro 10.27 is focused on improving day-to-day operations for admins, making Jamf easier to work with and device management simpler. To prevent database issues that could require restoring from a backup, it is important that you do not stop Tomcat or downgrade. 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. Ubuntu Server 18.04 LTS was moved to the Minimum Supported compatibility level.Ī database schema change will be made to update which tables groups are stored in. ![]() Ubuntu Server 20.04 LTS was added to the Recommended compatibility level. If you have questions or experience any issues during this process, contact Jamf Support.Īdded support for Ubuntu Server 20.04 LTS 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. Increased startup time: Duplicated columns stored in the mobile_device_installed_applications database table will be moved during the initial server startup when upgrading. 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. 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. 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. The recommended InnoDB buffer pool size is around 50 to 70% of the total system memory for dedicated database servers. 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. For more information, see the Incremental Upgrade Scenarios for Jamf Pro 10.0.0 or Later Knowledge Base article. ![]() 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.Īn incremental upgrade is required for upgrades from 10.13.0 or earlier to Jamf Pro 10.25.0 or later. For instructions, see the Upgrading to MySQL 8.0 Knowledge Base article.Ī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. 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). Jamf Pro 10.27.0 includes a database performance enhancement which requires MySQL 5.7.8 or later.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |