NVIDIA GRID – vGPU 352.83-354.80

Written by Thomas Poppelgaard. Posted in CentOS, Citrix, GRID, GRID 2.0, HDX 3D Pro, Horizon, Linux, Microsoft, NVIDIA, RHEL, Ubuntu, vGPU, VMware, vSphere, Windows 10, Windows 7, Windows 8.1, Windows Server 2008R2, Windows Server 2012R2, XenApp, XenDesktop, XenServer

nvidiagrid

Hi All

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

NVIDIA have released new drivers that supports Windows 10 + fix several bugs.

If you want to test Server 2016 then the new Windows 10 drivers works, I have just tried and they work but they are not “certified” so test this with your own risk, please. Always test this in a test environment and this is not for production environments, unless you want to be early innovators 😉

#HINT – Windows 10 is not supported on Citrix XenServer 6.2 only on Citrix XenServer 6.5.
## HINT – Linux drivers are only available with Tesla M6, M60.

Whats new in vGPU 352.83-354.80

NVIDIA have released a new version of vGPU 352.83-354.80 for NVIDIA GRID 1.0 (K1, K2) GRID 2.0 Tesla M6 and Tesla M60 platform.

Included in this release is

  • NVIDIA GRID Virtual GPU Manager versions 352.83 for Citrix XenServer 6.5 SP1
  • NVIDIA GRID Virtual GPU Manager versions 352.83 for Citrix XenServer 6.2 SP1 with hotfixes XS62ESP1009 and XS62ESP1011
  • NVIDIA GRID Virtual GPU Manager version 352.83 for VMware vSphere 6.0 Hypervisor (ESXi)
  • NVIDIA Windows drivers for vGPU version 354.80
  • NVIDIA Linux drivers for vGPU version 352.83.

 

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

Update existing vGPU GRID Manager (Hypervisor)

GRID vGPU Manager 352.83 upgrade for Citrix XenServer 6.2

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

Methodology 1 – the manual way “No GUI”

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

If you have NVIDIA GRID K1 / K2
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-kepler-xenserver-6.2-352.83.i386.rpm 
Preparing packages for installation...
If you have NVIDIA GRID TESLA M6 / M60
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-6.2-352.83.i386.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

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 352.83, if it is then your host is ready for GPU awesomeness and make your VM rock.

GRID vGPU Manager 352.83 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-352.83.x86_64.rpm 
Preparing packages for installation...
If you have NVIDIA GRID TESLA M6 / M60
[root@localhost ~]# rpm -Uv NVIDIA-vGPU-xenserver-6.5-352.83.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-352.83.x86_64-supplemental-pack.tar.bz2 ”

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

“NVIDIA-vGPU-xenserver-6.5-352.83.x86_64-supplemental-pack.tar.bz2 ”

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 352.83, if it is then your host is ready for GPU awesomeness and make your VM rock.

 

GRID vGPU Manager 352.83 for VMware vSphere 6.x

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_352.83-1OEM.600.0.0.2494585.vib
If you have NVIDIA GRID TESLA M6 / M60 select following file:
[root@lesxi ~] esxcli software vib install -v /NVIDIA-vGPU-VMware_ESXi_6.0_Host_Driver_352.83-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 352.83, 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.

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 🙂

New driver functionality with 354.80

  • 354.80_grid_win8_win7_64bit_international.exe
  • 354.80_grid_win8_win7_international.exe
  • 354.80_grid_win10_64bit_international.exe
  • 354.80_grid_win10_international.exe
  • NVIDIA-Linux-x86_64-352.83-grid.run

#1 Linux driver is not available with Citrix XenServer 6.2 or 6.5 and ESX for K1/K2. This is only available with GRID vGPU for M60

Linux support in only available with GRID Tesla M6 / M60

GRID vGPU with Linux guest VMs is supported on Tesla M60 and M6, with the following distributions:

  • Red Hat Enterprise Linux 6.6, 7
  • CentOS 6.6, 7
  • Ubuntu 12.04, 14.04 LTS

 

Source

GRID K1/K2 – sources

Download vGPU 352.83-354.80 for XenServer 6.2 for GRID K1 / K2 her

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

Download vGPU 352.83-354.80 for vSphere 6 for GRID K1 / K2 here

 

Tesla M6/M60 – sources

vGPU Grid Manager + Drivers are only available to customers and NVIDIA NPN partners.

Download if you are a NPN partner

Download if you are a GRID 2.0 customer

vGPU 352.83-354.80 for XenServer 6.2 for Tesla M6 / M60

vGPU 352.83-354.80 for XenServer 6.5 for Tesla M6 / M60

vGPU 352.83-354.80 for vSphere 6 for Tesla M6 / M60

NVIDIA GRID – AppGuide (REVIT)

Written by Thomas Poppelgaard. Posted in Autodesk, GRID, Horizon, NVIDIA, Revit, VMware, vSphere

Hi All.

I want to share this with you all, Luke Wignall and his team from NVIDIA have created some great AppGuides, that helps with understanding how many users can you put on a NVIDIA GRID system with either K1/K2 in a VMware environment. These guides are made together with vendors such as Autodesk. The guides focus on following apps Autodesk Revit.

In this blogpost my goal is to highlight the great work NVIDIA have done creating the scalability app guides and these guides helps you if you want to virtualize Autodesk Revit with NVIDIA GRID and VMware Horizon. The guides are great – cause they give an idea what you would require in a virtualized environment and these can be reused for other virtualized platforms such as Citrix and Microsoft – keep in mind that results might be different. If you would like to get more informations about how the setup is configured and which methodology i recommend you read the AppGuide, you can download it in under source in the end of this article.

The appguides gives a great idea to understand the impact of CPU and how the GPU are giving value.

Autodesk-Logo-2013

revit2015

About Autodesk Revit 2015

Autodesk Revit is Building Information Modeling (BIM) software with features for architectural design, MEP and structural engineering, and construction.  Revit requires a GPU as you rotate, zoom, and interact with drawings. It also creates heavy CPU load as it manages all the elements of a drawing via a database, which means we need high performance storage as well.  The heaviest Revit CPU usage occurs during data-rich operations like file open/save and model updates. As a result both CPU and GPU need to be considered in architecting your vGPU solution.  The size of your drawing file, the concurrency of your users, and the level of interaction with 3D data need to be factored into defining your user groups.

Results Appguide for Autodesk Revit 2015

autodesk-nvidia-vmware

The following are results of our testing, looking for the greatest scalability while still within performance expectations.  Its important to note that your users, your data, and your hardware, will impact these results and you may decide a different level of performance or scalability is required to meet your individual business needs. As the RFO Benchmark does not currently exercise some of Revit’s newest GPU capabilities, and was built to push the limits of dedicated hardware versus the shared resources of VDI, the decision was made to stop testing once the host’s CPU was approaching 100% utilized and test times had climbed past twice what we were finding on the a single physical workstation with dedicated resources.  We then met with the Autodesk Revit team, discussed the results, reviewed the tests in action, and determined with eyes on that this was still within what a typical user would deem acceptable and usable. It’s been well documented that storage performance is key to providing high performance graphics workloads, especially with many users and ever-growing file or model sizes.

FYI – Lower scores are better, representing less time to perform the activity in below tables.

results with Intel Ivy Bridge processors & NVIDIA GRID K2 (K220Q GPU Profile)

revit2015_01

results with Intel Ivy Bridge processors & NVIDIA GRID K2 (K240Q GPU profile)

revit2015_03

results with Haswell processors & NVIDIA GRID K2 (K240Q GPU profile)

revit2015_04

Here are the results when we push for more scalability, bringing the maximum number of VDI guests to 20 and 24.  We have added a 15 second staggered start to emulate synthetic human behavior.

revit2015_05

Revit 2015 users per server

Based on our findings, NVIDIA GRID provides the following performance and scalability metrics for Autodesk Revit 2015; using the lab equipment shown below, using the RFO benchmark, and in working with Autodesk and their emphasis on usability.  Of course, your usage will depend on your models but this is guidance to help guide your implementation.
revit2015-users-pr-server

 

Source

Download the NVIDIA GRID vGPU APPLICATION GUIDE FOR AUTODESK REVIT 2015 ON VMWARE HORIZON here

 

NVIDIA GRID – AppGuide (AutoCAD)

Written by Thomas Poppelgaard. Posted in AutoCAD, Autodesk, Best Practise, Desktop Virtualization, End User Computing, GRID, Horizon, NVIDIA, VMware, vSphere

Hi All.

I want to share this with you all, Luke Wignall and his team from NVIDIA have created some great AppGuides, that helps with understanding how many users can you put on a NVIDIA GRID system with either K1/K2 in a VMware environment. These guides are made together with vendors such as Autodesk. The guides focus on following apps Autodesk AutoCAD.

In this blogpost my goal is to highlight the great work NVIDIA have done creating the scalability app guides and these guides helps you if you want to virtualize Autodesk AutoCAD 2015 with NVIDIA GRID and VMware Horizon. The guides are great – cause they give an idea what you would require in a virtualized environment and these can be reused for other virtualized platforms such as Citrix and Microsoft – keep in mind that results might be different. If you would like to get more informations about how the setup is configured and which methodology i recommend you read the AppGuide, you can download it in under source in the end of this article.

The appguides gives a great idea to understand the impact of CPU and how the GPU are giving value.

Autodesk-Logo-2013

AutoCAD_2016

About AutoCAD 2015

Autodesk AutoCAD is one of the most globally used software platforms for CAD design and documentation.  AutoCAD leverages both CPU and GPU to deliver a high quality user experience, and as a result, there are several things that need to be considered in architecting your GRID vGPU solution: the size of your map data, the concurrency of your users, and the level of interaction with primary 2D and some 3D data.

Results NVIDIA Appguide for Autodesk AutoCAD 2015

autodesk-nvidia-vmware

The following are results of our testing, looking for the greatest scalability while still within performance expectations.  It’s important to note that your users, your data, and your hardware will impact these results, and you may decide a different level of performance or scalability is required to meet your individual business needs. As the Catalyst benchmark does not push AutoCAD’s GPU capabilities, and was built to push the limits of dedicated hardware versus the shared resources of VDI, the decision was made to stop testing once the CPU was approaching 100% utilized and test times had climbed past twice what we were finding on the a single physical workstation with dedicated resources.  We then met with the Autodesk AutoCAD team, discussed the results, reviewed the tests in action, and physically verified that this was still within what a typical user would deem acceptable and usable. When running AutoCAD, anything higher than 20 FPS is awesome, but users generally don’t notice the difference once you exceed 30 FPS.  However, once you drop below 10 FPS, the software is going to feel very sluggish and become unusable by the time you hit 5 FPS. • 20 fps above is good • Below 10fps – sluggish • 5 fps – unusable

  • 32VM : K220Q perform better than K120Q but K120Q is still maintain avg 31FPS. 
  • 40VM : Due to vGPU configuration, need K120Q, avg FPS is 24 FPS
  • 48VM : one you hit 40 VM running, avg FPS is dropping below 10 FPS. 

AutoCAD requires significant CPU resources, so investing in higher CPU speeds and more cores will pay off on performance and scalability.  For medium to large models, K240Q performance might be better for a real use scenario. Since your own situation is different, you must test with your own models to ensure the most accurate results. The chart below shows a comparison between two different sets of VDI guests, one using the K2 and its K220Q profile, the other a K1 and its similarly sized frame buffer profile, the K120Q:

äutocad2015_scaling-01

Notice that as scale, the number of concurrent VM’s increases, there is an obvious drop in performance, and logs will show this is the CPU becoming 100% utilized.  This is a “peak workload” test as all sessions are started in unison, we would expect humans to be more staggered in their workflow.

The next chart shows results when we add that synthetic human behavior, we delay the launching of each session by 5 seconds, this offsets the tests and prevents all tests hitting the same function and impacting the CPU in unison.

äutocad2015_scaling-02
Notice that with delayed launching, or staggered starts, the performance remains high to a much greater scale of concurrent sessions.

Additional findings from this testing:
vCPU –  2 vCPU are sufficient for this benchmark, however increasing model size and complexity will change this. 
• Virtual System Memory – 2 GB is sufficient for this benchmark, however increasing model size and complexity will change this.  
• K220Q/K120Q  : both show capped FPS caused by frame rate limiting (FRL) 
• vGPU has 45 fps frame limiter for performance balancing across multiple VM

AutoCAD 2015 Users per server

Based on the NVIDIA GRID™ Performance Engineering Lab (GRID P.E.L.) findings, NVIDIA GRID provides the following performance and scalability metrics for Autodesk AutoCAD 2015. These metrics are based on tests with the lab equipment shown in the graphic below, using the Cadalyst benchmark, and in working with Autodesk and their emphasis on end user usability.  Of course, your usage will depend on your models and equipment, so this Application Guide is intended to be used as a starting point for your implementation.

autocad-users-per-server

 

Source

Download the NVIDIA GRID vGPU APPLICATION GUIDE FOR AUTODESK AUTOCAD 2015 ON VMWARE HORIZON here

 

NVIDIA GRID – AppGuide (ArcGIS Pro)

Written by Thomas Poppelgaard. Posted in Best Practise, End User Computing, ESRI, GRID, Horizon, NVIDIA, VMware

Hi All.

I want to share this with you all, Luke Wignall and his team from NVIDIA have created some great AppGuides, that helps with understanding how many users can you put on a NVIDIA GRID system with a K2 in a VMware environment. These guides are made together with vendors such as ESRI. The guides focus on following apps ESRI ArcGIS Pro.

In this blogpost my goal is to highlight the great work NVIDIA have done creating the scalability app guides and these guides helps you if you want to virtualize ESRI Pro with NVIDIA GRID and VMware Horizon. The guides are great – cause they give an idea what you would require in a virtualized environment and these can be reused for other virtualized platforms such as Citrix and Microsoft – keep in mind that results might be different. If you would like to get more informations about how the setup is configured and which methodology i recommend you read the AppGuide, you can download it in under source in the end of this article.

The appguides gives a great idea to understand the impact of CPU and how the GPU are giving value.

esri

arcgis

About ESRI ArcGIS Pro

ESRI ArcGIS Pro 1.0 is a  Geographic Information Systems (GIS) application for mapping, visualizing, editing, and analyzing spatial data.  Esri recommends a GPU for best end user experience, but as ArcGIS Pro 1.0 also generates heavy CPU load, this also needs to be considered in architecting your vGPU solution.  The size of your map data, the concurrency of your users, and the level of interaction with 3D data all need to be considered when defining your user groups.

Results NVIDIA Appguide for ESRI ArcGis Pro

esri-nvidia-vmware

The following are the full results of our testing.  The baseline was the 45 second draw time sum – anything greater than that value represented a worsening UX while less would be a better UX.  Looking for both performance and scalability, we tested looking for the greatest number of virtual desktops, and therefore the greatest scalability, while still within performance expectations and the threshold of 45 seconds.  It’s important to note that your users, your data, and your hardware will impact these results and you may decide a different level of performance or scalability is required to meet your individual business needs.   Tests were also run to look for potential NUMA issues that can negatively impact performance.  This is where the physical GPU and its PCI-e channels are tied to one physical CPU, while the virtual desktop is running on the other physical CPU, so communication with the physical GPU has to move over the QPI between the two physical CPUs.  This creates a bottleneck and can cause performance issues.  However, in our testing, the application is sufficiently CPU bound that NUMA affinity made little difference. The results in the table below show the decrease in performance as we increased vCPU counts, and then the increase in scalability with synthetic human behavior (think time):

esri-arcgis-users-pr-server-2

ArcGIS – users pr server

Based on NVIDIA Performance Engineering Lab findings, NVIDIA GRID provides the following performance and scalability metrics for Esri ArcGIS 3D Pro 1.0. These metrics are based on tests with the lab equipment shown in the graphic below, using the Esri API based “heavy 3D” benchmark and in working with Esri to determine acceptable performance.  Of course, your usage will depend on your models, but this is guidance to help guide your implementation.

esri-arcgis-users-pr-server

Source

Download the NVIDIA GRID vGPU APPLICATION GUIDE FOR ESRI ARCGIS PRO 1.0 – 3D ON VMWARE HORIZON here

Citrix XenDesktop 7.8 and Citrix XenApp 7.8

Written by Thomas Poppelgaard. Posted in AMD, AppDNA, Apple, Citrix, Datacenter and Cloud, Desktop Virtualization, DirectX 12, End User Computing, FrameHawk, GRID, GRID 2.0, HDX, HDX 3D Pro, Intel, Linux, Linux Virtual Desktop, Microsoft, NVIDIA, OS X, Provisioning, Provisioning Services, Receiver, vGPU, Virtualization Ready, VMware, vSphere, Windows 10, Windows Server 2016, XenApp, XenDesktop

citrixxendesktopandxenapp78

Citrix have released a new version of Citrix XenDesktop 7.8 and XenApp 7.8 and is now available for download.

Citrix raises the bar of for user experience and new product release for Storefront 3.5, Provisioning Services 7.8, Citrix Receiver 12.1.10 for Mac (OSX), License Server 11.13.1.2 for Windows, XenApp Secure Browser Deployment Kit, AppDNA 7.8, Session Recording 7.8.

This is WILD Citrix released 7.7 in 30th December 2015 with so many features and already two months after we got a major release out.. If you havent upgraded your 7.x environment 7.8 is worth a try.

HINT! – Remember first thing you do is downloading the new version of Citrix License Server 11.13.1.2 cause this is a requirement for below products to work.

Lets look at the build 7.8

The product release includes the following new and enhanced features.

  • AppDisks For more information, see the AppDisks article.
  • Enhanced support for Microsoft Application Virtualization  (App-V) App-V article.
  • Applications node in Studio For more information, see the Manage applications and Create Delivery Groups articles.
  • Updated Create Delivery Group wizard and Edit Delivery Group interface  For more information, see the Create Delivery Groups and Manage applications articles.
  • Improved tag interface in Studio For more information, see the Tags article.
  • Requirements, installation, and configuration updates
  • Call Home Citrix Call Home  performs periodic collections of your system and product configuration, plus performance, error, and other information. This information is sent to Citrix Insight Services for proactive analysis and resolution For details, see the Citrix Insight Services article.
  • Citrix Insight Services link available from within Director You can access Citrix Insight Services (CIS) from the User drop-down in Director to access additional diagnostic insights. The data available in CIS comes from sources including Call Home and Citrix Scout.
  • VMware SSL thumbprint The VMware SSL thumbprint feature addresses a frequently-reported error when creating a host connection to a VMware vSphere hypervisor. Previously, administrators had to manually create a trust relationship between the Delivery Controllers in the Site and the hypervisor’s certificate before creating a connection. The VMware SSL thumbprint feature removes that manual requirement: the untrusted certificate’s thumbprint is stored on the Site database so that the hypervisor can be continuously identified as trusted by XenApp and XenDesktop, even if not by the Controllers. When creating a vSphere host connection in Studio, a dialog box allows you to view the certificate of the machine you are connecting to. You can then choose whether to trust it.

Virtual Delivery Agents (VDAs) 7.8

Version 7.8 of the VDA for Server OS and the VDA for Desktop OS include the following enhancements:

  • App-V and Framehawk installer options. The VDA installers offer two additional items you can select on the Features page in the graphical interface or specify on the command line.

Framehawk. Opens UDP ports 3224-3324. Framehawk uses a bidirectional UDP port range (default is 3224-3324) to exchange Framehawk display channel data with Citrix Receiver. For more information, see Framehawk virtual channel.

Citrix App-V Publishing Components. Installs components required if you will use applications from Microsoft App-V packages. For more information, see App-V.

  • HDX 3D Pro product edition availability. HDX 3D Pro is now available in the VDA for Windows Desktop OS in all XenApp 7.8 and XenDesktop 7.8 product editions. In earlier releases, only certain product editions supported the 3D Pro VDA. HDX 3D Pro is not currently supported on Windows 10.
  • KACD .MSI file included in VDA packages. This file is included to support future customization of authentication. This file was not included with earlier releases.

HDX technologies

The following new and enhanced HDX technologies features are included in the VDAs:

  • Framehawk support for HDX 3D Pro VDI. HDX 3D Pro support for the Framehawk virtual channel is extended from XenApp to XenDesktop VDI. This gives users greater flexibility to view large CAD models while on the move on a corporate or public wireless network, or working from an offshore location over a high latency connection. For more information on Framehawk, see Framehawk virtual channel.
  • Framehawk server scalability improvements. Over 40% average reduction in memory footprint. Up to 20% increase in CPU efficiency.
  • Framehawk touch scrolling improvements. Over 50% improvement in bandwidth efficiency when scrolling via touch input. Significantly increased frame rate resulting in a smoother user experience.
  • GPU acceleration for DirectX windowed applications on Windows 10 VDAs. This release adds support for GPU acceleration for DirectX 10, 11 and 12 windowed applications on Windows 10 VDAs.
  • Thinwire Build to lossless enhancements. The Build to lossless visual quality for Thinwire has been updated to sharpen fuzzy imagery at a faster rate than delivered in XenApp and XenDesktop 7.6 FP3, and to improve lossy or lossless frame detection. For the main Thinwire article, see Thinwire Compatibility Mode.
  • Reduced VDA memory footprint in Thinwire. The graphics encoder processing pipeline now eliminates the use of an intermediate frame buffer when running Thinwire without video codec compression.
  • Clientname passthrough in double-hop sessions. Applications can use the updated WFAPI SDK to query the client endpoint name and pass this information from any Citrix Receiver to published desktops (XenApp/XenDesktop) and through to a XenApp application (a “double-hop”). This clientname awareness in the XenApp session means that users can seamlessly roam from location to location, and the “double-hop” application will be notified of the change in clientname without having to disconnect or reconnect the session. For more information on how to write conforming applications, see the WFAPI SDK documentation or defer to your application SI/ISV.

Session Recording 7.8

Session Recording 7.8.0 includes support for Platinum XenApp 7.8 and XenDesktop 7.8.  This support includes:

  • Session recording support from a Desktop OS VDA. Record on-screen activity of a user session hosted from a Desktop OS VDA over any type of connection, subject to corporate policy and regulatory compliance.
  • Record sessions on remote PC. Support for recording sessions in Remote PC Access.
  • Delivery Group rules.
  • Keyword filtering during rule configuration.
  • Special handling for unsupported graphics modes.
  • Windows 10 support.
  • Thinwire Compatibility Mode support.

AppDNA 7.8

AppDNA 7.8 includes the following enhancements:

Provisioning 7.8

The folllowing new features are available with Provisioning Services 7.8:

Generation 2 Virtual Machines

System Center Virtual Machine Manager Generation 2 VMs can be provisioned through Provisioning Services. Generation 2 VMs are optimized for modern workloads, that is, the operating system does not carry the overhead of legacy drivers, devices and x86 architectures.

How does it work?

Virtual machine (VM) generation determines the virtual hardware and functionality available to the VM. Within a Hyper-V environment, there are two types of supported VMs: generation 1 and generation 2. Generation 2 VMs possess a simplified virtual hardware model, and support Unified Extensible Firmware Interface (UEFI) firmware rather than BIOS-based firmware.

In previous versions of Hyper-V, only Generation 1 VMs were supported. With the introduction of Windows Server 2012 R2, there are two generations of VMs to choose from when you create a VM. With Generation 2 VMs,the following functionality was introduced:

  • PXE boot by using a standard network adapter
  • Boot from a SCSI virtual hard disk
  • Boot from a SCSI virtual DVD
  • Secure boot
  • UEFI firmware support

Unified Extensible Firmware Interface (UEFI) enhancements

This release of Provisioning Services provides continued hardening for UEFI support. UEFI represents a standard firmware interface for PCs, and is designed to replace BIOS (basic input/output system). With these enhancements, Citirx Provisioning Services provides:

  • improved security by helping to protect the pre-boot process against bootkit attacks.
  • support for larger disk drives (greater than 2.2 terabytes).
  • support for modern, 64-bit firmware device drivers which can be used to leverage large amounts of memory during startup.
  • the capability to use BIOS with modern UEFI hardware.

StoreFront 3.5

What’s new in the StoreFront 3.5

StoreFront includes the following new features and enhancements.

Updated StoreFront management console – The StoreFront management console contains a significant number of changes, which enable:

  • Store-centric console architecture – Authentication and Citrix Receiver for Web settings are organized around stores to simplify navigation for multi-store deployment.
  • Different authentication settings for different stores.
  • Configuring delegation of authentication to XenApp or XenDesktop farms or sites.
  • Configuring multi-site high availability.
  • Configuring optimal NetScaler Gateway routing.
  • Setting a Receiver for Web site as the default site in IIS.
  • Configuring many other settings previously done with web.config.

New administration PowerShell SDK:

  • Cmdlets in the new SDK are prefixed with STF and focus on administration tasks grouped around StoreFront deployment-wide configuration, stores, authentication, and Citrix Receiver for Web.
  • Citrix provides high-level example scripts to enable you to script and automate StoreFront deployments quickly and easily.

The existing cmdlets prefixed with DS are deprecated. They are still available and supported in StoreFront 3.5 to enable a gradual transition to the new SDK.

Configuration export and import:

You can export the entire configuration of a StoreFront deployment. You can import the exported configuration to a deployment with the same StoreFront version for restoration or replication.

Self-service password reset (SSPR):

Users can unlock their Active Directory accounts or reset their passwords using StoreFront. This requires XenApp 6.5.

Zone-based optimal gateway routing:

XenApp 7.7 and 7.8 and XenDesktop 7.7 and 7.8 support applications or desktops from different zones in a single site. You can configure a different NetScaler Gateway for HDX connections to applications or desktops from a different zone.

Global Server Load Balancing (GSLB) powered zone preference:

You can configure GSLB in NetScaler 11.0-65.x and above to supply zone preference information to StoreFront. Along with this feature, you can configure StoreFront to direct the startrequests to the most preferred XenApp or XenDesktop farms or sites for the user location.

Background Server Health Check:

StoreFront runs periodic health checks on each XenApp and XenDesktop broker to reduce the impact of intermittent server availability. You can control the frequency of the health check.

TLS 1.2 support

This StoreFront release supports TLS 1.2.

Source

Download Citrix XenDesktop 7.8 and Citrix XenApp 7.8 here and all the above medias included in the product release. (requires MyCitrix ID)

Recent Comments

Jacquelynn

|

Practical discussion . BTW , others are searching for a DoJ Form FD-258 , my business encountered a fillable form here http://pdf.ac/4ItUrp

Sindy Degraw

|

Hi Thomas! Invaluable commentary . I loved the specifics . Does anyone know if I could get a sample a form copy to type on ?

Dwain

|

Hi Thomas,

Thanks for the information, but the link appears dead. Having the same issue with XenServer / XenDesktop 7.6 Grid K2 / AutoCAD

Sinbad

|

Need your experise guys….

Is there any documentation you might know where I can download stating that antivirus is not required in building or setting-up my own Citrix XENServer Host O.S.

Thanks,
Sinbad

Karmdeep

|

Can any one let me know how soon is Citrix going to release the next version of 1y0-351 Exam for Netscaler IOS ver.11.