Skip To Content

ArcGIS Enterprise 11.2 system requirements

ArcGIS Enterprise provides a system for mapping, visualization, data management, and analytics, as well as a flexible deployment model allowing for use on-premises, in the cloud, and on virtual machines.

A base ArcGIS Enterprise deployment includes several components that are designed to work together. In addition to these components, you can add one or more ArcGIS Server licensing roles or other ArcGIS Server types to your ArcGIS Enterprise deployment to meet specific workflow requirements in your organization.

This page lists support information that is common to most parts of an ArcGIS Enterprise deployment—such as cloud and virtualization support policies—and provides links to other pages to help you understand the requirements for each component and site in an ArcGIS Enterprise deployment.

System requirements pages

Each ArcGIS Enterprise component has specific requirements unique to that component. Read the system requirements page for each component, site, and app you deploy as well as the requirements pages for tools such as ArcGIS Enterprise Builder or ArcGIS Enterprise SDK. Use the following links to access each page:

For ArcGIS GeoAnalytics Server requirements, see Best practices for GeoAnalytics Server sites.

Microsoft Windows operating system requirements

The following Windows operating systems are supported for most ArcGIS Enterprise components and sites. At present, the exception to this is ArcGIS Notebook Server.

Supported operating systemLatest update or service pack tested

Windows Server 2022 Standard and Datacenter

Sept 2023 update

Windows Server 2019 Standard and Datacenter

Sept 2023 update

Windows Server 2016 Standard and Datacenter

Sept 2023 update


  • Prior and future updates or service packs for these operating system versions are supported unless otherwise stated. The operating system version and updates must also be supported by the operating system provider.
  • The Desktop Experience option is required on all versions of Windows Server.

See the page for each component you want to install for additional operating system requirements. See Operating system limitations - Windows for information on limitations when using ArcGIS on Windows.

Firewall settings

Each component in an ArcGIS Enterprise deployment communicates over a specific set of ports. If a port is used to communicate between machines, you must open that port in the machine's firewall. If a port is used for internal communication, verify the port isn't being used by another application that is running on the machine.

Use the following list and links to help you find all the ports used by each component you can have in an ArcGIS Enterprise deployment:

View a diagram of the ports used in an ArcGIS Enterprise deployment.

Supported web browsers

Most ArcGIS Enterprise components include wizards or interfaces that you access through a web browser. The following browsers are supported for most components:

  • Google Chrome version 111 and later
  • Microsoft Edge version 111 and later
  • Mozilla Firefox version 113 and later
  • Mozilla Firefox version 102 (ESR)
  • Safari version 15 and later

*Scene Viewer and scene-based apps have their own browser requirements. Some of the ArcGIS apps also have their own requirements. See each app's documentation for details.

For best performance and full functionality, use the latest version of a browser listed above. Only WebGL-enabled, 64-bit browsers are supported. The website leverages the local storage capabilities (similar to cookies) of the browser. If this storage is disabled, the site will not function properly. To learn how to enable local storage, consult the browser's documentation.

ArcGIS Enterprise on cloud platforms

You can deploy ArcGIS Enterprise on many cloud platforms. Any cloud platform that provides virtual machines that meet the basic system requirements for operating system and system specifications is supported for use with ArcGIS Enterprise.

In addition to basic support, Esri provides deployment tooling and prebuilt virtual machine images on two cloud platforms: Amazon Web Services (AWS) and Microsoft Azure. When deploying on these two cloud platforms, it's recommended that you use the specialized tooling and images to simplify deployment.

Esri does not provide technical support for provisioning and configuring cloud infrastructure beyond what ArcGIS Enterprise deployment tooling creates and manages as part of its normal operations. For cloud platforms other than AWS and Azure, for which Esri does not provide specialized deployment tooling, support is limited to troubleshooting software-specific issues.

ArcGIS Enterprise also supports native cloud functionality such as storage and databases on several cloud platforms. Examples include Amazon Simple Storage Service (S3) and Microsoft Azure SQL Database. See the documentation for each ArcGIS component for information on the native cloud functionality that's supported.


Implementing ArcGIS Notebook Server on a cloud platform has a few additional requirements. See the ArcGIS Notebook Server system requirements for details.

Supported virtualization environments

All components of ArcGIS Enterprise are fully supported on virtual environments as long as they run on supported operating systems. When running third-party applications with ArcGIS Enterprise, such as relational databases, the application must also be supported in a virtual environment. Check the third-party vendor for its virtualization support.

The following virtualization environments are known to perform well with ArcGIS Enterprise and its components:

  • VMware vSphere 7.0, 8.0
  • Microsoft Hyper-V

Inclusion on the list above does not imply an endorsement or higher level of support. A lack of inclusion on the list above does not imply that an environment or specific version is not supported; it means that it is not an environment or version that Esri or its partners have explicitly tested.

For additional information, see Deploy ArcGIS Server on virtualized hardware.

ArcGIS Enterprise architecture

You must install all ArcGIS Enterprise components for a single deployment within a single data center or equivalent, such as a cloud region or network, to provide low latency connectivity between each component. In some cases, it is required that you have components or directories in the same data center.

The following are examples:

  • If you have an ArcGIS Server site that contains three machines, all three machines must reside in the same data center; the machines cannot be split across multiple data centers.
  • Federated ArcGIS Server sites, the portal with which they are federated, the portal's hosting server, and each type of ArcGIS Data Store in an ArcGIS Enterprise deployment must reside in the same data center.
  • All Portal for ArcGIS, ArcGIS Data Store, and ArcGIS Server machines in a highly available ArcGIS Enterprise deployment must be in the same data center; the primary and standby machines cannot be split across separate data centers.

    To safe guard against loss of a single data center, you can create a secondary deployment in a separate data center. See Disaster recovery and replication for more information.

  • Web services and the data they reference need to be in the same data center or cloud region to avoid performance problems. Therefore, your data source and the ArcGIS Server site where the service is running must be in the same data center.
  • Performance may be poor when ArcGIS Server sites and their corresponding configuration stores and other ArcGIS Server directories are not in the same data center. Similarly, performance may be poor when Portal for ArcGIS machines and their content directories are not in the same data center.

In addition, ArcGIS clients (such as ArcGIS Pro) that publish to ArcGIS Enterprise should be deployed in the same cloud region or network as ArcGIS Enterprise to avoid latency and performance problems when publishing web layers. This is especially important when publishing hosted layers, which copy data from the data source to machines in the ArcGIS Enterprise deployment.