Skip to main content

Upgrade ArcGIS Enterprise

Upgrading ArcGIS Enterprise requires upgrading each component. The sections of this page provide an overview of the process and links to specific instructions for upgrading each component.

Before proceeding with an upgrade, take a backup of your ArcGIS Enterprise deployment in case you need to recover the content, services, and data that existed prior to the upgrade.

Versions supported for direct upgrade

Recent versions of ArcGIS Enterprise support a direct upgrade to the latest version. Older versions may require multiple upgrades to reach the latest version of ArcGIS Enterprise. If upgrading through multiple versions, carefully review the What's new topic for each version between your starting version and the final version you are upgrading to. The table below indicates the latest version supported for direct upgrade for each version of ArcGIS Enterprise.

See Considerations for choosing a software version for more information about choosing a version that meets your organization's needs.

Note:

See the archived documentation for the release notes of retired versions.

Caution:

Even if a software version supports direct upgrade, you may still need to perform multiple upgrades to access tools for migrating deprecated services, apps, data, or other items. Carefully review the considerations for upgrades and retired features before upgrading any ArcGIS Enterprise components.

Source version

Latest target version supported for direct upgrade

11.0 - 12.0

12.1

10.8 - 10.9.1

11.5

10.7 - 10.7.1

11.3

10.5 - 10.6.1

10.9.1

If your source version supports direct upgrades to your target version, the setup files for the target version of each component will automatically upgrade the component. There is no need to obtain and install each previously released version in sequence or uninstall your current version. For example, if your current version is 11.5, you can directly upgrade to version 12.1.

If your source version does not support direct upgrades to your target version, you will need to perform one or more upgrades to an interim version. For example, if your current version is 10.9.1, you cannot directly upgrade to 12.1. You must perform an upgrade to at least version 11.0, because this is the earliest version that does support direct upgrades to 11.5. The interim version can be no higher than 11.5, because that is the latest version supported for direct upgrades from 10.9.1. From an interim version within this range, you can perform a second upgrade directly to 12.1.

ArcGIS Enterprise upgrade order

The recommended order to upgrade the components in your ArcGIS Enterprise deployment is as follows:

  1. Upgrade Portal for ArcGIS.

  2. Upgrade ArcGIS Web Adaptor (for Portal for ArcGIS).

  3. Upgrade ArcGIS Web Adaptor (for Portal for ArcGIS) for IIS or Java (Windows).

  4. Upgrade the ArcGIS Server site serving as the hosting server.

  5. Upgrade ArcGIS Web Adaptor (for ArcGIS Server).

  6. Upgrade ArcGIS Web Adaptor (for ArcGIS Server) for IIS or Java (Windows).

  7. Upgrade ArcGIS Data Store.

  8. If your ArcGIS Enterprise deployment includes them, upgrade any other federated server sites.

    Federated server sites should match the version of the base ArcGIS Enterprise deployment.

    See the upgrade information for any additional federated ArcGIS Enterprise servers you need to upgrade.

  9. Install the Web Styles setup if you want to use a complete set of 3D symbology from Scene Viewer. For additional information, see Scene Viewer requirements.

Upgrade considerations

To ensure the success of your upgrade, there are a variety of considerations that you should take into account. Carefully review these considerations before proceeding with the upgrade process.

  • Take a backup of ArcGIS Enterprise before upgrading any components. If the upgrade process fails, you may need to use the backup to restore the previous state of your deployment.

  • Review What's new in ArcGIS Enterprise for information about changes in support and functionality.

  • The version of all base ArcGIS Enterprise components must be the same.

  • The system requirements may have changed in later versions. Make sure that you are able to meet the requirements of the version you are upgrading to for each component of ArcGIS Enterprise.

  • Make sure that the required ports are open for each machine involved in the upgrade.

  • Supported geodatabase versions may be different in later versions. You may need to upgrade your geodatabase as part of your ArcGIS Enterprise upgrade.

  • You don't need to upgrade ArcGIS Pro at the same time as ArcGIS Enterprise. However, it is recommended that you keep ArcGIS Pro and ArcGIS Enterprise at companion versions. See Companion ArcGIS Pro and ArcGIS Enterprise versions for more information.

  • If your organization uses a utility network, ensure that the versions of ArcGIS Enterprise, ArcGIS Pro, and utility network are compatible. See Utility network compatibility for more information.

  • During an upgrade, if more space is needed for installed resources than is available in the default /tmp directory, you can specify an alternate setup temp location by setting the IATEMPDIR environment variable to a larger directory.

  • During upgrades, if the system temp directory does not have enough space to backup your files and folders, you can either run the export TMPDIR=/path/to/new/tmp command to set a larger alternative temp directory, or expand the size of the system temp directory.

  • It is recommended that you confirm how ArcGIS Enterprise was originally installed and use the same approach for the upgrade. For example, if your deployment was created using ArcGIS Enterprise Builder or an ArcGIS Enterprise Cloud Builder application (AWS or Microsoft Azure), use the corresponding builder to perform the upgrade if possible.

  • You can use an identical, isolated standby environment to avoid downtime during an upgrade. As an administrator, you can upgrade your standby environment while your production environment remains accessible. To learn more about this upgrade strategy and about how to upgrade your highly available or replicated environment, see Upgrade highly available and replicated environments.

  • After the upgrade is complete, it is recommended that you run the portalScan.py and serverScan.py scripts to check for security best practices with your upgraded organization.

Retired features