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/ 

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

HPE Discover London 2015

Written by Thomas Poppelgaard. Posted in Augmented Reality, Citrix, Cloud, Desktop Virtualization, End User Computing, Envy, Events, FrameHawk, GRID, GRID 2.0, HDX, HDX 3D, HDX 3D Pro, HPE, HPE Discover, M710P, Moonshot, NVIDIA, Oculus Rift, Provisioning Services, Quadro, Sprout, Tesla, Virtual Reality, VMware, XenDesktop, XenServer

HPdiscover-independentInflucerprogram

Last year I was invited by HPE to go to their EMEA event HPE Discover in London, which took place the first week of December. I was invited there as part of their Hewlett Packard Enterprise Independent Influencer Program, and I was super proud of being part of this well organized program, which Kristen Reyes manages. HUGE kudos to Kristen Reyes and her team for putting together one of the most organized events I have ever attended as a blogger. Last time I attended HPE Discover was some years ago at their big US HPE Discover which took place at Las Vegas. I remember it was HUGE with lots of people – an epic experience that my previously employer, Arrow ECS managed the trip for. I had pretty high expectations going to the HPE Discover and I knew it was going to be good, but not as good as it REALLY was.

HPE Independent Influencer Program:

I am proud of being part of this program – let me tell you which profiles are part of the program including myself.

The team behind HPE took care of us from the time I flew all the way from Denmark to London. They made sure we got the right hotel and then once at the venue, we got a special VIP room where we got introduce each other. Team had a plan for what happend exclusively for the group. This reminds me of the Citrix CTP program I am humble to be part of where we also meet 2 times a year and are taken especially care of.

HPdiscoverLondon2015-3

If you want to read more about the individuals tech bloggers, that are in the program, click here.

I highly recommend you follow above persons, as they are awesome people. This is the first time I have been with such a wide  range of technology bloggers in my life and it was a huge difference – so thank you to HPE for daring to put so many different profiles together.

 

Let’s talk about HPE Discover in London 2015

There was 13.000 attendees. YES! That is INSANE and it felt like being in United States but I was in London. London can also have huge venues and they succeeded with cherry top on the beautiful cake. Yes HPE pulled it off! Please other big vendors – start making EMEA events because London is a perfect spot for this! Citrix, VMware, Microsoft… EMEA salutes you..

poppelgaard_twitter01

HPdiscoverLondon2015

I was in for a surprise the first day of the keynote when Meg Whitman kicked off HPE Discover, and Satya Nadella Microsoft CEO talked even thought it was via a conf call (but still pretty cool) and Microsoft showed the flag. I would have loved if Satya could have come in person since that would have been my first time seeing Mr. Nadella in person.

poppelgaard_twitter02

After a great keynotes learning about where HPE is taking the company, it was time to walk around the expo to see what innovative technologies were hidden and what others I was allowed to blog about.

Next gen consumer products for engineers & designers

HP ENVY 34

HP envy 4k IMG_5222

This device is so beautiful the brand new HP Envy 34, its the widest screen I have ever seen on a professional computer and its powered by Intel HD530 GPU and NVIDIA GTX 960A GPU. The speakers are B&O (Danish design brand).

Price for this device is approx 1700 USD – that’s pretty cheap for an All-in-one machine.

Another beautiful Augmented Reality device I tried was the HP Sprout. This device makes it possible to quickly edit 3D models in real time by taking objects from reality and scanning them directly in to the device. Then you can manipulate with the object and then print it out on a 3Dprinter. This process increases  the speed of making a design. Right now, the device is only available for consumers but we might see that change soon for enterprises since the unit was displayed at the HPE Discover 🙂  – so watch out for this space. I also saw AMD had setup several Oculus Rift DK2 units running some great demos. Great to see that VR was at HPE Discover.

HP sprout HPdiscoverLondon2015-VR

Deep Learning & The Machine

IMG_5231  the machine

I meet many of the brains behind the Deep Learning “things” HPE are doing, and its VERY impressive where they are, and how HPE differs to their competitors. I can’t talk much about it now – and will leave it up to how things are evolving later this year – and then blog more about it when the information is available to the public. But if you are fascinated by the future and AI / Deep learning you should look at what HPE is doing with the concept, “The Machine”. If you look at what they are trying to accomplish and put the puzzle together yourself, you might see for yourself how HPE will make a difference in how next generation datacenters will be built – that’s a fact.

Learn more about the HPE “The Machine” here

Citrix Octoblu & HPE – The Cube
(The ultimate iOT automated conference room)

The Cube

HPE Smart Digital Collaboration Space (1107), a.k.a. “The Cube.” . That was the name of this cool concept.

This was mind-blowing – and one of the most innovative things I saw at HPE Discover with IoT using Citrix Octoblu.

HPE, together with Aruba and Octoblu have teamed together to create a beautiful workflow that automates a conference room with iOT.

All visitors could try this at the event. HPE allowed 3-4 people to enter the cube as a group. We were asked our name and then were given an iPhone to bring into “The Cube”. The system then welcomed use by name and the room went from “green” to “red” (which was Philips Hue that did this), so the people outside could clearly see that the room was occupied and a meeting was taking place. An HP tablet on the door outside also showed the room was occupied and listed the attendees by name. Inside, the HP surface PCs connected to Skype for Business, Samsung TV started and a business session went live. At the end,  “The Cube” took a selfie and put on twitter and sent the photo to our emails and after we left the room. Upon exiting, it reset all the workflows and the room was lit green again – ready for next group. Amazing 🙂

IMG_5255IMG_5258

Below is the workflow that was created in Octoblu

Octoblue Workflow HPE

Try out octoblu here if you havent tried it yet. Its still beta and “FREE” https://octoblu.com/

Read the official blog post from Citrix about the solution

 

HPE & NVIDIA GRID offerings

HPDiscoverLondon2015-NVIDIAnvidia-tesla-m6

It was great to see all the new NVIDIA GRID 2.0 solutions. Two gentlemen proudly showed the HPE ProLiant WS460C Gen9 that now supports NVIDIA Tesla M60 and NVIDIA Tesla M6. This means higher density and more performance. So great to see that HPE is a pioneer, offering the entire solution from NVIDIA. There is soon NVIDIA GTC – and I expect we will see some data on customers running on HPE solution with M60/M6 and we get some data on how many users can run on these new offerings. It’s actually my first time seeing on-hands the M6 GPU from NVIDIA and it looks beautiful and green. These GPUs are made for low end GPU workloads all the way up to high end GPU workloads. The performance of the M60 is 2x the performance compared to K2 (GRID 1.0)

Please keep in mind that NVIDIA has changed GRID 2.0 so when you buy the GPUs, you also have to buy a “software” license.
Your NPN (NVIDIA preferred partner) should be able to help you with providing you the correct information. This license is required both for Pass-through and vGPU of the M60 and M6.

grid-license

 

Moonshot and beyond

IMG_5275IMG_5276IMG_5278

HPE Moonshot has been a subject I have been following for a while now. It all started when one of my great friends (and fellow CTP) Dane Young talked about HP Moonshot and why it differs to the market. HPE liked Young’s view – and his face is now on the wall at the Houston research facility. So if you are a client or a partner, you might know Dane Young – or you will if you are in Houston to see what HPE is doing with HPE Moonshot.

Citrix had a booth at the HPE Discover and they showed how Citrix is working and offered on a HPE Moonshot stack.

The HPE Moonshot team had several sessions talking about the next generation “trader workstation” which opens my eyes on how users use a computer. Traders are actually some of the most “difficult” users to satisfy – and they have a very short lifetime as an employee because its so hard what they do is so stressful. The amount of monitors and amount of data they look at is shocking and the high availability for this is nothing like you have never seen before. If these people cant work, the moneyflow stops moving – something you don’t want in the financial world. Designers are one thing, but I would definitely call traders the most difficult users. So what´s so amazing about the HPE Moonshot offering? HPE has a new catridge called the M710P, which was released in the Summer 2015. It has a high amount of CPU/GPU (or as others call it APU which is a CPU/GPU processor in 1 unit). Lots of memory and high speed disks. This is all build in a super small server which we call a cartridge. This cartridge can be put in a system and an OS can be installed and now you can have many users connecting to the catridge and using multiple sessions from Microsoft Remote Desktop Services combine this with Citrix super power “XenApp” and you now have an amazing flagship for having high amount of users with low cost. Nothing is virtualized and everything is running on bare metal. The beauty about the moonshot is that in 1 chassis you can put in 45 catridges of the M710P.

Moonshot cartridge building blocks for Citrix workloads

These are the offering that HPE have with Moonshot and Citrix and you can build amazing workloads. Personally, I would look at the M710p because I think this is the cartridge that is mature for the workload. I normally design Citrix solutions with.. wait are you talking about GPU? Yes I am..

moonshot-buildingblocks

If you remember some time ago, Brian Madden, said “Imagine if you could put 20.000 users in a single rack? Let’s see what has happended since then. Things have evolved – and with the new cartridge M710p, its much more powerful than the first cartridges that were built for Citrix

brianmadden_moonshot

Citrix is using Moonshot internally

At HPE Discover, Citrix had a session with Bob Thompson from Citrix and together with the HPE Moonshot team EMEA telling how Citrix is using HPE Moonshot.

I had never heard about Citrix is using it at this scale – and big surprise their demo cloud is also running on Moonshot.

poppelgaard_twitter03

Insights what Citrix IT are doing with HPE Moonshot

  • “Citrix on Citrix” – team responsible for deploying Citrix products internally
  • Upgrading to latest version of XenApp
  • Seamless app access from Windows 10 devices
  • Superior user experience
  • Improved security (e.g. both FIPS Compliant and Common Criteria certified)
  • Migrating to Moonshot (m710) for XenApp from HP Blades
  • Designed and optimized for XenApp
  • Less: power consumption, space and cabling
  • 8,500 sessions, across the globe in (4) data centers

“WOW so why arent more people using Moonshot, if this is so good and Citrix is doing this, it is mature”.

citrix-moonshot

citrix-moonshot-02

M710P & Citrix – Next gen trader workstation

I am very impressed about this new machine and HPE is having HUGE success with this machine for the financial buisness. In fact, some of the biggest banks in the world are running on this. Surprised ? IT’S TRUE

Let’s look at the details of what it is.

moonshot-m710p-nextgentraderworkstation

Here is a typical trader running with 4 monitors connecting to 1 catridge M710p and only 47% of the GPU is utilized. AMAZING!

IMG_5246 IMG_5245

HPE-nextgentraderworkstation

 

M710P catridge – hardware specifications

m710p front m710p back

WORKLOADsVideo transcoding , Application Delivery
CPU+GPUIntel Xeon E3-1284Lv4 with on-die GPU (GT3e: Iris Pro P6300)

4 core, 8 thread, 2.9 GHz (3.8GHz Turbo), GPU, 128MB DRAM

MEMORY32GiB of ECC-protected memory, dual-memory channels

4 x 8GB LV SO-DIMMs at 1600MT/s

NETWORKIntegrated NIC: dual port 10GbE Mellanox CX3 PRO

Supported Switch(s): 45 port 10GbE Downlinks, 4 x 40GbE QSFP uplinks

STORAGELocal SSD boot and data: 120GB, 240GB, 480GB or 960GB

m.2 (2280) form factor

POWERCartridge: 83W peak, 50W typical
OSUbuntu 15.05 w/KVM, RHEL 6.5,7.0 w/KVM, SLES 11.4/12,

Windows Server 2012 R2, 2008R2, CentOS 6.7, 7.2

What you get in a 4.5U chassis?

  • 1.44TB RAM
  • 90 10Gb NICs (internal)
  • 8 x 40Gb QSFP+ uplinks (320Gb/s total bandwidth)
  • 2 independent L2/3 switches with 450Gb throughput
  • 45 GPUs
  • 45 CPUs
  • 180 Cores (360 with HyperThreading)
  • 5.4TB, 10.8Tb, 21.6TB or 43TB iSSD Storage
  • 1800 users (conservative @ 40 per server)

Moonshot – what can you get in a rack

  • 10 x 4.3U Chassis
  • 14.4TB RAM
  • 20 independent L2/3 switches with 4.5Tb throughput
  • 450 GPUs
  • 450 CPUs
  • 1180 Cores (3600 with HyperThreading)
  • 54TB – 430TB iSSD Storage
  • 18,000 XenApp users (@40 users per server)

I hope the above gives you a pretty good idea on where Moonshot is going – and this is just for Citrix. HPE Moonshot is much more though -it’s a huge eco system build for enterprises and cloud providers, so check it out https://www.hpe.com/us/en/servers/moonshot.html

More informations about HPE Moonshot M710p – The Trader Workstation:

Bringing the Benefits of a Hosted Desktop Solution to Traders

Where can I try this

Book at demo and try HP Moonshot M700/M710/M710p here –  http://discoverylab-hpe.com/book-a-demo/

 

Summary

HPE Discover 2015 blew my mind – and it looks like we are going to have an amazing year in 2016.

I would like to say thank you to Kristen Reyes from HPE for making this happen. Each time I didn’t know what to do, she and her team took great care of me and made sure I meet the correct people at HPE – and there was always “open doors” (which isn’t always the case when techies sees a guy with a “blogger” sign around his neck).

Kristen Reyes

 

Citrix XenDesktop 7.7 and Citrix XenApp 7.7

Written by Thomas Poppelgaard. Posted in Citrix, Datacenter and Cloud, Desktop Virtualization, Director, End User Computing, FrameHawk, HDX 3D, HDX 3D Pro, Hyper-V, Local App, Lync, Microsoft, NVIDIA, Personal vDisk, Profile Management, Provisioning Services, Receiver, SQL, StoreFront, vGPU, VMware, vSphere, Windows 10, Windows 7, Windows 8.1, Windows Server 2008R2, Windows Server 2012R2, XenApp, XenDesktop, XenServer

xd77

Citrix have released a new version of Citrix XenDesktop 7.7 and XenApp 7.7

My first impressions of this release is, this is the release you should update to if you are running Citrix XenDesktop 7.x, the speed improvements in the GUI is incredible, its snappy realiable and makes you work without waiting it for loading when you click around the catalogs and the delivery groups. The 7.7 release is an important release from Citrix where Citrix is now fully supporting Microsoft Azure, so you can provisioning VDI or XenApp machines on Microsoft Azure with MCS technology. Another long waited feature is “Zones” this feature will be loved by customers that have branch offices where there is a requirement to install local Citrix infrastructure components such as Studio, Director, Site database, Zones was very common used in IMA architecture and now its finally implemented in FMA, great job Citrix. These are just some of the all the new huge improvements and this is the best release of XenApp/XenDesktop. Other new product release that is included in the XenDesktop/XenApp 7.7 media is HDX RealTime Optimization Pack 2.0, License Server 11.13.1, Profile Management 5.4, Citrix Provisioning 7.7, Citrix Receiver 4.4 is not in the iso, but you have to download this seperated, which i highly recommends.

What a great year to finish with and happy updating and I wish you all a Happy New Year.

Citrix XenDesktop 7.7 & Citrix XenDesktop 7.7 contains following software updates and new features and enhancements, this blog post covers all whats new in the architecture and components. Citrix Provisioning 7.7 is covered in a seperated article here.

Whats new in release 7.7 FMA

This product release includes the following new and enhanced features.

  • Zones

citrix xa xd 7.7

Deployments that span widely-dispersed locations connected by a WAN can face challenges due to network latency and reliability. Configuring zones can help users in remote regions connect to local resources without forcing connections to traverse large segments of the WAN. Using zones allows effective Site management from a single Citrix Studio console, Citrix Director, and the Site database. This saves the costs of deploying, staffing, licensing, and maintaining additional Sites containing separate databases in remote locations.

Zones can be helpful in deployments of all sizes. You can use zones to keep applications and desktops closer to end users, which improves performance.

For more information, see the Zones article.

  • Improved database flow and configuration

When you configure the databases during Site creation, you can now specify separate locations for the Site, Logging, and Monitoring databases. Later, you can specify different locations for all three databases. In previous releases, all three databases were created at the same address, and you could not specify a different address for the Site database later.

You can now add more Delivery Controllers when you create a Site, as well as later. In previous releases, you could add more Controllers only after you created the Site.

For more information, see the Databases and Controllers articles.

  • Application limits

Configure application limits to help manage application use. For example, you can use application limits to manage the number of users accessing an application simultaneously. Similarly, application limits can be used to manage the number of simultaneous instances of resource-intensive applications, this can help maintain server performance and prevent deterioration in service.

For more information, see the Manage applications article.

  • Multiple notifications before machine updates or scheduled restarts

You can now choose to repeat a notification message that is sent to affected machines before the following types of actions begin:

Updating machines in a Machine Catalog using a new master image

Restarting machines in a Delivery Group according to a configured schedule

If you indicate that the first message should be sent to each affected machine 15 minutes before the update or restart begins, you can also specify that the message be repeated every five minutes until the update/restart begins.

For more information, see the Manage Machine Catalogs and Manage machines in Delivery Groups articles.

  • API support for managing session roaming

By default, sessions roam between client devices with the user. When the user launches a session and then moves to another device, the same session is used and applications are available on both devices. The applications follow, regardless of the device or whether current sessions exist. Similarly, printers and other resources assigned to the application follow.

You can now use the PowerShell SDK to tailor session roaming. This was an experimental feature in the previous release.

For more information, see the Sessions article.

  • API support for provisioning VMs from hypervisor templates

When using the PowerShell SDK to create or update a Machine Catalog, you can now select a template from other hypervisor connections. This is in addition to the currently-available choices of VM images and snapshots.

  • Support for new and additional platforms

See the System requirements article for full support information. Information about support for third-party product versions is updated periodically.

By default, SQL Server 2012 Express SP2 is installed when you install the Delivery Controller. SP1 is no longer installed.

The component installers now automatically deploy 32-bit and 64-bit Microsoft Visual C++ 2012 runtimes, as well as 2008 and 2010 runtimes. Visual C++ 2005 is no longer deployed.

You can install Studio or VDAs for Windows Desktop OS on machines running Windows 10.

You can create connections to Microsoft Azure virtualization resources.

The product ISO no longer includes versions of the Citrix Receiver for Mac and the Citrix Receiver for Linux. You (or your users) can download and install the Citrix Receivers from the Citrix website. Alternatively, you can make those Citrix Receivers available from your StoreFront server (see the Make Citrix Receiver installation files available on the server section in the StoreFront 3.0.x documentation, or the equivalent documentation for the StoreFront version you are using).

Whats new in Citrix Director 7.7

The Citrix Director version provided with this release contains the following new and enhanced features:

  • Proactive monitoring and alerting

You can now configure proactive alerting and notifications when thresholds are reached. This enables quicker responses even when you are not viewing the monitoring console.

For more information, see Alerts and notifications.

  • SCOM integration

Deployments that use Microsoft System Center 2012 – Operations Manager to monitor deployments can now view alerts provided by the Operations Manager on the Dashboard and in other high level views in Citrix Director. For example, if connections to supported hypervisors fail, the administrator can check Citrix Director for Operations Manager alerts. After reviewing alert details in Citrix Director, the administrator can then switch to the Operations Manager console for additional troubleshooting, if needed.

For more information, see SCOM alerts.

  • Windows Authentication

Citrix Director now supports Integrated Windows Authentication. For single sign-on, a user’s Windows credentials are automatically used to access Citrix Director. This support allows users to log on to their machines using any credential provider and supporting hardware, and use that logged-on identity to access Citrix Director.

For  more information, see Use Citrix Director with Integrated Windows Authentication.

  • Desktop and Server OS usage

The Trends view now shows the usage of Desktop OS by Site and by Delivery group, and it shows the usage of Server OS by site, by Delivery group, and by Machine. This gives you a real-time view of your OS usage, enabling you to quickly assess your site’s capacity needs.

For more information, see Monitor historical trends across a Site.

  • Application limits in Citrix Director

Application limits configured in Studio are shown in existing views and counts in Citrix Director. For example, the User Connection Failures on the Dashboard will indicate when a connection attempt fails because it would exceed an application limit.

For more information, see Application limits.

What’s new in HDX RealTime Optimization Pack 2.0

Citrix Licensing Manager – Enables downloading and allocation of license files from the License Server on which the Citrix Licensing Manager is installed. You can specify a date range for the historical usage and export it to a CSV file.  The CSV file provides daily usage information including the number of licenses in overdraft. License Server VPX does not support the Citrix Licensing Manager.

  • Simple License Service is replaced – The Citrix Licensing Manager replaces the Simple License Service web UI.
  • Partial allocation of licenses – When using the Citrix Licensing Manager to download your licenses, you can specify how many licenses to download for a product. Previously, the Simple License Service allowed only a complete download of licenses for a product.
  • Citrix Licensing Customer Experience Improvement Program (CEIP) and Call Home support for License Server VPX  – Voluntary data collection programs in which Citrix products gather anonymous or identified configuration, performance, error, and usage data from your deployment and automatically send the data to Citrix. For more information, see “Citrix Licensing Customer Experience Improvement Program (CEIP) and Call Home” in Technical overview.
  • License Administration Console defaults to Hyper Text Transfer Protocol Secure  – When the License Administration Console installs, it defaults to https

What’s New in Profile Management 5.4

When upgrading Profile management, the installer removes the old version along with the WMI Provider, and then installs the new version. If you perform the upgrade after separating the two components, the WMI Provider is not upgraded. In this case, install it separately to ensure the two components remain compatible with each other and your VDAs.  You must provide the standalone WMI MSI file or installer for Versions 7.5 and 7.6 of the VDA so that the correct version of the WMI Provider installs after upgrading Profile management.

If you upgrade to Profile management 5.4 on a VDA earlier than version 7.7, use profilemgt_x64/x86.msi to do so. If you upgrade on a Version 7.7 VDA, Profile management 5.4 and WMI Provider 5.4 are automatically installed (by profilemgt_x64/x86.msi and UpmVDAPlugin_x64/x86.msi).

Source

Download Citrix XenDesktop 7.7 here (Require MyCitrix ID)

Download Citrix XenApp 7.7 here (Require MyCitrix ID)

Download Citrix Profile Management 5.4 here

Download Citrix HDX Optimization Pack 2.0 here

Download Citrix License Server 11.13.1 here (For Windows or VPX appliance)

Download Citrix Windows Receiver 4.4 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

 

 

Recent Comments

Server 2016 Migration

|

Hello I wish to to share a comment here concerning you to definitely be able to inform you just how much i personally Loved this particular study. I have to elope in order to aTurkey Day time Supper but desired to leave ya an easy comment. We preserved you Same goes with be returning subsequent function to read more of yer quality articles. Keep up the quality work.

Server 2016 Migration

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.