Windows Server 2022 RDS CAL | USER & Device

Windows Server 2022 Remote Desktop Services (RDS, Previously known as Terminal Services): is the capability of Windows server 2022 to provide connectivity to end users to be able to access Windows desktops and applications remotely including delivering individual virtualized applications, providing secure mobile and remote desktop access, and providing end users the ability to run their applications and desktops from the cloud. Windows Server 2022 Remote Desktop Services (RDS) CALs, or Client Access Licenses, are a type of license that allow users to access the Remote Desktop Services of a Windows Server 2022 environment. The RDS CAL is required for each user or device that connects to the RDS environment, and it provides access to the features and functionality of the RDS server. Remote Desktop Services 2022 has numerous advantages compared to the previous version. Easier management of access licenses is of great importance. Windows Server 2022 Remote Desktop Services (RDS) also characterized by forward compatibility. So you can continue to use this program even if a new version of the Windows server should appear. There are two type of Remote Desktop Services Cal:

• RDS User CAL - for every user who accesses the server to use services, regardless of the number of devices they use for that access. Like, Your employees access the corporate network using multiple devices or if there are simply more devices than users in the organization. In this case, you would need to purchase a user CAL for every user who accesses the server, regardless of the number of devices they use for that access.

• RDS Device CAL - for every device that accesses your server, regardless of the number of users who use that device to access the server. Like, Your employees share devices, such as shift workers, or there are likely more employees than devices in the organization. In this case, you would need to purchase a device CAL for every device used to access the server.

If looking for previous/older version Remote Desktop CAL? Please visit: RDS-2019, RDS-2016 & RDS-2012

Deploy A Remote Desktop environment in Windows Server 2022

Use the following steps to deploy the Remote Desktop servers in your environment. You can install the server roles on physical machines or virtual machines, depending on whether you are creating an on-premises, cloud-based, or hybrid environment. If you are using virtual machines for any of the Remote Desktop Services servers, make sure you have prepared those virtual machines.

1. Add all the servers you're going to use for Remote Desktop Services to Server Manager:

• In Server Manager, click Manage > Add Servers.

• Click Find Now.

• Click each server in the deployment (for example, Contoso-Cb1, Contoso-WebGw1, and Contoso-Sh1) and click OK.

2. Create a session-based deployment to deploy the Remote Desktop Services components:

• In Server Manager, click Manage > Add Roles and Features.

• Click Remote Desktop Services installation, Standard Deployment, and Session-based desktop deployment.

• Select the appropriate servers for the RD Connection Broker server, RD Web Access server, and RD Session Host server (for example, Contoso-Cb1, Contoso-WebGw1, and Contoso-SH1, respectively).

• Select Restart the destination server automatically if required, and then click Deploy.

• Wait for the deployment to complete successfully

3. Add RD License Server:

• In Server Manager, click Remote Desktop Services > Overview > +RD Licensing.

• Select the virtual machine where the RD license server will be installed (for example, Contoso-Cb1).

• Click Next, and then click Add.

4. Activate the RD License Server and add it to the License Servers group:

• In Server Manager, click Remote Desktop Services > Servers. Right-click the server with the Remote Desktop Licensing role installed and select RD Licensing Manager.

• In RD Licensing Manager, select the server, and then click Action > Activate Server.

• Accept the default values in the Activate Server Wizard. Continue accepting default values until you reach the Company information page. Then, enter your company information.

• Accept the defaults for the remaining pages until the final page. Clear Start Install Licenses Wizard now, and then click Finish.

• Click Action > Review Configuration > Add to Group > OK. Enter credentials for a user in the AAD DC Administrators group, and register as SCP. This step might not work if you are using Azure AD Domain Services, but you can ignore any warnings or errors.

5. Add the RD Gateway server and certificate name:

• In Server Manager, click Remote Desktop Services > Overview > + RD Gateway.

• In the Add RD Gateway Servers wizard, select the virtual machine where you want to install the RD Gateway server (for example, Contoso-WebGw1).

• Enter the SSL certificate name for the RD Gateway server using the external fully qualified DNS Name (FQDN) of the RD Gateway server. In Azure, this is the DNS name label and uses the format servicename.location.cloudapp.azure.com. For example, contoso.westus.cloudapp.azure.com.

• Click Next, and then click Add.

6. Create and install self-signed certificates for the RD Gateway and RD Connection Broker servers.

• In Server Manager, click Remote Desktop Services > Overview > Tasks > Edit Deployment Properties.

• Expand Certificates, and then scroll down to the table. Click RD Gateway > Create new certificate.

• Enter the certificate name, using the external FQDN of the RD Gateway server (for example, contoso.westus.cloudapp.azure.com) and then enter the password.

• Select Store this certificate and then browse to the shared folder you created for certificates in a previous step. (For example,\Contoso-Cb1\Certificates.)

• Enter a file name for the certificate (for example, ContosoRdGwCert), and then click Save.

• Select Allow the certificate to be added to the Trusted Root Certificate Authorities certificate store on the destination computers, and then click OK.

• Click Apply, and then wait for the certificate to be successfully applied to the RD Gateway server.

• Click RD Web Access > Select existing certificate.

• Browse to the certificate created for the RD Gateway server (for example, ContosoRdGwCert), and then click Open.

• Enter the password for the certificate, select Allow the certificate to be added to the Trusted Root Certificate store on the destination computers, and then click OK.

• Click Apply, and then wait for the certificate to be successfully applied to the RD Web Access server.

• Repeat sub-steps for the RD Connection Broker - Enable Single Sign On and RD Connection Broker - Publishing services, using the internal FQDN of the RD Connection Broker server for the new certificate's name (for example, Contoso-Cb1.Contoso.com).

7. Export self-signed public certificates and copy them to a client computer. If you are using certificates from a trusted certificate authority, you can skip this step.

• Launch certlm.msc.

• Expand Personal, and then click Certificates.

• In the right-hand pane right-click the RD Connection Broker certificate intended for client authentication, for example Contoso-Cb1.Contoso.com.

• Click All Tasks > Export.

• Accept the default options in the Certificate Export Wizard accept defaults until you reach the File to Export page.

• Browse to the shared folder you created for certificates, for example \Contoso-Cb1\Certificates.

• Enter a File name, for example ContosoCbClientCert, and then click Save.

• Click Next, and then click Finish.

• Repeat substeps for the RD Gateway and Web certificate, (for example contoso.westus.cloudapp.azure.com), giving the exported certificate an appropriate file name, for example ContosoWebGwClientCert.

• In File Explorer, navigate to the folder where the certificates are stored, for example \Contoso-Cb1\Certificates.

• Select the two exported client certificates, then right-click them, and click Copy.

• Paste the certifcates on the local client computer.

8. Configure the RD Gateway and RD Licensing deployment properties:

1. • In Server Manager, click Remote Desktop Services > Overview > Tasks > Edit Deployment Properties.

   • Expand RD Gateway and clear the Bypass RD Gateway server for local addresses option.

   • Expand RD licensing and select Per User

   • Click OK.

9. Create a session collection. These steps create a basic collection. Check out Create a Remote Desktop Services collection for desktops and apps to run for more information about collections.

1. • In Server Manager, click Remote Desktop Services > Collections > Tasks > Create Session Collection.

   • Enter a collection Name (for example, ContosoDesktop).

   • Select an RD Session Host Server (Contoso-Sh1), accept the default user groups (Contoso\Domain Users), and enter the Universal Naming Convention (UNC) Path to the user profile disks created above (\Contoso-Cb1\UserDisks).

   • Set a Maximum size, and then click Create.

You've now created a basic Remote Desktop Services infrastructure. If you need to create a highly-available deployment, you can add a connection broker cluster or a second RD Session Host server.

Install RDS CAL on the Remote Desktop License server

Use the following instructions to install RDS CAL on Your license server. Once the CALs are installed, the license server will issue them to users as appropriate.

Note: You need Internet connectivity on the computer running Remote Desktop Licensing Manager but not on the computer running the license server.

• • 1. On the license server (usually the first RD Connection Broker), open the Remote Desktop Licensing Manager.

    2. Right-click the License server (Your server name, example: Contoso-Cb1), and then click Install Licenses.

    3. In the Install Licenses Wizard, on the Welcome to the Install Licenses Wizard page, click Next.

    4. On the License Program page, select License Pack (Retail Purchase if you purchased from us), and then click Next.

    5. Enter the 5x5 Retail license key (The license key you will receive from us after your purchase), click Add, and then click Next.

Verify connectivity on Remote Desktop Licensing Manager

To verify the functionality of the deployment, use Remote Desktop Connection (RDC) to connect to the remote host. The use of the license will be verified on the Remote Desktop license server.

• Verify client connectivity:
• To verify client connectivity in a session-based desktop deployment: Establish a client connection in a session-based desktop deployment using a valid license
• To verify client connectivity in a virtual machine-based desktop deployment: Establish a client connection in a virtual machine-based desktop deployment using a valid license.

Remote Desktop Integration and Deployment Documentation:

1. Deploy your Remote Desktop environment

2. Set up the Remote Desktop web client for your users:

3. Supported configurations for Remote Desktop Services

4. Install Remote Desktop Session Host without the Connection Broker role service: