NVIDIA GRID 5.0 released (384.73/385.41)

Written by Thomas Poppelgaard. Posted in CentOS, Citrix, dVGA, GRID, Horizon, Linux, Maxwell, Microsoft, NVENC, NVIDIA, Pascal, Quadro, RDS, RemoteFX, RHEL, Tesla, Ubuntu, vGPU, VMware, vSphere, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008R2, Windows Server 2012R2, Windows Server 2016

nvidiagrid

Hi All

Its time to update your NVIDIA TESLA M6, M10, M60 environment or start using the new TESLA P4, P6, P40, P100 with GRID 5.0.

NVIDIA have released new drivers for NVIDIA GRID 5.0 for September 2017.

This release includes the following software:

  • NVIDIA GRID Virtual GPU Manager version 384.73 for the Citrix XenServer, VMware vSphere, Huawei UVP
  • NVIDIA Windows driver version 385.41
  • NVIDIA Linux driver version 384.73

New in this Release:

  • Support for GPUs based on the NVIDIA® Pascal™ architecture
  • Compute mode support for GRID vGPU and pass-through GPU on GPUs based on the NVIDIA Pascal architecture
  • New GRID vGPU schedulers for GPUs based on the NVIDIA Pascal architecture
  • Support for NVML and nvidia-smi on 32-Bit Windows VMs
  • Application-level monitoring of GRID vGPU engine utilization
  • Encoder session monitoring
  • Support for NVENC on Linux GRID vGPUs
  • Removal of support for GRID K1 and GRID K2 GPUs
  • Software enforcement of licensing requirements
  • Miscellaneous bug fixes

Supported NVIDIA GPUs with GRID 5.0

  • Tesla M6
  • Tesla M10
  • Tesla M60
  • Tesla P4
  • Tesla P6
  • Tesla P40
  • Tesla P100

Supported Hypervisors with GRID 5.0

  • Citrix XenServer
    Citrix XenServer 7.0, 7.1, 7.2 (supported with Tesla M6, M10, M60, P4, P6, P40, P100)
    Citrix XenServer 6.5 (supported with Tesla M6, M10, M60)
  • VMware vSphere
    VMware vSphere 6.5 (supported with Tesla M6, M10, M60, P4, P6, P40, P100)
    Vmware vSphere 6.0 update3, update 2, update 1, RTM b2494585 (supported with Tesla M6, M10, M60, P4, P6, P40, P100)
    VMware vSphere 5.5 (supported with Tesla M6,M10,M60)
  • Microsoft Hyper-V 2016
    Microsoft Windows Server 2016 with Hyper-V role (supported with Tesla M6, M10, M60, P4, P6, P40, P100)
    note: Microsoft Windows Server with Hyper-V role supports GPU pass-through over Microsoft Virtual PCI bus. This bus is supported through paravirtualized drivers. 
  • Red Hat Enterprise Linux with KVM
    Red Hat Enterprise Linux with KVM 7.2, 7.3 (supported with Tesla M6, M10, M60, P4, P6, P40, P100)
    Red Hat Enterprise Linux with KVM 7.0, 7.1 (supported with Tesla M6,M10,M60)
  • Huawei UVP
    Huawei UVP RC520 (supported with Tesla M60)

Whats new in GRID 5.0 – 384.73-385.41

NVIDIA have released a new version of GRID 5.0 – 384.73-385.41 for NVIDIA GRID  (Tesla M6, M10, M60, P4, P6, P40, P100 platform)

Included in this release is

  • NVIDIA GRID Virtual GPU Manager versions 384.73 for Citrix XenServer 6.5 SP1
  • NVIDIA GRID Virtual GPU Manager versions 384.73 for Citrix XenServer 7
  • NVIDIA GRID Virtual GPU Manager versions 384.73 for Citrix XenServer 7.1
  • NVIDIA GRID Virtual GPU Manager version 384.73 for VMware vSphere 6.0 Hypervisor (ESXi)
  • NVIDIA GRID Virtual GPU Manager version 384.73 for VMware vSphere 6.5 Hypervisor (ESXi)
  • NVIDIA Windows drivers for vGPU version 385.41
  • NVIDIA Linux drivers for vGPU version 384.73.

Important:

The GRID vGPU Manager and Windows guest VM drivers must be installed together. Older VM drivers will not function correctly with this release of GRID vGPU Manager. Similarly, older GRID vGPU Managers will not function correctly with this release of Windows guest drivers

Windows Guest OS support in vGPU 385.41

GRID vGPU 385.41 supports following Windows release as a guest OS

  • Microsoft Windowss 7 (32/64bit)
  • Microsoft Windows 8 (32/64bit)
  • Microsoft Windows 8.1 (32/64bit)
  • Microsoft Windows 10 (32/64bit)
  • Microsoft Windows Server 2008R2
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2016

Linux Guest OS support in vGPU 384.73

GRID vGPU 384.73 supports following Linux distributions as a guest OS only on supported Tesla GPUs

  • Red Hat Enterprise Linux 7.0-7.3
  • CentOS 7.0-7.3
  • Ubuntu 16.04 LTS
  • Ubuntu 14.04 LTS

Important driver notes to GRID 5.0

  • In pass-through mode, GPUs based on the Pascal architecture support only 64-bit guest operating systems. No 32-bit guest operating systems are supported in pass-through mode for these GPUs.
  • ESXi 6.0 Update 3 is required for pass-through mode on GPUs based on the Pascal architecture.
  • Windows 7 and Windows Server 2008 R2 are not supported in pass-through mode on GPUs based on the Pascal architecture.
  • Only Tesla M6 is supported as the primary display device in a bare-metal deployment.
  • 32-bit Windows 10 is supported only on Tesla M6, Tesla M10, and Tesla M60 GPUs.
  • Red Hat Enterprise Linux with KVM 7.0 and 7.1 are supported only on Tesla M6, Tesla M10, and Tesla M60 GPUs.
  • Red Hat Enterprise Linux with KVM supports Windows guest operating systems only under specific Red Hat subscription programs. For details, see Certified guest operating systems for Red Hat Enterprise Linux with KVM.
  • Windows 7, Windows Server 2008 R2, 32-bit Windows 10, and 32-bit Windows 8.1 are supported only on Tesla M6, Tesla M10, and Tesla M60 GPUs.

Guide – Update existing vGPU GRID Manager (Hypervisor)


 

GRID vGPU Manager 384.73 for Citrix XenServer 6.5

If you have a NVIDIA GRID M6, M10, M60, P4, P6, P40, P100 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 6.5, use the rpm -U command to upgrade:

If you have NVIDIA GRID TESLA M6 / M10 / M60 / P4 / P6 / P40 / P100
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-6.5-384.73.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

If you have NVIDIA GRID K1 / K2 select following file:

“NVIDIA-vGPU-kepler-xenserver-6.5-384.73.x86_64.iso ”

If you have NVIDIA GRID M10/ M6/M60 select following file:

“NVIDIA-vGPU-xenserver-6.5-384.73.x86_64.iso ”

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 384.73 for Citrix XenServer 7

If you have a NVIDIA GRID M6, M10, M60, P4, P6, P40, P100 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 7, use the rpm -U command to upgrade:

If you have NVIDIA GRID TESLA M6 / M10 / M60 / P4 / P6 / P40 / P100
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-7.0-384.73.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

 

If you have NVIDIA GRID M6/M10/M60/P4/P6/P40/P100 select following file:

“NVIDIA-vGPU-xenserver-7.0-384.73.x86_64.iso ”

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 384.73, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 384.73 for Citrix XenServer 7.1, 7.2

If you have a NVIDIA GRID M6, M10, M60, P4, P6, P40, P100 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 7.1, use the rpm -U command to upgrade:

If you have NVIDIA GRID TESLA M6 / M10 / M60 / P4 / P6 / P40 / P100
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-7.1-384.73.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

 

If you have NVIDIA GRID M6/ M10/M60/P4/P6/P40/P100 select following file:

“NVIDIA-vGPU-xenserver-7.1-384.73.x86_64.iso ” if XenServer 7.1

“NVIDIA-vGPU-xenserver-7.2-384.73.x86_64.iso ” if XenServer 7.2

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 384.73, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 384.73 for VMware vSphere 6.0

To update the NVIDIA GPU VIB, you must uninstall the currently installed VIB and install the new VIB.

To uninstall the currently installed VIB:

  1. Stop all virtual machines using 3D acceleration.
  2. Place the ESXi host into Maintenance mode.
  3. Open a command prompt on the ESXi host.
  4. Stop the xorg service by running the command:/etc/init.d/xorg stop
  5. Remove the NVIDIA VMkernel driver by running the command:vmkload_mod -u nvidia
  6. Identify the NVIDIA VIB name by running this command:esxcli software vib list | grep NVIDIA
  7. Remove the VIB by running the command:esxcli software vib remove -n nameofNVIDIAVIBYou can now install a new NVIDIA GPU VIB
  8. Use the esxcli command to install the vGPU Manager package:
If you have NVIDIA GRID TESLA M6 / M10 / M60 / P4 / P6 / P40 / P100 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-VMware_ESXi_6.0_Host_Driver_384.73-1OEM.600.0.0.2494585.vib

After the ESXi host has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

[root@lesxi ~]# vmkload_mod -l | grep nvidia 
Preparing packages for installation...

Validate

run nvidia-smi

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 384.73, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 384.73 for VMware vSphere 6.5

To update the NVIDIA GPU VIB, you must uninstall the currently installed VIB and install the new VIB.

To uninstall the currently installed VIB:

  1. Stop all virtual machines using 3D acceleration.
  2. Place the ESXi host into Maintenance mode.
  3. Open a command prompt on the ESXi host.
  4. Stop the xorg service by running the command:/etc/init.d/xorg stop
  5. Remove the NVIDIA VMkernel driver by running the command:vmkload_mod -u nvidia
  6. Identify the NVIDIA VIB name by running this command:esxcli software vib list | grep NVIDIA
  7. Remove the VIB by running the command:esxcli software vib remove -n nameofNVIDIAVIBYou can now install a new NVIDIA GPU VIB
  8. Use the esxcli command to install the vGPU Manager package:
If you have NVIDIA GRID TESLA M6 / M10 / M60 / P4 / P6 / P40 / P100 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-VMware_ESXi_6.5_Host_Driver_384.73-1OEM.650.0.0.2494585.vib

After the ESXi host has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

[root@lesxi ~]# vmkload_mod -l | grep nvidia 
Preparing packages for installation...

Validate

run nvidia-smi

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 384.73 if it is then your host is ready for GPU awesomeness and make your VM rock.

Update existing vGPU Driver (Virtual Machine)

When the hypervisor vGPU GRID manager is updated next is updating the Virtual Machines vGPU driver.

  • 385.41_grid_win8_win7_32bit_international.exe
  • 385.41_grid_win8_win7_server2012R2_server2008R2_64bit_international.exe
  • 385.41_grid_win10_32bit_international.exe
  • 385.41_grid_win10_server2016_64bit_international.exe
  • NVIDIA-Linux-x86_64-384.73-grid.run (only available with M10/M6/M60)

The vGPU driver for Windows 7, 8, 8.1, 10 is available with NVIDIA GRID vGPU download. This is available for both M6/M10/M60/P4/P6/P40/P100

The vGPU driver for Linux is only available for vGPU with following Tesla GPU M10/M6/M60

Update your Golden Images and reprovisioning the new virtual machines with updated vGPU drivers, if you have stateless machines update vGPU drivers on each.

#HINT – Express upgrade of drivers is the recommended option according to the setup. If you use the “Custom” option, you will have the option to do a “clean” installation. The downside of the “clean installation” is that it will remove all profiles and custom settings. The pro of using the clean installation option is that it will reinstall the complete driver, meaning that there will be no old driver files left on the system. I most of the time recommends using a “Clean” installation to keep it vanilla 🙂

#HINT (Citrix XenDesktop 7.6-7.11 customers)

The NVIDIA GRID API provides direct access to the frame buffer of the GPU, providing the fastest possible frame rate for a smooth and interactive user experience. If you install NVIDIA drivers before you install a VDA with HDX 3D Pro, NVIDIA GRID is enabled by default.

To enable NVIDIA GRID on a VM, disable Microsoft Basic Display Adapter from the Device Manager. Run the following command and then restart the VDA: Montereyenable.exe -enable -noreset

If you install NVIDIA drivers after you install a VDA with HDX 3D Pro, NVIDIA GRID is disabled. Enable NVIDIA GRID by using the Montereyenable tool provided by NVIDIA.

To disable NVIDIA GRID, run the following command and then restart the VDA: Montereyenable.exe -disable -noreset

#HINT (Citrix XenDesktop 7.12/7.13/7.14/7.15 customers)

The NVIDIA GRID API provides direct access to the frame buffer of the GPU, providing the fastest possible frame rate for a smooth and interactive user experience. If you install NVIDIA drivers before you install a VDA with HDX 3D Pro, NVIDIA GRID is enabled by default.

To enable NVIDIA GRID on a VM, disable Microsoft Basic Display Adapter from the Device Manager. Run the following command and then restart the VDA: NVFBCEnable.exe -enable -noreset

If you install NVIDIA drivers after you install a VDA with HDX 3D Pro, NVIDIA GRID is disabled. Enable NVIDIA GRID by using the NVFBCEnable tool provided by NVIDIA.

To disable NVIDIA GRID, run the following command and then restart the VDA: NVFBCEnable.exe -disable -noreset

 

docs.nvidia.com

NVIDIA have done a great job creating a documentation portal for all their products including NVIDIA GRID.

the url is https://docs.nvidia.com

Source

NVIDIA Virtual GPU Software Documentation

https://docs.nvidia.com/grid/index.html

NVIDIA Virtual GPU Software Supported Products

NVIDIA Virtual GPU Software Quick Start Guide

Tesla M6/M10/M60/P4/P6/P40/P100 – sources

vGPU Grid Manager + Drivers are only available to customers and NVIDIA NPN partners for M6/M10/M60/P4/P6/P40/P100

Download if you are a NPN partner

Download if you are a GRID M6, M10, M60, P4, P6, P40, P100 customer

 

NVIDIA GRID 4.2 released (367.92/369.95)

Written by Thomas Poppelgaard. Posted in CentOS, Citrix, Datacenter and Cloud, Desktop Virtualization, End User Computing, GRID, HDX, HDX 3D, HDX 3D Pro, Horizon, Linux, Microsoft, NVENC, NVIDIA, Quadro, RHEL, Tesla, Ubuntu, vDGA, vGPU, VMware, vSphere, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008R2, Windows Server 2012R2, Windows Server 2016, XenApp, XenDesktop, XenServer

nvidiagrid

Hi All

Its time to update your NVIDIA GRID K1, K2, M10, M6, M60 environment.

NVIDIA have released new drivers for NVIDIA GRID 4.2 for March 2017.

New in this Release:

  • NVIDIA GRID 4.2 has multiple fixes that improve memory management and NVFBC optimizations that ensure that surface allocations in the Frame Buffer are managed more efficiently to increase stability. The latest release includes frame buffer residency optimizations. Now, during high-memory pressure situations where there is a lack of or high competition for frame buffer, users remain resident-in.
  • Miscellaneous bug fixes
  • Support for Citrix XenServer 7.1
  • Support for the following Linux guest OS versions:
    • Red Hat Enterprise Linux 7.3
    • CentOS 7.3
    • Ubuntu 16.04 LTS

Important notes – Note: XenServer 7.1 is the last XenServer release supported on GRID K1 and K2. Citrix XenServer 6.2 is no longer supported.

Whats new in vGPU 367.92-369.95

NVIDIA have released a new version of vGPU 367.92-369.95 for NVIDIA GRID  (K1, K2, Tesla M6, M10 and M60 platform)

Included in this release is

  • NVIDIA GRID Virtual GPU Manager versions 367.92 for Citrix XenServer 6.5 SP1
  • NVIDIA GRID Virtual GPU Manager versions 367.92 for Citrix XenServer 7
  • NVIDIA GRID Virtual GPU Manager versions 367.92 for Citrix XenServer 7.1
  • NVIDIA GRID Virtual GPU Manager version 367.92 for VMware vSphere 6.0 Hypervisor (ESXi)
  • NVIDIA GRID Virtual GPU Manager version 367.92 for VMware vSphere 6.5 Hypervisor (ESXi)
  • NVIDIA Windows drivers for vGPU version 369.95
  • NVIDIA Linux drivers for vGPU version 367.92.

Important:

The GRID vGPU Manager and Windows guest VM drivers must be installed together. Older VM drivers will not function correctly with this release of GRID vGPU Manager. Similarly, older GRID vGPU Managers will not function correctly with this release of Windows guest drivers

Windows Guest OS support in vGPU 369.95

GRID vGPU 369.95 supports following Windows release as a guest OS

  • Microsoft Windowss 7 (32/64bit)
  • Microsoft Windows 8 (32/64bit)
  • Microsoft Windows 8.1 (32/64bit)
  • Microsoft Windows 10 (32/64bit)
  • Microsoft Windows Server 2008R2
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2016

Linux Guest OS support in vGPU 367.92

GRID vGPU 367.92 supports following Linux distributions as a guest OS only on supported Tesla GPUs
Import: GRID K1/K2 do not support vGPU on Linux guest os.

  • Red Hat Enterprise Linux 7.0-7.3
  • CentOS 7.0-7.3
  • Ubuntu 16.04 LTS
  • Ubuntu 14.04 LTS

Guide – Update existing vGPU GRID Manager (Hypervisor)

 

GRID vGPU Manager 367.92 for Citrix XenServer 6.5

If you have a NVIDIA GRID K1, K2, M6, M60 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 6.5, use the rpm -U command to upgrade:

If you have NVIDIA GRID K1 / K2
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-kepler-xenserver-6.5-367.92.x86_64.rpm 
Preparing packages for installation...
If you have NVIDIA GRID TESLA M10 / M6 / M60
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-6.5-367.92.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

If you have NVIDIA GRID K1 / K2 select following file:

“NVIDIA-vGPU-kepler-xenserver-6.5-367.92.x86_64.iso ”

If you have NVIDIA GRID M10/ M6/M60 select following file:

“NVIDIA-vGPU-xenserver-6.5-352.83.x86_64.iso ”

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 367.92 for Citrix XenServer 7

If you have a NVIDIA GRID K1, K2, M6, M60 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 7, use the rpm -U command to upgrade:

If you have NVIDIA GRID K1 / K2
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-kepler-xenserver-7.0-367.92.x86_64.rpm 
Preparing packages for installation...
If you have NVIDIA GRID TESLA M10 / M6 / M60
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-7.0-367.92.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

If you have NVIDIA GRID K1 / K2 select following file:

“NVIDIA-vGPU-kepler-xenserver-7.0-367.92.x86_64.iso ”

If you have NVIDIA GRID M10/ M6/M60 select following file:

“NVIDIA-vGPU-xenserver-7.0-352.83.x86_64.iso ”

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 367.92 for Citrix XenServer 7.1

If you have a NVIDIA GRID K1, K2, M6, M60 vGPU GRID manager installed in Citrix XenServer. Upgrade with one of below methodology:

Methodology 1 – the manual way “No GUI”

Upgrading an existing installation of the NVIDIA driver on Citrix XenServer 7.1, use the rpm -U command to upgrade:

If you have NVIDIA GRID K1 / K2
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-kepler-xenserver-7.1-367.92.x86_64.rpm 
Preparing packages for installation...
If you have NVIDIA GRID TESLA M10 / M6 / M60
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-7.1-367.92.x86_64.rpm 
Preparing packages for installation...

The recommendation from NVIDIA is to shutdown all VMs using a GPU. The machine does continue to work during the update, but since you need to reboot the XenServer itself, it’s better to gracefully shutdown the VMs. So after your VMs have been shutdown and you upgraded the NVIDIA driver, you can reboot your host.

[root@localhost ~]# xe host-disable
[root@localhost ~]# xe host-reboot

Methodology 2 – the “GUI” way

Select Install Update… from the Tools menu
 Click Next after going through the instructions on the Before You Start section
 Click Add on the Select Update section and open NVIDIA’s XenServer Supplemental Pack ISO

If you have NVIDIA GRID K1 / K2 select following file:

“NVIDIA-vGPU-kepler-xenserver-7.1-367.92.x86_64.iso ”

If you have NVIDIA GRID M10/ M6/M60 select following file:

“NVIDIA-vGPU-xenserver-7.1-352.83.x86_64.iso ”

Click Next on the Select Update section
 In the Select Servers section select all the XenServer hosts on which the Supplemental Pack should be installed on and click Next
 Click Next on the Upload section once the Supplemental Pack has been uploaded to all the XenServer hosts
Getting Started
 Click Next on the Prechecks section
 Click Install Update on the Update Mode section
 Click Finish on the Install Update section

After the XenServer platform has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

Validate from putty or XenCenter CLI

run lsmod | grep nvidia

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 367.92 for VMware vSphere 6.0

To update the NVIDIA GPU VIB, you must uninstall the currently installed VIB and install the new VIB.

To uninstall the currently installed VIB:

  1. Stop all virtual machines using 3D acceleration.
  2. Place the ESXi host into Maintenance mode.
  3. Open a command prompt on the ESXi host.
  4. Stop the xorg service by running the command:/etc/init.d/xorg stop
  5. Remove the NVIDIA VMkernel driver by running the command:vmkload_mod -u nvidia
  6. Identify the NVIDIA VIB name by running this command:esxcli software vib list | grep NVIDIA
  7. Remove the VIB by running the command:esxcli software vib remove -n nameofNVIDIAVIBYou can now install a new NVIDIA GPU VIB
  8. Use the esxcli command to install the vGPU Manager package:
If you have NVIDIA GRID K1 / K2 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-kepler-VMware_ESXi_6.0_Host_Driver_367.92-1OEM.600.0.0.2494585.vib
If you have NVIDIA GRID TESLA M10 / M6 / M60 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-VMware_ESXi_6.0_Host_Driver_367.92-1OEM.600.0.0.2494585.vib

After the ESXi host has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

[root@lesxi ~]# vmkload_mod -l | grep nvidia 
Preparing packages for installation...

Validate

run nvidia-smi

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 367.92 for VMware vSphere 6.5

To update the NVIDIA GPU VIB, you must uninstall the currently installed VIB and install the new VIB.

To uninstall the currently installed VIB:

  1. Stop all virtual machines using 3D acceleration.
  2. Place the ESXi host into Maintenance mode.
  3. Open a command prompt on the ESXi host.
  4. Stop the xorg service by running the command:/etc/init.d/xorg stop
  5. Remove the NVIDIA VMkernel driver by running the command:vmkload_mod -u nvidia
  6. Identify the NVIDIA VIB name by running this command:esxcli software vib list | grep NVIDIA
  7. Remove the VIB by running the command:esxcli software vib remove -n nameofNVIDIAVIBYou can now install a new NVIDIA GPU VIB
  8. Use the esxcli command to install the vGPU Manager package:
If you have NVIDIA GRID K1 / K2 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-kepler-VMware_ESXi_6.5_Host_Driver_367.92-1OEM.650.0.0.2494585.vib
If you have NVIDIA GRID TESLA M10 / M6 / M60 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-VMware_ESXi_6.5_Host_Driver_367.92-1OEM.650.0.0.2494585.vib

After the ESXi host has rebooted, verify that the GRID package installed and loaded correctly by checking for the NVIDIA kernel driver in the list of kernel loaded modules.

[root@lesxi ~]# vmkload_mod -l | grep nvidia 
Preparing packages for installation...

Validate

run nvidia-smi

Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by running the nvidia-smi command, which should produce a listing of the GPUs in your platform:

Check driver version is 367.92, if it is then your host is ready for GPU awesomeness and make your VM rock.

Update existing vGPU Driver (Virtual Machine)

When the hypervisor vGPU GRID manager is updated next is updating the Virtual Machines vGPU driver.

  • 369.95_grid_win8_win7_32bit_international.exe
  • 369.95_grid_win8_win7_server2012R2_server2008R2_64bit_international.exe
  • 369.95_grid_win10_32bit_international.exe
  • 369.95_grid_win10_server2016_64bit_international.exe
  • NVIDIA-Linux-x86_64-367.92-grid.run (only available with M10/M6/M60)

The vGPU driver for Windows 7, 8, 8.1, 10 is available with NVIDIA GRID vGPU download. This is available for both K1/K2/M10/M6/M60

The vGPU driver for Linux is only available for vGPU with following Tesla GPU M10/M6/M60

Update your Golden Images and reprovisioning the new virtual machines with updated vGPU drivers, if you have stateless machines update vGPU drivers on each.

#HINT – Express upgrade of drivers is the recommended option according to the setup. If you use the “Custom” option, you will have the option to do a “clean” installation. The downside of the “clean installation” is that it will remove all profiles and custom settings. The pro of using the clean installation option is that it will reinstall the complete driver, meaning that there will be no old driver files left on the system. I most of the time recommends using a “Clean” installation to keep it vanilla 🙂

#HINT (Citrix XenDesktop 7.6-7.11 customers)

The NVIDIA GRID API provides direct access to the frame buffer of the GPU, providing the fastest possible frame rate for a smooth and interactive user experience. If you install NVIDIA drivers before you install a VDA with HDX 3D Pro, NVIDIA GRID is enabled by default.

To enable NVIDIA GRID on a VM, disable Microsoft Basic Display Adapter from the Device Manager. Run the following command and then restart the VDA: Montereyenable.exe -enable -noreset

If you install NVIDIA drivers after you install a VDA with HDX 3D Pro, NVIDIA GRID is disabled. Enable NVIDIA GRID by using the Montereyenable tool provided by NVIDIA.

To disable NVIDIA GRID, run the following command and then restart the VDA: Montereyenable.exe -disable -noreset

#HINT (Citrix XenDesktop 7.12/7.13 customers)

The NVIDIA GRID API provides direct access to the frame buffer of the GPU, providing the fastest possible frame rate for a smooth and interactive user experience. If you install NVIDIA drivers before you install a VDA with HDX 3D Pro, NVIDIA GRID is enabled by default.

To enable NVIDIA GRID on a VM, disable Microsoft Basic Display Adapter from the Device Manager. Run the following command and then restart the VDA: NVFBCEnable.exe -enable -noreset

If you install NVIDIA drivers after you install a VDA with HDX 3D Pro, NVIDIA GRID is disabled. Enable NVIDIA GRID by using the NVFBCEnable tool provided by NVIDIA.

To disable NVIDIA GRID, run the following command and then restart the VDA: NVFBCEnable.exe -disable -noreset

 

Source

GRID K1/K2 – sources

Download vGPU 352.83-354.80 for XenServer 6.5 for GRID K1 / K2 here

Download vGPU 352.83-354.80 for XenServer 7.0 for GRID K1 / K2 here

Download vGPU 367.92-369.95 for XenServer 7.1 for GRID K1 / K2 here

Download vGPU 367.92-369.95 for vSphere 6 for GRID K1 / K2 here

Download vGPU 367.92-369.95 for vSphere 6.5 for GRID K1 / K2 here

Tesla M10/M6/M60 – sources

vGPU Grid Manager + Drivers are only available to customers and NVIDIA NPN partners for M10/M6/M60.

Download if you are a NPN partner

Download if you are a GRID M10, M6, M60 customer

vGPU 367.92-369.95 for XenServer 6.5 for Tesla M10 / M6 / M60

vGPU 367.92-369.95 for XenServer 7 for Tesla M10 / M6 / M60

vGPU 367.92-369.95 for XenServer 7.1 for Tesla M10 / M6 / M60

vGPU 367.92-396.95 for vSphere 6 for Tesla M10 / M6 / M60

vGPU 367.92-396.95 for vSphere 6.5 for Tesla M10 / M6 / M60

Other Sources

NVIDIA blog – https://blogs.nvidia.com/blog/2017/03/10/nvidia-grid-march-2017/ 

Mozilla Firefox 40.x Blocks GPU Acceleration for WebGL, Direct2D, DirectWrite with Citrix XenApp on Windows 2008R2/2012/2012R2

Written by Thomas Poppelgaard. Posted in AMD, Citrix, Desktop Virtualization, End User Computing, GRID, GRID 2.0, HDX 3D, Intel, Microsoft, NVIDIA, RES Software, vDGA, VMware, vSphere, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008R2, Windows Server 2012, Windows Server 2012R2, Workspace Manager, XenApp, XenDesktop, XenServer

Mozilla Firefox 40.x Blocks GPU Acceleration for WebGL, Direct2D, DirectWrite with Citrix XenApp on Windows 2008R2/2012/2012R2

One of the great things about adding a GPU in a Citrix XenApp environment is that you can allow rich graphics and offload CPU and run your DirectX, OpenGL  applications on a XenApp server. In latest version of Mozilla Firefox WebGL, Direct2D, DirectWrite this have been disabled, so you can’t open webpages that uses these graphics in a Citrix XenApp session.

Symptoms or Error

If you open Mozilla Firefox 40.x and try to open a webGL website like http://madebyevan.com/webgl-water
this will not load anymore cause WebGL is default now disabled in Mozilla Firefox. Mozilla Firefox 40.x  blocks GPU acceleration for WebGL, Direct2D, DirectWrite in remote sessions on Windows Server operating systems.

2015-09-15_1553

To determine what content Firefox is blocking, run Firefox in your XenApp remote session and enter the address about:support into the browser address bar. In the section labelled “Graphics” you will see the following content disabled (as of Firefox version 40.0.3):

Direct2D Enabled             Blocked for your graphics card because of unresolved driver issues.
DirectWrite Enabled         false (6.3.9600.17999)
WebGL Renderer             Blocked for your graphics card because of unresolved driver issues.

2015-09-15_1555

Solution

The text “Blocked for your graphics card” is misleading as, in this case, it is not the specific graphics card but general Windows Server operating system remote sessions that are blocked. Mozilla’s published advice on how to override the graphics driver blocks also applies to XenApp sessions on workstation operating system (see bottom of this Mozilla Wiki – Blocklisting/Blocked Graphics Drivers).

Enable WebGL in Mozilla Firefox

In Mozilla Firefox entering the address about:config into the address bar and setting webgl.force-enabled=true will enable WebGL for XenApp on operating system (Server 2008R2/2012/2012R2)

webgl

 

You can double click on it and then it will become enabled. (with the value=true) and this is user set.
These settings can be change with a policy or with profile management such as RES Workspace Manager or others.

webgl-working

Now you can open the WebGL demo and the graphics will work

2015-09-15_1557

Enable DirectDraw2D

In Mozilla Firefox entering the address about:config into the address bar and setting gfx.direct2d.force-enabled=true will enable WebGL for XenApp on operating system (Server 2008R2/2012/2012R2)

direct2d

You can double click on it and then it will become enabled. (with the value=true) and this is user set.
These settings can be change with a policy or with profile management such as RES Workspace Manager or others.

direct2d-working

Enable DirectDraw2D

In Mozilla Firefox entering the address about:config into the address bar and setting gfx.font_rendering.directwrite.enabled=true will enable DirectWrite for XenApp on operating system (Server 2008R2/2012/2012R2)

directwrite

You can double click on it and then it will become enabled. (with the value=true) and this is user set.
These settings can be change with a policy or with profile management such as RES Workspace Manager or others.

directwrite-working

Users should be aware and note the caveats and warnings that Mozilla advises if taking this route to above settings for DirectWrite, Direct2D, WebGL

This issue only affects server operating system (example – Win 2012 R2 and Win 2008 R2) and XenApp.

How to force-enable blocked graphics features

If you would like to forcibly enable a graphics feature that is blocked on your system, follow these instructions. Warning: do this at your own risk. There usually are good reasons why features are blocked.

To force-enable WebGL, go to about:config and set webgl.force-enabled=true.

To force-enable WebGL anti-aliasing, go to about:config and set webgl.msaa-force=true.

To force-enable Layers Acceleration, go to about:config and set layers.acceleration.force-enabled=true.

On Windows Vista and Windows 7, to force-enable Direct2D Content Acceleration, go to about:config and set gfx.direct2d.force-enabled=true.

On Android, to force-enable StageFright software decoding, go to about:config and set stagefright.force-enabled=true.

On Windows, you can also spoof your graphics system information to help debug driver blacklisting issues (see bug 604771):

  1. Create spoofed-firefox.bat in the installation folder (e.g. C:\Program Files (x86)\Mozilla Firefox)
  2. Set the new values of spoofed variables ending with a command to launch Firefox:
    SET MOZ_GFX_SPOOF_WINDOWS_VERSION=60001
    SET MOZ_GFX_SPOOF_VENDOR_ID=0x8086
    SET MOZ_GFX_SPOOF_DEVICE_ID=0x0046
    SET MOZ_GFX_SPOOF_DRIVER_VERSION=8.15.10.2302
    “C:\Program Files (x86)\Mozilla Firefox\firefox.exe” -p -no-remote
  3. Double-click spoofed-firefox.bat and create a profile if required
  4. Click the Firefox button, then select Help, finally Troubleshooting Information and check the Graphics section.

If force-enabling a feature doesn’t work, that probably means that your hardware doesn’t support it. For example, layers acceleration currently requires support for 4Kx4K textures, which rules out some graphics cards, like the Intel G31/G33.

Source

Firefox article

http://support.citrix.com/article/CTX202065 (credits to Rachel Berry for writing this CTX article)

Another great blogpost to read about this subject is my friend / CTP fellow Barry Schiffer http://www.barryschiffer.com/citrix-hdx-3d-pro-and-nvidia-grid-browser-experience/ He was the guy who wrote a great blogpost with some very interesting results on performance tuning Mozilla Firefox in a XenApp/XenDesktop session.

 

NVIDIA GRID 2.0

Written by Thomas Poppelgaard. Posted in 8.1, Citrix, DirectX 12, FrameHawk, GRID, GRID 2.0, HDX 3D, HDX 3D Pro, Maxwell, Microsoft, NVIDIA, Server 2012R2, vDGA, vGPU, View, VMware, vSphere, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2008R2, Windows Server 2012, Windows Server 2012R2, XenApp, XenDesktop, XenServer

Nvidia grid 2.0 2x

NVIDIA GRID 2.0

NVIDIA have released the next generation of GRID 2.0. GRID 2.0 is based on the Maxwell architecture and the GRID 1.0 (K1/K2) was based on the Kepler architecture. I have been working with the GRID 1.0 technology since 2012 and it have matured alot in its 2 years of history. When the K1/K2 was released they was first working with GPU pass-through and then vGPU got introduced and you could virtualize the GPUs and increase density, which people wanted. Citrix was with their hypervisor the first company that supported NVIDIA GRID 1.0 and they was also the first company integrating vGPU into their Citrix Studio, so companies could easier provisioning machines with either MCS technology or PVS technology. VMware supported GRID 1.0 vGPU technology in 2015 in their hypervisor VMware vSphere 6.0 and fully integrated with their EUC stack VMware View, so companies can fully provisioning machines. The great thing about GRID 2.0 is that there is no need for a conversation when to choose either a K1 or a K2, if you required GPU compute or GPU framebuffer, M60 are being added to the tope end of the range  and bringing 2x the performance, and if you have bladeserver’s, you can add the powerfull vGPU technology into the bladeserver’s with the M6.

Please notice that M6 will 0nly be supporting newer architecture of vendors not old platforms.

Maxwell architecture

Maxwell architecture is the new architecture of GPUs and a powerful GPU you might know is the Titan X

New GPUs GRID 2.0 and specifications

In GRID 2.0 NVIDIA now have a GPU for blade servers a MXM single socket, High-end GPU called M6

In GRID 2.0 NVIDIA replaces K1/K2 with the new PCIe 3.0 Dual Socket, Dual High-end GPU called M60
The M60 delivers 4096 CUDA or compute and 16GB GDDR5 memory/framebuffer

The M60 has 6x the h.264 encoders of the K2, and also Maxwell supports 4:4:4 chroma sub sampling, which is great news for encoders.

maxwell_grid

Certified GRID 2.0 servers

Click the link to see which servers are certified for M60 and M6
http://www.nvidia.com/object/grid-certified-servers.html

M6 have following servers supported:

m6 certifiedM60 have following servers supported:

m60 certificed

vGPU software editions and license

nvidiagrid20licensemodel

NVIDIA GRID 2.0 software is available in three editions that deliver accelerated virtual desktops to support the needs of your users. These editions include Virtual PC, Virtual Workstation, and Virtual Workstation Extended. GRID perpetual licenses are sold by Concurrent User (CCU).

NVIDIA GRID 2.0 (CCU) stands for ConCurrent User. So basically, per running VM as regardless of whether the user is connected to the VM or not, the VM is connected to the GPU and so consumes a license

NVIDIA GRID 2.0 software is much more than a “driver”. While the software package does include a guest driver for Windows and Linux, it also includes the NVIDIA GRID vGPU manager for VMware vSphere and Citrix XenServer, as well as the license server and M6/M60 mode switching utility.

NVIDIA Tesla M6 and M60 profiles are specific to the M6 and M60. There will be similar profiles as to what NVIDIA had on K1 and K2 (512 MB through 4 GB), all with twice the number of users on M6/ M60 compared to K1/K2. Plus, there is an additional 8 GB profile on M6/M60 which also adds support for CUDA, which wasn’t available on K1/K2.

NVIDIA GRID 2.0 is Maxwell only. If you are an existing customer K1/K2 are unchanged and will remain as a parallel option.

nvidiagrid20licensemodel 2

 

nvidiagrid20licensemodel 3

The NVIDIA GRID 2.0 solution

nvidiagrid20

Summary

GA of NVIDIA GRID 2.0 (M60 and M6) will be 15 September 2015.

To get NVIDIA GRID 2.0 if you are a Citrix customer you need:
Server hardware that supports NVIDIA GRID 2.0 +NVIDIA GPU M60 or M6 + NVIDIA vGPU Software license + Citrix XenDesktop or XenApp License (XenServer is included in XD/XA licenses)

To get NVIDIA GRID 2.0 if you are a VMware customer you need:
Server hardware that supports NVIDIA GRID 2.0 +NVIDIA GPU M60 or M6  + NVIDIA vGPU Software license + VMware Horizon license (Horizon includes vSphere for Desktop)

If you are a Citrix customer that wants to run on VMware vSphere you need:

Server hardware that supports NVIDIA GRID 2.0 + NVIDIA GPU M60 or M6 + NVIDIA vGPU Software license + Citrix XenDesktop or XenApp License + VMware vSphere Enterprise Plus license or vSphere for Desktop license

Source

Mac Client Printer Mapping Fix for Citrix XenDesktop/XenApp 7.6

Written by Thomas Poppelgaard. Posted in Best Practise, Citrix, Windows 7, Windows 8, Windows 8.1, Windows Server 2008R2, Windows Server 2012, Windows Server 2012R2, XenApp, XenDesktop

Mac Client Printer Mapping Fix for Citrix XenDesktop/XenApp 7.6

Hi all

If you have users that have a Apple Mac OSX device such as (iMac, Macbook, Macbook Pro) then this article might be interesting for you. I am helping many clients around the world and I often see more companies adapting Apple OSX devices. Specially SMB and Enterprises are adapting Apple Macbook products these days cause they are powerfull computers and have some of the best design and reliability. Many companies have no other option to adapt Apple OSX devices, so they attract the right talented employee, which are requesting this device if they want to work at the company, and you think this is funny then welcome to reality, Apple is back and more powerful than before. The good news is that Citrix can help with this and bring any app to work on these devices and secure the workspace with the Citrix Receiver where the user connect to a central and secure solution. The challenge comes when the user have local printers to their mac device and now tell IT they want to print from their Citrix session.

In latest release of Citrix XenDesktop, XenApp 7.6 if your users on Mac OSX devices, wants to use local printers and then connect to their remote Citrix VDI (Windows 8/8.1) or XenApp (Server 2012/2012R2) and then print, this is not going to work. Before this article got released users would only be able to get local printing working  to a Windows 7 VDI or a XenApp server running Server 2008R2.

If you have users running pure Windows Computers, then you are not going to run into this issue with getting local printers to work with a Citrix environment running Windows 7/8/8.1, Server 2008R2/2012/2012R2.

In Citrix XenDesktop 7.6, default policies are set to map all client printers, so you dont have configure this policy.

Summary if you have a Mac device and Citrix Receiver and local printers installed on your Mac, now you want to accomplish connecting to your VDI (Windows 8/8.1) XenApp (Windows Server 2012/2012R2) then you are going to fail, do below and you succeed.

Solution:

(how to get local printers to work on a Apple OSX computer with Citrix Receiver to a XenDesktop/XenApp 7.6 environment running Windows 8/8.1 or Server 2012/2012R2)
  1. On the desktop you want to configure, open Control Panel > View Devices and Printers.
  2. Select any Printer, for example Microsoft XPS Document Writer.
  3. Click Print server properties, as displayed in the following screen shot:
    User-added image
  1. Select Drivers tab.
  2. Click Add > Next.
  3. Choose Processor Architecture, click Next.
  4. Select Windows Update.
  5. Select Manufacturer ‘HP’ and Printers ‘HP Color LaserJet 2800 Series PS’ (if there are two versions of this driver displayed, choose the Microsoft version)
  6. Click NextFinish.
  7. Now connect or reconnect to your Citrix XenApp session running (Server 2012/2012R2) or Citrix XenDesktop VDI session running (Windows 8/8.1) then your local printers will be mapped in Citrix session and you can print.

Have fun.

/Poppelgaard

Citrix technology professional – CTP, and Microsoft Most Valuable Professional MVP, Thomas Poppelgaard provides professional services. Write to me on my email thomas@poppelgaard.com or call on my cell +45 53540356

Source

CTX139020

Recent Comments

MarilynToush

|

This message is posted here using XRumer + XEvil 3.0
XEvil 3.0 is a revolutionary application that can bypass almost any anti-botnet protection.
Captcha Recognition Google, Facebook, Yandex, VKontakte, Captcha Com and over 8.4 million other types!
You read this – it means it works! 😉
Details on the official website of XEvil.Net, there is a free demo version.

Server 2016 Support

|

Wonderful website. A lot of useful info here. I am sending it to a few friends ans also sharing in delicious. And obviously, thanks for your sweat!

Server 2016 Support

Thomas Poppelgaard

|

Thanks Jose, I have corrected the map plus updated the map so 29 datacenters are now alive.

Jose Brenes

|

Your map of Australia is wrong. You have put the state of Victoria inside the West Australian state.

Tobias K

|

Note that on XenServer 7.1, installing VDA 7.13 also works to enable vGPUs running XenDesktop 7.11 even using the newer “NvFBCEnable.exe -enable -noreset” command. Tested with an M60 using various profiles.