Microsoft Remote Desktop Services [RDS] allows users to access centralized applications and workstations in the data center remotely. Microsoft RDS is the new expanded and renamed Microsoft Terminal Services. In this post I will document the implementation of RDS in my home lab using an ‘all-in-one’ configuration. vBoring Blog Series: Setup Remote Desktop Services in Windows Server 2012 R2 Setup RD Licensing Role on Windows Server 2012 R2 Setup RD Gateway Role on Windows Server 2012 R2 Server Roles in RDS: There are three core roles to setup a RDS environment and are as follows: Remote Desktop Session Host [RDSH]: Applications are installed and published from the Session Host servers. Remote Desktop Connection Broker [RDCB]: This role handles user sessions by load balancing among the RD Session Host servers. Also allows disconnected users to reconnect to their existing sessions without starting a new one. Remote Desktop Web Access [RDWA]: This role provides a web portal to access the RDS environment. Also allows Windows 7 & 8 desktops to connect using the RemoteApp and Desktop Connection. The follows roles are not required but add additional abilities to RDS: Remote Desktop Gateway [RDG]: This role enables remote users to use the Remote Desktop Protocol (RDP) over HTTPS. It is placed on the edge of your network and acts as the entry point to your RDS environment externally. Remote Desktop Virtualization Host [RDVH]: This allows RDS integration … Continue reading Setup Remote Desktop Services in Windows Server 2012 R2