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

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

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

NVIDIA GRID Test Drive

NVIDIA GRID Website

NVIDIA GRID News

NVIDIA GRID YouTube Channel

Questions? Ask on our Forums

NVIDIA GRID on LinkedIn

Follow NVIDIAGRID on Twitter

Citrix License FAQ regarding vGPU 

Vmware License FAQ regarding vGPU

 

Mac Client Printer Mapping Fix for Citrix XenDesktop/XenApp 7.6

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

NVIDIA GRID vGPU 346.68-348.27

NVIDIA GRID vGPU 346.68-348.27

NVIDIA have released a new GRID Virtual GPU Manager 346.68 for Citrix XenServer 6.5 and VMware vSphere 6.
NVIDIA have in this release also released Windows drivers for vGPU 348.27

Important:

The GRID Virtual GPU Manager 346.68 is not updated in this release, its only the Windows drivers for vGPU 348.27
If you have GRID Virtual GPU Manager 346.68 installed in either XenServer or VMware you only need to update your VMs.

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.

 

What is fixed in Windows driver for vGPU 348.27 VM using Citrix XenServer 6.5

346.68_-_xenserver_fix

What is fixed in Windows drivers for vGPU 348.27 VM using VMware vSphere 6

346.68_vSphere_fix

 

Source

Download NVIDIA GRID vGPU 346.68-348.27 for Citrix XenServer 6.5 here

Download NVIDIA GRID vGPU 346.68-348.27 for VMware vSphere 6 here

Microsoft Most valuable professional MVP award

Microsoft Most valuable professional MVP
Microsoft Most valuable professional

 

Hi all

I am very proud to be awarded Microsoft Most Valuable Professional (MVP) by Microsoft.

This is my first award from Microsoft and I am now part of a fine bunch of geeks. Expect many great things coming from me around Microsoft 🙂

Thank you all for your support and believing in the values I do, I will make sure to bring lots of knowledge into the MVP program.

/Thomas Poppelgaard

mvp

 

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

thomas poppelgaard CTP & Microsoft Most Valuable Professional MVP