When setting up RDS you have the option of running the three core roles run on a single server or separate each role onto its own server. The RDS License role handles the licensing for RDS.įor additional reading about the roles for RDS check out the Microsoft RDS Overview Installing RDS Roles: When the trial period ends RDS will no longer accept connections. Licensing: RDS comes with a 120 day trial period.Remote Desktop Virtualization Host : This allows RDS integration with a Hyper-V hypervisor to manage virtual desktops.Remote Desktop Gateway : 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.The follows roles are not required but add additional abilities to RDS: Also allows Windows 7 & 8 desktops to connect using the RemoteApp and Desktop Connection. Remote Desktop Web Access : This role provides a web portal to access the RDS environment.Also allows disconnected users to reconnect to their existing sessions without starting a new one. Remote Desktop Connection Broker : This role handles user sessions by load balancing among the RD Session Host servers.Remote Desktop Session Host : Applications are installed and published from the Session Host servers.There are three core roles to setup a RDS environment and are as follows: Setup RD Gateway Role on Windows Server 2012 R2.Setup RD Licensing Role on Windows Server 2012 R2.Setup Remote Desktop Services in Windows Server 2012 R2.In this post I will document the implementation of RDS in my home lab using an ‘all-in-one’ configuration. Microsoft RDS is the new expanded and renamed Microsoft Terminal Services. Microsoft Remote Desktop Services allows users to access centralized applications and workstations in the data center remotely.
0 kommentar(er)
