Public mode

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

Some sources or documents need attention: 257/260 feeds/APIs · 416/439 docs · checked 21:54 UTC Customize Public modeDiscuss ChangeIntel on Discord

Remote Desktop Services supported configurations

This page's changes and edits · All guidance changes

Microsoft's edit ·

add connection broker detail for WS2025

Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit 3435221 · +13 −12 lines · also on GitHub

⋯ 34 unchanged lines
3535
3636 Windows Server 2016 removes the restriction for the number of Connection Brokers you can have in a deployment when using Remote Desktop Session Hosts (RDSH) and Remote Desktop Virtualization Hosts (RDVH) that also run Windows Server 2016. The following table shows which versions of RDS components work in a highly available deployment with three or more Connection Brokers.
3737
38 −|3+ Connection Brokers in HA|RDSH or RDVH 2022|RDSH or RDVH 2019|RDSH or RDVH 2016|
39 −|---|---|---|---|
40 − |Windows Server 2022 Connection Broker|Supported|Supported|Supported|
41 − |Windows Server 2019 Connection Broker|N/A|Supported|Supported|
42 − |Windows Server 2016 Connection Broker|N/A|N/A|Supported|
38 +|3+ Connection Brokers in HA|RDSH or RDVH 2025|RDSH or RDVH 2022|RDSH or RDVH 2019|RDSH or RDVH 2016|
39 +|---|---|---|---|---|
40 + |Windows Server 2025 Connection Broker|Supported|Supported|Supported|Supported|
41 + |Windows Server 2022 Connection Broker|N/A|Supported|Supported|Supported|
42 + |Windows Server 2019 Connection Broker|N/A|N/A|Supported|Supported|
43 + |Windows Server 2016 Connection Broker|N/A|N/A|N/A|Supported|
4344
4445 ## Support for graphics processing unit (GPU) acceleration
4546
⋯ 11 unchanged lines
5758
5859 The following table shows the scenarios supported by different versions of RDSH hosts.
5960
60 −|Feature|Windows Server 2016|Windows Server 2019|Windows Server 2022|
61 −|---|---|---|---|
62 −|Use of hardware GPU for all RDP sessions|Yes|Yes|Yes|
63 −|H.264/AVC hardware encoding (if supported by the GPU)|Yes|Yes|Yes|
64 −|Load balancing between multiple GPUs presented to the OS|No|Yes|Yes|
65 −|H.264/AVC encoding optimizations for minimizing bandwidth usage|No|Yes|Yes|
66 −|H.264/AVC support for 4K resolution|No|Yes|Yes|
61 +|Feature|Windows Server 2016|Windows Server 2019|Windows Server 2022|Windows Server 2025|
62 +|---|---|---|---|---|
63 +|Use of hardware GPU for all RDP sessions|Yes|Yes|Yes|Yes|
64 +|H.264/AVC hardware encoding (if supported by the GPU)|Yes|Yes|Yes|Yes|
65 +|Load balancing between multiple GPUs presented to the OS|No|Yes|Yes|Yes|
66 +|H.264/AVC encoding optimizations for minimizing bandwidth usage|No|Yes|Yes|Yes|
67 +|H.264/AVC support for 4K resolution|No|Yes|Yes|Yes|
6768
6869 ### VDI support for GPUs
6970
⋯ 60 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 21:54 UTC · 257 of 260 readable · 255 fully read · documentation 416/439 current