RDS, VDI and Azure Virtual Desktop: Choosing Desktop Virtualization

Choosing between RDS, VDI and Azure Virtual Desktop: application compatibility, role services, licensing, FSLogix profile management and a session host capacity example.
Technical summary
Technology
Remote Desktop Services, VDI, Azure Virtual Desktop, FSLogix, Windows Server
Topic
Choosing a desktop virtualization model
Level
Intermediate
Prerequisites
  • Windows Server and Active Directory knowledge
  • User and application inventory
In this article8 sections

Desktop virtualization projects usually start with the wrong question: “RDS, VDI or AVD?” The right question is whether the application to be delivered runs on multi-user Windows Server, and where the profile will live. The three models, namely session-based Remote Desktop Services (RDS) on Windows Server, VDI that gives each user a separate Windows client VM, and Microsoft’s managed service Azure Virtual Desktop (AVD), answer these two questions differently. Below we compare the three on application compatibility, profile management, licensing and infrastructure load, and finish with a capacity calculation example.

Desktop virtualization models

The basic distinction is how many users share one operating system instance:

  • Session-based (RDS Session Host): Many users sign in concurrently on a single Windows Server instance. It is the most resource-efficient model; but all users share the same operating system, the same installed applications and the same resources.
  • Pooled VDI: At each session, the user connects to an available Windows client VM in the pool; VMs are derived from a common image, and user-specific data is kept in the profile solution.
  • Personal VDI: Each user has a permanently assigned VM. Users can install their own applications; it is the model with the highest management load and resource consumption.
  • Azure Virtual Desktop: Microsoft operates the control plane, such as the connection broker, gateway and web access; session hosts run in Azure (or on Azure Local). It can deliver both multi-session and personal desktops.

The application usually makes the decision. An application that doesn’t support multi-user Windows Server, uses a per-user hardware lock or requires local administrator rights rules out RDS from the start. Delivering a single ERP client or office applications to dozens of users, on the other hand, is where the session-based model is strongest. Start the pilot with the application, not the infrastructure.

RDS architecture and role services

An RDS deployment on Windows Server consists of interconnected role services:

Role service Function
RD Session Host Runs user sessions and applications
RD Connection Broker Directs users to a suitable host, reconnects dropped sessions, balances load
RD Web Access Publishes the desktop and RemoteApp list as a web and subscription feed
RD Gateway Carries RDP connections from the internet inside HTTPS (TCP 443); performance improves with UDP 3391
RD Licensing Manages and distributes RDS CALs
RD Virtualization Host Manages client VMs on Hyper-V in the on-premises VDI scenario

In a small deployment, Connection Broker, Web Access and Licensing can run on the same server; but that server becomes a single point of failure. High availability for the Connection Broker needs a shared SQL Server database (or Azure SQL Database) and a DNS record. RD Gateway should be used instead of an RDP port left open to the internet, and combined with multi-factor authentication. Publishing RDP (TCP 3389) directly to the internet isn’t an acceptable method. It isn’t up for debate either.

# Basic session-based deployment (RemoteDesktop module)
New-RDSessionDeployment -ConnectionBroker "rdcb01.corp.local" `
  -WebAccessServer "rdweb01.corp.local" `
  -SessionHost "rdsh01.corp.local","rdsh02.corp.local"

New-RDSessionCollection -CollectionName "Office" `
  -SessionHost "rdsh01.corp.local","rdsh02.corp.local" `
  -ConnectionBroker "rdcb01.corp.local"

Set-RDLicenseConfiguration -LicenseServer "rdlic01.corp.local" `
  -Mode PerUser -ConnectionBroker "rdcb01.corp.local"

Until the RDS license server is activated, the deployment runs with a 120-day grace period. When it ends, connections for which no license can be issued are refused. This is the common scenario: setup was done months ago, the license server was forgotten, and one Monday morning nobody can connect. Activate the license server and install the CALs in the first week of the setup.

VDI: personal and pooled desktops

On-premises VDI gives users a real Windows 10/11 client experience. Because desktop applications are tested on the client operating system, compatibility problems drop, and users are less affected by each other’s resource consumption. The price is the server and system infrastructure and the operational load:

  • Each VM carries its own operating system memory and disk; for the same number of users, noticeably more resources are needed than with the session-based model.
  • Image management, update waves and antivirus scans starting at the same time create “boot storm” and “update storm” effects; storage design is based on these peaks, not the average.
  • With personal desktops, each VM is a separate management object; patching, backup and inventory must be managed like a desktop fleet.

On Windows Server Hyper-V, Microsoft’s full VDI tool is the RDS Virtualization Host role; for projects that need large-scale pool management, image distribution and autoscaling, third-party VDI platforms are also considered. Whatever the platform, VM sizing principles don’t change; details are in the virtual machine sizing article.

Azure Virtual Desktop

In AVD, the connection broker, gateway, web client and diagnostics layer are operated by Microsoft; you manage the session hosts, storage and network. Because session hosts use reverse connect, you don’t need to open inbound ports from the internet to the hosts.

Points to look at when deciding on AVD:

  • Windows 11 Enterprise multi-session: The client operating system on which multiple users can sign in at once is supported only in Azure and on Azure Local. It combines the resource efficiency of RDS with client application compatibility.
  • Host pools: Defined as pooled or personal; in a pool, load balancing is chosen as “breadth-first” (spread users across hosts) or “depth-first” (fill one host, then move to the next). Depth-first suits autoscaling that shuts down idle hosts to reduce cost.
  • Identity: Session hosts can join Active Directory or Microsoft Entra ID; in both cases user identity is authenticated through Entra ID.
  • Cost items: Compute (VM hours), disks, profile storage (Azure Files or Azure NetApp Files), network egress and optional backup. There is no separate charge for the control plane; the licensing condition must be met.

For current features and requirements, the Azure Virtual Desktop documentation is the reference.

Licensing and profile management

Licensing requirements

Model Basic licensing requirement
On-premises RDS Windows Server license for the hosts, Windows Server CAL and RDS CAL (per user or per device)
On-premises VDI Windows Server license for the Hyper-V hosts; Windows virtualization rights for accessing client VMs (such as a Windows Enterprise E3/E5 user subscription or Windows VDA)
AVD, Windows client An eligible Microsoft 365 or Windows Enterprise license per user
AVD, Windows Server host RDS CAL with Software Assurance (SA) or an RDS user subscription

Running office applications in a shared environment is a separate topic: using Microsoft 365 Apps on RDS or a multi-session host requires “shared computer activation,” and this feature exists only in certain subscription plans. This is usually the licensing gap discovered later in the project. For the details of the rules and a plan comparison, see the choosing Microsoft 365 licenses and Windows Server licensing for virtualization articles. Since licensing terms can change, verify Microsoft’s current product terms before buying.

Profile management with FSLogix

In pooled models (RDS, pooled VDI, multi-session AVD), a user may land on a different host each time; the profile needs to be independent of the host. FSLogix keeps the user profile in a VHDX file on an SMB share and attaches it like a local profile at sign-in. Sign-in is faster than with a classic roaming profile; it carries large content such as the Outlook cache, OneDrive and Teams data without trouble. The right to use FSLogix requires no extra fee for users with the eligible licenses in the table above.

reg add "HKLM\SOFTWARE\FSLogix\Profiles" /v Enabled /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\FSLogix\Profiles" /v VHDLocations /t REG_MULTI_SZ /d "\\fs01.corp.local\profiles$" /f
reg add "HKLM\SOFTWARE\FSLogix\Profiles" /v VolumeType /t REG_SZ /d VHDX /f
reg add "HKLM\SOFTWARE\FSLogix\Profiles" /v SizeInMBs /t REG_DWORD /d 30000 /f
reg add "HKLM\SOFTWARE\FSLogix\Profiles" /v DeleteLocalProfileWhenVHDShouldApply /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\FSLogix\Profiles" /v FlipFlopProfileDirectoryName /t REG_DWORD /d 1 /f

NTFS permissions on the profile share are set so that each user can only create and access their own folder. Profile shares opened with a broad “Everyone: Full Control” permission are still seen; that means every user can access someone else’s profile disk. If profile storage depends on a single file server, that server is the single point of failure for the whole desktop environment. Highly available SMB (Scale-Out File Server, Azure Files) or FSLogix Cloud Cache should be considered. The full list of settings is in the FSLogix documentation.

Comparison table

Criterion RDS On-premises VDI AVD
Resources per user Low High Low with multi-session
Application compatibility Server operating system constraint Full client Full client
Operating the control plane You You Microsoft
Scaling Depends on hardware purchases Depends on hardware purchases Within minutes, usage-based
Data location On premises On premises Azure region or Azure Local
Suitable scenario A small number of standard applications Specialized software, persistent desktop Flexible scale, remote work

When AVD is chosen, access latency to on-premises application and file servers becomes decisive. If the desktop is in Azure and the ERP database is on premises, every query crosses the WAN link; users report this as “AVD is slow.” The desktop isn’t to blame. Moving the application servers to the cloud too, or a plan for a good-quality site-to-site connection, is part of the decision.

Capacity calculation example

The calculation below is to show the method; the values are assumptions and are replaced with pilot measurements in a real project.

  • Total users: 150; peak concurrently connected users (assumption): 120.
  • Session host size: 8 vCPU, 48 GB memory.
  • Pilot result (assumption): one host carries 20 concurrent office users while keeping the target response time.

Calculation: 120 ÷ 20 = 6 hosts. For the service to continue while one host is in maintenance or failed, 7 hosts are needed with N+1. Total resources are 7 × 8 = 56 vCPU and 7 × 48 = 336 GB memory. For profile storage, with an upper limit of 30 GB per user, the theoretical ceiling is 150 × 30 = 4.5 TB; but since VHDX grows dynamically, starting capacity is calculated from the actual profile sizes of the pilot users, and the ceiling goes into the quota plan.

During the pilot, the processor queue, memory usage, disk latency and sign-in time on the session host are monitored together. Video conferencing, heavy browser-based applications and Teams use noticeably increase the resources needed per user; verify that VDI optimization for Teams (offloading media processing to the client device) is enabled. If optimization is off, a video call eats the session host’s CPU.

For designing on-premises RDS and VDI infrastructure, see our virtualization and data management page; for Azure Virtual Desktop projects, our Microsoft 365 and Azure services page.

Frequently asked questions

What licenses does RDS need?

You need a Windows Server license for the servers running the session hosts, a Windows Server CAL for each user or device accessing the server, and in addition an RDS CAL. RDS CALs can be bought per user or per device and are distributed through the RD Licensing server.

Can I install Windows 11 multi-session on my own Hyper-V server?

No. Windows 11 Enterprise multi-session is supported only within Azure Virtual Desktop, in Azure and on Azure Local. For a multi-user desktop on on-premises Hyper-V, Windows Server-based RDS is used.

Is a separate license needed to use FSLogix?

No. FSLogix can be used at no extra charge by users with an eligible Microsoft 365, Windows Enterprise, Windows VDA or RDS CAL/RDS user subscription license. Verify the current eligibility list in Microsoft’s FSLogix documentation.

Is RDS or AVD cheaper?

There is no single right answer. With RDS, hardware, licensing and operating costs are upfront and fixed; with AVD, compute and storage are paid by usage, and operating the control plane goes away. If working hours are well defined and autoscaling can be used, AVD can be advantageous; in environments running constantly at full load, on-premises RDS cost is more predictable.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek System Support

Server installation, configuration, incident response and scheduled maintenance. Active Directory, virtualization and backup are managed with the same discipline.

Knowledge Center

Other articles