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
| Scenario | Use default admin RDP? | Use RDS Session Host? |
|---|---|---|
| One admin maintains the server | Yes | No |
| Two admins occasionally connect | Yes | No |
| Three people need to sign in at once | No | Yes |
| Staff need QuickBooks, Sage, ERP, Office, or MetaTrader on the server | No | Yes |
| Users connect to a web app on IIS | Yes | No |
| Users connect to SQL Server from their own computers | Yes | No |
| You want RemoteApp instead of full desktop access | No | Yes |
Default RDP is for administration. RDS Session Host is for user sessions.
Side-by-side comparison
| Feature | Default 2-session admin RDP | RDS Session Host |
|---|---|---|
| Main purpose | Remote server administration | Multi-user desktops and apps |
| Concurrent sessions | 2 administrative sessions | Based on hardware and licensing |
| RDS CAL required | No | Yes |
| RDS Licensing role | Not required | Required for production |
| RemoteApp support | No | Yes |
| Full desktop access | Yes, for admins | Yes, for users |
| Best for | Maintenance, monitoring, troubleshooting | Daily staff work |
| Example use | Check updates, services, SQL Server, IIS | QuickBooks, Sage, ERP, MetaTrader, Microsoft 365 Apps |
| Setup effort | Already available | Requires 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.
Test environment:
| Item | Value |
|---|---|
| Provider | Raff Technologies |
| OS | Windows Server 2025 Datacenter Evaluation |
| Build | 26100 |
| CPU | 4 vCPU |
| RAM | Approximately 8 GB |
| Test date | 2026-05-24 |
| Tester | Serdar Tekin |
We used this server to verify four things:
- The RDS roles were not installed by default.
- Two administrative RDP sessions could run at the same time.
- A third RDP session was blocked in default admin mode.
- 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.
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.
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.
