Requirements

Licensing

VertiGIS Studio Licensing

VertiGIS Studio Printing is licensed software.

To obtain a license, contact Customer Service.

Printing is also available as a free 60-day trial with full functionality for evaluation purposes.

ArcGIS Identity

Printing uses the modern ArcGIS pattern and ArcGIS Identities to author and access content and applications. Printing uses an Esri portal to store your print layout items. You must have either ArcGIS Online or ArcGIS Enterprise Portal 10.8.1+.

For on-premises installations of Studio Printing, the Printing Engine is deployed within your ArcGIS Enterprise environment, so an ArcGIS Enterprise license is required. The Cloud version does not require an ArcGIS Enterprise license. See On-Premises Printing vs Cloud Printing for more information.

Authoring Requirements

Sign-in Requirements

You require an ArcGIS Identity to create and share VertiGIS Studio print layouts.

Browser Requirements for VertiGIS Studio Print Designer

Print Designer runs in a desktop environment with a minimum screen resolution of 1280 x 720.

Designer supports the following browsers:

Print Designer requires a 64-bit browser.

Supported Host Applications

You can use the following applications to host and print layouts and layout packages:

Supported Client Browsers

VertiGIS Studio Printing supports the following browsers:

Requirements for On-Premises Printing

On-premises deployments require ArcGIS Enterprise to host and execute the GP task of the ArcGIS Pro-based Printing Engine.

Supported Versions of Portal for ArcGIS

VertiGIS Studio Printing works with Portal for ArcGIS in ArcGIS Enterprise 10.8.1+.

We strongly recommend you use ArcGIS Enterprise 1.11 or later and the CIM3 - v3 version of the ArcGIS Pro-based Printing Engine.

The CIM3 version of the ArcGIS Pro-based Printing Engine has more functionality and performs better than the CIM2 - v2 version of the ArcGIS Pro-based Printing Engine.

Hardware Requirements for On-Premises Printing Servers

Most of the processing is handled by theArcGIS Pro-based Printing Engine GP task running on your ArcGIS Enterprise server.

Minimum Hardware Requirements for an On-Premises VertiGIS Studio Printing Server

Hardware Component

Minimum

Recommended

Random Access Memory (RAM)

8 GB

16 GB or higher

Storage Drive (HDD, SSD)

1 GB

5 GB or higher

CPU

2-core processor, 2 GHz, x64

4-core processor, 2 GHz or higher, x64

Operating System Requirements for On-Premises Printing Servers

On-premises Printing servers require Windows Server 2019, Windows Server 2022, or Windows Server 2025.

Web Server Requirements for On-Premises Printing Servers

On-premises Printing servers require the Internet Information Services (IIS) feature of the Windows operating system. The Post Installer application automatically enables IIS by enabling the Web Server role, along with the Application Initialization, ASP.NET 4.5, Windows Authentication, and WebSocket Protocol service roles and all of their service role dependencies.

If you uninstall on-premises Printing, all previously enabled IIS features remain enabled.

.NET Requirements for On-Premises Printing Servers

On-premises Printing servers require .NET Framework 4.8+.

Ports

On-premises Printing does not expose any ports, so you do not need to adjust your firewall settings. VertiGIS Studio Printing (including Print Designer) relies on the ports that IIS uses (ports 80 and 443 by default).

Cookie Requirements

VertiGIS Studio Printing does not use cookies.

TCP/IPv6 Requirements

By default, ArcGIS Enterprise servers are configured to allow TCP/IPv6. Disabling this setting prevents the ArcGIS Pro-based Printing service from functioning correctly on-premises.

Cross-Origin Resource Sharing (CORS) Requirements

By default, ArcGIS portals (including ArcGIS Online) allow cross-domain requests using CORS. If you configure the Organization | Settings | Security | Allow Origins setting in the portal that you use with VertiGIS Studio Printing, then you must add VertiGIS Studio Printing as an allowed origin.

The origin to allow depends on your deployment: