Remotefx для windows 10

Вопрос

As we don’t have gpedit.msc on Windows 10 HOME edition, how can we enable RemoteFX in order to use USB devices when connecting to an RDP server? Maybe editing a registry key. if yes .. which one?

Все ответы

From this case below, we can see that:

HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client

With a value of fUsbRedirectionEnableMode. If you set this to 2, that should be the same as enabling the policy.

However, RemoteFX vGPU requirements:

Windows Server 2016 or Windows 10

DX 11.0 compatible GPU with WDDM 1.2 compatible driver

Windows Server RD Virtualization Host role enabled (enables Hyper-V Role)

Server with a CPU that supports SLAT (Second Level Address Translation)

However, we cannot enable Hyper-V in Home edition, this feature only be supported on Pro and Enterprise/Education edition.

Microsoft RemoteFX on Windows Server and Windows 10 | Parallels

RemoteFX is a set of technologies that enhance the visual experience of Remote Desktop Protocol (RDP), thus allowing users to experience rich media support, highly synchronized audio and graphics, making it feel like they are using a locally executing desktop when in fact they are accessing the desktop remotely. The intellectual idea behind RemoteFX was developed by Calista Technologies, which was acquired by Microsoft and developed to create the current, final version of RemoteFX.

Microsoft RemoteFX

Microsoft RemoteFX brought graphics hardware support to Hyper-V virtual machines (VMs) when it was released as part of Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2 back in 2011.

Among the innovations that RemoteFX introduced was RemoteFX vGPU, which enabled hardware acceleration in VMs by allowing them to tap physical graphic processing units (GPUs) and presenting them as virtualized GPUs. Others include RemoteFX USB Redirection, which allowed peripheral USB devices to be used with VMs, and the RemoteFX Callista codec, which allowed the use of high-fidelity video and text in VMs.

Another major feature was Windows Multimedia Redirection (MMR), which was used to stream multimedia content using Windows Media Player (WMP) through a remote session. The media stream was redirected to the client through MMR, and it was suitable for supported video formats on the local area network (LAN). However, MMR was missing some key points, including the following:

• Non-WMP content (such as Flash and QuickTime formats) was not supported.
• MMR needed to be decoded and rendered on the client computer. The result was limited streaming quality according to client machine specifications.
• The bandwidth usage was dependent on the bit rate of the original video. If you had to stream videos with a high bitrate, a fast connection was needed, which was less than ideal.
• In cases of low bandwidth or high latency networks, the user experience was terrible. The frame rate was low, and there was too much frame skipping, resulting in data loss and unstable streaming.

Windows Server 2012 and Windows 8 led to further improvements in the major RemoteFX features. It also introduced other innovations, including RemoteFX Adaptive Graphics, RemoteFX for WAN, RemoteFX Multi-Touch, and RemoteFX Media Redirection AP.

RemoteFX was further improved in the subsequent Windows Server 2016 and Windows 10 Enterprise releases. Microsoft RemoteFX Media Streaming replaced MMR entirely, which still did not support all types of video content. On the other hand, RemoteFX Media Streaming combined broad video format support with the H.264 codec to provide host-side rendering and redirection.

Benefits of Microsoft RemoteFX Media Streaming

1. Detection and redirection of all media content, including but not limited to Silverlight, Flash, QuickTime, and HTML5 videos. Users have a consistent experience regardless of video formats or video applications.
2. When compared to RDP in Windows 7, Microsoft RemoteFX Media Streaming consumes up to 90% less bandwidth. The actual difference in bandwidth depends on the size and frame rate of the original video.
3. Microsoft RemoteFX Media Streaming leverages network auto-detection and the client capabilities to dynamically adapt the encoding bitrate and frame rate to provide the optimum user experience.
4. The user experience is excellent even on WAN networks due to adaptive media streaming and Microsoft RemoteFX Media Streaming leveraging the User Datagram Protocol (UDP).

Configuration Requirements

RemoteFX in Windows Server 2012 and higher versions were designed to make things simpler with out-of-the-box features. When connecting to a virtual desktop that had RemoteFX virtual graphics processing unit (vGPU) installed, the host Hyper-V server must have a non-server core setup without any media codecs. Additional configuration is not required when enabling RemoteFX Media Streaming along with the rest of Remote Desktop Services.

Other requirements include:

• A DirectX 11.0-compatible GPU with a WDDM 1.2-compatible driver. If you are using Windows Server 2008 R2 SP1, the server must have at least one DirectX 9.0c and 10.0 capable graphics card.
• A CPU with enabled Second-Level Address Translation (SLAT) support
• Installed instances and VMs created with and running on Hyper-V
• A non-Domain Controller host machine
• RemoteFX vGPU support is enabled in the following operating systems:
• Windows 7 SP1
• Windows 8.1
• Windows 10 1703 or later
• Windows Server 2016 in a single-session deployment only

It is recommended to use graphics cards designed to run on professional workstations, although any GPU with OpenGL and OpenCL functionality and DirectX 11.0 is supported. The RemoteFX virtual graphics adapter is only supported by Enterprise editions of Windows.

To get started with Parallels RAS, download your free trial.

Deploy graphics devices using RemoteFX vGPU

Applies to: Windows Server 2016, Microsoft Hyper-V Server 2016

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.

The vGPU feature for RemoteFX makes it possible for multiple virtual machines to share a physical GPU. Rendering and compute resources are shared dynamically among virtual machines, making RemoteFX vGPU appropriate for high-burst workloads where dedicated GPU resources are not required. For example, in a VDI service, RemoteFX vGPU can be used to offload app rendering costs to the GPU, with the effect of decreasing CPU load and improving service scalability.

RemoteFX vGPU requirements

Host system requirements:

• Windows Server 2016
• A DirectX 11.0-compatible GPU with a WDDM 1.2-compatible driver
• A CPU with Second Level Address Translation (SLAT) support

Guest VM requirements:

Additional considerations for guest VMs:

• OpenGL and OpenCL functionality is only available in guests running Windows 10 or Windows Server 2016.
• DirectX 11.0 is only available for guests running Windows 8 or later.

Enable RemoteFX vGPU

To configure RemoteFX vGPU on your Windows Server 2016 host:

1. Install the graphics drivers recommended by your GPU vendor for Windows Server 2016.
2. Create a VM running a guest OS supported by RemoteFX vGPU. To learn more, see RemoteFX 3D Video Adapter (vGPU) support.
3. Add the RemoteFX 3D graphics adapter to the VM. To learn more, see Configure the RemoteFX vGPU 3D adapter.

By default, RemoteFX vGPU will use all available and supported GPUs. To limit which GPUs the RemoteFX vGPU uses, follow these steps:

1. Navigate to the Hyper-V settings in Hyper-V Manager.
2. Select Physical GPUs in Hyper-V Settings.
3. Select the GPU that you don’t want to use, and then clear Use this GPU with RemoteFX.

Configure the RemoteFX vGPU 3D adapter

You can use either the Hyper-V Manager UI or PowerShell cmdlets to configure the RemoteFX vGPU 3D graphics adapter.

Configure RemoteFX vGPU with Hyper-V Manager

Stop the VM if it’s currently running.

Open Hyper-V Manager, navigate to VM Settings, then select Add Hardware.

Select RemoteFX 3D Graphics Adapter, then select Add.

Set the maximum number of monitors, maximum monitor resolution, and dedicated video memory, or leave the default values.

• Setting higher values for any of these options will impact your service scale, so you should only set what is necessary.
• When you need to use 1 GB of dedicated VRAM, use a 64-bit guest VM instead of 32-bit (x86) for best results.

Select OK to finish the configuration.

Configure RemoteFX vGPU with PowerShell cmdlets

Use the following PowerShell cmdlets to add, review, and configure the adapter:

Monitor performance

The performance and scale of a RemoteFX vGPU-enabled service are determined by a variety of factors such as number of GPUs on your system, total GPU memory, amount of system memory and memory speed, number of CPU cores and CPU clock frequency, storage speed, and NUMA implementation.

Host system memory

For every VM enabled with a vGPU, RemoteFX uses system memory both in the guest operating system and in the host server. The hypervisor guarantees the availability of system memory for a guest operating system. On the host, each vGPU-enabled virtual desktop needs to advertise its system memory requirement to the hypervisor. When the vGPU-enabled virtual desktop starts, the hypervisor reserves additional system memory in the host.

The memory requirement for the RemoteFX-enabled server is dynamic because the amount of memory consumed on the RemoteFX-enabled server is dependent on the number of monitors that are associated with the vGPU-enabled virtual desktops and the maximum resolution for those monitors.

Host GPU video memory

Every vGPU-enabled virtual desktop uses the GPU hardware video memory on the host server to render the desktop. In addition, a codec uses the video memory to compress the rendered screen. The amount of memory needed for rendering and compression is directly based on the number of monitors provisioned to the virtual machine. The amount of reserved video memory varies based on the system screen resolution and how many monitors there are. Some users require a higher screen resolution for specific tasks, but there’s greater scalability with lower resolution settings if all other settings remain constant.

Host CPU

The hypervisor schedules the host and VMs on the CPU. The overhead is increased on a RemoteFX-enabled host because the system runs an additional process (rdvgm.exe) per vGPU-enabled virtual desktop. This process uses the graphics device driver to run commands on the GPU. The codec also uses the CPU to compress screen data that needs to be sent back to the client.

More virtual processors mean a better user experience. We recommend allocating at least two virtual CPUs per vGPU-enabled virtual desktop. We also recommend using the x64 architecture for vGPU-enabled virtual desktops because the performance on x64 virtual machines is better compared to x86 virtual machines.

GPU processing power

Every vGPU-enabled virtual desktop has a corresponding DirectX process that runs on the host server. This process replays all graphics commands it receives from the RemoteFX virtual desktop onto the physical GPU. This is like running multiple DirectX applications at the same time on the same physical GPU.

Usually, graphics devices and drivers are tuned to run only a few applications on the desktop at a time, but RemoteFX stretches the GPUs to go even further. vGPUs come with performance counters that measure the GPU response to RemoteFX requests and help you make sure the GPUs aren’t stretched too far.

When a GPU is low on resources, read and write operations take a long time to complete. Administrators can use performance counters to know when to adjust resources and prevent downtime for users.

Learn more about performance counters for monitoring RemoteFX vGPU behavior at Diagnose graphics performance issues in Remote Desktop.

Microsoft RemoteFX on Windows Server and Windows 10 | Parallels

RemoteFX is a set of technologies that enhance the visual experience of Remote Desktop Protocol (RDP), thus allowing users to experience rich media support, highly synchronized audio and graphics, making it feel like they are using a locally executing desktop when in fact they are accessing the desktop remotely. The intellectual idea behind RemoteFX was developed by Calista Technologies, which was acquired by Microsoft and developed to create the current, final version of RemoteFX.

Microsoft RemoteFX

Microsoft RemoteFX brought graphics hardware support to Hyper-V virtual machines (VMs) when it was released as part of Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2 back in 2011.

Among the innovations that RemoteFX introduced was RemoteFX vGPU, which enabled hardware acceleration in VMs by allowing them to tap physical graphic processing units (GPUs) and presenting them as virtualized GPUs. Others include RemoteFX USB Redirection, which allowed peripheral USB devices to be used with VMs, and the RemoteFX Callista codec, which allowed the use of high-fidelity video and text in VMs.

Another major feature was Windows Multimedia Redirection (MMR), which was used to stream multimedia content using Windows Media Player (WMP) through a remote session. The media stream was redirected to the client through MMR, and it was suitable for supported video formats on the local area network (LAN). However, MMR was missing some key points, including the following:

• Non-WMP content (such as Flash and QuickTime formats) was not supported.
• MMR needed to be decoded and rendered on the client computer. The result was limited streaming quality according to client machine specifications.
• The bandwidth usage was dependent on the bit rate of the original video. If you had to stream videos with a high bitrate, a fast connection was needed, which was less than ideal.
• In cases of low bandwidth or high latency networks, the user experience was terrible. The frame rate was low, and there was too much frame skipping, resulting in data loss and unstable streaming.

Windows Server 2012 and Windows 8 led to further improvements in the major RemoteFX features. It also introduced other innovations, including RemoteFX Adaptive Graphics, RemoteFX for WAN, RemoteFX Multi-Touch, and RemoteFX Media Redirection AP.

RemoteFX was further improved in the subsequent Windows Server 2016 and Windows 10 Enterprise releases. Microsoft RemoteFX Media Streaming replaced MMR entirely, which still did not support all types of video content. On the other hand, RemoteFX Media Streaming combined broad video format support with the H.264 codec to provide host-side rendering and redirection.

Benefits of Microsoft RemoteFX Media Streaming

1. Detection and redirection of all media content, including but not limited to Silverlight, Flash, QuickTime, and HTML5 videos. Users have a consistent experience regardless of video formats or video applications.
2. When compared to RDP in Windows 7, Microsoft RemoteFX Media Streaming consumes up to 90% less bandwidth. The actual difference in bandwidth depends on the size and frame rate of the original video.
3. Microsoft RemoteFX Media Streaming leverages network auto-detection and the client capabilities to dynamically adapt the encoding bitrate and frame rate to provide the optimum user experience.
4. The user experience is excellent even on WAN networks due to adaptive media streaming and Microsoft RemoteFX Media Streaming leveraging the User Datagram Protocol (UDP).

Configuration Requirements

RemoteFX in Windows Server 2012 and higher versions were designed to make things simpler with out-of-the-box features. When connecting to a virtual desktop that had RemoteFX virtual graphics processing unit (vGPU) installed, the host Hyper-V server must have a non-server core setup without any media codecs. Additional configuration is not required when enabling RemoteFX Media Streaming along with the rest of Remote Desktop Services.

Other requirements include:

• A DirectX 11.0-compatible GPU with a WDDM 1.2-compatible driver. If you are using Windows Server 2008 R2 SP1, the server must have at least one DirectX 9.0c and 10.0 capable graphics card.
• A CPU with enabled Second-Level Address Translation (SLAT) support
• Installed instances and VMs created with and running on Hyper-V
• A non-Domain Controller host machine
• RemoteFX vGPU support is enabled in the following operating systems:
• Windows 7 SP1
• Windows 8.1
• Windows 10 1703 or later
• Windows Server 2016 in a single-session deployment only

It is recommended to use graphics cards designed to run on professional workstations, although any GPU with OpenGL and OpenCL functionality and DirectX 11.0 is supported. The RemoteFX virtual graphics adapter is only supported by Enterprise editions of Windows.

To get started with Parallels RAS, download your free trial.