Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Article Number: 000217251

How To - Standard Remote Desktop Services Deployment - Step by Step

Summary: This step-by-step guide covers how to setup Remote Desktop Services in a domain, with the various RDS roles distributed amongst several servers. Both GUI and PowerShell methods are explained. The corresponding video demonstrates the process. ...

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content

Instructions

General Prerequisites
  • Existing functional active directory domain.
  • Servers hosting RDS roles should be joined to the domain.

For more information about the various RDS roles, visit:
https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-roles This hyperlink is taking you to a website outside of Dell Technologies.

Step 1 - Deploy the RDS Environment - Prepare the Servers:
  1. In Server Manager, on the computer that will become the RDS Connection Broker for the deployment, on the left pane, right click the All Servers node and then click Add Servers.
Server Manager. Add Deployment Servers to the Dashboard.
Figure 1: Add deployment servers to the Server Manager Dashboard.
  1. Click “Find Now” and then shift the servers of the deployment to the right hand side and click Ok.
Add deployment servers to the Server Manager Dashboard.
Figure 2: Add deployment servers to the Server Manager Dashboard.
  1. Still in Server Manager, click Manage and Add Roles and Features.
  2. On the Before you begin screen, click Next.
  3. Select the Remote Desktop Services installation ratio button and then Next.
Select Remote Desktop Services installation.
Figure 3: Select the installation type.
  1. On the Select deployment type screen, click the Standard Deployment ratio button  and then Next.
Select Standard Deployment.
Figure 4: Select the deployment type.
  1. On the "Select deployment scenario" screen, select Session based deployment and then Next.
Choose Session-based desktop deployment.
Figure 5: Select the deployment scenario.
  1. Click Next on the Review role services screen.
  2. In the Specify RD Connection Broker server, pick the server that will be the connection broker for the deployment and move it to the right hand side and click Next.
Specify the connection broker server for the deployment by moving it to the right hand side.
Figure 6: Specify the RD Connection Broker for the deployment.
  1. On the Specify RD Web access server screen, select the applicable server and again move it to the right hand side and click Next.
Specify the Web Access server for the deployment by moving it to the right hand side.
Figure 7: Specify the RD Web Access server for the deployment.
  1. On the Specify RD Session Host servers screen, move to the right hand side the servers that will be the Session Hosts in the deployment. Click Next one more time.
Specify the Session host servers for the deployment by moving them to the right hand side.
Figure 8: Specify the RD Session Hosts servers for the deployment.
  1. Click to check the "Restart the destination server automatically if required" box and then click Deploy.
Confirm all by clicking Deploy.
Figure 9: Deploy the selected options.
  1. At the completion screen click Close.

Deploy the RDS Environment - Review the Deployment:
  1. Still in Server Manager (of the computer that was configured as the connection broker), click "Remote Desktop Services" on the left navigation pane.
  2. Review the deployment properties displayed under "Deployment Overview" and "Deployment Servers".
  3. Notice that no server has been configured as an RDS license server. This RDS role is installed separately.
Overview of the RDS dashboard.
Figure 10: Review the deployment.

Deploy the RDS Environment - Install and Configure the RDS License Server:
  1. Under "Deployment Overview", click the green plus sign for the RD Licensing role.
  2. On the Select a Server screen, click the applicable server. This demo uses the domain controller as the RD Licensing Server. Move the selected server to the right hand side and click Next.
Specify the license server for the deployment by moving it to the right hand side.
Figure 11: Select the RD License Server for the deployment.
  1. Click Add on the Confirm selections screen.
  2. Wait for the installation of this role to complete and click Close.
  3. Back in Server Manager, under Deployment Servers. The server hosting the RD Licensing Role should be listed.
  4. To configure the license server, connect to the server that has been configured as the RD License server (the Domain Controller in this demo).
  5. In Server Manager, click Tools, then Remote Desktop Services and then Remote Desktop Licensing Manager.
Open Remote Desktop Licensing Manager.
Figure 12: Opening Remote Desktop Licensing Manager.
  1. Right Click the Server hostname and then click Review Configuration.
Review Configuration.
Figure 13: Review the deployment.
  1. Note the warning indicating that the RDS License Server must belong to the Terminal Server License Servers group in Active Directory. Click "Add to Group" to fix this warning, then click Continue and then Ok and Ok again.
Click Add to Group.
Figure 14: Configure the RD License Server's group membership in Active Directory.
  1. Open the Services.msc management console, locate the Remote Desktop Licensing service and restart it.
  2. Return to RD Licensing Manager, right click the server name, click Refresh, then right click it again and click Review Configuration. Note that the warning is now gone.
Review Configuration.
Figure 15: Review the deployment.
  1. Right click the server again and click Activate Server.
Click Activate Server.
Figure 16: Activate the RD License Server.
  1. Click Next at the Welcome screen, select the appropriate connection method (Automatic for this demo) and click Next.
Specify the connection method.
Figure 17: Specify the Connection Method.
  1. Enter the Company Information and click Next.
  2. Wait for the server to activate, uncheck “Start Install Licenses Wizard now” and click Finish.
Uncheck "Start Install Licenses Wizard now".
Figure 18: Skip the RD CALs installation wizard.

Note: For more information and guidelines on RDS CALs and how to install them, check out Install and Activate an RDS Session Host without a Connection Broker (Workgroup) - Windows Server 2022 .
  1. Return to the server that has been configured as the RDS Connection Broker for the deployment, in Server Manager, under Deployment Overview, click Tasks and then Edit deployment properties.
In Deployment Overview, click Edit Deployment properties.
Figure 19: Edit the deployment properties.
  1. Click the RD Licensing node and choose the licensing mode (for this demo, “Per User”) and click Ok.
Click RD licensing and then choose Per User licensing mode.
Figure 20: Configure the RD licensing mode for the deployment.


Deploy the RDS Environment - Create a Collection on the RDS Deployment:

A collection holds the Remote Desktop Services resources that will be available to users.
  1. Still in the RDS Connection Broker server, in Server Manager, click on the Collections node to the left, and under Tasks, click Create Session Collection.
Click Create Session Collection.
Figure 21: Create the RDS Collection.
  1. At the Before you begin screen click Next.
  2. Enter a name for the collection and click Next.
  3. At the Specify RD Session Host screen, click to move the applicable RDS Session Hosts servers to the right hand side and click Next.
Specify the Session Hosts servers of the deployment by moving them to the right hand side.
Figure 22: Specify the RDS Session Hosts for the Collection.
  1. At the Specify user groups screen, add the users or groups that will have permissions to connect to this new collection. In this demo, the default group of Domain Users is already selected. Click Next.
Specify the Active Directory users that will have access to the collection and session hosts.
Figure 23: Specify the Active Directory users that will have access to the Collection.
  1. For this demo, click to uncheck "Enable user profile disks" and click Next and then Create.
  2. When the collection is created, click Close.
At the completion screen, click Close.
Figure 23: Complete the Collection creation process.

The deployment is ready to begin receiving connections.

Additional Information - Deploy the RDS Environment. Complete the deployment using PowerShell:

The RDS setup completed above can also be deployed via PowerShell with the following lines (executed on the server that will become the RDS Connection Broker of the deployment):

This first line creates the deployment specifying the Connection Broker, the Web Access Server and with just one RD session host:
New-RDSessionDeployment -ConnectionBroker RDSLab-CB.RDSLab.local -WebAccessServer RDSLab-WA.RDSLab.local -SessionHost RDSLab-SH1.RDSLab.local

The next line adds the second RD session host to the deployment:
Add-RDServer -Server RDSLab-SH2.RDSLab.local -Role RDS-RD-SERVER -ConnectionBroker RDSLab-CB.RDSLab.local

The third line installs the RDS Licensing role on the domain controller:
Add-RDServer -Server RDSLab-DC.RDSLab.local -Role RDS-LICENSING -ConnectionBroker RDSLab-CB.RDSLab.local

The fourth line configures the licensing server and licensing mode for the deployment. This line will ask for confirmation:
Set-RDLicenseConfiguration -LicenseServer RDSLab-DC.RDSLab.local -Mode PerUser -ConnectionBroker RDSLab-CB.RDSLab.local

And the fifth line creates the RDS Collection:
New-RDSessionCollection -CollectionName "Collection1" -SessionHost @("RDSLab-SH1.RDSLab.local","RDSLab-SH2.RDSLab.local") -ConnectionBroker "RDSLab-CB.RDSLab.local"
The five lines needed to complete the RDS deployment of this tutorial executed in PowerShell ISE.
Figure 24: Usage of the New-RDSessionDeployment PowerShell cmdlet.

After adding all of the servers to the dashboard in Server Manager and clicking refresh, the result is the same obtained using the GUI: a newly installed Standard RDS deployment.
 
 

Additional Information

Refer to this video:


You can also view this video on YouTube.

Article Properties

Affected Product

Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022

Last Published Date

02 Nov 2023

Version

2

Article Type

How To

Back to Top