Upgrading Jamf Pro Using the Installer on Windows

  1. Prepare to upgrade:
    1. Review the following articles:
    2. Ensure that you have backed up the current database.

      For more information, see Backing Up the Database.

    3. On Windows, ensure the following:
      • You are logged in as a local administrator, not as a domain administrator.


        Full local administrator privileges are required to install Jamf Pro on Windows Server. If you are unable to install Jamf Pro, Group Policy Object restrictions may be the cause. Check the GPO settings or contact someone in your organization who can ensure that GPO restrictions allow you full administrator privileges.

      • Apache Tomcat is stopped. For instructions, see the Starting and Stopping Tomcat article.

    4. If you are upgrading from Jamf Pro 10.15.0 or earlier and currently have MySQL 5.7.7 or earlier installed, follow the instructions in the Upgrading to MySQL 8.0 article to upgrade to MySQL 8.0.
    5. If you are upgrading from Jamf Pro 10.13.0 or earlier, follow the instructions in the Migrating to Java 11 article to migrate from Java 8 to Java 11.
  2. Run the Jamf Pro Installer:

    If an upgrade fails, do not click OK. Contact Jamf Support immediately.

    1. Copy the most current version of the Jamf Pro Installer for Windows (Jamf Pro Installer.msi) to the server.
    2. To obtain the Jamf Pro Installer for Windows, log in to Jamf Account and navigate to the Products page for Jamf Pro
    3. Double-click the installer and follow the onscreen instructions to complete the upgrade.

      If you customized the log4j.properties file in Jamf Pro 10.30.x or earlier, you must edit the log4j2.xml file and reapply your customizations. The log4j.properties file is backed up to the following location: C:\Program Files\JSS\Backups


      If you are upgrading to Jamf Pro 10.6.0 or later, you must make a one-time change to the MySQL configuration to avoid performance issues. See "Step 3. Configuring MySQL" in the Creating the Jamf Pro Database Using the Jamf Pro Server Tools Command-Line Interface article for instructions.

  3. Verify server settings:
    1. Verify that the Connector settings for port 8443 in the server.xml file match the settings listed in the Configuring Supported Ciphers for Tomcat HTTPS Connections article, and modify them if needed.
    2. If you modified the server.xml file, restart Tomcat.
  4. (Optional) Disable TLS 1.0 and 1.1 in Java 11

    If you are using the TLS 1.0 or 1.1 protocols in Java 11 for any existing workflows, it is recommended that you disable them since they are deprecated. For instructions, see the Disabling TLS 1.0 and 1.1 in Java 11 article.

  5. To complete the upgrade, log in to Jamf Pro and verify devices are checking in as expected.