This website is an independent fan project dedicated to the Remote Desktop Connection client and is not an official Microsoft resource.
Before RDP: The Age of Dumb Terminals and Text Screens
The story of Remote Desktop Connection begins long before Windows dominated desktops. In the 1980s and early 1990s, the idea of working on a computer that stood somewhere else was already familiar to anyone who had used a mainframe or a Unix workstation: users sat at simple terminals and sent commands to a central machine that did all the real work. Those early systems delivered text, not pictures, and they required technical knowledge that ordinary office workers simply did not have.
The dream that drove the next decade of engineering was easy to state and hard to build: give a person at a slow machine the full graphical experience of a powerful one over a modest network link. Sending raw screen data across a network was hopelessly inefficient, so researchers concentrated on smart encoding — transmitting only what changed on screen, compressing repeated patterns, and caching frequently drawn elements. Every remote access tool you use today, including the Remote Desktop Connection client, is a direct descendant of that research.
Microsoft watched this space carefully. Windows was becoming the universal interface of business computing, and the company understood that if graphical work environments were to survive the transition to networks, they would need a graphical remoting protocol of their own — not a text terminal, but a way to project the entire Windows desktop across a wire.
Citrix Roots and the Birth of the RDP Protocol
The pivotal chapter is one of the more interesting licensing stories in software history. In the mid-1990s, a company called Citrix Systems had built MetaFrame, a product that remoted Windows sessions from multi-user NT servers to lean clients, based on its own protocol technology. Microsoft, which had been developing a multi-user version of Windows NT of its own, chose cooperation over competition: in 1997 the two companies signed an agreement under which Microsoft licensed Citrix's core remoting technology.
Out of that licensing deal came two siblings. Citrix kept and extended its protocol as ICA, while Microsoft developed its own protocol for Windows NT Server 4.0 Terminal Server Edition, released in 1998: the Remote Desktop Protocol, or RDP. The first Microsoft client that spoke it was called the Terminal Services Client, and it allowed a low-powered desktop to run a full Windows session hosted on a central server. For many businesses, this was revolutionary — a room full of aging PCs could suddenly behave like brand-new machines.
RDP kept evolving at a rapid pace. Version 4.0 in the Terminal Server Edition was followed by 5.0 with Windows 2000, which brought the client its recognizable modern character. Windows XP introduced version 5.1 with better color depth, local printer support, and the ability to share the console session. Each release narrowed the gap between sitting at the remote machine and sitting somewhere else, and each release pushed the client further into everyday use.
The Client Gets Its Name: mstsc Becomes Remote Desktop Connection
With Windows XP in 2001, Microsoft polished and renamed its client for the consumer audience: Terminal Services Client became Remote Desktop Connection, launched from the executable mstsc.exe that administrators still type today. Suddenly ordinary home and office users had a friendly window where they could type a computer name, enter their Windows credentials, and land on their own desktop from anywhere on the network.
The years that followed turned the client into a complete professional tool. Windows XP Professional allowed incoming connections directly, so a home PC could be reached from the office. Windows Server 2003 brought RDP 5.2 with driver redirection and genuine multi-monitor thinking on the server side; Vista delivered RDP 6.0 with Network Level Authentication, a security milestone that verifies the user before any session resources are committed. Windows 7 added RDP 7.0 with smooth multimedia and true multi-monitor redirection, and subsequent releases layered on better compression, RemoteFX graphics, and gateway integration.
Just as important was what surrounded the protocol. Microsoft introduced the Remote Desktop Gateway so that sessions could traverse the internet through a single encrypted HTTPS channel, the Remote Desktop Session Host for multi-user server workloads, and the portable .rdp file format that lets users save a fully configured connection and reopen it with one click. The client stopped being a mere viewer and became the front door of an entire remote work architecture.
A Quiet Constant in a Loud Industry
The decades after Windows XP saw an endless parade of commercial remote access products arrive with flashy marketing and subscription pricing. Remote Desktop Connection survived them all by standing still in the best possible sense: it stayed free, stayed built in, and stayed honest about what it does. Administrators never abandoned it because no competitor could match the simplicity of a tool that speaks Windows' own language, logs in with Windows' own credentials, and is managed through Windows' own policies.
The ecosystem also grew beyond the desktop. Microsoft shipped official RDP clients for macOS, iOS, and Android, which meant a Windows machine could be operated from an iPad on a train or a MacBook in a coffee shop. Enterprise products such as Remote Desktop Services, Azure Virtual Desktop, and cloud-based Windows instances all kept using the same protocol underneath, so the skills a person builds with the classic client transfer directly to modern cloud environments — a rare continuity in this industry.
Today the client that launched as Terminal Services Client more than twenty-five years ago is still one of the most-used utilities on Earth. Millions of help-desk tickets, server reboots, late-night deployments, and remote workdays pass through it daily, and the vast majority of those sessions begin the same way they did in 2001: someone types a computer name, presses Enter, and the distant desktop appears.
Looking Ahead
The history of Remote Desktop Connection is a reminder that the best tools are the ones that quietly refuse to disappear. Born from a licensing deal, matured through twenty-five years of protocol revisions, and now extended toward cloud desktops, RDP has outlasted trends that once promised to replace it. As hybrid work cements itself and graphics-heavy applications move into remote sessions, the client's role will only deepen. Our prediction as fans is simple: in another decade, people will still be typing mstsc into the Start menu — and it will still just work.