Anatomy of an RDS server deployment
When IT people say "RDS server," they rarely mean one machine. A production deployment is a set of Windows Servers, each running one or more RDS role services, fronted by the network. A minimal setup might combine every role on two servers for redundancy; an enterprise farm spreads roles across dedicated machines behind a load balancer.
The reason for the split is separation of concerns: the servers users actually log into (Session Hosts) are isolated from the servers that admit traffic (Gateway), route connections (Broker), and track licenses (Licensing). If a Session Host needs rebooting for patches, the rest of the farm keeps brokering connections.
For background on the platform itself, see our Remote Desktop Services explainer — this page goes deeper into the technical pieces.
The role services in detail
| Role service | Technical job | Scaling notes |
|---|---|---|
| RD Session Host | Runs the Windows multi-session kernel; hosts user sessions, published desktops, and RemoteApp programs. | Scale out by adding hosts; size CPU/RAM per concurrent user profile. |
| RD Connection Broker | Maintains the session directory, routes new connections, reconnects dropped sessions to the right host. | Run redundantly — if the broker is down, reconnection breaks. |
| RD Gateway | Encapsulates RDP in HTTPS so remote users connect without a VPN; enforces connection authorization policies. | Place at the network edge; pair with a certificate from a trusted CA. |
| RD Web Access | IIS-based portal listing published resources; launches .rdp files or RemoteApp via the browser. | Often co-located with the Gateway. |
| RD Licensing | Issues and tracks RDS CALs (per-user or per-device); enforces the grace period for unlicensed servers. | One licensing server can serve the whole farm; back up its database. |
On the Session Host, the multi-session kernel is what makes RDS different from a desktop OS: Windows Server is built to keep dozens of interactive sessions isolated in one OS instance, with per-session namespaces for registry, devices, and window stations. That's why RDS requires Windows Server — desktop Windows is licensed and engineered for a single interactive user.
How a user session flows
Follow a remote user connecting to a published desktop:
- Client connects to the RD Gateway over HTTPS. The gateway checks the user's credentials and connection authorization policy.
- The Gateway forwards the RDP stream internally to the Connection Broker (or directly to a host in tiny deployments).
- The Broker checks its session directory: does this user already have a disconnected session on a host? If yes, the user is reconnected there — their open apps are exactly as they left them.
- If no existing session, the broker picks the least-loaded Session Host in the collection and the logon proceeds there.
- The Session Host creates the session, applies Group Policy, maps printers/drives per policy, and presents the desktop or RemoteApp.
- RD Licensing is consulted to issue or validate the CAL for the connecting user or device.
When the user disconnects (rather than logging off), the session stays alive on the host for a configurable timeout — which is why "reconnect to my session" works after a dropped VPN or a laptop lid closing.
Ports and protocols
RDS traffic ultimately rides on RDP, which uses TCP port 3389 by default. In a gateway deployment, external clients only need HTTPS (TCP 443) to reach the RD Gateway — the gateway translates between the external HTTPS stream and internal RDP. This is a major security win: you never expose 3389 directly to the internet.
Internally, Session Hosts, the Broker, and the Licensing server communicate over standard Windows networking (RPC, SMB, and RDP between roles). Keep the role servers on a trusted internal segment, patch them like any server fleet, and enforce Network Level Authentication (NLA) so sessions authenticate before the desktop loads.
Security note: Exposing raw RDP (port 3389) to the internet invites brute-force login attempts. Always front RDS with the RD Gateway (or a VPN), require NLA, and use strong, unique passwords plus account lockout policies.
Deployment checklist
Before rolling out an RDS server farm, work through this list:
- Size the Session Hosts for your user profile — office workers, developers, and CAD users need very different CPU/RAM per session. Pilot with a representative group first.
- Plan licensing early: Windows Server licenses plus RDS CALs (per-user vs per-device — pick the model matching how people connect), plus CALs for the applications you publish.
- Deploy the Gateway with a real certificate from a trusted CA; self-signed certs train users to click through warnings.
- Make the Broker and Licensing redundant (or at least backed up) — they're small but load-bearing.
- Configure Group Policy for session timeouts, drive/printer redirection, and RemoteApp publishing before users arrive.
- Test the full external path — Gateway, broker routing, reconnection after a dropped session, and printing — from outside the corporate network.
- Set up monitoring for host CPU/RAM, session counts, and licensing grace-period warnings.
Common RDS use cases
RDS shines wherever Windows applications must be centralized: call centers and task workers sharing a standard app set; branch offices running line-of-business software hosted at HQ; contractors and BYOD scenarios where data must never leave the datacenter; legacy applications that only run on Windows and can't be rewritten; and regulated industries where central control, auditing, and data residency matter.
It's a weaker fit for developers needing local admin, GPU-heavy workloads (see dedicated GPU servers), or single users who just want a personal always-on Windows box.
RDS server vs hosted RDP
An RDS server farm is infrastructure you own: you buy the servers, track the CALs, patch the roles, and monitor the farm. A hosted RDP server is the opposite trade — you rent one Windows server, get login credentials, and skip every role above. For a single user or a small team needing always-on Windows desktops (trading, automation, development, remote work), hosted RDP delivers 90% of the practical benefit with roughly 1% of the administration.
If that sounds like your situation, browse the plans and pricing page — and if you're still weighing the two paths, the FAQ covers common decision points.
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
RDS Server: FAQ
An RDS server is a Windows Server configured with the Remote Desktop Services role, allowing multiple users to connect to desktops and applications remotely at the same time. In practice it is usually a small farm of role services: Session Hosts, a Connection Broker, a Gateway, and Licensing.
RDS ultimately uses RDP on TCP port 3389 internally. In a gateway deployment, external clients connect to the RD Gateway over HTTPS (port 443), and the gateway proxies the RDP traffic — port 3389 is never exposed directly to the internet.
A regular (hosted) RDP server is a single Windows machine you rent and log into remotely. An RDS server is infrastructure you build and manage yourself to serve many simultaneous users, with session brokering, gateways, published apps, and CAL licensing.
Yes, in addition to Windows Server licenses — each user or device connecting through RDS typically requires an RDS Client Access License, tracked by the RD Licensing role. Confirm current terms in Microsoft's documentation, as licensing changes over time.
No — exposing raw RDP to the internet invites brute-force attacks. Always front RDS with the RD Gateway (HTTPS/443) or a VPN, require Network Level Authentication, and enforce strong passwords and lockout policies.
When you need one or a few always-on Windows desktops rather than infrastructure for dozens of users. Hosted RDP gives you login credentials and a working desktop with no roles to configure, no CALs to track, and no farm to monitor.
