In my install it rebooted after the Remote Desktop Services role but did not for Session Collection and RemoteApp. Here is what the progress window looks like.
Click NextĬheck the box labeled Restart the destination server automatically if required then click Deploy Since we did the Quick Start selection the Connection Broker, Web Access and Session Host roles will be installed on the single server. Change selection to Session-based desktop deployment and click Next We are setting up application publishing. Either option will allow you to grow with your environment! If you pick a Quick Start setup you can add additional servers to each role to allow expansion. If you have a large number of users you will run through the Standard deployment where the three core services run on separate servers. In my environment I will have the three core RDS roles running on a single VM (all-in-one con. To start open Server Manager then click Manager -> Add Roles and FeaturesĬhange the selection to Remote Desktop Services Installation then click Next No matter which setup you pick they both can scale outward depending on user growth.įor my documentation I went with a single server called a Quick Start setup. If your environment is large you will want to separate these roles to spread the resources across multiple servers. If you are setting RDS up for a lab or a small environment then a all-in-one setup would save you hardware resources. 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. Please remember to mark the replies as answers if they help.Microsoft Remote Desktop Services allows users to access centralized applications and workstations in the data center remotely. Therefore, I suggest you create a domain and join the server into the domain to perform further tests.
Most of the old powershell commands and GUI programs that would have allowed you to configure/manage a standalone RDSH server have This includes most (if not all) of the new powershell commands and server manager. The thing to keep in mind is that most of the tools provided to make managing/configuring RDSH servers easier in 2012 will not work Now, it is not impossible to have a RDSH server that is not joined to a domain and/or not a member of a collection. Same is true for Virtual Desktops (VMs), they are designed to be managed as a collection. "Server 2012 RDS is designed under the basic premise that RDS servers will be joined to a domain, at least one RD Connection Broker will be present, and that RDSH servers will be managed as a collection using Server Manager (and/or powershell). Please check TP's comment within this thread below: