You can use ArcGIS Enterprise Cloud Builder for Microsoft Azure 12.0 to upgrade Version 2 (V2) deployments created using ArcGIS Enterprise Cloud Builder for Microsoft Azure 11.0 or later.
To upgrade 10.8.x or 10.9.x Version 2 (V2) deployments, you can upgrade using an interim version of Cloud Builder, test the deployment, and then use Cloud Builder 12.0 to upgrade to the current release. Which interim version you use will depend on the components and functionality present in your deployment. Read the information in Before you upgrade to determine which interim version (or versions) you need. Use the Other versions menu in the help to access instructions for the interim version you choose.
Version 1 (V1) deployments, 10.7.1 and earlier deployments, and registered enterprise geodatabases must be upgraded similar to how you upgrade on-premises deployments.
Note:
You must connect using the same Azure account when you upgrade as you did when you created the deployment.
You can upgrade to 12.0 directly from 11.0 or later, but only if your deployment does not include components or items that are no longer supported.
Before you upgrade
Create backups of all ArcGIS Enterprise components before you upgrade.
Upgrading ArcGIS Enterprise software can be a resource-intensive process that requires additional virtual machine resources. To ensure that there are enough resources to upgrade, it is recommended that you temporarily scale up the memory and processing resources on the Azure virtual machine instances before you begin the upgrade process.
Read Upgrade ArcGIS Enterprise and read the following deployment-specific considerations before you upgrade.
Version 1 (V1) deployments
For deployments earlier than 10.6 or Version 1 (V1) deployments, no management options are available from ArcGIS Enterprise Cloud Builder for Microsoft Azure 12.0. To upgrade those deployments, you must connect to the machines in Azure and upgrade the software in the same way as on-premises deployments, which will include multiple upgrades because you cannot upgrade directly from 10.9.1 or earlier deployments.
After you upgrade, do not use ArcGIS Enterprise Cloud Builder for Microsoft Azure for postdeployment operations including registering databases with ArcGIS Server, installing CA-issued certificates, and connecting to or deleting these upgraded deployments.
ArcGIS Data Store
Be aware of the following changes related to ArcGIS Data Store.
Tile cache data store
The tile cache data store is no longer supported. If your deployment includes hosted scene layers with caches stored in the tile cache data store, you must add an Azure Blob Storage container as the object store and migrate hosted scene layer caches from the tile cache data store to the object store before you upgrade to 12.0.
The tools to migrate hosted scene layer caches are present in ArcGIS Enterprise 11.4 and 11.5. If your deployment is at an earlier release, you must upgrade to 11.4 or 11.5 to migrate caches. Follow the instructions in the 11.4 or 11.5 help to upgrade and to migrate hosted scene layer caches to the object store.
After you migrate hosted scene layer caches to the object store and test them to ensure they function as expected, use Cloud Builder 12.0 to upgrade to the current release.
Cloud Builder 12.0 will remove the tile cache data store from the deployment when you upgrade.
Object store
If you are upgrading from 11.0, 11.1, 11.2, or 11.3 and the deployment includes an ArcGIS Data Store object store, it will be removed when you use Cloud Builder to upgrade. After the upgrade is complete, add an Azure Blob Storage container as the object store.
The ArcGIS Data Store object store included with deployments created with Cloud Builder 11.3 and earlier only stored ephemeral data (feature query caches). The next time the feature services are queried after the deployment is upgraded, caches will be built in the new object store.
Graph store
Primary-standby mode for the graph store is not supported starting with 11.5. Upgrading an 11.2, 11.3, or 11.4 graph store running in primary-standby mode places the graph store in single instance mode, and the standby machine is removed. If you require a highly available graph store, you can add two machines to the graph store after you upgrade.
ArcGIS GeoEvent Server
Before you can upgrade an ArcGIS GeoEvent Server 10.9 or earlier Version 2 (V2) site that contains multiple machines, you must remove all but one machine from the site and upgrade to an interim version. Remove the machines before you complete the export referred to below.
Before you upgrade ArcGIS GeoEvent Server sites, export the ArcGIS GeoEvent Server site's configuration. After you complete the upgrade process, you must import the ArcGIS GeoEvent Server site's configuration using the file you exported before you started the upgrade process.
ArcGIS GeoAnalytics Server
ArcGIS GeoAnalytics Server is no longer supported. If you are upgrading from 11.0, 11.1, or 11.2 and the deployment includes an ArcGIS GeoAnalytics Server site, do the following before you upgrade:
- Unregister all big data file shares from the site. If these were added in the portal, remove them in the portal. If they were added in ArcGIS Server Manager, remove them using ArcGIS Server Manager.
- Remove the site from the GeoAnalytics Server role in the portal.
- Unfederate the ArcGIS GeoAnalytics Server site.
Retired apps
Apps created using ArcGIS Web AppBuilder or ArcGIS Configurable Apps are no longer supported. Replace these apps before you upgrade.
See the ArcGIS Blog article Dive into ArcGIS Enterprise 11.5 before you delve into 12 for more information.
Azure Files
Deployments that use Azure Files for the configuration store and portal content directory were deprecated at 11.4. In an upcoming release, upgrades of this type of deployment will no longer be supported. It is recommended that you upgrade the deployment to the current release and then migrate these types of deployments using the wegbisdr utility that is installed with Portal for ArcGIS.
Upgrade 11.0, 11.1, 11.2, 11.3, 11.4, or 11.5 deployments using Cloud Builder
A new version of ArcGIS Enterprise Cloud Builder for Microsoft Azure is available with each ArcGIS release.
If you created an 11.0, 11.1, 11.2, 11.3, 11.4, or 11.5 deployment using ArcGIS Enterprise Cloud Builder for Microsoft Azure, you can install the latest version of ArcGIS Enterprise Cloud Builder for Microsoft Azure and use it to upgrade the deployment to the current release.
To upgrade a deployment you launched with ArcGIS Enterprise Cloud Builder for Microsoft Azure, complete the following steps:
- Download and install the latest version of ArcGIS Enterprise Cloud Builder for Microsoft Azure.
- Start ArcGIS Enterprise Cloud Builder for Microsoft Azure.
- Sign in to Microsoft Azure.
If you want to use the Microsoft Azure Government cloud and have an Azure Government subscription, check U.S. Government Cloud.
Note:
The account you use to connect must be assigned the following roles at a minimum:
- The Azure Reader role at the subscription scope level
- The Azure Contributor role at the resource group scope level if you will use resource groups that you create outside Cloud Builder
- Choose the Azure subscription that contains the ArcGIS Server site or ArcGIS Enterprise deployment you want to upgrade and click next.
- Show V2 Sites and, in the Deployments list, open the details for the deployment you want to upgrade.
- Click the
Upgrade Deployment button
.When you start the upgrade process from any part of an ArcGIS Enterprise deployment, Cloud Builder upgrades the entire deployment. For example, if you clicked the Upgrade Deployment button for an ArcGIS Server site that is federated with the ArcGIS Enterprise portal, ArcGIS Enterprise is upgraded in its entirety, not just the ArcGIS Server site.
- Provide the username and password of the machine administrator.
Use the same account you used when you created the instances in your deployment.
- If your machines are part of an existing Windows domain in your Azure environment, click Domain Join Options.
- On the Domain Join Options dialog box, ensure that the Join Existing Windows Domain? option is checked.
- Provide the name of the Azure Active Directory domain.
- Provide the username and password for the domain administrator.
- Click Apply.
- If you included Azure monitoring when you created the deployment using Cloud Builder, you can disable the Log Analytics agent on all the machines in the deployment.
Microsoft retired the Log Analytics agent in 2024, so it is recommended that you remove this retired agent.
- To proceed, you must check the disclaimer check boxes to acknowledge the following:
- That you created a backup of the deployment before you started the upgrade process.
- That you migrated hosted scene layer caches to the object store before you started the upgrade process. Any hosted scene layers that still have caches in the tile cache data store will not function after you upgrade.
- If you are upgrading a single-tier deployment that includes a spatiotemporal big data store, you must check the disclaimer box to acknowledge that the machines have at least 32 GB of memory.
Ensure that all of the machines running the spatiotemporal big data store have at least 32 GB of memory.
- Click Next to proceed to the License and Credentials settings.
- Under Site License, provide the current license files.
- If you are upgrading an ArcGIS Enterprise portal, browse to the Portal for ArcGIS license file for Portal License and choose the user type for the license. The user type affects which apps portal members can use.
- If you are upgrading an ArcGIS Enterprise portal (which always includes a hosting server) or a stand-alone ArcGIS GIS Server site, browse to the ArcGIS GIS Server license for Server License.
- Type the username and password for Site Administrator.
You created this account when you created the deployment. Use the same username and password.
- Type the username and password for ArcGIS Service Account.
You created this account when you created the deployment. Use the same username and password.
- Click Next to proceed to the Deployment Options settings.
- Choose or create a storage account to contain the artifacts that Cloud Builder creates during the upgrade process. To create a storage account, follow these steps:
- Type a unique name for the storage account. Click Check Availability to confirm that the storage account name is unique.
- Choose the Azure region where the storage will reside.
- Choose an existing resource group or create one.
- Choose the type of redundancy for the storage account: Geo-Redundant, Locally Redundant, or Read-Access Geo-Redundant.
See Azure Storage redundancy in the Microsoft Azure documentation for a description of each option.
- Once the storage account is created, click Close.
- To optionally upload a Microsoft PowerShell script that will run on all machines in the deployment after they are upgraded, provide the script and related information in the Post Deployment Script section as described below.
- Script file path—Provide the location and name of the script file. You can paste the path into the text box, or click the options button
to browse to the file's location. - Timeout (in minutes)—Define the amount of time, in minutes, to allow the script to run. If the script does not complete in the time specified, Cloud Builder will end the process to prevent a hung script from blocking the upgrade process from completing. The minimum timeout is five minutes; the maximum is 300 minutes.
- Script parameters—If the script requires parameters to run, provide those here. Syntax for the parameters is -<parameter> <value>.
- Run script as ArcGIS service account—By default, the script will run using the ArcGIS service account that you specified on the Licenses and Credentials page when you created the deployment or added a federated server. It is recommended that you use this account because it does not have elevated privileges. If you uncheck this option, the script runs using the local system account on each machine.
Tip:
Failure of the postdeployment script does not affect the upgrade process. If upgrade succeeds but the postdeployment script fails, you'll receive a success message with warnings.
- Script file path—Provide the location and name of the script file. You can paste the path into the text box, or click the options button
- Click Next.
- If the ArcGIS Enterprise portal includes federated servers, provide the username and password for the account that runs the ArcGIS Server service for each federated server in the ArcGIS Service Account section.
The licenses you provide must be for the correct role for each federated server.
- If the ArcGIS Enterprise portal includes a federated multiple-machine ArcGIS Notebook Server site, provide the username and password for the Notebook Server site administrator.
- Click Next.
- Review the settings in the Summary pane. If anything needs to be changed, click Back to go to the page where you need to change the information.
Tip:
Click Save summary to save your upgrade information to a text file so you can refer to it for information such as license file location and the names of machines that were upgraded.
- Click Save automation artifacts to export an archive file (.zip) containing information and files you can use in automation scripts to perform upgrades of this deployment.
- Browse to a location on the local disk where the archive file will be created and type a name for the file.
- Choose the automation format.
- Click Generate to create the file.
- To automate upgrades, run the Upgrade-ArcGISSite.ps1 script in an Azure PowerShell console or, to upgrade with Azure CLI on Bash, run the upgradeArcGISSite.sh script in a bash shell.
- Confirm that all settings are correct and save the files you need.
- Do not proceed to the next step. Cancel out of Cloud Builder and use the automation script, which you will customize, to upgrade.
- Click Finish to upgrade.
Note:
Upgrades can take up to five hours to complete depending on the size of your deployment. Do not close ArcGIS Enterprise Cloud Builder for Microsoft Azure until the upgrade process finishes for all components in the deployment or until you correct for a time-out error as described below.
Due to a current restriction in Microsoft Azure Resource Manager (ARM), running templates times out at 90 minutes. If your upgrade takes longer than 90 minutes, you will receive a time-out error. Do not close Cloud Builder after receiving the time-out error. Wait 60 minutes after you receive the time-out error, and retry the upgrade operation. To do that, click the Back button to return to the beginning of the operation, step through the Cloud Builder windows again, and click Finish.
If you encounter problems upgrading, review the log files created in the %temp% directory on the machine where Cloud Builder is installed. By default, that directory is C:\Users\<your login>\AppData\local\temp.
- If your deployment contains a federated ArcGIS Notebook Server 11.1 or 11.0 site, do the following after the deployment upgrade successfully finishes:
- Make a remote desktop connection to the virtual machine where ArcGIS Notebook Server is running. Connect using the machine administrator credentials you specified when you created the deployment.
- Copy the new ArcGIS Docker images to the ArcGIS Notebook Server machine and run the postinstallation utility.
- If the deployment includes an ArcGIS GeoEvent Server site, import the ArcGIS GeoEvent Server site's configuration using the file you exported before you started the upgrade process.
Upgrade V1 or 10.7.1 or earlier deployments
If you created your deployment using ArcGIS Enterprise Cloud Builder for Microsoft Azure 10.7.1 or earlier, or if you have a V1 deployment, you must upgrade the ArcGIS software in the same way as on-premises installations. Even if your deployment is currently 11.5, if you created it at an earlier release and upgraded it to 11.5, you must continue to manually upgrade the components.
See the following for each component you need to upgrade for information about interim versions and how to upgrade each component:
After you upgrade, do not use ArcGIS Enterprise Cloud Builder for Microsoft Azure for postdeployment operations such as registering databases with ArcGIS Server or managing machines.
Upgrade geodatabases in registered databases
If you enabled a geodatabase in any of the databases you registered with your ArcGIS Server sites, you can upgrade the geodatabase after upgrading ArcGIS Server or ArcGIS Pro in your Azure deployment. See Upgrade an enterprise geodatabase in SQL Server or Upgrade a geodatabase in PostgreSQL in the ArcGIS Pro help for instructions.