How to Configure Remote Desktop Licensing Mode

Understanding Remote Desktop Licensing

Remote Desktop Services (RDS) allows multiple users to connect remotely to a Windows server. To manage these connections legally and efficiently, RDS requires licenses for each user or device that connects to the server. These licenses, known as Client Access Licenses (CALs), are essential for compliance and ensuring that connections are not disrupted due to licensing issues.

Licensing Modes

Per Device

A license is assigned to each device that connects to the RD Session Host server. This mode is ideal for environments where multiple users share a limited number of devices. For instance, in a shift-based workplace where several employees use the same computer, a Per Device CAL is more economical and straightforward.

Per User

A license is assigned to each user account that connects to the RD Session Host server. This mode is suitable for environments where users access the server from multiple devices, such as a personal laptop, desktop, or mobile device. In organizations with mobile workforces or remote workers, Per User CALs provide flexibility and ease of management.

Choosing the Right Licensing Mode

Selecting the appropriate licensing mode depends on your organization's needs and usage patterns. Factors to consider include the number of users, the number of devices, and the mobility of your workforce. Misconfiguration can lead to compliance issues and interrupted access, making it crucial to evaluate your licensing needs accurately.

Importance of Compliance

Configuring the licensing mode correctly is not just about uninterrupted access; it also ensures that your organization remains compliant with Microsoft's licensing policies. Non-compliance can result in fines and other penalties, so understanding and implementing the correct licensing strategy is critical.

By comprehensively understanding and correctly configuring Remote Desktop licensing, organizations can optimize their RDS environments, ensuring seamless remote access while maintaining compliance and cost efficiency.

Configuring Remote Desktop Licensing Mode

Using Group Policy (GPO)

Group Policy is a powerful tool for managing settings across multiple computers in an Active Directory environment. Here's how to configure RDS licensing mode using GPO.

Configuring GPO for Licensing Mode

1. Open Group Policy Management: Press Win + R , type gpmc.msc , and press Enter. This opens the Group Policy Management Console (GPMC).
2. Navigate to the Desired GPO: In the GPMC, expand the forest and domain containing the Group Policy Object (GPO) you want to configure. Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing .
3. Set the Licensing Mode: Find the policy named Set the Remote Desktop licensing mode . Double-click to open the policy setting, select Enabled , and then choose either Per User or Per Device licensing mode.
4. Specify the License Server: Enable the policy named Use the specified Remote Desktop license servers . Enter the Fully Qualified Domain Name (FQDN) of your RD License server(s).
5. Apply the GPO: Link the GPO to the appropriate Organizational Unit (OU) that contains your RD Session Host servers.

Configuring via PowerShell

PowerShell provides a scripting approach for configuring RDS licensing mode, which is particularly useful for automation and bulk changes.

Steps to Configure Licensing Mode using PowerShell

1. Open PowerShell as Administrator: Right-click the Start button and select Windows PowerShell (Admin) .

2. Set the Licensing Mode: Execute the following command to set the licensing mode:

powershell :

$RDSMode = "PerUser" # Replace "PerUser" with "PerDevice" if needed

$obj = Get-WmiObject -Namespace "Root/CIMv2/TerminalServices" -Class Win32_TerminalServiceSetting

$obj.ChangeMode($RDSMode)

3. Specify the License Server: Run this command to specify your license server:

powershell :

$LicenseServer = "YourLicenseServerName"

$obj.SetSpecifiedLicenseServerList($LicenseServer)

4. Verify Configuration: To ensure the settings have been applied, use:

powershell :

$obj.GetSpecifiedLicenseServerList()

Configuring via Windows Registry

For environments without Group Policy, the Windows Registry offers a manual way to configure licensing settings.

Steps to Configure Licensing Mode using the Registry

1. Open Registry Editor: Press Win + R , type regedit , and press Enter to open the Registry Editor.
2. Navigate to Licensing Key: Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core .
3. Set Licensing Mode: Create or modify the LicensingMode DWORD value: Set LicensingMode to 2 for Per Device . Set LicensingMode to 4 for Per User .
4. Specify the License Server: Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\LicenseServers . Add a new key with the name of your license server.
5. Restart the Server: Restart your server to apply the changes.

Common Issues and Troubleshooting

Proper configuration often requires addressing common issues that may arise during the setup and operation of Remote Desktop Services (RDS). Here are some frequent problems and how to resolve them:

Grace Period Expiration

The RDS grace period allows unlicensed connections for a limited time after initial setup. Typically, this period lasts 120 days, giving administrators time to configure the licensing server and acquire the necessary CALs. If you encounter connection denials after the grace period expires:

• Verify Licensing Configuration: Ensure that your RDS CALs are correctly installed and assigned.
• Check License Server Availability: Confirm that the license server is online and reachable by the RD Session Host.
• Grace Period Reset: In some cases, it may be necessary to reset the grace period, though this should be a last resort and done in compliance with licensing agreements.

Firewall Settings

Firewall settings can block communication between the RD Session Host and the license server, leading to licensing issues. Ensure that your firewall is configured to allow traffic on the following ports:

• Port 135: Used for RPC Endpoint Mapper, essential for initiating connections.
• Port 445: Used for Microsoft-DS (SMB) and necessary for file sharing and other network activities.
• Port 3389: The default port for RDP traffic, essential for remote desktop connections.

License Server Activation

Your license server must be activated to issue RDS CALs. Use the Remote Desktop Licensing Manager to:

• Verify Activation Status: Check the status of the license server to ensure it is active.
• Activate the Server: If not already activated, follow the prompts in the Licensing Manager to activate the server. This can be done online or via telephone.
• Install CALs: Ensure that the required number of CALs are installed and properly configured for either Per User or Per Device mode.

Troubleshooting Steps

1. Run Licensing Diagnoser: Use the Remote Desktop Licensing Diagnoser tool to identify and troubleshoot issues.
2. Event Viewer Logs: Check the Event Viewer for any RDS-related errors or warnings that might indicate licensing problems.
3. Network Connectivity: Verify that there are no network connectivity issues between the RD Session Host and the license server.

By proactively managing these common issues, you can ensure a smooth and compliant RDS environment, minimizing downtime and enhancing the user experience. Properly configured and maintained licensing not only ensures legal compliance but also supports seamless and reliable remote desktop access.

Why Choose TSplus

For a more seamless remote desktop experience and advanced management features, consider using TSplus. Our solutions offer robust remote access and management capabilities, simplifying your IT infrastructure. Visit TSplus for more information and to explore our remote desktop solutions.

Conclusion

Configuring Remote Desktop Licensing Mode is essential for maintaining a compliant and functional RDS environment. Whether using Group Policy, PowerShell, or Windows Registry, proper configuration ensures that your users can connect without interruption and that your organization stays within licensing requirements.