RemoteFX: Difference between revisions
Content deleted Content added
Citation bot (talk | contribs) Added date. | Use this bot. Report bugs. | Suggested by Whoop whoop pull up | #UCB_webform 1139/3458 |
|||
| (16 intermediate revisions by 12 users not shown) | |||
| Line 5: | Line 5: | ||
RemoteFX components introduced in Windows Server 2008 R2 SP1 include: |
RemoteFX components introduced in Windows Server 2008 R2 SP1 include: |
||
* RemoteFX vGPU: the ability to present a virtualized instance of a physical GPU into multiple Windows 7 virtual machines. This provides VMs with access to the physical GPU, enabling hardware-acceleration for rich graphics scenarios such as 3D rendering and game play. |
* RemoteFX vGPU: the ability to present a virtualized instance of a physical GPU into multiple Windows 7 virtual machines. This provides VMs with access to the physical GPU, enabling hardware-acceleration for rich graphics scenarios such as 3D rendering and game play. |
||
* RemoteFX USB Redirection: generalized support for redirecting USB devices into Windows 7 VMs. This allows peripheral devices connected to thin client terminals to be used within virtual machines.<ref>{{cite web|url=https://techcommunity.microsoft.com/t5/Enterprise-Mobility-Security/Introducing-Microsoft-RemoteFX-USB-Redirection-Part-2/ba-p/247060|title=Introducing Microsoft RemoteFX USB Redirection: Part 2|publisher=Microsoft Enterprise Mobility + Security Team}}</ref><ref>{{cite web|url=https://techcommunity.microsoft.com/t5/Enterprise-Mobility-Security/Introducing-Microsoft-RemoteFX-USB-Redirection-Part-3/ba-p/247085|title=Introducing Microsoft RemoteFX USB Redirection: Part 3|publisher=Microsoft Enterprise Mobility + Security Team}}</ref> |
* RemoteFX USB Redirection: generalized support for redirecting USB devices into Windows 7 VMs. This allows peripheral devices connected to thin client terminals to be used within virtual machines.<ref>{{cite web|url=https://techcommunity.microsoft.com/t5/Enterprise-Mobility-Security/Introducing-Microsoft-RemoteFX-USB-Redirection-Part-2/ba-p/247060|title=Introducing Microsoft RemoteFX USB Redirection: Part 2|date=8 September 2018 |publisher=Microsoft Enterprise Mobility + Security Team}}</ref><ref>{{cite web|url=https://techcommunity.microsoft.com/t5/Enterprise-Mobility-Security/Introducing-Microsoft-RemoteFX-USB-Redirection-Part-3/ba-p/247085|title=Introducing Microsoft RemoteFX USB Redirection: Part 3|date=8 September 2018 |publisher=Microsoft Enterprise Mobility + Security Team}}</ref> |
||
* RemoteFX Codec (also referred to as RemoteFX Calista Codec): a lossy codec that is capable of preserving a high-fidelity experience for both video and text. The RemoteFX Codec does not require any special hardware, and uses the CPU for encoding.<ref>{{cite news|url=http://msdn.microsoft.com/en-us/library/ff635792.aspx|title=RemoteFX Codec|publisher=Microsoft Protocol Specifications}}</ref> |
* RemoteFX Codec (also referred to as RemoteFX Calista Codec): a lossy codec that is capable of preserving a high-fidelity experience for both video and text. The RemoteFX Codec does not require any special hardware, and uses the CPU for encoding.<ref>{{cite news|url=http://msdn.microsoft.com/en-us/library/ff635792.aspx|title=RemoteFX Codec|publisher=Microsoft Protocol Specifications}}</ref> |
||
| Line 12: | Line 12: | ||
* RemoteFX Adaptive Graphics: The RemoteFX graphics pipeline dynamically adapts to various runtime conditions, such as graphic content types, CPU and network bandwidth availability, and client rendering speed.<ref>{{cite web|url=http://blogs.msdn.com/b/rds/archive/2012/08/06/remotefx-adaptive-graphics-in-windows-server-2012-and-windows-8.aspx|title=RemoteFX Adaptive Graphics in Windows Server 2012 and Windows 8|publisher=Remote Desktop Services Blog}}</ref> |
* RemoteFX Adaptive Graphics: The RemoteFX graphics pipeline dynamically adapts to various runtime conditions, such as graphic content types, CPU and network bandwidth availability, and client rendering speed.<ref>{{cite web|url=http://blogs.msdn.com/b/rds/archive/2012/08/06/remotefx-adaptive-graphics-in-windows-server-2012-and-windows-8.aspx|title=RemoteFX Adaptive Graphics in Windows Server 2012 and Windows 8|publisher=Remote Desktop Services Blog}}</ref> |
||
* RemoteFX for WAN: a series of changes to the network transport pipeline to support UDP and ensure a fluid experience in both WAN and wireless network configurations.<ref>{{cite web|url=http://blogs.msdn.com/b/rds/archive/2012/08/23/remotefx-for-wan-overview-of-intelligent-and-adaptive-transports-in-windows-8-and-windows-server-2012.aspx|title=RemoteFX for WAN: Overview of Intelligent and Adaptive Transports in Windows 8 and Windows Server 2012|publisher=Remote Desktop Services Blog}}</ref> |
* RemoteFX for WAN: a series of changes to the network transport pipeline to support UDP and ensure a fluid experience in both WAN and wireless network configurations.<ref>{{cite web|url=http://blogs.msdn.com/b/rds/archive/2012/08/23/remotefx-for-wan-overview-of-intelligent-and-adaptive-transports-in-windows-8-and-windows-server-2012.aspx|title=RemoteFX for WAN: Overview of Intelligent and Adaptive Transports in Windows 8 and Windows Server 2012|publisher=Remote Desktop Services Blog}}</ref> |
||
* RemoteFX Multi-Touch: supports remoting of gestures (e.g. pinch and zoom) between the client and host with up to 256 |
* RemoteFX Multi-Touch: supports remoting of gestures (e.g. pinch and zoom) between the client and host with up to 256 touchpoints<ref name=serverblog>{{cite web|url=http://blogs.technet.com/b/windowsserver/archive/2012/05/09/windows-server-2012-remote-desktop-services-rds.aspx|title=Windows Server 2012 Remote Desktop Services (RDS)|date=29 May 2020 |publisher=Windows Server Blog}}</ref> |
||
* RemoteFX Media Redirection API: allows Voice over IP (VoIP) applications to natively integrate with RemoteFX, and enables transmission and rendering of audio and video content directly on the client side.<ref>{{cite web|url=http://blogs.msdn.com/b/rds/archive/2012/07/24/fast-and-fluid-audio-video-experience-with-the-new-lync-and-remotefx.aspx|title=Fast and fluid audio/video experience with the new Lync and RemoteFX|publisher=Remote Desktop Services Blog}}</ref> |
* RemoteFX Media Redirection API: allows Voice over IP (VoIP) applications to natively integrate with RemoteFX, and enables transmission and rendering of audio and video content directly on the client side.<ref>{{cite web|url=http://blogs.msdn.com/b/rds/archive/2012/07/24/fast-and-fluid-audio-video-experience-with-the-new-lync-and-remotefx.aspx|title=Fast and fluid audio/video experience with the new Lync and RemoteFX|publisher=Remote Desktop Services Blog}}</ref> |
||
* Choice of GPU: All RemoteFX features can be used with either a software-emulated GPU, which is available by default in all virtual machines and session hosts, or they can benefit from hardware acceleration when a physical video card is placed in the server and the RemoteFX vGPU is enabled.<ref>{{cite web|url=http://blog.concurrency.com/infrastructure/remote-desktop-services-in-windows-8/|title=Remote Desktop Services in Windows 8 |work=concurrency.com}}</ref> |
* Choice of GPU: All RemoteFX features can be used with either a software-emulated GPU, which is available by default in all virtual machines and session hosts, or they can benefit from hardware acceleration when a physical video card is placed in the server and the RemoteFX vGPU is enabled.<ref>{{cite web|url=http://blog.concurrency.com/infrastructure/remote-desktop-services-in-windows-8/|title=Remote Desktop Services in Windows 8 |work=concurrency.com}}</ref> |
||
| Line 19: | Line 19: | ||
* RemoteFX vGPU: updated to support [[DirectX 11]]<ref name=serverblog /> |
* RemoteFX vGPU: updated to support [[DirectX 11]]<ref name=serverblog /> |
||
* RemoteFX USB Redirection: updated to support all desktop remoting scenarios vGPU-enabled virtual machines, traditional VMs, desktop sessions and physical desktop hosts<ref name=serverblog /> |
* RemoteFX USB Redirection: updated to support all desktop remoting scenarios vGPU-enabled virtual machines, traditional VMs, desktop sessions and physical desktop hosts<ref name=serverblog /> |
||
* RemoteFX Codec (also referred to as RemoteFX Progressive Calista Codec): updated to include progressive rendering, which is more effective for rendering content over the WAN by sending images at full resolution only if bandwidth permits.<ref>{{cite web|url=http://croftcomputers.wordpress.com/2012/04/23/remotefx-windows-server-2008-r2-vs-windows-sever-2012/|title=RemoteFX – Windows Server 2008 R2 vs. Windows Server 2012|work=croftcomputers.wordpress.com}}</ref> |
* RemoteFX Codec (also referred to as RemoteFX Progressive Calista Codec): updated to include progressive rendering, which is more effective for rendering content over the WAN by sending images at full resolution only if bandwidth permits.<ref>{{cite web|url=http://croftcomputers.wordpress.com/2012/04/23/remotefx-windows-server-2008-r2-vs-windows-sever-2012/|title=RemoteFX – Windows Server 2008 R2 vs. Windows Server 2012|work=croftcomputers.wordpress.com|date=23 April 2012 }}</ref> |
||
=== Windows Server 2016, Windows 10 Enterprise === |
=== Windows Server 2016, Windows 10 Enterprise === |
||
| Line 33: | Line 33: | ||
== Requirements == |
== Requirements == |
||
In Windows Server 2008 R2, the RemoteFX Codec could be leveraged for both session hosting (Remote Desktop Session Hosts) and VDI scenarios (and Remote Desktop Virtualization Hosts). The RemoteFX vGPU and RemoteFX USB Redirection features could only be used in VDI scenarios (Remote Desktop Virtualization Hosts).<ref>{{cite web|url=https://technet.microsoft.com/en-us/library/ff817578(WS.10).aspx|title=Microsoft RemoteFX|publisher=Microsoft Technet}}</ref> |
In Windows Server 2008 R2, the RemoteFX Codec could be leveraged for both session hosting (Remote Desktop Session Hosts) and VDI scenarios (and Remote Desktop Virtualization Hosts). The RemoteFX vGPU and RemoteFX USB Redirection features could only be used in VDI scenarios (Remote Desktop Virtualization Hosts).<ref>{{cite web|url=https://technet.microsoft.com/en-us/library/ff817578(WS.10).aspx|title=Microsoft RemoteFX|date=2 July 2012 |publisher=Microsoft Technet}}</ref> |
||
Windows 10 version 1511 brings RemoteFX to client Hyper-V, removing dependency on [[Remote Desktop Services]] role.<ref>{{cite web|url=https://www.reddit.com/r/Windows10/comments/3kr2lk/after_9_months_of_begging_it_looks_like_remotefx/|title=After 9 months of begging, it looks like RemoteFX is coming to client Hyper-V|publisher=Reddit}}</ref> |
Windows 10 version 1511 brings RemoteFX to client [[Hyper-V]], removing dependency on [[Remote Desktop Services]] role.<ref>{{cite web|url=https://www.reddit.com/r/Windows10/comments/3kr2lk/after_9_months_of_begging_it_looks_like_remotefx/|title=After 9 months of begging, it looks like RemoteFX is coming to client Hyper-V|date=13 September 2015 |publisher=Reddit}}</ref> |
||
Generation 2 VMs on Windows Server 2012 R2 do not support RemoteFX.<ref>{{cite web|title=Generation 2 Virtual Machine Overview|publisher=Microsoft Technet|url=https://technet.microsoft.com/en-us/library/dn282285.aspx}}</ref> Windows Server 2016 added such support.<ref>{{cite web|title=RemoteFX and vGPU Improvements in Windows Server 2016 Hyper-V|url=https://blog.workinghardinit.work/2015/09/01/remotefx-and-vgpu-improvements-in-windows-server-2016-hyper-v/}}</ref> |
Generation 2 VMs on Windows Server 2012 R2 do not support RemoteFX.<ref>{{cite web|title=Generation 2 Virtual Machine Overview|date=25 October 2016 |publisher=Microsoft Technet|url=https://technet.microsoft.com/en-us/library/dn282285.aspx}}</ref> Windows Server 2016 added such support.<ref>{{cite web|title=RemoteFX and vGPU Improvements in Windows Server 2016 Hyper-V|date=September 2015 |url=https://blog.workinghardinit.work/2015/09/01/remotefx-and-vgpu-improvements-in-windows-server-2016-hyper-v/}}</ref> |
||
In Windows Server 2012, all features of RemoteFX (with the exception of the vGPU) can be used with or without a physical GPU present in the server.<ref>{{cite web|url=http://blogs.msdn.com/b/rds/archive/2012/07/25/delivering-a-fast-and-fluid-user-experience-on-wan-remotefx-in-windows-server-2012-and-windows-8.aspx|title=Delivering a Fast and Fluid User Experience on WAN RemoteFX in Windows Server 2012|publisher=Remote Desktop Services Blog}}</ref> When no GPU is present in the server, a synthetic software-emulated GPU is used to render content. When a GPU is present in the server, it can be used to hardware accelerate the graphics via the RemoteFX vGPU feature. |
In Windows Server 2012, all features of RemoteFX (with the exception of the vGPU) can be used with or without a physical GPU present in the server.<ref>{{cite web|url=http://blogs.msdn.com/b/rds/archive/2012/07/25/delivering-a-fast-and-fluid-user-experience-on-wan-remotefx-in-windows-server-2012-and-windows-8.aspx|title=Delivering a Fast and Fluid User Experience on WAN RemoteFX in Windows Server 2012|publisher=Remote Desktop Services Blog}}</ref> When no GPU is present in the server, a synthetic software-emulated GPU is used to render content. When a GPU is present in the server, it can be used to hardware accelerate the graphics via the RemoteFX vGPU feature. |
||
| Line 43: | Line 43: | ||
=== RemoteFX vGPU Requirements === |
=== RemoteFX vGPU Requirements === |
||
The RemoteFX vGPU has the following requirements:<ref name="hardware2008r2">{{cite web|url= https://technet.microsoft.com/en-us/library/ff817602(WS.10).aspx|title=Hardware Considerations for RemoteFX|publisher=Microsoft TechNet}}</ref> |
The RemoteFX vGPU has the following requirements:<ref name="hardware2008r2">{{cite web|url= https://technet.microsoft.com/en-us/library/ff817602(WS.10).aspx|title=Hardware Considerations for RemoteFX|date=2 July 2012 |publisher=Microsoft TechNet}}</ref> |
||
* [[Hyper-V]] must be installed on the server. The VMs must be created and run using Hyper-V. |
* [[Hyper-V]] must be installed on the server. The VMs must be created and run using Hyper-V. |
||
* The server's CPU must support [[Second Level Address Translation]] (SLAT), and have it enabled. |
* The server's CPU must support [[Second Level Address Translation]] (SLAT), and have it enabled. |
||
* For Windows Server 2008 R2 SP1, at least one [[DirectX]] 9.0c and 10.0 capable graphics card must be installed on the server. |
* For Windows Server 2008 R2 SP1, at least one [[DirectX]] 9.0c and 10.0 capable graphics card must be installed on the server. |
||
* For Windows Server 2012, at least one DirectX 11.0 capable graphics card with a WDDM 1.2 driver must be installed on the server.<ref>{{cite web|url=http://blogs.msdn.com/b/rds/archive/2012/06/13/richvgpu.aspx|title=Your desktop will be a rich DX11-based experience, and your virtual GPU should be too|publisher=Remote Desktop Services Blog}}</ref> |
* For Windows Server 2012, at least one DirectX 11.0 capable graphics card with a WDDM 1.2 driver must be installed on the server.<ref>{{cite web|url=http://blogs.msdn.com/b/rds/archive/2012/06/13/richvgpu.aspx|title=Your desktop will be a rich DX11-based experience, and your virtual GPU should be too|publisher=Remote Desktop Services Blog}}</ref> |
||
* The host machine must not be a Domain Controller. For single server configuration, Microsoft supports running Domain Controller as a Hyper-V virtual machine.<ref>{{cite web|url=http://support.microsoft.com/kb/2506417|title=New and existing RemoteFX-enabled virtual machines do not start on a domain controller that is running the Remote Desktop Virtualization Host service in Windows Server 2008 R2 Service Pack 1}}</ref> |
* The host machine must not be a Domain Controller. For single server configuration, Microsoft supports running Domain Controller as a Hyper-V virtual machine.<ref>{{cite web|url=http://support.microsoft.com/kb/2506417|title=New and existing RemoteFX-enabled virtual machines do not start on a domain controller that is running the Remote Desktop Virtualization Host service in Windows Server 2008 R2 Service Pack 1|date=23 February 2023 }}</ref> |
||
Windows Server 2008 R2 with SP1 has been tested for up to twelve virtual machines per GPU, for a total of twenty-four virtual machines on two physical GPUs.<ref name=hardware2008r2 /> |
Windows Server 2008 R2 with SP1 has been tested for up to twelve virtual machines per GPU, for a total of twenty-four virtual machines on two physical GPUs.<ref name=hardware2008r2 /> |
||
| Line 55: | Line 55: | ||
Graphics cards that meet these are typically professional workstation products such as ATI/AMD's FirePro, v5800, v5900, v7800, v7900, v8800, v9800, and Nvidia's Quadro 2000, 3800, 4000, 4800, 5000, 5800, 6000, Quadro FX 2800M and 880M, QuadroPlex 7000 and Tesla M2070Q.<ref>{{cite web|url=http://www.windowsservercatalog.com/results.aspx?&chtext=&cstext=&csttext=&chbtext=&bCatID=1283&cpID=0&avc=10&ava=0&avq=37&OR=1&PGS=25&ready=0|title=RemoteFX qualified video cards|publisher=Windows Server Catalog}} {{Dead link|date=November 2016}}</ref> |
Graphics cards that meet these are typically professional workstation products such as ATI/AMD's FirePro, v5800, v5900, v7800, v7900, v8800, v9800, and Nvidia's Quadro 2000, 3800, 4000, 4800, 5000, 5800, 6000, Quadro FX 2800M and 880M, QuadroPlex 7000 and Tesla M2070Q.<ref>{{cite web|url=http://www.windowsservercatalog.com/results.aspx?&chtext=&cstext=&csttext=&chbtext=&bCatID=1283&cpID=0&avc=10&ava=0&avq=37&OR=1&PGS=25&ready=0|title=RemoteFX qualified video cards|publisher=Windows Server Catalog}} {{Dead link|date=November 2016}}</ref> |
||
Servers running the RemoteFX vGPU need to accommodate such graphics cards with either larger power supplies and more PCIe slots<ref>{{cite news|url=http://dcsblog.burtongroup.com/data_center_strategies/2010/03/is-that-a-graphics-card-in-my-server.html|title=Is That a Graphics Card in My Server?|work=dcsblog.burtongroup.com}}</ref> or alternatively connect existing servers to an external PCIe expansion chassis. |
Servers running the RemoteFX vGPU need to accommodate such graphics cards with either larger power supplies and more PCIe slots<ref>{{cite news|url=http://dcsblog.burtongroup.com/data_center_strategies/2010/03/is-that-a-graphics-card-in-my-server.html|title=Is That a Graphics Card in My Server?|work=dcsblog.burtongroup.com}}</ref> or alternatively, connect existing servers to an external PCIe expansion chassis. |
||
=== Guest OS requirements === |
=== Guest OS requirements === |
||
The RemoteFX virtual graphics adapter is only supported by Enterprise editions of Windows,<ref>{{cite web|url=https://social.technet.microsoft.com/wiki/contents/articles/16652.remotefx-vgpu-setup-and-configuration-guide-for-windows-server-2012.aspx#Requirements_for_RemoteFX_vGPU|title=RemoteFX vGPU Setup and Configuration Guide for Windows Server 2012|publisher=Microsoft TechNet Wiki}}</ref> starting from Windows 7 SP1. Other editions are missing the required drivers to use the RemoteFX graphics adapter and will fall back to the default emulated graphics adapter instead. |
The RemoteFX virtual graphics adapter is only supported by Enterprise editions of Windows,<ref>{{cite web|url=https://social.technet.microsoft.com/wiki/contents/articles/16652.remotefx-vgpu-setup-and-configuration-guide-for-windows-server-2012.aspx#Requirements_for_RemoteFX_vGPU|title=RemoteFX vGPU Setup and Configuration Guide for Windows Server 2012|date=17 January 2024 |publisher=Microsoft TechNet Wiki}}</ref> starting from Windows 7 SP1. Other editions are missing the required drivers to use the RemoteFX graphics adapter and will fall back to the default emulated graphics adapter instead. |
||
== References == |
== References == |
||
Latest revision as of 12:07, 9 May 2024
Microsoft RemoteFX is a Microsoft brand name that covers a set of technologies that enhance visual experience of the Microsoft-developed remote display protocol Remote Desktop Protocol (RDP).[1] RemoteFX was first introduced in Windows Server 2008 R2 SP1 and is based on intellectual property that Microsoft acquired and continued to develop since acquiring Calista Technologies.[2] It is a part of the overall Remote Desktop Services workload.
History
[edit]Windows Server 2008 R2 SP1
[edit]RemoteFX components introduced in Windows Server 2008 R2 SP1 include:
- RemoteFX vGPU: the ability to present a virtualized instance of a physical GPU into multiple Windows 7 virtual machines. This provides VMs with access to the physical GPU, enabling hardware-acceleration for rich graphics scenarios such as 3D rendering and game play.
- RemoteFX USB Redirection: generalized support for redirecting USB devices into Windows 7 VMs. This allows peripheral devices connected to thin client terminals to be used within virtual machines.[3][4]
- RemoteFX Codec (also referred to as RemoteFX Calista Codec): a lossy codec that is capable of preserving a high-fidelity experience for both video and text. The RemoteFX Codec does not require any special hardware, and uses the CPU for encoding.[5]
Windows Server 2012
[edit]In Windows Server 2012, the following components were added to RemoteFX.[6]
- RemoteFX Adaptive Graphics: The RemoteFX graphics pipeline dynamically adapts to various runtime conditions, such as graphic content types, CPU and network bandwidth availability, and client rendering speed.[7]
- RemoteFX for WAN: a series of changes to the network transport pipeline to support UDP and ensure a fluid experience in both WAN and wireless network configurations.[8]
- RemoteFX Multi-Touch: supports remoting of gestures (e.g. pinch and zoom) between the client and host with up to 256 touchpoints[9]
- RemoteFX Media Redirection API: allows Voice over IP (VoIP) applications to natively integrate with RemoteFX, and enables transmission and rendering of audio and video content directly on the client side.[10]
- Choice of GPU: All RemoteFX features can be used with either a software-emulated GPU, which is available by default in all virtual machines and session hosts, or they can benefit from hardware acceleration when a physical video card is placed in the server and the RemoteFX vGPU is enabled.[11]
In addition, the following components were updated:
- RemoteFX vGPU: updated to support DirectX 11[9]
- RemoteFX USB Redirection: updated to support all desktop remoting scenarios vGPU-enabled virtual machines, traditional VMs, desktop sessions and physical desktop hosts[9]
- RemoteFX Codec (also referred to as RemoteFX Progressive Calista Codec): updated to include progressive rendering, which is more effective for rendering content over the WAN by sending images at full resolution only if bandwidth permits.[12]
Windows Server 2016, Windows 10 Enterprise
[edit]In Windows Server 2016 (RDP 10), the following components were added to RemoteFX.[13]
- OpenGL 4.4 and OpenCL 1.1 API support in a virtual machine with the RemoteFX adapter
- More dedicated VRAM for the RemoteFX adapter
- Various performance improvements in transport and API implementations
RemoteFX Media Streaming (H.264) replaced Multi Media Redirection (MMR). Note: MMR is now completely removed from RDP 10 given that RemoteFX Media Streaming works for all types of video content whereas MMR which just worked for some.[14]
RemoteFX vGPU Deprecation
[edit]Beginning in July 2020 RemoteFX vGPU was deprecated in all versions of Windows because of security vulnerabilities. It was scheduled to be completely removed in February 2021.[15]
Requirements
[edit]In Windows Server 2008 R2, the RemoteFX Codec could be leveraged for both session hosting (Remote Desktop Session Hosts) and VDI scenarios (and Remote Desktop Virtualization Hosts). The RemoteFX vGPU and RemoteFX USB Redirection features could only be used in VDI scenarios (Remote Desktop Virtualization Hosts).[16]
Windows 10 version 1511 brings RemoteFX to client Hyper-V, removing dependency on Remote Desktop Services role.[17]
Generation 2 VMs on Windows Server 2012 R2 do not support RemoteFX.[18] Windows Server 2016 added such support.[19]
In Windows Server 2012, all features of RemoteFX (with the exception of the vGPU) can be used with or without a physical GPU present in the server.[20] When no GPU is present in the server, a synthetic software-emulated GPU is used to render content. When a GPU is present in the server, it can be used to hardware accelerate the graphics via the RemoteFX vGPU feature.
RemoteFX vGPU Requirements
[edit]The RemoteFX vGPU has the following requirements:[21]
- Hyper-V must be installed on the server. The VMs must be created and run using Hyper-V.
- The server's CPU must support Second Level Address Translation (SLAT), and have it enabled.
- For Windows Server 2008 R2 SP1, at least one DirectX 9.0c and 10.0 capable graphics card must be installed on the server.
- For Windows Server 2012, at least one DirectX 11.0 capable graphics card with a WDDM 1.2 driver must be installed on the server.[22]
- The host machine must not be a Domain Controller. For single server configuration, Microsoft supports running Domain Controller as a Hyper-V virtual machine.[23]
Windows Server 2008 R2 with SP1 has been tested for up to twelve virtual machines per GPU, for a total of twenty-four virtual machines on two physical GPUs.[21]
Although any GPU meeting the above requirements will be capable of using RemoteFX, the Windows Server Catalog carries an additional qualification to further define the requirements for server-qualified GPUs. These specifications define GPUs configuration requirements and provide VM performance targets.[24] Graphics cards that meet these are typically professional workstation products such as ATI/AMD's FirePro, v5800, v5900, v7800, v7900, v8800, v9800, and Nvidia's Quadro 2000, 3800, 4000, 4800, 5000, 5800, 6000, Quadro FX 2800M and 880M, QuadroPlex 7000 and Tesla M2070Q.[25]
Servers running the RemoteFX vGPU need to accommodate such graphics cards with either larger power supplies and more PCIe slots[26] or alternatively, connect existing servers to an external PCIe expansion chassis.
Guest OS requirements
[edit]The RemoteFX virtual graphics adapter is only supported by Enterprise editions of Windows,[27] starting from Windows 7 SP1. Other editions are missing the required drivers to use the RemoteFX graphics adapter and will fall back to the default emulated graphics adapter instead.
References
[edit]- ^ "Microsoft Announces New VDI Brand RemoteFX". Redmond Channel Partner.
- ^ "Explaining Microsoft RemoteFX". Windows Virtualization Team Blog.
- ^ "Introducing Microsoft RemoteFX USB Redirection: Part 2". Microsoft Enterprise Mobility + Security Team. 8 September 2018.
- ^ "Introducing Microsoft RemoteFX USB Redirection: Part 3". Microsoft Enterprise Mobility + Security Team. 8 September 2018.
- ^ "RemoteFX Codec". Microsoft Protocol Specifications.
- ^ "What's New in Windows Server 2012". Remote Desktop Services Blog.
- ^ "RemoteFX Adaptive Graphics in Windows Server 2012 and Windows 8". Remote Desktop Services Blog.
- ^ "RemoteFX for WAN: Overview of Intelligent and Adaptive Transports in Windows 8 and Windows Server 2012". Remote Desktop Services Blog.
- ^ a b c "Windows Server 2012 Remote Desktop Services (RDS)". Windows Server Blog. 29 May 2020.
- ^ "Fast and fluid audio/video experience with the new Lync and RemoteFX". Remote Desktop Services Blog.
- ^ "Remote Desktop Services in Windows 8". concurrency.com.
- ^ "RemoteFX – Windows Server 2008 R2 vs. Windows Server 2012". croftcomputers.wordpress.com. 23 April 2012.
- ^ "RemoteFX vGPU Updates in Windows Server Next". Retrieved 2016-09-15.
- ^ "Remote Desktop Protocol (RDP) 10 AVC/H.264 improvements in Windows 10 and Windows Server 2016 Technical Preview". Retrieved 2016-09-15.
- ^ "Update to disable and remove the RemoteFX vGPU component in Windows". Retrieved 2020-10-23.
- ^ "Microsoft RemoteFX". Microsoft Technet. 2 July 2012.
- ^ "After 9 months of begging, it looks like RemoteFX is coming to client Hyper-V". Reddit. 13 September 2015.
- ^ "Generation 2 Virtual Machine Overview". Microsoft Technet. 25 October 2016.
- ^ "RemoteFX and vGPU Improvements in Windows Server 2016 Hyper-V". September 2015.
- ^ "Delivering a Fast and Fluid User Experience on WAN RemoteFX in Windows Server 2012". Remote Desktop Services Blog.
- ^ a b "Hardware Considerations for RemoteFX". Microsoft TechNet. 2 July 2012.
- ^ "Your desktop will be a rich DX11-based experience, and your virtual GPU should be too". Remote Desktop Services Blog.
- ^ "New and existing RemoteFX-enabled virtual machines do not start on a domain controller that is running the Remote Desktop Virtualization Host service in Windows Server 2008 R2 Service Pack 1". 23 February 2023.
- ^ "RemoteFX Additional Qualifications". Windows Server Catalog.
- ^ "RemoteFX qualified video cards". Windows Server Catalog. [dead link]
- ^ "Is That a Graphics Card in My Server?". dcsblog.burtongroup.com.
- ^ "RemoteFX vGPU Setup and Configuration Guide for Windows Server 2012". Microsoft TechNet Wiki. 17 January 2024.
