Skip to main content

Review postupgrade considerations

Following an upgrade, consider the following points to ensure that your organization runs smoothly:

  • If your organization uses a persistent volume to store backups, a new store must be registered following an upgrade due to changes in the underlying backup store components. Once you have validated the upgrade, registered a new backup store, and updated existing backup schedules to use the new store, you can unregister the old backup store and delete the persistent volume to recover resources in the cluster. If needed, the old backup store can be used to restore your organization to the earlier version. If you choose not to delete the old backup store, ensure that all future backups use the newly registered store.

  • If your organization is not already configured with a performance profile, upgrading will not apply one. Instead, it is recommended that you scale your services to at least match the requests and limits set by a performance profile.

  • 11.x extensions are not compatible with ArcGIS Enterprise 12.x on Kubernetes. When upgrading to version 12.0 or later from a previous version, services with 11.x extensions enabled will remain in a stopped state. The upgrade completes with a success_with_warnings report.

    Note:

    If a service has more than one extension enabled, the service will remain stopped until all extensions are updated.

  • If a member's user type is no longer available after upgrading, you must assign them a different user type. For a list of available user types, see User types.

  • After upgrading, some user types may include additional apps that were previously available only as add-on licenses. If an app is included with a member's assigned user type, you don't need to assign the member an add-on license for that app. See An introduction to licensing apps to learn more about apps and the user types that include them.

  • When one or more add-on licenses assigned to members are included with their user types after upgrading, a notice appears on the Overview tab of the organization page stating that some members have licenses assigned twice. You can unassign duplicate add-on licenses from all applicable members to free up those licenses.

  • After upgrading, you must complete a package update to deploy ArcGIS Living Atlas of the World content to ensure that your organization members have access to the latest content.

  • ArcGIS License Manager is no longer required to enable named user licensing for ArcGIS Pro, ArcGIS Pro extensions, and ArcGIS Drone2Map.

  • To use the location sharing capability, increase the volume size of the spatiotemporal and index store a minimum of 150 GiB.

  • For organizations with Notebook Services, notebook and notebook web tool items will not automatically update to the latest notebook runtime during an upgrade. After you have upgraded, administrators and authors must update their notebook and notebook web tool items to the latest runtime. See Specify the runtime of a notebook for more information.

    Note:

    After updating a notebook, overwrite associated web tools to ensure that the runtime used by the notebook web tools is also updated.

  • If you use a configure.properties file to automate the configuration of a new organization, upgrading may change the properties required for that file. The properties-file-validator.sh tool checks for deleted or renamed properties. The properties-file-converter.sh tool converts an old properties file to a new properties file. These tools are located in the /arcgis-enterprise/<version>/setup/tools/properties-tools directory.

  • If you configured routing services by publishing routing services using your network dataset, it is recommended that you reconfigure your routing services after an upgrade to use the latest capabilities.

  • To republish routing services using your network dataset, complete the following steps:

  1. Sign in as a default administrator or custom role with the appropriate privileges to manage organization settings.

  2. At the top of the site, click Organization, and click Settings.

  3. Click Utility services.

  4. Click Directions and Routing.

  5. Click Update routing services and choose A network dataset that I'd like to publish.

  6. Follow the steps in Configure routing services to configure routing services using your network dataset.

If you encounter issues following an upgrade, review Troubleshoot updates and upgrades.