What Is RDS? Remote Desktop Services Explained for Business Owners

• Last updated: 29 July 2026
• Cloud Desktop,Virtual Desktop
• Written by Editorial Team

Remote Desktop Services (RDS) is a Windows Server technology that lets multiple people log in to one central server and each work in their own Windows session, from any device, anywhere. Instead of every employee needing a powerful office PC, the applications and files run on the server, and each user simply connects to it. It is the technology behind what many businesses still call their terminal server.

One quick clarification before we go further: this article is about Microsoft Remote Desktop Services. If you searched for Amazon RDS, that is an unrelated Amazon Web Services database product that happens to share the acronym.

What Is Remote Desktop Services (RDS)?

RDS is a role built into Windows Server that turns one server into a shared workspace for many users. Each person who connects gets their own session: their own desktop, their own open applications, and their own files, all running side by side on the same machine without interfering with each other.

If the concept sounds familiar, that is because it is not new. Microsoft introduced this technology as Terminal Services in the 1990s and renamed it Remote Desktop Services with Windows Server 2008 R2. The name changed, the idea did not: centralize the computing on a server, and let people reach it from anywhere. Thousands of businesses still run accounting software, ERP systems, and line-of-business applications this way, because it solves a stubborn set of problems in one move: everyone works on the same version of the software, data never leaves the server, and a lost laptop does not mean lost files.

How Does RDS Work?

A working RDS environment is a set of server roles that cooperate. You do not need to memorize them, but knowing the names helps when talking to IT people or providers:

• RD Session Host: the workhorse. This is the server your users actually log in to and where their applications run. Larger environments run several session hosts side by side.
• RD Connection Broker: the traffic director. It decides which session host a user lands on and reconnects them to their existing session if they drop off.
• RD Gateway: the secure front door. It lets users connect over the internet through an encrypted connection without exposing the server directly.
• RD Web Access: a browser page where users can see and launch their published desktops and applications.
• RD Licensing: the bookkeeper. It tracks the client access licenses (CALs) that every connecting user or device requires.

When an employee opens their laptop at home and connects, the gateway checks their credentials, the broker finds their session, and the session host does the actual computing. To the user it just looks like Windows. All the complexity lives on the server side, which is exactly the point, and it is also why the question of who manages that server side matters so much. Businesses that want the benefits without operating those roles themselves typically use a remote desktop hosting provider, where the entire stack arrives already built, licensed, and monitored.

What Is the Difference Between RDS and RDP?

These two acronyms get mixed up constantly, and the distinction is simple:

• RDP (Remote Desktop Protocol) is the language of the connection. It is the protocol that carries your screen image one way and your keyboard and mouse the other way.
• RDS (Remote Desktop Services) is the platform that uses RDP to serve many users at once, with sessions, load balancing, licensing, and management around it.

The Remote Desktop feature built into Windows on your office PC is plain RDP: one person connecting to one machine that still has to be powered on, patched, and sitting in your office. RDS is what you graduate to when five, fifteen, or fifty people need that kind of access and you want it managed properly rather than through a tangle of individual PC connections.

What Do Businesses Actually Use RDS For?

The pattern across industries is remarkably consistent: RDS shows up wherever several people need the same Windows applications and the same data, reliably, from more than one location.

• Accounting and tax firms run QuickBooks, Sage, Drake, and UltraTax on a session host so the whole team works in the same company files simultaneously, including seasonal staff who join for a few months and leave.
• Law and professional services firms keep case management and document systems on the server so client data never lives on a personal laptop.
• Businesses with legacy applications use RDS to keep an older Windows program alive and centrally managed long after it stopped being practical to install on every new PC.
• Companies with branch offices or remote staff give everyone an identical work environment regardless of what device or location they connect from.
• Seasonal and project-based teams add users for the busy months and remove them afterward, paying only for active seats instead of buying hardware that sits idle half the year.

What Is RemoteApp?

Not everyone needs a whole remote desktop, and RDS has an answer for that too. RemoteApp is an RDS feature that publishes a single application instead of a full desktop. The program runs on the session host, but on the user’s screen it opens in its own window, sitting alongside their local applications as if it were installed on their machine.

This solves a specific and common situation: a team that lives in local tools like email and a browser but needs one central Windows application, say the accounting system or an industry database, available to everyone. Publishing just that application keeps the experience simple for users, reduces the resources each session consumes on the server, and narrows what a user can touch, which security teams appreciate. Many businesses run a mix: full desktops for staff whose whole day happens in the hosted environment, RemoteApp for everyone who only dips into one or two programs.

What Are RDS CALs, and Why Does Licensing Trip People Up?

Enabling the RDS role on Windows Server is free. Using it is not. Every user or device that connects needs a Remote Desktop client access license, an RDS CAL, purchased on top of the Windows Server license. CALs come in two flavors: per user (a named person connects from any number of devices) and per device (a specific machine, used by any number of people, such as a shared shift workstation).

This is the part of RDS that generates the most grief in-house. CALs must be bought in advance, tracked as staff come and go, and defended in a Microsoft audit. Under-licensing creates compliance risk; over-licensing wastes money on seats nobody uses. It is also the part that disappears entirely under a hosted model, where licensing is bundled into the monthly per-user fee through the provider’s service agreement with Microsoft. We will break down CAL types and real costs in a dedicated guide.

How Does RDS Compare to VDI and Cloud PCs?

RDS is one of three broad ways to deliver Windows remotely, and knowing which is which prevents expensive mismatches:

• RDS (shared sessions): many users share one server, each in their own session. The most economical model per user, ideal for standard business applications. Its main constraint is that users share the machine’s resources, so one person’s very heavy workload can be felt by neighbors on an undersized server.
• VDI (individual virtual machines): every user gets their own complete virtual Windows machine, the model behind most virtual desktop hosting plans. Stronger isolation and per-user performance, at a higher cost per seat and considerably more infrastructure to operate.
• Cloud PCs (Windows 365 and similar): Microsoft’s subscription take on the personal cloud desktop, a fixed-spec machine per user at a fixed monthly price, with simplicity as the selling point and less room for customization.

For most small and mid-sized businesses running office, accounting, and line-of-business software, RDS sessions deliver the best price for the performance, which is why the model has outlived every prediction of its demise. The individual-machine approaches earn their premium when users need admin rights on their own machine, run resource-hungry applications, or have isolation requirements that shared sessions cannot meet.

Should You Run RDS In-House or Use a Hosted Provider?

An honest comparison, because in-house RDS is the right answer for some organizations:

Running it yourself makes sense when you already have Windows Server expertise on staff, you own recent server hardware with capacity to spare, and your user count is stable enough that CAL planning is straightforward. The technology is mature and well documented, and complete control stays in your hands.

Hosted RDS makes sense when any of those conditions fail: the terminal server is approaching another expensive refresh, nobody on the team enjoys patching Windows Server at 11 pm, headcount swings with the seasons, or an audit letter about CALs would cause a scramble. A hosted desktop environment converts the hardware, licensing, security, backups, and support into one flat monthly fee per user, deployed in days rather than the weeks a new in-house build takes.

The economics usually come down to scale and staffing. A ten-person firm with no IT department almost always comes out ahead hosted. A three-hundred-seat company with a capable infrastructure team may not. In between, it is worth pricing both honestly, including the hours your people spend keeping the in-house version alive.

Frequently Asked Questions About RDS

1. Is RDS the same as RDP?

   No. RDP (Remote Desktop Protocol) is the communication technology that carries your screen, keyboard, and mouse between devices. RDS (Remote Desktop Services) is the Windows Server platform that uses RDP to deliver desktops and applications to many users at once. Every RDS environment uses RDP, but a simple one-to-one RDP connection is not RDS.

2. Does RDS come included with Windows Server?

   The RDS role is built into Windows Server and can be enabled at no extra software cost. However, using it beyond the trial period requires Remote Desktop client access licenses (RDS CALs) for every user or device, purchased separately from the Windows Server license itself.

3. How many users can connect to one RDS server?

   There is no fixed limit in the software. The practical number depends on the server’s processor, memory, and what applications people run. Light office work supports far more concurrent users per server than heavy accounting, database, or design workloads, which is why session hosts are sized to the team using them.

4. Is RDS still supported by Microsoft?

   Yes. Remote Desktop Services remains a supported role in current versions of Windows Server, including Windows Server 2025. Microsoft also offers cloud-native alternatives such as Azure Virtual Desktop and Windows 365, but classic RDS continues to run a large share of business remote-access environments.

5. What replaced Terminal Services?

   Nothing replaced it; it was renamed. Microsoft rebranded Terminal Services as Remote Desktop Services starting with Windows Server 2008 R2. If you still run what your team calls a terminal server, you are running an early generation of the same technology described in this article.