How to properly organize Remote Desktop Services?

Question

Active Directory

Hello!
It is planned to organize the infrastructure on Windows Server 2019 for convenient work with terminal servers.
AD is currently deployed. It is necessary to deploy about 20 servers for different user groups.
There are more devices than users.
Please tell me how best to distribute RDS roles among servers, do I need some additional server to control the rest? What is the best way to license?
And what are the best practices for such a task?

Answer 1

With the specified number of RDSH servers (20):
1. RD Connection Broker in High Availability mode (minimum 2 servers). Will require the use of MS SQL (at least 2 servers in the Availability Group)
2. RD Gateway (if you need access to RDS from outside and / or you are supposed to use HTML5 RDWeb), at least 2 servers for fault tolerance plus settings synchronization (CAP and RAP policies, local settings) NPS) - can be combined on RDCB servers
3. RD Licensing - it doesn't matter, the component can be placed on any server, even on CD
4. RD Web - out of the box comes the old client (classic RDWeb), which uses ActiveX components and works fine only in IE. If you want Remote Desktop in any browser - install HTML5 RDWeb (modern RDWeb), installation requires a client client and RD Gateway - can be combined on RDCB servers. There is one drawback for modern RDWeb - licensing per user (Per User RDS CAL) is required
5. RD Session Hosts - using RDCB, create the necessary collections with the necessary access and other settings and add RDSH servers to them
6. Balancing RDCB, RDWeb, RD Gateway
RDCB, RDWeb, RD Gateway roles can be combined on the same server to reduce the total number of servers.

Answer 2

IMHO. If you need fault tolerance, I would do this: 2 servers under the gateway, 2 under the broker, the rest in the farm. + 1 for the SQL server is for the broker, for fault tolerance, you can also 2 in the Always On availability group. But this is if you want to freeze.