How to Set Up Remote Desktop Services on Windows Server 2025

Softkeyworld Team · 15 November 2026

To set up Remote Desktop Services on Windows Server 2025, join the server to a domain, open Server Manager > Manage > Add Roles and Features, choose Remote Desktop Services installation, then a Quick Start or Standard session-based deployment. Add an RD Licensing server, activate it, install RDS 2025 CALs, set the licensing mode and publish a session collection.

Written by the Softkeyworld technical team · Updated October 2026

Remote Desktop Services (RDS) is still the most practical way for a small or mid-sized business to give staff a full Windows desktop, or a handful of line-of-business apps, from anywhere. It runs on hardware you already own and works with Microsoft's Remote Desktop clients on every major platform. The catch is that RDS has more moving parts than people expect: a deployment wizard, several role services, certificates, and a separate licensing server that will quietly stop your users connecting after 120 days if you ignore it.

This guide walks through a session-based RDS deployment on Windows Server 2025 the way we would do it for a real office: plan the roles, deploy them, sort out licensing properly, publish a desktop or RemoteApp programs, and then secure external access with RD Gateway. If you have not built the server yet, start with our Windows Server 2025 download, install and activation guide and come back once the OS is activated and patched.

Key takeaways

  • RDS deployments are created through the Remote Desktop Services installation option in Add Roles and Features, not by ticking individual roles.
  • A Windows Server 2025 session host needs Windows Server 2025 RDS CALs; older RDS CALs will not license it.
  • You get a 120-day grace period. After that, connections fail unless an activated licence server is issuing CALs.
  • Every RDS user or device also needs a regular Windows Server CAL. The two are separate licences.
  • Never expose port 3389 directly to the internet. Publish access through RD Gateway on 443.

What Remote Desktop Services actually consists of

RDS is not one role but a set of role services that work together. In a small deployment several of them can sit on one server; in larger ones they are split for performance and resilience. Knowing what each one does makes the wizard far less mysterious.

Role service What it does Required?
RD Session Host (RDSH) Hosts the user sessions, desktops and RemoteApp programs. This is where the CPU and RAM go. Yes
RD Connection Broker Routes users to a session host, reconnects them to existing sessions and balances load across a farm. Yes
RD Web Access Publishes the RDWeb portal and the feed that clients subscribe to; also hosts the HTML5 web client. Yes
RD Licensing Stores, issues and tracks RDS CALs. Yes, after the 120-day grace period
RD Gateway Tunnels RDP over HTTPS so remote users can connect securely without a VPN. Strongly recommended for external access
RD Virtualization Host Hyper-V based VDI, giving each user a full virtual machine. Only for VM-based deployments

For most small businesses, a session-based deployment (many users sharing one or more session hosts) is the right model. It is what this guide covers.

Before you start: prerequisites checklist

  1. An Active Directory domain. The deployment wizard requires the servers to be domain members. Per-user CAL tracking also depends on AD.
  2. A dedicated session host if you can. Running RDS on a domain controller is not a configuration we recommend: users get interactive logons on the box that holds your directory, and troubleshooting becomes messy. A separate VM for RDS is cleaner.
  3. Windows Server 2025 activated and fully updated, with a static IP address and a sensible hostname (renaming after deployment is painful).
  4. A domain admin account to run the wizard, and a security group (for example RDS-Users) for the people who will connect.
  5. A public DNS name and certificate if staff will connect from outside, for example remote.yourcompany.co.uk.
  6. Applications installed in RD Session Host install mode after the role is deployed (more on this below).

Choosing between Standard and Datacenter matters too. Standard covers two virtual machines per fully licensed host, which is usually enough for a domain controller plus an RDS server. If you plan to run more VMs on the same host, read our explainer on Windows Server 2025 Standard vs Datacenter licensing and virtualisation before buying.

Quick Start or Standard deployment?

The wizard offers two deployment types. Both build the same components; the difference is how much control you get.

Option What it does Best for
Quick Start Installs Connection Broker, Web Access and Session Host on a single server and creates a default session collection with some sample RemoteApps. Labs, proofs of concept, very small offices
Standard deployment Lets you place each role service on the server of your choice, and add more session hosts later. Production, anything you expect to grow

We use Standard even on a single server: you can still assign every role to one machine, but you control the collection settings from the start.

Step-by-step: deploy session-based RDS

1. Add your servers to Server Manager

If the roles will be spread across more than one machine, open Server Manager on the server you will manage from, choose Manage > Add Servers, click Find Now, and add every server that will take part. The wizard can only target servers in this pool.

2. Run the Remote Desktop Services installation

  1. In Server Manager choose Manage > Add Roles and Features.
  2. On Installation Type select Remote Desktop Services installation.
  3. Choose Standard deployment, then Session-based desktop deployment.
  4. Assign the RD Connection Broker, RD Web Access and RD Session Host servers. On a single-server build, pick the same server each time.
  5. Tick Restart the destination server automatically if required and click Deploy.

The session host reboots during this process. When the wizard finishes, a new Remote Desktop Services node appears in Server Manager with a Deployment Overview diagram.

If you prefer PowerShell, the equivalent is a single command run from an elevated session:

New-RDSessionDeployment -ConnectionBroker rds01.corp.local -WebAccessServer rds01.corp.local -SessionHost rds01.corp.local

3. Add the RD Licensing role service

In Remote Desktop Services > Overview, click the green RD Licensing icon in the deployment diagram, select the server that will hold your CALs, and click Add.

4. Activate the licence server and install CALs

  1. Open Remote Desktop Licensing Manager (licmgr.exe).
  2. Right-click the server and choose Activate Server. The automatic (internet) method is easiest.
  3. Complete the company information pages, then run Install Licenses and enter your RDS CAL agreement or licence pack details.
  4. Right-click the server again, choose Review Configuration, and if prompted click Add to Group so the server is in the Terminal Server License Servers group in AD.

5. Set the licensing mode for the deployment

This is the step people forget, and it is behind most "no Remote Desktop license servers available" errors we see. In Remote Desktop Services > Overview, open Tasks > Edit Deployment Properties, expand RD Licensing, choose Per User or Per Device to match the CALs you installed, and confirm the licence server is listed. Via PowerShell:

Set-RDLicenseConfiguration -LicenseServer rds01.corp.local -Mode PerUser -ConnectionBroker rds01.corp.local

Then run RD Licensing Diagnoser (lsdiag.msc) on the session host. It should report the licensing mode, the licence server and available CALs with no warnings.

6. Create a session collection

Go to Remote Desktop Services > Collections > Tasks > Create Session Collection. Give it a name users will see (for example "Office Desktop"), select the session host, replace the default Domain Users with your RDS-Users group, and decide on user profile disks. Profile disks store each user's profile as a VHDX on a file share, which keeps profiles consistent if you later add a second session host. Point them at a UNC path such as \\fs01\UserDisks$ and set a sensible maximum size.

PowerShell equivalent: New-RDSessionCollection -CollectionName "Office Desktop" -SessionHost rds01.corp.local -ConnectionBroker rds01.corp.local

7. Install applications the right way

On a session host, install software from an elevated Command Prompt after running change user /install, and return to normal mode with change user /execute. Also check the vendor's licensing terms: many desktop applications, Office included, have specific rules for multi-user RDS environments, and consumer or retail editions are often not permitted on a shared session host.

8. Publish RemoteApp programs (optional)

If users need a single application rather than a whole desktop, open the collection and choose RemoteApp Programs > Tasks > Publish RemoteApp Programs. Tick the applications and click Publish. Once at least one RemoteApp is published, the full desktop is hidden from the RDWeb feed by default; you can re-enable it with Set-RDRemoteDesktop -CollectionName "Office Desktop" -ShowInWebAccess $true.

RDS licensing on Windows Server 2025, explained plainly

Licensing is where most RDS projects go wrong, so it is worth slowing down here. According to Microsoft's RDS client access licence documentation, a deployment runs for 120 days without a licence server. After that, every client must hold a valid RDS CAL issued by an activated licence server.

Point Per User RDS CAL Per Device RDS CAL
Assigned to A named user in Active Directory A physical device
Best when Staff connect from laptops, phones and home PCs Shift workers share a fixed set of terminals
Enforcement Not technically enforced; compliance is your responsibility Enforced; temporary CAL issued on first connection
Workgroup support Cannot be tracked outside a domain Works without AD
Web client Supported Not supported for the HTML5 web client

Two rules catch people out. First, RDS CALs are backward compatible but not forward compatible: a Windows Server 2025 session host needs 2025 RDS CALs, and the licence server must itself run Windows Server 2025 to issue them. Microsoft's supported configurations page spells out that upgrading a session host means upgrading the licence server too. Second, RDS CALs sit on top of standard Windows Server CALs; each user or device needs both. Our guide to Windows Server CALs, user vs device explains how to count the base CALs.

Secure remote access with RD Gateway

Opening TCP 3389 on your firewall and forwarding it to the session host is the single most common RDS mistake, and exposed RDP is a well-known target for brute-force and ransomware attacks. RD Gateway wraps RDP inside HTTPS on port 443, authenticates users before they reach the session host, and lets you control who may connect to what.

  1. In the deployment overview, click RD Gateway, select a server (ideally the one facing your firewall), and enter the external FQDN that will appear on the certificate.
  2. Open Tasks > Edit Deployment Properties > Certificates. Assign a publicly trusted certificate to RD Gateway and RD Web Access, and a certificate matching the internal FQDN to the two Connection Broker entries. Self-signed certificates are for testing only.
  3. Under RD Gateway in deployment properties, decide whether to bypass the gateway for local addresses. For consistent behaviour, many admins untick the bypass option.
  4. Forward only TCP 443 (and optionally UDP 3391 for the UDP transport) to the gateway. Leave 3389 closed externally.
  5. Add multi-factor authentication if you can. RD Gateway supports NPS-based MFA extensions, and this is worth the effort for any internet-facing service.

Optional: the HTML5 web client

The Remote Desktop web client lets users connect from a browser with no client installed. It requires RD Gateway, publicly trusted certificates and per-user CALs. Install it on the RD Web Access server with Install-Module -Name RDWebClientManagement, then Install-RDWebClientPackage, import the broker certificate with Import-RDWebClientBrokerCert, and publish with Publish-RDWebClientPackage -Type Production -Latest. Users browse to https://remote.yourcompany.co.uk/RDWeb/webclient/. Microsoft's web client admin guide covers updates and troubleshooting.

Connecting users and day-two tuning

Users on Windows can open the Remote Desktop Connection client (mstsc) or subscribe to the RDWeb feed, which places published apps in their Start menu. On Mac, iOS and Android they use Microsoft's Remote Desktop or Windows App client and add the workspace URL. A few settings are worth adjusting in the collection properties once people are using the system:

  • Session limits: end disconnected sessions after a few hours so abandoned sessions do not hold RAM and locked files indefinitely.
  • Client settings: disable drive or clipboard redirection if data-loss prevention matters; leave printer redirection on only if your drivers behave.
  • Sizing: start with generous RAM. Browsers and Teams dominate memory use in shared sessions far more than Office itself does.
  • Patching: drain the host (change logon /drain) before maintenance windows so new users are not sent to a server about to reboot.

If you are coming from an older RDS farm, our comparison of Windows Server 2025 vs 2022 outlines the platform changes worth knowing before you migrate.

Common RDS errors and what they usually mean

Symptom Likely cause Fix
"There are no Remote Desktop License Servers available to provide a license" Grace period expired; licensing mode or server not set Set mode and server in deployment properties; check with lsdiag.msc
Licence server shows CALs but none issued CAL version older than the session host, or mode mismatch Install CALs matching the host version and mode
Certificate warning on connect Self-signed or name-mismatched certificate Use a public certificate whose name matches the external FQDN
"Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable" 443 not forwarded, or DNS points elsewhere Check port forwarding, DNS and the gateway's resource authorisation policy

Frequently asked questions

Do I need RDS CALs just for admins to manage the server?

No. Windows Server allows two simultaneous administrative remote sessions without installing the RD Session Host role or buying RDS CALs. RDS CALs are needed once you install RD Session Host for ordinary users.

Can I use Windows Server 2022 RDS CALs on a 2025 session host?

No. CALs work with the same or earlier server versions only. A 2025 session host needs 2025 RDS CALs, issued from a licence server running Windows Server 2025.

Can RDS run on a single server?

Yes. Connection Broker, Web Access, Session Host, Licensing and Gateway can all share one server in a small office. Keep it separate from the domain controller where possible.

What happens when the 120-day grace period ends?

Users are refused with a licensing error unless the session host can reach an activated licence server holding suitable CALs. Configure licensing on day one rather than waiting for the deadline.

Does Windows Server 2025 Essentials support RDS?

Essentials is aimed at small file, print and directory workloads and is not designed to act as a multi-user session host. For RDS, Standard or Datacenter is the appropriate edition.

Our recommendation

For most small and mid-sized offices, a Standard deployment on one or two Windows Server 2025 VMs, per-user RDS CALs, and RD Gateway with a proper certificate is a reliable, supportable setup. Build the licensing and gateway pieces at the start rather than bolting them on later, and the deployment will run quietly for years. If you need a genuine licence for the host itself, Windows Server 2025 Standard covers most single-host RDS builds; contact our support team if you are unsure which edition fits.

Get Windows Server 2025 Standard

Related reading

Resource Why read it
Windows Server 2025 install and activation guide Build and activate the host before deploying RDS
Windows Server CALs explained Count the base CALs every RDS user also needs
Server 2025 Standard vs Datacenter Choose the right edition for your VM count
Need a genuine licence key? Shop licences