rss logo

How set up a Windows RDS Farm architecture

Microsoft logo

Nowadays, it is quite common to see RDS environments in companies. Generally and for small structures (less than 30 users) a single server is sufficient. But in the case of a larger number of simultaneous users, slowdown can occur despise the increase in 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 take the load of a very large number of simultaneous connections, it will be necessary to set up an RDS Farmwhich consists of separating the various services (broker, license server, session host, etc…) into several servers. This will also allow to create a pool of RD Session Host servers that will take care of the users. And this is exactly what we will see in the article below.

RDS Farm Architecture

Here is the architecture that we will put in place.

RDS Farm Architecture.

Install (broker.std.local)

We can either install our RDS architecture from the PowerShell command line or from the graphical interface.

Install from GUI

Add servers to managed

  • From Server Manager do a right click to All Servers > Add Servers :
  • Add Servers :

Install

  • Still from Server Manager go to Manage > Add Roles and Features :
  • At the first windows click Next :
  • Choose Remote Desktop Services installation :
  • Choose Standard deployment :
  • Select Session-based dektop deployment :
  • Simply click Next :
  • Add the broker server :
  • Also add the broker server as the RD Web Access server :
  • Now add the RDS servers as Hosts servers :
  • Check the Restart the destination box and click Deploy to install :

Install with PowerShell

  • Install RDS Services via PowerShell :
PS C:\> Add-WindowsFeature -Name RDS-Connection-Broker,RDS-Licensing,RDS-RD-Server -IncludeManagementTools -Restart
  • Then deploy via PowerShell :
PS C:\> Import-Module RemoteDesktop
PS C:\> New-RDSessionDeployment -ConnectionBroker broker.std.local -WebAccessServer broker.std.local -SessionHost rds01.std.local

Post-Install

Once installed we need to configure.

RD Licensing (broker.std.local)

  • From Server Manager go to Remote Desktop Services > Overview and click to RD Licensing icon to add a Licensing Server :
  • Select the broker server as the RD Licensing server :
  • Click Add :
  • Then Close :

Adding RD Session Host Servers

  • From the Deployment Overview, do a right click to RD Session Host and click to Add RD Session Servers :
  • Add the others RDS servers :
  • Check the Restart remote computers box and click to Add :
  • Once installed we can close the Window :

Set Users Profiles Share (rdsprofiles.std.local)

  • Do a right click on the User_Profiles folder and go to Properties :
  • Then set the share as shown here :

Create Collection

  • From the Deployment Overview, do a right click to RD Session Host and click to Create Session Collection :
  • Click Next :
  • Give a name to the RDS Collection :
  • Add the RDS Servers to the Collection :
  • Specify the user groups that should connect to the RDS farm :
  • Specify the folder share that we previously set up on the RDSPROFILES server :
  • Click Create :
  • Then Close once all operations are terminated :

Add DNS entry (AD Server)

  • Open the DNS Manager console from an Active Directory server :
  • From the domain zone, add new Host (A) DNS entries :
  • For example with three RDS Session Host :

Client Connection

  • The client will use the rdsfarm dns entry to connect to one of the RDS Session Host :
Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Contact :

contact mail address