Complete guide to RDS management and RDSH

Last updated:April 2015

Essential Guide

Browse Sections

Editor's note

With Windows Server 2008 R2, RDS replaced Terminal Services as Microsoft's thin-client technology, enabling users to access desktops virtually.

Remote Desktop Services (RDS) is built into Windows operating systems and allows data to exist in a central location, simplifying management for systems administrators. It consists of six main components, including the Remote Desktop Connection Broker, Remote Desktop Gateway and Remote Desktop Session Host (RDSH). RDSH allows a server to host session-based desktops or RemoteApp programs.

We have all of your RDSH and RDS management questions answered with this comprehensive guide covering features and upgrades, RemoteFX, issues, including printer redirection problems and auto reboot concerns, and more.

1What does RemoteFX add?

RemoteFX has gone through some serious evolution. When it was a part of Windows Server 2008, it was a side product that ran as an option on top of RDP. When Windows Server 2012 hit the market, all that changed. RemoteFX can now run its own coding for VDI, essentially replacing RDP in some cases. Now that it's so prominent, it's important to know what else this feature can do.

2Nobody's perfect: RDS issues

RDS and RDSH are far from perfect. From printer redirection problems to the possibility of losing data during unwanted reboots, there are challenges to overcome. But if your environment is set up right, RDS might just be the simpler VDI alternative that you are looking for. Take a look at some common problems to keep an eye out for.