Deploying Remote Desktop Services (RDSH) in a Workgroup (without Domain)

This article illustrates the process of setting up and arranging a Remote Desktop Session Host terminal server role on a standalone server running Windows Server 2019/2022 in a workgroup environment, devoid of any accompanying roles such as Connection Broker, Remote Desktop Web Access, or RDS Gateway. This will be a single server RDS deployment on Windows Server 2019/2022.

How to Install Remote Desktop Services Role on Windows Server 2019/2022?

It is supposed that you have already installed Windows Server and configured basic settings (IP address, server name, time/date, installed updates, etc.). Then you can install the RDS role. To do it, you can use either Server Manager or PowerShell.

To install the RDS using Server Manager, select Remote Desktop Session Host and Remote Desktop Licensing in Role-based or Feature-based installation -> Server roles -> Remote Desktop Services

You can also install Windows Server roles using PowerShell:

Install-WindowsFeature -Name RDS-Licensing, RDS-RD-Server –IncludeManagementTools

Check which RDS roles are installed on your server:

Get-WindowsFeature -Name RDS* | Where installed

Configure Remote Desktop Licensing Role and Add RDS Licenses (CALs)

The next step is to configure the Remote Desktop Licensing role, which provides licensing for user RDP connections. You can install and activate Remote Desktop Licensing on this host or place the RDLicensing role on another server. One server with the RDS Licensing role can issue licenses to any number of RDS hosts.

The Remote Desktop Licensing role is used to manage licenses for users who connect remotely to a remote desktop server. This role enables administrators to assign licenses to users and control their usage. Without an active Remote Desktop Licensing role, users will not be able to access the remote desktop server.

Configure Remote Desktop Session Host in a Workgroup

Go to Control Panel -> System and Security -> Administrative Tools -> Remote Desktop Services -> Remote Desktop Licensing Diagnoser. Note that your server is not yet configured to receive RDS CALs from the licensing server. The following messages prove it:

• The licensing mode for the Remote Desktop Session Host server is not configured
• Number of licenses available for clients: 0

Configure RDS licensing settings with the Local Group Policy Editor (gpedit.msc):

1. Go to Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing;
2. Change Set the Remote Desktop licensing mode to Per Device;
3. In Use the specified Remote Desktop license servers option, specify the IP address of the server RDLicensing server is installed on. If the licensing server is installed locally, enter localhost or 127.0.0.1;
   
4. In Set the Remote licensing mode option, specify the licensing mode for the RD Session Host server, select Per Device;
   
5. Update local Group Policy settings and run the Remote Desktop Licensing Diagnoser. Make sure that it sees your RDS CALs.