You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-desktop/virtual-desktop-fall-2019/configure-vm-gpu-2019.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ You must also configure an application group, or use the default desktop applica
35
35
36
36
To take advantage of the GPU capabilities of Azure N-series VMs in Azure Virtual Desktop, you must install the appropriate graphics drivers. Follow the instructions at [Supported operating systems and drivers](../../virtual-machines/sizes-gpu.md#supported-operating-systems-and-drivers) to install drivers from the appropriate graphics vendor, either manually or using an Azure VM extension.
37
37
38
-
Only drivers distributed by Azure are supported for Azure Virtual Desktop. Additionaly, for Azure VMs with NVIDIA GPUs, only [NVIDIA GRID drivers](../../virtual-machines/windows/n-series-driver-setup.md#nvidia-grid-drivers) are supported for Azure Virtual Desktop.
38
+
Only drivers distributed by Azure are supported for Azure Virtual Desktop. Additionaly, for Azure VMs with NVIDIA GPUs, only [NVIDIA GRID drivers](../../virtual-machines/windows/n-series-driver-setup.md#nvidia-gridvgpu-drivers) are supported for Azure Virtual Desktop.
39
39
40
40
After driver installation, a VM restart is required. Use the verification steps in the above instructions to confirm that graphics drivers were successfully installed.
41
41
@@ -87,4 +87,4 @@ To verify that Remote Desktop is using GPU-accelerated encoding:
87
87
These instructions should have you up and running with GPU acceleration on one session host (one VM). Some additional considerations for enabling GPU acceleration across a larger host pool:
88
88
89
89
* Consider using a [VM extension](../../virtual-machines/extensions/overview.md) to simplify driver installation and updates across a number of VMs. Use the [NVIDIA GPU Driver Extension](../../virtual-machines/extensions/hpccompute-gpu-windows.md) for VMs with NVIDIA GPUs, and use the AMD GPU Driver Extension for VMs with AMD GPUs.
90
-
* Consider using Active Directory Group Policy to simplify group policy configuration across a number of VMs. For information about deploying Group Policy in the Active Directory domain, see [Working with Group Policy Objects](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)).
90
+
* Consider using Active Directory Group Policy to simplify group policy configuration across a number of VMs. For information about deploying Group Policy in the Active Directory domain, see [Working with Group Policy Objects](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)).
Copy file name to clipboardExpand all lines: includes/virtual-machines-n-series-windows-support.md
+3-8Lines changed: 3 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ NVIDIA Tesla (CUDA) drivers for all NC* and ND*-series VMs (optional for NV*-ser
24
24
> As an alternative to manual CUDA driver installation on a Windows Server VM, you can deploy an Azure [Data Science Virtual Machine](../articles/machine-learning/data-science-virtual-machine/overview.md) image. The DSVM editions for Windows Server 2016 pre-install NVIDIA CUDA drivers, the CUDA Deep Neural Network Library, and other tools.
25
25
26
26
27
-
### NVIDIA GRID drivers
27
+
### NVIDIA GRID/vGPU drivers
28
28
> [!Note]
29
29
>For Azure NVads A10 v5 VMs we recommend customers to always be on the latest driver version. The latest NVIDIA major driver branch(n) is only backward compatbile with the previous major branch(n-1). For eg, vGPU 17.x is backward compatible with vGPU 16.x only. Any VMs still runnig n-2 or lower may see driver failures when the latest drive branch is rolled out to Azure hosts.
30
30
>>
@@ -39,15 +39,12 @@ The GRID drivers redistributed by Azure don't work on non-NV series VMs like NCv
39
39
40
40
The Nvidia extension always installs the latest driver.
41
41
42
-
For Windows 11 22H2/21H2, Windows 10 22H2, Server 2019/2022:
42
+
For Windows 11 up to and including 23H2, Windows 10 up to and including 22H2, Server 2019/2022:
-[GRID 14.1 (512.78)](https://download.microsoft.com/download/7/3/6/7361d1b9-08c8-4571-87aa-18cf671e71a0/512.78_grid_win10_win11_server2016_server2019_server2022_64bit_azure_swl.exe) (.exe) is the last supported driver from NVIDIA. The newer 15.x and above don't support Windows Server 2016.
53
50
@@ -68,6 +65,4 @@ For Windows Server 2012 R2:
68
65
>To enable the remote call again, change the setting to 1 or simply delete the regkey.
69
66
70
67
71
-
72
-
73
68
For links to all previous Nvidia GRID driver versions, visit [GitHub](https://github.com/Azure/azhpc-extensions/blob/master/NvidiaGPU/resources.json).
0 commit comments