How to Configure Remote Desktop Services on Windows Server 2012 R2

How to Configure Remote Desktop Services on Windows Server 2012 R2

Remote Desktop Services (RDS) in Windows Server 2012 R2 is a platform for delivering virtualised applications and desktops to users. Whether you need to provide shared session-based desktops, RemoteApp published applications, or full VDI (Virtual Desktop Infrastructure), RDS is the centralised service framework that makes it possible. This guide walks through the full RDS role installation, the three deployment models, and the initial configuration of an RDS infrastructure.

RDS Role Services Overview

Windows Server 2012 R2 RDS consists of several role services that work together:

• RD Session Host (RDSH): Hosts sessions for multiple users on a single server. Users connect and run applications directly on the server
• RD Connection Broker: Load-balances connections across multiple Session Hosts and manages session reconnection
• RD Web Access (RD Web): Provides a web portal where users browse and launch RemoteApp programs or desktops
• RD Gateway: Allows secure remote connections over HTTPS from the internet, wrapping RDP traffic in an SSL tunnel
• RD Licensing: Manages RDS Client Access Licenses (CALs) required for each user or device connecting to RDS
• RD Virtualisation Host: Hosts pooled or personal virtual desktop VMs for VDI deployments

Prerequisites

• Windows Server 2012 R2 servers (one or more, depending on deployment scale)
• All servers joined to the same Active Directory domain
• An administrative account with Domain Admin or equivalent privileges
• RDS CALs purchased and available for the RD Licensing server
• SSL certificate for RD Gateway and RD Web Access (self-signed works for internal testing)

Step 1 — Choose a Deployment Type

RDS in Windows Server 2012 R2 offers three deployment scenarios via Server Manager:

1. Quick Start: Installs all RDS roles on a single server — suitable for small deployments and testing
2. Standard Deployment: Distributes RDS roles across multiple servers for scalability and high availability
3. VDI Deployment: Uses Hyper-V to provide individual virtual desktop VMs

Step 2 — Install RDS Roles

For a standard multi-server deployment, install the required role services on each server. Install RD Session Host on the session host servers:

Install-WindowsFeature -Name RDS-RD-Server -IncludeManagementTools -Restart

Install RD Connection Broker on the broker server:

Install-WindowsFeature -Name RDS-Connection-Broker -IncludeManagementTools

Install RD Web Access:

Install-WindowsFeature -Name RDS-Web-Access -IncludeManagementTools

Install RD Licensing:

Install-WindowsFeature -Name RDS-Licensing -IncludeManagementTools

Install RD Gateway:

Install-WindowsFeature -Name RDS-Gateway -IncludeManagementTools

Step 3 — Create the RDS Deployment via Server Manager

The recommended method for initial RDS deployment on Windows Server 2012 R2 is through Server Manager’s RDS deployment wizard, which configures all the role services and their relationships in a unified workflow:

1. Open Server Manager and click Add Roles and Features
2. Select Remote Desktop Services installation
3. Choose Standard deployment
4. Select Session-based desktop deployment
5. Assign servers to each role: RD Connection Broker, RD Web Access, RD Session Host
6. Complete the wizard — Server Manager handles all role installations and trust configuration

Alternatively, use PowerShell for automated deployment:

New-RDSessionDeployment -ConnectionBroker "rdcb.domain.com" -WebAccessServer "rdwa.domain.com" -SessionHost "rdsh01.domain.com", "rdsh02.domain.com"

Step 4 — Add RD Session Hosts to the Deployment

After the initial deployment, add additional Session Host servers to increase capacity:

Add-RDServer -Server "rdsh03.domain.com" -Role "RDS-RD-Server" -ConnectionBroker "rdcb.domain.com"

Step 5 — Configure the RD Licensing Server

Point the RDS deployment to the licensing server and configure the licensing mode:

# Set the licensing server and mode (PerUser or PerDevice):
Set-RDLicenseConfiguration -LicenseServer "rdlic.domain.com" -Mode PerUser -ConnectionBroker "rdcb.domain.com" -Force

Activate the license server and install CALs through the RD Licensing Manager GUI (licmgr.exe), or via the web activation portal if the server has internet access.

Step 6 — Verify the RDS Deployment

# Get a summary of the RDS deployment:
Get-RDServer -ConnectionBroker "rdcb.domain.com"

# Check session host configuration:
Get-RDSessionHost -CollectionName "Desktop Collection" -ConnectionBroker "rdcb.domain.com"

# Check licensing configuration:
Get-RDLicenseConfiguration -ConnectionBroker "rdcb.domain.com"

Step 7 — Create the Initial Session Collection

A Session Collection groups one or more Session Hosts and defines user access, application availability, and connection settings. Create a collection:

New-RDSessionCollection -CollectionName "Desktop Pool" -SessionHost "rdsh01.domain.com", "rdsh02.domain.com" -ConnectionBroker "rdcb.domain.com" -CollectionDescription "Standard desktops for all users"

Step 8 — Configure Group Policy for RDS

Apply Group Policy settings to control RDS behaviour. Key policies are under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services:

# Example: Set time limits for disconnected sessions via registry (equivalent to GPO):
Invoke-Command -ComputerName "rdsh01.domain.com" -ScriptBlock {
    Set-ItemProperty -Path "HKLM:SOFTWAREPoliciesMicrosoftWindows NTTerminal Services" -Name "MaxDisconnectionTime" -Value 900000 -Type DWord
    Set-ItemProperty -Path "HKLM:SOFTWAREPoliciesMicrosoftWindows NTTerminal Services" -Name "MaxIdleTime" -Value 3600000 -Type DWord
}

Step 9 — Test a Remote Desktop Connection

Verify that users can connect. From a client machine:

mstsc /v:rdcb.domain.com

The Connection Broker will load-balance the session to the least-loaded Session Host. For RD Web Access, navigate to https://rdwa.domain.com/RDWeb in a browser.

Summary

Remote Desktop Services on Windows Server 2012 R2 provides a comprehensive platform for centralised application and desktop delivery. The role-based architecture — with Session Host, Connection Broker, Web Access, Gateway, and Licensing working in concert — scales from a single-server Quick Start deployment to a multi-server high-availability environment. Successful RDS deployment requires careful planning of server roles, licensing mode selection, SSL certificates, and Group Policy configuration to deliver a reliable, manageable remote access experience for your users.