Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 416/439 docs · checked 22:55 UTC Customize Public modeDiscuss ChangeIntel on Discord

Remote Desktop Services supported configurations

This page's changes and edits · All guidance changes

Microsoft's edit ·

rds article updates

Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit 98cdb9b · +6 −6 lines · also on GitHub

11 ---
22 title: Supported configurations for Remote Desktop Services
3 −description: Provides information about supported configurations for RDS in Windows Server 2016 and Windows Server 2019.
3 +description: Provides information about supported configurations for RDS in Windows Server.
44 ms.author: wscontent
5 −ms.date: 07/14/2020
5 +ms.date: 05/15/2024
66 ms.topic: article
77 ms.assetid: c925c7eb-6880-411f-8e59-bd0f57cc5fc3
88 author: robinharwood
⋯ 1 unchanged line
1010 ---
1111 # Supported configurations for Remote Desktop Services
1212
13 −>Applies to: Windows Server 2022, Windows Server 2016, Windows Server 2019
13 +>Applies to: Windows Server 2025, Windows Server 2022, Windows Server 2016, Windows Server 2019
1414
15 −When it comes to supported configurations for Remote Desktop Services environments, the largest concern tends to be version interoperability. Most environments include multiple versions of Windows Server. For example, you may have an existing RDS deployment running an earlier version of Windows Server but want to upgrade to Windows Server 2016 to take advantage of the new features (like support for OpenGL/OpenCL, Discrete Device Assignment, or Storage Spaces Direct). The question then becomes, which RDS components can work with different versions and which need to be the same?
15 +When it comes to supported configurations for Remote Desktop Services environments, the largest concern tends to be version interoperability. Most environments include multiple versions of Windows Server. For example, you may have an existing RDS deployment running an earlier version of Windows Server but want to upgrade to Windows Server 2025 to take advantage of the new features. The question then becomes, which RDS components can work with different versions and which need to be the same?
1616
1717 So with that in mind, here are basic guidelines for supported configurations of Remote Desktop Services in Windows Server.
1818
⋯ 4 unchanged lines
2323
2424 - Use the most recent version of Windows Server for your Remote Desktop infrastructure (the Web Access, Gateway, Connection Broker, and license server). Windows Server is backward-compatible with these components, which means a Windows Server 2016 RD Session Host can connect to a 2019 RD Connection Broker, but not the other way around.
2525
26 −- For RD Session Hosts - all Session Hosts in a collection need to be at the same level, but you can have multiple collections. You can have a collection with Windows Server 2016 Session Hosts and one with Windows Server 2019 Session Hosts.
26 +- For RD Session Hosts - all Session Hosts in a collection need to be at the same level, but you can have multiple collections. You can have a collection with Windows Server 2016 Session Hosts and one with Windows Server 2025 Session Hosts.
2727
28 −- If you upgrade your RD Session Host to Windows Server 2019, also upgrade the license server. Remember that a 2019 license server can process CALs from all previous versions of Windows Server, down to Windows Server 2003.
28 +- If you upgrade your RD Session Host to Windows Server 2025, also upgrade the license server. Remember that a 2025 license server can only process CALs from previous versions of Windows Server.
2929
3030 - Follow the upgrade order recommended in [Upgrading your Remote Desktop Services environment](upgrade-to-rds.md#flow-for-deployment-upgrades).
3131
⋯ 98 unchanged lines

Microsoft's Markdown source from MicrosoftDocs/windowsserverdocs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 07:51 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Oct 22:55 UTC · 258 of 260 readable · 256 fully read · documentation 416/439 current