Most RDS implementations start out with a single server or at least a single RDSH. Once you have the roles established for successful connectivity here, it is a natural next step to add additional RDSH servers to accommodate more users. Or perhaps you want to segregate different types of users (and their applications) onto different RDSH servers. Whatever your reasoning, chances are that at some point you will want to add additional servers into your RDS environment. Let's add a second server to ours so that you can see how this process works.
We have a single RDS server online, running Windows Server 2016. It is named RDS1 and is already performing the roles of RD Connection Broker, RD Session Host, and RD Web Access. We will now use the management interface on RDS1 in order to add a second RDSH server to our infrastructure. The name of our new server is RDS2, and it is already joined to our domain.