Autodesk AutoCAD 2016 / 2017 critical hotfix for Citrix customers using NVIDIA or INTEL GPUs

Written by Thomas Poppelgaard. Posted in AutoCAD, Autodesk, Citrix, GRID, HDX 3D, HDX 3D Pro, Hyper-V, Intel, Microsoft, NVIDIA, VMware, vSphere, Windows 10, Windows 7, Windows 8.1, Windows Server 2008R2, Windows Server 2012, Windows Server 2012R2, Windows Server 2016, XenApp, XenDesktop, XenServer

Earlier this year I have seen several customers having issues with AutoCAD in Citrix not defaulting to the primary display adapter, so the GPU wouldn be fully functioning and Autodesk AutoCAD 2016/2017 would turn off hardware acceleration. This issue have been seen on NVIDIA Gpus such as GRID, NVIDIA also have a official KB on this http://nvidia.custhelp.com/app/answers/detail/a_id/4092/ and issue is also seen with INTEL gpu such as Iris Pro Graphics more specific on solutions with HPE Moonshot 710p and 710x.

Issue is identified on both Citrix XenApp 7.x (Windows Server OSs) and Citrix XenDesktop 7.x (Workstation OSs)

“The primary display adapter is not shown as the default in a Citrix environment.”

autocad_issue

I am happy to share that Autodesk have finally fixed this “bug” with Citrix and now the GPUs will work correctly with Autodesk AutoCAD 2016 and Autodesk AutoCAD 2017 when you apply below hot fix for the product you have.

Accumulated hotfix 4 for AutoCAD 2016 based applies to:

This hotfix for citrix applies to the following releases with the AutoCAD 2016 Service Pack 1 already installed:

  • Autodesk AutoCAD 2016
  • Autodesk AutoCAD Architecture 2016
  • Autodesk AutoCAD Civil 3D 2016
  • Autodesk AutoCAD Electrical 2016
  • Autodesk AutoCAD Map 3D 2016
  • Autodesk AutoCAD Mechanical 2016
  • Autodesk AutoCAD MEP 2016
  • Autodesk AutoCAD P&ID 2016
  • Autodesk AutoCAD Plant 3D 2016
  • Autodesk AutoCAD Utility Design 2016

Issues Resolved by This Hotfix for citrix

  • There is a security vulnerability with ATIL image files within a drawing.
  • The primary display adapter is not shown as the default in a Citrix environment.
  • Opening an Excel hyperlink resizes the AutoCAD application window to match the Excel sheet size.
  • Locked objects can be edited by Matchprop command.
  • Publish borders are cut off with certain sheet sizes.
  • Background masks are not ignoring the Xrefoverride setting.
  • Can crash when panning transparently in multiple viewports.
  • Performance problem opening files containing specific objects in AutoCAD 2016 may appear as if files cannot be opened.
  • Use of the LISP (command) function within the (mapcar) function results in VVC Internal Error.
  • Grip stretch doesn’t work correctly when DYNMODE equals value other than 2 or 3.
  • acedCallBackOnCancel is not detected for Lispcallable Functions.
  • Certain VBA Macros throw an execution error.
  • DWG file fails to insert into another DWG file.
  • Can crash when Copy/Paste a block by Ctrl+C, Ctrl+V.
  • Can crash when opening AutoCAD in Windows 10.
  • AcSettingSync.exe launched when running OPTIONS command.
  • Annotations in Architectural units format are changing to Decimal format.

Accumulated hotfix 4 for AutoCAD LT 2016 applies to:

this hotfix for citrix applies to the following release:

  • Autodesk AutoCAD LT 2016 with the AutoCAD LT Service Pack 1 already installed

Issues Resolved by This Hotfix for citrix

  • There is a security vulnerability with ATIL image files within a drawing.
  • The primary display adapter is not shown as the default in a Citrix environment.
  • Opening an Excel hyperlink resizes the AutoCAD LT application window to match the Excel sheet size.
  • Locked objects can be edited by Matchprop command.
  • Publish borders are cut off with certain sheet sizes.
  • Background masks are not ignoring the Xrefoverride setting.
  • May crash when panning transparently in multiple viewports.
  • Performance problem opening files containing specific objects in AutoCAD LT 2016 may appear as if files cannot be opened.
  • Grip stretch doesn’t work correctly when DYNMODE equals value other than 2 or 3.
  • DWG file fails to insert into another DWG file.
  • Can crash when Copy/Paste a block by Ctrl+C, Ctrl+V.
  • Can crash when opening AutoCAD LT in Windows 10.
  • AcSettingSync.exe launched when running OPTIONS command.
  • Annotations in Architectural units format are changing to Decimal format.

Apply this Service Pack to the following Autodesk products running on all supported operating systems and languages. Be sure to install the correct Service Pack.

This Service Pack can be applied to AutoCAD 2017 installed as a standalone application, AutoCAD-based Vertical products, and the Autodesk Design Suites listed below.

AutoCAD and Verticals Products:

  • AutoCAD 2017
  • AutoCAD LT 2017
  • AutoCAD Architecture 2017
  • AutoCAD Civil 3D 2017
  • AutoCAD Electrical 2017
  • AutoCAD Map 3D 2017
  • AutoCAD Mechanical 2017
  • AutoCAD MEP 2017
  • AutoCAD P&ID 2017
  • AutoCAD Plant 3D 2017
  • AutoCAD Utility Design 2017

Autodesk Design Suites:

  • Autodesk AutoCAD Design Suite 2017
  • Autodesk AutoCAD Inventor LT Suite 2017
  • Autodesk AutoCAD Revit LT Suite 2017
  • Autodesk AutoCAD with Advance Steel 2017
  • Autodesk Building Design Suite 2017
  • Autodesk Factory Design Suite 2017
  • Autodesk Infrastructure Design Suite 2017
  • Autodesk Plant Design Suite 2017
  • Autodesk Product Design Suite 2017
  • Autodesk Revit Collaboration Suite 2017

Display

 

Open and Save

  • Opening a drawing file using an Excel hyperlink was repositioning the AutoCAD application window.

PDF Import

  • Importing a PDF Underlay that was attached with relative path could fail.

Xref

  • The Xref status incorrectly displays the “Needs reloading” message when the dataset is opened from a UNC path to a shared folder.

General

  • When opening drawings created with AutoCAD Architecture, AutoCAD might crash if the drawing was saved again.
  • Plotting with certain visual styles might produce incorrect results.
  • Migrating custom settings might fail.

 

Source

Download the Autodesk AutoCAD 2017 Service Pack 1 here

Download Accumulated hotfix 4 for AutoCAD 2016 based products here

Download Accumulated hot fix 4 for AutoCAD 2016 here

AutoCAD mouse pointer issues with Citrix XenApp 7.6

Written by Thomas Poppelgaard. Posted in AMD, AutoCAD, Autodesk, Citrix, FirePro, GRID, GRID 2.0, HDX 3D, HDX 3D, Intel, Microsoft, NVIDIA, Quadro, vGPU, Windows Server 2008R2, Windows Server 2012, Windows Server 2012R2, XenApp

Citrix have released a limited hotfix for Citrix XenDesktop 7.6 and XenApp 7.6 that fixes an issue with Autodesk AutoCAD & AutoCAD Civil 3D where the  mouse pointer permanently displays as an hour glass. By applying this hotfix this fixes the issue for AutoCAD.

Source

Download the ICATS760WX64039 – For VDA Core Services 7.6 for Windows Server OS (64-bit) for Citrix XenApp 7.6 here

 

 

Google Chrome 45.x Blocks GPU Acceleration for WebGL, Direct2D, DirectWrite with Citrix XenApp on Windows 2008R2/2012/2012R2

Written by Thomas Poppelgaard. Posted in 8.1, Best Practise, Citrix, End User Computing, GRID, HDX, HDX 3D Pro, HowTo, Microsoft, Netscaler, NVIDIA, Receiver, Server 2012R2, vDGA, vGPU, VMware, vSphere, Windows 7, Windows Server 2008R2, Windows Server 2012, Windows Server 2012R2, XenApp, XenDesktop, XenServer

Solution: Google Chrome 45.x Blocks GPU Acceleration for WebGL, Direct2D, DirectWrite with Citrix XenApp on Windows 2008R2/2012/2012R2

Google Chrome v. 45  have changed their behaviour of their web browser, so they are blacklisting GPUs, which means hardware acceleration is disabled by default in a Remote session this behaviour is seen in Microsoft RDS with RemoteFX, Citrix XenApp 6.5 -> 7.6 with vGPU/GPU pass-through. Behaviour is also seen on Linux environments with Google Chrome.

Issue highlightet in a Citrix XenApp 7.6 (2008R2/2012/2012R2) with GPU

Open Google Chrome and type in chrome://gpu and then you will see if your RDS/XenApp with a GPU is working or not.
With Google Chrome v 45 the default behaviour is now that Google choose to disabling the GPU.

browser - chrome xa 2012r2 cpu issue - graphics feature issue

Google Chrome experience with a GPU (Citrix XenDesktop vs Citrix XenApp)

browser - chrome xd vs xa gpu - 2008R2 vs Win7

above picture confirms the GPU is not enabled in Google Chrome with RDS/XenApp

interesting is that Multiple Raster Threads in Win7 with a GPU is disable… why lets find out.

This is properly because you haven’t configured the CPU correctly in the hypervisor for the virtual machine.
* hint I did on purpose so you can understand it can be complex to troubleshoot if you don’t configure your environment correctly.

browser - chrome win7 cpu issue fix
best practices with HDX 3D Pro is 4 vCPU and in XenServer 6.5 you configure it 2:2

Then Multiple Raster Threads works in Win7 after you changed the configuration of the CPU on the Win7 vm.

browser - chrome win7 cpu fix

browser - chrome win7 cpu issue fixed

below picture confirms the GPU is not enabled in Google Chrome with RDS/XenApp in Server 2012R2

browser - chrome xd vs xa gpu - 2012r2 vs win81

Now we have validated that the GPU is blacklisted in RDS/XA with a GPU, lets see if we can fix this.

Performance with a WebGL web app in Google Chrome

CPU is very high when the Google Chrome is running the WebGL application. This is because its using the CPU to do software rasterize of the GPU and this makes your user able to run a webgl application without a GPU, but wait. We actually have a GPU in our RDS/XA server now, why is this not offloading the CPU, thats because Google desided to turn off GPU and blacklist them.

browser - chrome xa 2012r2 cpu issue

Solution

  1. Edit Google Chrome link and after the chrome.exe add
    –ignore-gpu-blacklistgooglechrome
  2. Open Google Chrome and run chrome://gpu in the browser
  3. Check if Hardware acceleration is now working for all functions in Google Chrome

browser - chrome xa 2012r2 cpu issue - graphics feature

GPU hardware acceleration is now working in RDS/XA with a GPU in Google Chrome and CPU is now offloaded to the GPU as you can see in the below picture.

browser - chrome xa 2012r2 cpu issue fixed

 

 

 

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

Recent Comments

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.

Alex

|

So how come version 3.11 doesn’t work for application switching?

John

|

Hello, how to allow SR-IOV for the Intel P580 in a m710x? (unable to find any settings in BIOS)

I get the following error: Dismount-VmHostAssignableDevice : The operation failed.
The device cannot be assigned to a virtual machine as the firmware (BIOS or UEFI) on this host computer system indicates that the device must remain in
contact with the firmware running in the host. The device can only be used in the management operating system. You should contact your OEM to determ
ine if a firmware upgrade is available, or if the PCI Express device can be reconfigured to be independent of the host firmware.

Aza

|

Great article Thomas.

Can you tell more about the difference in user density between M510 and M710x?
Citrix published an article with a LoginVSI test related to the M510 9https://www.citrix.com/blogs/2016/06/30/we-choose-to-go-to-the-moon/), but I’m more interested in the M170x because of its Iris Pro P580.