comparisonsintermediate8 min read·Updated May 23, 2026

Multi-User RDP: 2 Admin Sessions vs RDS Session Host

Decide when built-in 2-admin-session RDP is enough, when RDS Session Host is required, and how CAL licensing affects your Windows VPS workload.

Windows Remote Desktop warning showing that a third login is blocked because too many users are already signed in.
On this page

Don't have a Windows Server yet?

Deploy Windows Server 2019/2022/2025 in ~2 minutes. 6-month evaluation licence included.

Deploy Windows now

In short

Windows Server allows two administrative RDP sessions by default. That is enough for server maintenance, but not for a team using the server as a shared desktop. In our Raff test, two admin sessions worked at the same time. A third login was blocked until we disconnected an existing user. For 3+ daily desktop users, use RDS Session Host and plan RDS CAL licensing.

Quick verdict

ScenarioUse default admin RDP?Use RDS Session Host?
One admin maintains the serverYesNo
Two admins occasionally connectYesNo
Three people need to sign in at onceNoYes
Staff need QuickBooks, Sage, ERP, Office, or MetaTrader on the serverNoYes
Users connect to a web app on IISYesNo
Users connect to SQL Server from their own computersYesNo
You want RemoteApp instead of full desktop accessNoYes

Default RDP is for administration. RDS Session Host is for user sessions.

Side-by-side comparison

FeatureDefault 2-session admin RDPRDS Session Host
Main purposeRemote server administrationMulti-user desktops and apps
Concurrent sessions2 administrative sessionsBased on hardware and licensing
RDS CAL requiredNoYes
RDS Licensing roleNot requiredRequired for production
RemoteApp supportNoYes
Full desktop accessYes, for adminsYes, for users
Best forMaintenance, monitoring, troubleshootingDaily staff work
Example useCheck updates, services, SQL Server, IISQuickBooks, Sage, ERP, MetaTrader, Microsoft 365 Apps
Setup effortAlready availableRequires RDS role deployment and licensing configuration

What we tested on Raff

We tested this on a fresh Raff Windows VPS running Windows Server 2025 Datacenter Evaluation.

PowerShell output showing a Raff Windows VPS running Windows Server 2025 Datacenter Evaluation with build number, CPU count, and memory details.

Test environment:

ItemValue
ProviderRaff Technologies
OSWindows Server 2025 Datacenter Evaluation
Build26100
CPU4 vCPU
RAMApproximately 8 GB
Test date2026-05-24
TesterSerdar Tekin

We used this server to verify four things:

  1. The RDS roles were not installed by default.
  2. Two administrative RDP sessions could run at the same time.
  3. A third RDP session was blocked in default admin mode.
  4. RDS roles had to be installed separately before moving toward a real RDS deployment.

When two admin sessions are enough

Use default Windows Server RDP when the server is mainly hosting services and only one or two admins need access.

This is enough when:

  • You manage the server yourself.
  • You and one colleague occasionally check logs, services, or updates.
  • The server runs SQL Server, IIS, a trading bot, or another service.
  • Users connect to the application directly, not to a Windows desktop.
  • You do not need RemoteApp, profile disks, or staff desktop sessions.

Example: if you host an ASP.NET app on IIS, your customers use the website in their browser. They do not need to RDP into the server. Default admin RDP is enough for maintenance.

Example: if SQL Server runs on the VPS, analysts can connect from their own devices using SQL Server Management Studio. They do not need to sign in to the Windows desktop.

What two admin sessions look like

We created two temporary administrator accounts and signed in through RDP.

PowerShell query user output showing two active administrative RDP sessions on a Windows Server VPS.

This is normal Windows Server remote administration mode. Two admin sessions can be active at the same time.

That does not make the server a multi-user desktop server. It only means two administrators can maintain the machine.

What happens when a third user connects

After two sessions were already active, we tried to sign in as a third test user.

Windows blocked the login and asked us to disconnect an existing user.

Windows Remote Desktop warning showing that a third login is blocked because too many users are already signed in.

This is the practical limit that matters for SMBs.

If three employees need to use the same Windows desktop environment, default RDP is the wrong tool. You need RDS Session Host.

When you need RDS Session Host

Use RDS Session Host when users need to sign in to the server and work there every day.

You need RDS Session Host when:

  • 3+ users need concurrent desktop sessions.
  • Staff need QuickBooks Desktop, Sage, ERP software, MetaTrader, or Microsoft 365 Apps on the server.
  • You want to publish individual apps with RemoteApp.
  • You need separate user sessions and profiles.
  • You want a managed multi-user desktop environment instead of two admin logins.

RDS Session Host is a Windows Server role for session-based desktops and apps. Microsoft describes Remote Desktop Services as a role-based infrastructure for full desktops and RemoteApp programs, and the RD Session Host role holds the session-based apps and desktops you share with users.

RDS Session Host is not installed by default

A fresh Windows Server VPS does not start as an RDS Session Host.

Before installation, we checked the main RDS roles with PowerShell:

powershellGet-WindowsFeature RDS-RD-Server, RDS-Licensing, RDS-Connection-Broker, RDS-Web-Access | Format-Table Name, DisplayName, InstallState -AutoSize

The roles were available, but not installed.

PowerShell output showing Remote Desktop Services roles available but not installed on a fresh Windows Server VPS.

That distinction matters. Having RDP enabled does not mean you have deployed RDS.

Basic RDS role install summary

For a small single-server test deployment, the role installation starts with PowerShell:

powershellInstall-WindowsFeature -Name RDS-RD-Server, RDS-Licensing, RDS-Connection-Broker, RDS-Web-Access -IncludeManagementTools

After installation and reboot, we checked the roles again:

powershellGet-WindowsFeature RDS-RD-Server, RDS-Licensing, RDS-Connection-Broker, RDS-Web-Access | Format-Table Name, DisplayName, InstallState -AutoSize

The roles showed as installed.

PowerShell output showing Remote Desktop Services roles installed after reboot on a Windows Server VPS.

This proves the server has the RDS role components installed. It does not mean the server is production-ready.

A production RDS deployment still needs licensing configuration, user access planning, security hardening, profile planning, and workload testing.

RDS CALs are not optional

If users or devices connect to an RD Session Host running Windows Server, they need RDS Client Access Licenses.

That is separate from normal Windows Server admin RDP.

Use this rule:

Access typeRDS CAL needed?
One or two admins maintaining the serverNo
Users connecting to IIS websiteNo
Users connecting to SQL Server over TCPNo
Staff signing in to an RDS Session Host desktopYes
Staff using RemoteApp from an RDS Session HostYes

For licensing details, read RDS CAL Licensing on Windows Server.

Decision tree

textAre only one or two admins connecting for maintenance?
|
|-- Yes
|   Use default admin RDP.
|   No RDS Session Host.
|   No RDS CALs for those admin sessions.
|
|-- No
    Do three or more users need to sign in to the Windows desktop?
    |
    |-- Yes
    |   Use RDS Session Host.
    |   Plan RDS CALs.
    |   Size the VPS by workload.
    |
    |-- No
        Do users access an app, website, database, or service directly?
        |
        |-- Yes
        |   Keep default admin RDP for maintenance.
        |   Do not force users through a shared desktop.

Sizing RDS Session Host

Size by workload, not by user count alone.

WorkloadStarting estimate
3-5 light desktop users4 vCPU / 8-16 GB RAM
5-10 office users8 vCPU / 32 GB RAM
10+ accounting or ERP users16 vCPU / 64 GB RAM or larger
QuickBooks Desktop usersAdd RAM per active user and test file performance
Microsoft 365 Apps usersPlan for Outlook cache, profiles, and updates
MetaTrader usersSize by number of terminals, charts, and EAs

A 10-user QuickBooks deployment and a 10-user MetaTrader deployment do not behave the same. QuickBooks, Outlook, Excel, browsers, ERP clients, and database tools all have different memory and CPU patterns.

For production, start with a realistic plan, test the actual application, then resize if needed.

When not to use RDS

Some cases sound like RDS, but are better solved another way.

NeedBetter approach
Two admins need to manage the VPSUse default RDP
Customers need a web appHost it on IIS
Analysts need SQL accessLet them connect to SQL Server remotely
Users need shared filesUse a file share, not a shared desktop
A script must run every nightUse Task Scheduler or a service
A trading bot must run 24/7Run it under a controlled user or service account

RDS Session Host is useful when people need desktop sessions. Do not add it just because multiple people use something hosted on the server.

Common mistakes

Installing RDS Session Host for two admins

If only two administrators need access, keep default RDP. RDS adds licensing and management work without solving a real problem.

Treating admin RDP like a shared office desktop

Default admin RDP is not a team desktop. The third user will be blocked or forced to disconnect someone else.

Forgetting RDS CALs

Installing the RDS Session Host role is not the same as licensing the deployment. Plan RDS CALs before giving access to staff.

Sizing by user count only

Five QuickBooks users, five Office users, and five MetaTrader users can produce very different load. Size by application behavior.

Leaving test users behind

If you create temporary test users, delete them after testing:

powershellRemove-LocalUser -Name "RaffTestAdmin1"
Remove-LocalUser -Name "RaffTestAdmin2"

What Raff recommends

Use default RDP for server maintenance.

Use RDS Session Host only when users need daily desktop sessions or RemoteApp access.

For most SMBs, the decision is simple:

  • Running a website, database, API, or background service: default RDP is enough.
  • Running QuickBooks, Sage, ERP, Office apps, MetaTrader, or other desktop apps for multiple staff: plan RDS Session Host.
  • Unsure which one applies: start with the user workflow. If people need to open the Windows desktop, it is probably RDS.

Tested on

Tested on Raff Windows VPS, Windows Server 2025 Datacenter Evaluation, build 26100, 4 vCPU, approximately 8 GB RAM, 2026-05-24. We verified the two-session admin RDP behavior, the third-session block, RDS role availability before installation, and RDS role state after installation and reboot. Tester: Serdar Tekin

What's next

Sources

Published May 23, 2026 · Last updated May 23, 2026