Migrating to Another Server

Updated: 15 April 2022
Product: Jamf Pro

This article describes how to migrate Jamf Pro to a new host server. The operating system of the new host server does not need to be the same as the existing host server. For example, an installation of Jamf Pro running on a macOS 10.13 server can be migrated to an Ubuntu 18.04 LTS server.

Keep the following in mind when migrating to another server:
  • To perform a migration, you must be able to point the existing internal and external DNS entries to the new host server. You can do this by changing the DNS entries or using the same IP address on the new host server.
    Warning:

    If you cannot change the DNS entries or use the same IP address, the Jamf Pro URL will be different, requiring you to re-enroll all mobile devices and computers. This could require physically configuring every enrolled device. If you cannot use the DNS strategy described here, contact Jamf Support for assistance.

  • The migration process may vary depending on your source and target environments, including any customizations you may have made. You may need to perform additional steps not covered in this article. In addition, Jamf Pro must be migrated properly to avoid MDM communication issues. If you need assistance, contact Jamf Support.

Migration Methods

Different migration methods are needed depending on whether the software (Jamf Pro, Java, MySQL) installed on the existing host server are the latest versions available.
Method 1: Migrate to the new host server when all software is up to date

  • No software upgrades are necessary.

  • Nothing is changed on the existing host server.

  • Falling back to the existing host server is easy if problems occur.

  • Compatibility issues are unlikely when installing the latest software on a newer operating system.

Method 2: Migrate to the new host server, then upgrade software

  • Nothing is changed on the existing host server.

  • Falling back to the existing host server is easy if problems occur.

  • Compatibility issues may occur when installing older software on a newer operating system.

Method 3: Upgrade software, then migrate to the new host server

  • Changes are made on the existing host server.

  • Falling back may require significant tie and effort, including restoring the entire existing hose server from a full host server backup.

  • Compatibility issues may occur when installing older software on a newer operating system.

  • Older software is installed on the new host server before new software is installed.

General Requirements

  • Jamf Pro Server Tools on the new host server

  • The latest Jamf Pro Installer for the operating system of the new host server

  • (Optional) The ability to change DNS entries so that the current URL pointing to the existing Jamf Pro server can be modified to point to the new Jamf Pro server
    Warning:

    If you cannot change the DNS entries or use the same IP address, the Jamf Pro URL will be different, requiring you to re-enroll all mobile devices and computers. This could require physically configuring every enrolled device. If you cannot use the DNS strategy described here, contact Jamf Support for assistance.

Method 1: Migration only–no upgrades necessary

When all software on the existing server is up to date, you can perform a migration requiring no software upgrades.

  1. Stop Tomcat and back up the existing Jamf Pro database. For instructions, see Backing Up the Database Using Jamf Pro Server Tools.
  2. Copy the database backup from the existing server to the new server or another location which will be accessible from the new server.
  3. (Optional) Copy the JSS folder from the existing server to the new server or another location which will be accessible from the new server. This will make it easier to restore or reference previous configuration files on the new server should the need arise. The paths to the JSS folder are:

    • Linux: /usr/local/jss/

    • Windows: C:\Program Files\JSS\

    • Mac: /Library/JSS/

  4. Update the DNS entry to point to the new server's IP address, or, if you are re-using the IP address of the existing server, shut down the existing server before configuring the new server.
  5. Install the latest MySQL, Java, and Jamf Pro versions and create the database on the new server following the instructions in the Jamf Pro Installation and Configuration Guide for the operating system of the new host server:
  6. Stop Tomcat on the new host server.
  7. Use Jamf Pro Server Tools to restore the backup on the new server. For instructions, see Restoring Database Backups Using Jamf Pro Server Tools.
  8. Start Tomcat on the new host server.
  9. Re-upload or create the SSL certificate in the new Jamf Pro. For more information, see SSL Certificate in the Jamf Pro Documentation.
    Note:

    You may also use the keystore file from the previous host server. See "Additional Information" below for details.

  10. Restart Tomcat.
  11. Verify the Jamf Pro web application can be accessed at the expected Jamf Pro URL.

Method 2: Migrate to new server, then upgrade software

If you have decided to migrate first and then upgrade the software, ensure the older software versions are (temporarily) compatible with the new server.

Requirements

  • The Jamf Pro Installer for the operating system of the new server which matches the version of Jamf Pro installed on the existing server

  • MySQL and Java installers for the operating system of the new server which match the software versions installed on the existing server

  1. Stop Tomcat and back up the existing Jamf Pro database. For instructions, see Backing Up the Database Using Jamf Pro Server Tools.
  2. Copy the database backup from the existing server to the new server or another location which will be accessible from the new server.
  3. (Optional) Copy the JSS folder from the existing server to the new server or another location which will be accessible from the new server. This will make it easier to restore or reference previous configuration files on the new server should the need arise. The paths to the JSS folder are:

    • Linux: /usr/local/jss/

    • Windows: C:\Program Files\JSS\

    • Mac: /Library/JSS/

  4. Update the DNS entry to point to the new server's IP address, or, if you are re-using the IP address of the existing server, shut down the existing server before configuring the new server.
  5. Install the same versions of MySQL, Java, and Jamf Pro on the new server that are installed on the existing server, and create the database on the new server. Follow the instructions in the Jamf Pro Installation and Configuration Guide for the version of Jamf Pro that you are installing:
  6. Stop Tomcat on the new server.
  7. Use Jamf Pro Server Tools to restore the backup on the new server. For instructions, see Restoring Database Backups Using Jamf Pro Server Tools.
    Note:

    You may need to use the legacy Jamf Pro database utility to restore the database depending on the version of Jamf Pro installed on the existing server.

  8. Start Tomcat on the new server.
  9. Re-upload or create the SSL certificate in the new Jamf Pro. For more information, see SSL Certificate in the Jamf Pro Documentation
    Note:

    You may also use the keystore file from the previous host server. See "Additional Information" below for details.

  10. Restart Tomcat.
  11. Verify the Jamf Pro web application can be accessed at the expected Jamf Pro URL.
  12. Upgrade the new host server to the most current MySQL, Java, and Jamf Pro following the instructions in the Incremental Upgrade Scenarios for Jamf Pro 10.0.0 or Later article.
  13. Verify the Jamf Pro web application can be accessed at the expected Jamf Pro URL.

Method 3: Upgrade software, then migrate to the new server

If you have decided to upgrade the software to the latest versions first and then migrate to the new server, ensure the newer software versions are (temporarily) compatible with the existing server.

Requirements

Ensure that you have the latest version of Jamf Pro Installer for the operating system of the existing server.

  1. Stop Tomcat and back up the existing Jamf Pro database. For instructions, see Backing Up the Database Using Jamf Pro Server Tools.
  2. Back up the entire existing server (in addition to the database backup).
    Important:

    You may need to restore the entire existing server from a backup if problems occur during the upgrade process.

  3. Upgrade the existing server to the most current MySQL, Java, and Jamf Pro versions following the instructions in the Incremental Upgrade Scenarios for Jamf Pro 10.0.0 or Later article.
  4. Verify the Jamf Pro web application can be accessed at the expected Jamf Pro URL.
  5. Stop Tomcat and back up the existing Jamf Pro database. For instructions, see Backing Up the Database Using Jamf Pro Server Tools.
  6. Copy the database backup from the existing server to the new server or another location which will be accessible from the new server.
  7. (Optional) Copy the JSS folder from the existing server to the new server or another location which will be accessible from the new server. This will make it easier to restore or reference previous configuration files on the new server should the need arise. The paths to the JSS folder are:

    • Linux: /usr/local/jss/

    • Windows: C:\Program Files\JSS\

    • Mac: /Library/JSS/

  8. Update the DNS entry to point to the new server's IP address, or, if you are re-using the IP address of the existing server, shut down the existing server before configuring the new server.
  9. Install the latest MySQL, Java, and Jamf Pro versions and create the database on the new server following the instructions in the Jamf Pro Installation and Configuration Guide for the operating system of the new server:
  10. Stop Tomcat on the new server.
  11. Use Jamf Pro Server Tools to restore the backup on the new server. For instructions, see Restoring Database Backups Using Jamf Pro Server Tools.
  12. Start Tomcat on the new host server.
  13. Re-upload or create the SSL certificate in the new Jamf Pro. For more information, see SSL Certificate in the Jamf Pro Documentation.
    Note:

    You may also use the keystore file from the previous host server. See "Additional Information" below for details.

  14. Restart Tomcat.
  15. Verify the Jamf Pro web application can be accessed at the expected Jamf Pro URL.

Copying the Certificate Keystore File to the New Server

You can copy the certificate keystore file used for SSL communication from the existing server to the new server.

  1. Open the server.xml file on the existing server. The location of the server.xml file depends on the platform and how you installed Jamf Pro. If you used the Jamf Pro Installer to install Jamf Pro, the server.xml file is in the following locations:

    • Linux: /var/local/jss/tomcat/conf/server.xml

    • Windows: C:\Program Files\JSS\Tomcat\conf\server.xml

    • Mac: /Library/JSS/Tomcat/conf/server.xml

  2. Find the location of the keystore file by locating the following line:
    keystoreFile="/path/to/keystore-file"
  3. Copy or make note of the keystore password from the server.xml file on the existing server. It should look similar to the following: 
    keystorePass="changeit"
  4. Copy the certificate keystore file from the existing server (or backup of the JSS folder) to the new server.
  5. Modify the server.xml file on the new server to point to the keystore file by locating the Connector Port element and adding the following lines:
    keystoreFile="/path/to/keystore-file"
keystorePass="changeit"
  6. Restart Tomcat on the new server.