In the simplest case, you can deploy a standalone server with the Remote Desktop Session Host (RDSH) role without the Connection Broker and RDS Web Access. In our small RDS deployment, there are only three Windows Server hosts with the following roles:

Remote Desktop Licensing (RD Licensing) - a licensing service for managing RDS licenses (CALs).

RD Web Access (RDWA) – a web interface to access remote desktops and RemoteApps.

Remote Desktop Gateway (RDGW) – provides secure access to the RDS farm from the Internet.

It is used to manage an RDS farm, distribute the workload, reconnect users to their sessions, store RDS collection settings, and published RemoteApps

Remote Desktop Connection Broker (RDCB) – an RDS connection broker.These are the main workhorses of an RDS farm on which user apps run

Remote Desktop Session Host (RDSH) – RDS session hosts.The RDS role in Windows Server includes the following components: Remote Desktop Services (RDS) Components Architecture How to Deploy Remote Desktop Services Farm Using PowerShell?.How to Publish RemoteApps in Remote Desktop Services?.Create Remote Desktop Services Collections on Windows Server.Creating a New RDS Deployment on Windows Server.Remote Desktop Services (RDS) Components Architecture.

Remote desktop management