As organizations continue modernizing their IT environments, the conversation around ArcGIS Pro has moved well beyond the desktop. What was once a workstation-bound application is now increasingly delivered through virtual desktop infrastructure (VDI)—not just for convenience, but to support performance, scale, and distributed teams.
Since 2025, there has been a noticeable shift in how these environments are built. Many organizations are reevaluating long-standing VMware deployments and exploring Hyper-V–based architectures. This isn’t simply a platform preference—it’s being driven by the performance and design requirements of ArcGIS Pro itself.
ArcGIS Pro Drives the Architecture—Not the Other Way Around
ArcGIS Pro sets a high bar for performance. It behaves less like a typical enterprise application and more like a high-end visualization or engineering tool, relying heavily on GPU acceleration, CPU performance, and fast storage. When those elements are not aligned, users feel it immediately—map navigation lags, tools take longer to execute, and productivity drops.
Because of this, ArcGIS Pro doesn’t adapt well to generic VDI designs. It requires an approach that treats virtual desktops more like workstations at scale, where each component is intentionally aligned to GIS workloads.
In practice, successful ArcGIS Pro VDI environments consistently prioritize:
- Balanced CPU performance to support both interactive work and background processing
- GPU acceleration for 2D rendering, 3D visualization, and select geoprocessing workflows
- Fast, low-latency storage to handle large project files and datasets
These are baseline requirements—not optimizations—for delivering a usable ArcGIS Pro experience in a virtualized environment.
GPU Virtualization Matters More Than the GPU Itself
When designing ArcGIS Pro VDI environments on Hyper-V, the conversation often starts with “what GPU should we use?”—but just as important is how that GPU is presented to virtual machines.
There are two primary approaches:
- Discrete Device Assignment (DDA), where a full GPU is passed directly to a single VM
- GPU virtualization (vGPU), where a single GPU is shared across multiple VMs
While DDA can deliver near-native performance, it limits density and flexibility. Each virtual machine requires dedicated hardware, making it difficult to efficiently support a range of user workloads.
For most ArcGIS Pro environments, NVIDIA vGPU-based models provide a more practical approach. By allowing multiple users to share GPU resources while maintaining strong performance, vGPU enables infrastructure to align more closely with actual demand.
In most ArcGIS Pro VDI environments, the goal isn’t to maximize performance for a single user—it’s to deliver consistent performance across many users. That’s where vGPU models tend to win.
This becomes especially important when supporting a mix of user types, where flexibility in GPU allocation provides more value than dedicating a full GPU to each virtual machine.
Example: Right-Sizing NVIDIA vGPU for ArcGIS Pro Users
Most ArcGIS Pro environments naturally fall into three user categories: light, medium, and heavy.
- Light users primarily view data, run simple queries, and present maps
- Medium users perform editing tasks, work in both 2D and 3D, and handle day-to-day GIS workflows
- Heavy users perform advanced visualization, spatial analysis, and GPU-accelerated geoprocessing
This model translates directly into how GPU resources should be allocated in a Hyper-V environment using NVIDIA vGPU.
A practical starting point looks like:
- Light users
~4 vCPU, 8 GB RAM, smaller vGPU profiles (such as 2Q) - Medium users
~8 vCPU, 16 GB RAM, mid-range vGPU profiles (such as 2Q–4Q) - Heavy users
~12–16 vCPU, 32 GB RAM, larger vGPU profiles (such as 4Q or higher)
In a Hyper-V deployment, vGPU allows these profiles to be assigned per VM, enabling multiple ArcGIS Pro users to share a single physical GPU while maintaining consistent performance.
This tiered approach is often more effective than assigning identical resources to every user, particularly in mixed environments.
Why Full VDI Still Matters for ArcGIS Pro
As organizations explore different delivery models, one lesson has become clear: ArcGIS Pro performs best when delivered through full virtual desktops, not shared or streamed application models.
The reason is resource isolation. ArcGIS Pro expects consistent access to CPU, memory, and GPU resources. In shared environments, those resources are contested, leading to unpredictable performance.
That’s why most mature deployments follow a simple principle:
Deliver ArcGIS Pro as a dedicated virtual desktop experience, even in multi-user environments.
This ensures each user receives a consistent and predictable performance profile.
Why Hyper-V Is Re-Emerging for ArcGIS Pro VDI
Since 2025, more organizations have revisited how they host ArcGIS Pro VDI environments, with a growing number shifting toward Hyper-V–based deployments. This reflects a broader effort to align GIS infrastructure with enterprise platforms while still meeting performance expectations.
Many IT environments are already deeply integrated with the Microsoft ecosystem. In that context, Hyper-V becomes a natural fit—not just as a hypervisor, but as part of a cohesive platform aligned with existing identity and management models.
More importantly, Hyper-V provides the level of control ArcGIS Pro environments demand. GIS workloads are highly sensitive to resource allocation, and even small changes in GPU configuration, VM sizing, or storage performance can impact user experience. Hyper-V allows these environments to be tuned with precision rather than constrained by generalized VDI designs.
This has led to renewed focus on on-premises and hybrid VDI designs, where performance and data locality remain priorities. In these architectures, Hyper-V commonly serves as the primary platform hosting ArcGIS Pro desktops.
Cloud services are still part of the equation—but used more intentionally. Rather than acting as the default destination, they are introduced to extend the environment for remote access, management, or peak demand. In this model, Hyper-V remains the foundation.
In practice, this approach centers around:
- Hyper-V as the primary VDI platform
- On-premises or hybrid deployments for performance and data proximity
- Selective use of cloud services for scalability
For ArcGIS Pro, this aligns closely with real-world usage—prioritizing consistent performance while allowing flexibility where it adds value.
Real-World ArcGIS Pro VDI Challenges (and What They Reveal)
Designing ArcGIS Pro VDI environments on paper is one thing—running them in production is another.
Several patterns tend to emerge:
- Storage often becomes the first bottleneck
Even well-sized environments struggle when profile containers or data storage introduce latency - GPU sizing directly impacts usability
Undersized or oversubscribed GPUs lead to poor 3D performance and inconsistent interaction - Latency defines the experience
Even a well-built environment can feel slow if users are too far from compute - User density must match workload type
Light, medium, and heavy users place very different demands on infrastructure
ArcGIS Pro exposes weaknesses in VDI design quickly—if something isn’t right, users will notice.
Lessons Learned from ArcGIS Pro VDI Deployments
After working through multiple environments, a few lessons stand out:
- If performance feels inconsistent, look at storage first
- Match GPU allocation to user behavior, not just user count
- “Working” is not the same as “performing well”
- Start small, validate, then scale
- Design for ArcGIS Pro—not for generic VDI standards
These are often the difference between an environment that technically works and one that users actually accept.
Bringing It All Together
Modernizing ArcGIS Pro delivery is less about choosing a platform and more about designing around the application.
VDI remains the foundation, but success depends on how well the environment supports ArcGIS Pro’s requirements. That includes:
- Treating VDI hosts as GIS workstations at scale
- Prioritizing GPU, storage, and balanced compute resources
- Delivering ArcGIS Pro through full virtual desktops
- Using Hyper-V as the core platform, with cloud services where they add value
Since 2025, the shift toward Hyper-V reflects a broader move toward platform alignment and operational efficiency. But the goal remains the same:
Delivering a consistent, high-performance ArcGIS Pro experience to end users.
Article Discussion: