Navigate to the Hyper-V settings in Hyper-V Manager.To limit which GPUs the RemoteFX vGPU uses, follow these steps: To learn more, see Configure the RemoteFX vGPU 3D adapter.īy default, RemoteFX vGPU will use all available and supported GPUs. Add the RemoteFX 3D graphics adapter to the VM.To learn more, see RemoteFX 3D Video Adapter (vGPU) support. Create a VM running a guest OS supported by RemoteFX vGPU.
#Opengl windows 10 remote desktop install#
Install the graphics drivers recommended by your GPU vendor for Windows Server 2016.To configure RemoteFX vGPU on your Windows Server 2016 host: DirectX 11.0 is only available for guests running Windows 8 or later.OpenGL and OpenCL functionality is only available in guests running Windows 10 or Windows Server 2016.For more information, see RemoteFX 3D Video Adapter (vGPU) support. A CPU with Second Level Address Translation (SLAT) support.A DirectX 11.0-compatible GPU with a WDDM 1.2-compatible driver.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.
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. The vGPU feature for RemoteFX makes it possible for multiple virtual machines to share a physical GPU. Because of security concerns, RemoteFX vGPU is disabled by default on all versions of Windows starting with the JSecurity Update and removed starting with the ApSecurity Update.