Nowadays, it is quite common to see RDS environments in companies. Generally for small structures (with fewer than 30 users) a single server is sufficient. However, in the case of a larger number of simultaneous users, slowdown can occur despite increasing hardware configuration, and it may be complicated to upgrade the architecture in the event that the number of users increases.
Therefore, if you want to set up a scalable solution that can handle a very large number of simultaneous connections, it will be necessary to set up an RDS Farm which involves separating the various services (broker, license server, session host, etc…) into several servers. This will also allow you to create a pool of RD Session Host servers that will handle the users. And this is exactly what we will see in the article below.
Here is the architecture that we will put in place.
We can either install our RDS architecture from the PowerShell command line or from the graphical interface.
PS C:\> Add-WindowsFeature -Name RDS-Connection-Broker,RDS-Licensing,RDS-RD-Server -IncludeManagementTools -Restart
PS C:\> Import-Module RemoteDesktop
PS C:\> New-RDSessionDeployment -ConnectionBroker broker.std.local -WebAccessServer broker.std.local -SessionHost rds01.std.local
Once installed we need to configure.