In this article, I will explain the step-by-step roll-out of a Windows 2012 R2 / 2016 RDS farm with the following features:
- Remote Desktop Session Host (x2)
- Service broker for distribution of connections
- Setting up a collection;
- Publishing RemoteApp on a web portal;
- Remote Desktop Gateway
- User Profile Disk (UPD)
To set up a complete rds farm, you need at least 4 servers without counting the domain controller and file and print server. All the servers on the farm must be in the field.
|LAB-RDS1.rdr-it.intra||172.16.0.184||Remote Desktop Session Host|
|LAB-RDS2.rdr-it.intra||172.16.0.185||Remote Desktop Session Host|
|LAB-RDS-BRK.rdr-it.intra||172.16.0.186||Service Broker / License Manager|
|LAB-RDS-GW-WEB.rdr-it.intra||172.16.0.187||Gateway Remote Desktop / Web Access|
For the realization of this lab, I also used an AD server, LAB-AD1.rdr.it.intra with the IP address 172.16.0.100. DC will also be used to store UPDs.
Server role definitions that are part of an RDS farm.
Remote Desktop Session Host: On these servers, the user sessions are open and allow them to work.
Service broker: This is the circulation agent for sessions in an environment with multiple remote desktop session hosts.
Remote Desktop Gateway: Its primary role is to provide secure access to the RDS infrastructure from the Internet. It connects to the farm using the HTTPS protocol and filters connections using access policy.
License Manager: This service is used for license distribution (CAL RDS).
The whole Lab was done under Windows 2012R2. The deployment of an RDS farm under Windows 2016/2019 is almost identical.