What is Remote Desktop Services?
Remote Desktop Services is a role in Windows Server that enables remote access to graphical desktops and applications. Its key trick is session-based computing: instead of giving each user their own virtual machine, one Windows Server hosts many simultaneous user sessions, and each user gets their own isolated desktop streamed to their device.
RDS grew out of what used to be called Terminal Services in older Windows Server versions. The rename reflected a broader job: RDS isn't just about full desktops anymore — it can publish individual applications (RemoteApp), so a user on a Mac or thin client can run a Windows program that appears as a window on their own desktop, while it actually executes on the server.
Organizations use RDS to centralize Windows applications: the software is installed once on the server, data stays in the datacenter, and users connect from anywhere with an RDP client. IT gets one place to patch and secure; users get their apps on any device.
RDS vs RDP: what's the difference?
People mix these up constantly, so let's be precise. RDP (Remote Desktop Protocol) is the protocol — the language spoken between your device and the remote machine, handling the screen image, keyboard, mouse, and sound. RDS (Remote Desktop Services) is the server-side platform — the set of Windows Server roles that manages sessions, brokers connections, publishes apps, and handles licensing for many users at once.
A useful analogy: RDP is the road, RDS is the traffic system. You use RDP every time you connect to any Windows server remotely — including a simple rented RDP server with a single admin account. RDS only enters the picture when you need many concurrent users, centralized app publishing, gateways, and connection brokering on infrastructure you manage yourself.
The core RDS components
A full RDS deployment is made of several role services that work together:
| Component | What it does |
|---|---|
| RD Session Host | The workhorse: hosts the actual user sessions and runs the desktops and RemoteApp programs. |
| RD Connection Broker | Directs incoming connections to the right session host, reconnects dropped sessions, and balances load across a farm. |
| RD Gateway | Lets remote users connect securely over the internet (HTTPS) without a VPN, proxying RDP traffic. |
| RD Web Access | A web portal where users see and launch their published desktops and RemoteApp programs from a browser. |
| RD Licensing | Manages RDS client access licenses (CALs) — the per-user or per-device licenses Microsoft requires for RDS connections. |
Small deployments sometimes combine several of these roles on one or two servers; larger ones split them across dedicated machines for scale and redundancy. Either way, the Session Host is where your users' desktops actually run — the other roles exist to get users there securely and keep track of them.
RDS deployment types
RDS supports two main ways of giving users a Windows experience:
- Session-based desktops — many users share each Session Host server, each in their own session. Efficient and cost-effective; best when users run a common set of applications.
- Virtual-machine-based desktops (VDI) — each user gets their own virtual machine, brokered by RDS. More isolation and personalization, at the cost of more hardware per user.
On top of either, RemoteApp can publish individual applications instead of full desktops — the user double-clicks an icon and the app window appears locally while running on the server. RemoteApp is popular for delivering one or two line-of-business apps to users who otherwise work on non-Windows devices.
RDS vs VDI
RDS session hosts and VDI are often presented as rivals, but they're different tools. RDS sessions share one Windows Server OS among many users, which is light on resources and simple to manage — but every user runs the same OS and application set, and one misbehaving app can affect the whole host. VDI gives each user a dedicated VM with their own OS, so users can have different configurations and stronger isolation — but you need far more CPU, RAM, and storage per user.
For task workers running standard office or line-of-business apps, session-based RDS is usually the economical choice. For developers, power users, or anyone needing admin rights inside their own desktop, VDI (or simply a dedicated RDP server per person) fits better.
A note on RDS licensing
RDS has licensing requirements beyond the Windows Server license itself: each user or device connecting through RDS generally needs an RDS Client Access License (CAL), tracked by the RD Licensing role. This is separate from the server license and is a real cost line in any RDS project — it's also the detail most commonly missed by teams planning their first deployment.
Licensing terms change over time and vary by agreement type, so treat this as a heads-up rather than a quote: confirm current RDS CAL requirements with Microsoft's documentation or your licensing reseller during planning, and budget for them alongside the hardware.
When hosted RDP is the simpler choice
Running your own RDS farm means servers to maintain, CALs to track, gateways to secure, and brokers to monitor. That's the right call for an IT department serving dozens or hundreds of staff. But if you just need one Windows desktop that's always online — for trading bots, automation, development, or remote work — a hosted RDP server gives you the remote Windows experience with none of the infrastructure: no CALs to manage, no roles to configure, just login credentials and a desktop.
Compare your options on the plans and pricing page, or read the FAQ if you're weighing self-hosted RDS against rented RDP.
Ready for your own RDP server?
Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan. Pay by credit/debit card, bank transfer, Bitcoin or altcoins.
3-day money-back guarantee · Instant setup · 30+ server locations · 99% uptime SLA
Remote Desktop Services: FAQ
Remote Desktop Services is a Windows Server role that lets multiple users connect to Windows desktops and applications over a network simultaneously. It manages user sessions, publishes individual apps via RemoteApp, and includes components like the RD Gateway, Connection Broker, and Licensing roles.
RDP (Remote Desktop Protocol) is the protocol — the language used for a remote desktop connection. RDS (Remote Desktop Services) is the server-side platform built on Windows Server that manages many simultaneous RDP sessions, brokers connections, publishes apps, and handles licensing.
The core role services are RD Session Host (runs user sessions), RD Connection Broker (routes connections and balances load), RD Gateway (secure internet access without VPN), RD Web Access (browser portal for published apps/desktops), and RD Licensing (manages RDS CALs).
RemoteApp is an RDS feature that publishes individual Windows applications rather than full desktops. Users launch an app icon and the program window appears on their local device while actually executing on the RDS server.
Generally, yes — in addition to the Windows Server license, each user or device connecting through RDS typically requires an RDS Client Access License (CAL), managed by the RD Licensing role. Confirm current requirements in Microsoft's documentation, as licensing terms change.
Run your own RDS farm when an IT team needs to serve many users with centralized Windows apps. Rent a hosted RDP server when you simply need one always-on Windows desktop for bots, automation, development, or remote work — with no roles to configure and no CALs to track.
