Remote Desktop Services (RDS) lets multiple users access Windows Server desktops and applications. For administrative access, Windows Server allows up to two remote sessions without RDS CALs. For multiuser access, install Remote Desktop Session Host and RD Licensing through Server Manager or PowerShell, activate the licensing server, select a licensing mode, and verify user connections.
Applies to: Windows Server 2016, 2019, 2022 and 2025. Components: RD Session Host and RD Licensing.
Requirements
Administrator access, a backup, a maintenance window for restart, and a supported Windows Server installation are required. Plan a suitable RDS licensing model for production use.
| Mode | Remote Desktop for Administration | RD Session Host |
|---|---|---|
| Use | Server administration only | Multiuser desktops and applications |
| Sessions | Up to two administrative sessions | Based on capacity and licensed users or devices |
| Licensing | No additional RDS CALs for the two administrative sessions | Appropriate RDS CALs or eligible service-provider licensing |
Steps
1. Install the roles in Server Manager
Open Server Manager > Manage > Add Roles and Features. Select Role-based or feature-based installation, choose your server, then Remote Desktop Services. Add Remote Desktop Session Host and Remote Desktop Licensing, accept required features, and click Install. Restart if requested. This role-based method installs the services; a complete RDS deployment with Connection Broker and RemoteApp requires a separate deployment workflow.
2. Alternative: install with PowerShell
Run PowerShell as administrator:
Install-WindowsFeature -Name RDS-RD-Server,RDS-Licensing -IncludeManagementTools
Get-WindowsFeature RDS-RD-Server,RDS-Licensing
3. Activate the RD Licensing server
Open Server Manager > Tools > Remote Desktop Services > Remote Desktop Licensing Manager. Right-click the licensing server, select Activate Server and complete the wizard. Then choose Install Licenses and enter the details of your licensing program. Activation alone does not install RDS CALs.
4. Configure the licensing mode
Open the Local Group Policy Editor and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing. Enable Use the specified Remote Desktop license servers and enter the license server name. Enable Set the Remote Desktop licensing mode and select Per User or Per Device. For workgroup deployments, standard RDS CAL licensing requires Per Device. For hosting under SPLA, confirm the applicable RDS SAL terms with your provider.
gpedit.msc gpupdate /force
5. Check the 120-day grace period
New RD Session Host installations generally have a 120-day licensing grace period. This does not replace licenses for ongoing use. Check the remaining period in an elevated PowerShell session:
$rds = Get-CimInstance -Namespace root/CIMV2/TerminalServices -ClassName Win32_TerminalServiceSetting Invoke-CimMethod -InputObject $rds -MethodName GetGracePeriodDays
6. Secure Remote Desktop
Enable Network Level Authentication (NLA), use strong passwords, restrict RDP access with firewall rules, VPN or RD Gateway, and keep Windows Server patched. Changing the RDP port alone does not secure the service. Read the guides on changing the RDP port and protecting RDP against brute force.
Verify
Verify that both roles are installed and check active sessions:
Get-WindowsFeature RDS-RD-Server,RDS-Licensing query session
Open RD Licensing Diagnoser and confirm that the licensing server is available, the correct mode is configured and compatible licenses are installed. Test two different licensed user accounts if multiuser access is required.
Troubleshooting
No Remote Desktop license servers available
Check that RD Licensing is activated, the license server is reachable, licenses are installed, and Group Policy points to the correct server.
Multiple users cannot connect
Check RD Session Host installation, user permissions, applied session limits and licensing configuration.
RDP connection fails
Check TermService, the listening port, firewall and NLA. See common RDP errors and solutions.
Get-Service TermService Test-NetConnection SERVER_IP -Port 3389
FAQ
How many RDP sessions are allowed without RDS?
Up to two concurrent remote administrative sessions are available without additional RDS CALs. These sessions are for server administration, not hosting user desktops.
What is the RDS grace period?
RD Session Host has a 120-day licensing grace period. After it expires, valid licensing and an available RD Licensing server are required for regular user sessions.
Do I need RDS CAL or SAL licenses?
Multiuser RDS use requires appropriate licenses. Standard deployments use per-user or per-device RDS CALs. Hosting providers may use eligible RDS SAL licensing under SPLA.
How do I change the RDP port?
Change the RDP listener port and matching firewall rules, then reconnect using the new port. Changing the port does not replace security controls.
How do I protect RDP against brute force?
Enable NLA, limit access with VPN or RD Gateway, apply account lockout policies and Windows updates, and restrict access to trusted users and networks.
Related Articles
- How to connect to a server via RDP
- How to change the RDP port
- Protect Windows RDP against brute force
- Common RDP errors and solutions
- Windows Server Evaluation: extend and convert
Windows Server and RDS with Unihost
Explore Windows Server and RDS licensing options and dedicated infrastructure: