Remote Desktop Services supported configurations

This page's changes and edits · All guidance changes

Microsoft's edit · 7 Jul 2025 22:22 UTC

update

Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit 81a6079 · +14 ~~−14~~ lines · also on GitHub

⋯ 45 unchanged lines

4646

4747 Remote Desktop Session Hosts and single-session client operating systems can take advantage of the physical or virtual GPUs presented to the operating system in many ways, including the [Azure GPU optimized virtual machine sizes](/azure/virtual-machines/windows/sizes-gpu), GPUs available to the physical RDSH server, and GPUs presented to the VMs by supported hypervisors.

4848

49 −See [Which graphics virtualization technology is right for you?](rds-graphics-virtualization.md) for help with figuring out what you need. For specific information about DDA, check out [Plan for deploying Discrete Device Assignment](../../virtualization/hyper-v/plan/plan-for-deploying-devices-using-discrete-device-assignment.md).

49 +See [Which graphics virtualization technology is right for you?](rds-graphics-virtualization.md) for help with figuring out what you need. For specific information about Discrete Device Assignment, see [Plan for deploying Discrete Device Assignment](../../virtualization/hyper-v/plan/plan-for-deploying-devices-using-discrete-device-assignment.md).

5050

51 −GPU vendors might have a separate licensing scheme for RDSH scenarios or restrict GPU use on the server OS. Verify the requirements with your favorite vendor.

51 +GPU vendors might have a separate licensing scheme for RDSH scenarios or restrict GPU use on the server OS. Verify the requirements with your vendor.

5252

53 −GPUs presented by a non-Microsoft hypervisor or Cloud Platform must have drivers digitally signed by WHQL and supplied by the GPU vendor.

53 +GPUs presented by a non-Microsoft hypervisor or cloud platform must have drivers digitally signed by WHQL and supplied by the GPU vendor.

5454

5555 ### Remote Desktop Session Host support for GPUs

5656

⋯ 24 unchanged lines

8181 > [!NOTE]

8282 > Because of security concerns, RemoteFX vGPU is disabled by default on all versions of Windows starting with the July 14, 2020 Security Update and removed starting with the April 13, 2021 Security Update. To learn more, see [KB 4570006](https://support.microsoft.com/help/4570006).

8383

84 −RDS supports RemoteFX vGPUs when VM is running as a Hyper-V guest on Windows Server. The following guest operating systems have RemoteFX vGPU support:

84 +RDS supports RemoteFX vGPUs when the VM is running as a Hyper-V guest on Windows Server. The following guest operating systems have RemoteFX vGPU support:

8585

8686 - Windows 11

8787 - Windows 10

88 −- Windows Server in a single-session deployment only

88 +- Windows Server, in a single-session deployment only

8989

9090 ### Discrete Device Assignment support

9191

92 −RDS supports Physical GPUs presented with Discrete Device Assignment from Hyper-V hosts running Windows Server 2016 or later. See [Plan for deploying Discrete Device Assignment](../../virtualization/hyper-v/plan/plan-for-deploying-devices-using-discrete-device-assignment.md) for more details.

92 +RDS supports physical GPUs presented with Discrete Device Assignment from Hyper-V hosts running Windows Server 2016 or later. See [Plan for deploying Discrete Device Assignment](../../virtualization/hyper-v/plan/plan-for-deploying-devices-using-discrete-device-assignment.md) for more details.

9393

9494 ## VDI deployment – supported guest operating systems

9595

⋯ 4 unchanged lines

100100

101101 > [!NOTE]

102102 >

103 −> - RDS doesn't support heterogeneous session collections. The OSs of all VMs in a collection must be the same version.

103 +> - RDS doesn't support heterogeneous session collections. The operating systems of all VMs in a collection must be the same version.

104104 > - You can have separate homogeneous collections with different guest OS versions on the same host.

105105 > - The Hyper-V host used to run VMs must be the same version as the Hyper-V host used to create the original VM templates.

106106

107107 ## Single sign-on

108108

109 −RDS in Windows Server supports two main SSO experiences:

109 +RDS in Windows Server supports two main single sign-on (SSO) experiences:

110110

111111 - In-app (Remote Desktop application on Windows, iOS, Android, and Mac)

112112 - Web SSO

113113

114114 Using the Remote Desktop application, you can store credentials either as part of the connection info ([Mac](clients/remote-desktop-mac.md)) or as part of managed accounts ([iOS](clients/remote-desktop-ios.md#manage-your-user-accounts), [Android](clients/remote-desktop-android.md#manage-your-user-accounts), Windows) securely through the mechanisms unique to each OS.

115115

116 −To connect to desktops and RemoteApps with SSO through the inbox Remote Desktop Connection client on Windows, you must connect to the RD Web page through Internet Explorer. The following configuration options are required on the server side. No other configurations are supported for Web SSO:

116 +To connect to desktops and RemoteApps with SSO through the inbox Remote Desktop Connection client on Windows, you must connect to the RD Web page through Internet Explorer. The following configuration options are required on the server side. No other configurations are supported for Web SSO.

117117

118 −- RD Web set to Forms-Based Authentication (Default)

119 −- RD Gateway set to Password Authentication (Default)

118 +- RD Web set to form-based authentication (Default)

119 +- RD Gateway set to password authentication (Default)

120120 - RDS Deployment set to "Use RD Gateway credentials for remote computers" (Default) in the RD Gateway properties

121121

122122 > [!NOTE]

123 −> Due to the required configuration options, Web SSO isn't supported with smartcards. Users who sign in via smartcards might face multiple prompts to sign in.

123 +> Due to the required configuration options, Web SSO isn't supported with smart cards. Users who sign in by using smart cards might face multiple prompts to sign in.

124124

125 −For more information about creating VDI deployment of RDS, see [Supported Windows 10 security configurations for Remote Desktop Services VDI](rds-vdi-supported-config.md).

125 +For more information about creating a VDI deployment of RDS, see [Supported Windows 10 security configurations for Remote Desktop Services VDI](rds-vdi-supported-config.md).

126126

127127 ## Using RDS with application proxy services

128128

129 −You can use RDS with [Microsoft Entra application proxy](/azure/active-directory/application-proxy-publish-remote-desktop). RDS doesn't support using [Web Application Proxy](../remote-access/web-application-proxy/web-app-proxy-windows-server.md).

129 +You can use RDS with [Microsoft Entra application proxy](/azure/active-directory/application-proxy-publish-remote-desktop). RDS doesn't support [Web Application Proxy](../remote-access/web-application-proxy/web-app-proxy-windows-server.md).

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.