ArcGIS Enterprise allows organisations to deploy GIS infrastructure on-premises or in the cloud, offering robust security and scalability.

Use the following guides to configure your ArcGIS Enterprise licences to maximise the most of your GIS.

Find your ideal user type with the ArcGIS user type finder or check the best fit for your organisation using the ArcGIS user type capability tool.

If your organisation currently uses ArcGIS Enterprise version 10.9 or earlier, review these considerations before upgrading to the latest 11.x version.

Install and activate

Administer, configure and manage

Upgrades, migration and best practices

For assistance with ArcGIS Enterprise licensing, get in touch with Esri Indonesia.

FAQs

  • Can user types be migrated between ArcGIS Online and ArcGIS Enterprise and if yes, will they be treated separately?

    No, the user types cannot be migrated between ArcGIS Online and ArcGIS Enterprise because each platform is set up and run differently and member will require a separate identity to access each platform. 

    ArcGIS Enterprise: Runs on-premises or in your private cloud. It requires hardware, software, and IT resources. 

    ArcGIS Online: Esri-hosted cloud platform with similar capabilities to ArcGIS Enterprise but runs fully in the cloud

  • Can users manage and change their own licences like they can with the concurrent licences?

    For the most part, no, unless they are an administrator within ArcGIS Enterprise they cannot change their user type. 

  • How may I add new user types and add-on applications to ArcGIS Enterprise?

    When you need to incorporate new ArcGIS Enterprise User Types or Add-on licences (eg. Creators, Mobile Workers, ArcGIS Pro, Drone2Map) to an ArcGIS Portal instance, the existing licence file can be edited so that the new user types or add-ons are updated in your licence file. A new copy of the licence file is then created in JSON format and is then imported into ArcGIS Portal. To complete this action, you will need to log a GIS support request and one of our specialists will assist you.

    Additional capabilities, such as GeoEvent Server, Image Server, or GeoAnalytics Server, are licenced separately as extensions to ArcGIS Enterprise. 

    For a high-level view of which apps are included in each user type for ArcGIS Enteprise, refer to the ArcGIS user type home page and for a full list of inclusions, refer to the 2023 to 2024 ArcGIS User Type Comparison Matrix. 

  • What are the prerequisites for licencing ArcGIS server component of ArcGIS Enterprise?

    When it comes to licencing the ArcGIS Server component of ArcGIS Enterprise is licenced by CPU cores.  

    The minimum purchase requirement for ArcGIS Enterprise is an "up-to-4 core" licence.This licence can be installed on a machine with two or four cores. If your machine has more than 4 cores (physical or virtual), you have the option to purchase additional cores, or virtualise the machine. By virtualising the machine, you can ensure that the 4-core licence of ArcGIS Enterprise is installed on only 4 (virtual) cores, meeting the licence agreement.  

    However, if you install a 4-core licence on an 8-core physical machine without virtualisation, ArcGIS Enterprise will utilise all 8 cores, violating the licence agreement.  

    To rectify this, you would need to purchase a licence for the four ‘additional cores’. 

  • Is the process of acquiring a named user licence in ArcGIS Enterprise similar to ArcGIS Online?

    The process of acquiring a licence in an ArcGIS Enterprise organisation is different than in an ArcGIS Online organisation. In ArcGIS Enterprise, ArcGIS Pro licences are stored in the ArcGIS Licence Manager application on a server behind the firewall. 

    When a member signs in to ArcGIS Pro with their organisation username and password, ArcGIS Enterprise validates their membership and licence assignment in the portal website using the secure HTTPS protocol. ArcGIS Pro then makes a call to ArcGIS Licence Manager to obtain a licence. If a licence is available, ArcGIS Pro starts. In this part of the process, ArcGIS Enterprise does not communicate with the licence manager. It is important to note that the communication between ArcGIS Pro and ArcGIS Enterprise uses a different protocol than the communication between ArcGIS Pro and ArcGIS Licence Manager. The firewall must be configured accordingly. 

  • How do we update our ArcGIS Enterprise Term licences?

    When an organisation renews their Enterprise Licence Agreement (ELA), they may be required to update their ArcGIS Enterprise Term licences. 
     
    These updated authorisation numbers must be applied in up to five locations: ArcGIS Server, ArcGIS Datastore, Portal for ArcGIS, ArcGIS Enterprise Geodatabase, and ArcGIS Licence Server Administrator 

    To update your ArcGIS Enterprise term licences, you need to ensure that your licence files are current before your old licences expire. For detailed instructions, follow this step-by-step guide. 

  • How do I update an expired Enterprise Geodatabase licence?

    f your organisation licences ArcGIS Server for a set time period, the geodatabase administrator can run the Update Enterprise Geodatabase Licence tool with a new ArcGIS Server authorisation file to update licence information in the geodatabase before the existing licence expires. This allows clients to continue working with the geodatabase without interruptions caused by expired licences. 

    The input workspace must be an enterprise geodatabase. This tool does not work with any other type of geodatabase. You must connect to the enterprise geodatabase as the geodatabase administrator to run this tool. 

    To generate a licence file for an enterprise geodatabases licenced with ArcGIS Enterprise on Kubernetes, use the exportGeodatabaseLicence REST operation.

  • How do I enable a server licencing role?

    To enable one of the server licencing role, authorise the software with an authorisation file for the licencing role. 

    Multiple server licences role can be applied to the same server, but it is recommended to deploy separate servers for each role.