GPU vendors may have a separate licensing scheme for RDSH scenarios or restrict GPU use on the server OS, verify the requirements with your favorite vendor. For specific information about DDA, check out Plan for deploying Discrete Device Assignment. See Which graphics virtualization technology is right for you? for help figuring out what you need.
Remote Desktop Services 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, GPUs available to the physical RDSH server, and GPUs presented to the VMs by supported hypervisors.
Additionally, GPU-accelerated rendering and encoding can be enabled for improved app performance and scalability. Applications that require a GPU can be used over the remote connection. Remote Desktop Services support systems equipped with GPUs. Support for graphics processing unit (GPU) acceleration The following table shows which versions of RDS components work in a highly available deployment with three or more Connection Brokers. 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. If you are creating a highly available environment, all of your Connection Brokers need to be at the same OS level.
Setup windows 10 and server 2012 r2 remote desktop services upgrade#
Remember that a 2019 license server can process CALs from all previous versions of Windows Server, down to Windows Server 2003.įollow the upgrade order recommended in Upgrading your Remote Desktop Services environment. If you upgrade your RD Session Host to Windows Server 2019, also upgrade the license server. You can have a collection with Windows Server 2016 Session Hosts and one with Windows Server 2019 Session Hosts. Windows Server 2019 is backward-compatible with these components, which means a Windows Server 2016 or Windows Server 2012 R2 RD Session Host can connect to a 2019 RD Connection Broker, but not the other way around.įor RD Session Hosts - all Session Hosts in a collection need to be at the same level, but you can have multiple collections. Use Windows Server 2019 for your Remote Desktop infrastructure (the Web Access, Gateway, Connection Broker, and license server).
Make sure to review the system requirements for Windows Server. So with that in mind, here are basic guidelines for supported configurations of Remote Desktop Services in Windows Server. The question then becomes, which RDS components can work with different versions and which need to be the same? Most environments include multiple versions of Windows Server - for example, you may have an existing Windows Server 2012 R2 RDS deployment 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). When it comes to supported configurations for Remote Desktop Services environments, the largest concern tends to be version interoperability. Supported configurations for Remote Desktop ServicesĪpplies to: Windows Server 2022, Windows Server 2016, Windows Server 2019
0 kommentar(er)
