Windows Server 2008 R2 significantly enhanced Remote Desktop Services (formerly Terminal Services), making it a compelling platform for delivering applications to remote users. RDS allows organizations to centralize application management while giving users access from virtually any device with a Remote Desktop client.
RDS Architecture and Deployment
A full RDS deployment consists of several role services: the RD Session Host runs the applications, the RD Connection Broker distributes sessions across multiple hosts, the RD Web Access provides a browser-based portal, and the RD Gateway enables secure access over HTTPS without VPN requirements.
RemoteApp is a key feature that presents individual applications in their own resizable windows on the client desktop, rather than showing a full remote desktop session. Users interact with remote applications as if they were running locally, complete with taskbar integration and file association. This provides a much more natural user experience than traditional full-desktop RDP sessions.
Plan your Session Host server capacity by estimating concurrent user counts and per-user resource requirements. A general guideline is 4 GB of RAM plus 250 MB per concurrent user session, though resource-heavy applications like CAD or development tools require more. Use RD Connection Broker with session load balancing to distribute users across multiple Session Hosts for scalability and redundancy.