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

 

 

 

Citrix Netscaler Gateway 11

Written by Thomas Poppelgaard. Posted in Citrix, Netscaler, NetScaler Gateway

Citrix have released Netscaler Gateway 11

This is a major release and one thing I love about this release is that the entire GUI is again changed and now there is support for VPN access with Android, IOS, Linux.

NetScaler Gateway 11.0 adds the following new features and enhancements:

Citrix NetScaler Gateway 11 with Unified Gateway

This feature extends NetScaler Gateway connectivity with access to any web application through a single URL, along with seamless single sign-on and sign-off. Single URL access can be configured for:

  • Internal organizational web applications
  • Software as a Service applications, including SAML based single sign-on when available
  • Outlook Web Access and SharePoint as clientless applications
  • Load balanced applications served through NetScaler load balancing virtual servers
  • XenApp and XenDesktop published resources.

The feature can be configured and managed with the Unified Gateway wizard in the NetScaler configuration utility. [#00552862, #0438356, #0519875, #0519875]

SmartControl

SmartControl allows policy-based management decisions for ICA connections through the VPN. SmartControl policies can be applied at the session level to control user’s ICA environment and to further manage ICA connections with SmartGroup sorting decisions.

Portal Customization and EULA

The Portal Customization options have been expanded to allow end-to-end customization of the VPN user portal. Administrators can apply themes to their VPN portal design or use themes as a foundation for their own customization or branding. An option to present VPN users an End User License Agreement (EULA) has also been added to the portal design. Portal themes and EULAs can be bound to a VPN virtual server or specified as global VPN parameters.

New and Updated Gateway Clients

NetScaler Gateway release 11.0 adds new plug-in clients for the following operating systems:

  • Android 4.1 or later
  • iOS 7 or later
  • Linux (Ubuntu 12.04 and 14.04)

Each of these clients provides full SSL VPN tunnel functionality through NetScaler Gateway and supports all authentication methods available in NetScaler Gateway 11.

Additionally, the Mac OS and Windows plug-ins have been refreshed and updated for the 11.0 release, including OS X 10.10 (Yosemite) support for the Mac OS X plug-in.

Plug-in Version Decoupling

The NetScaler Gateway client plug-ins are no longer coupled to the Citrix NetScaler Gateway 11 release versioning. Settings for version requirement per client OS type can be configured globally and within session policies.

Plug-in Icon Decoupling from Citrix Receiver

The desktop client plug-ins icons can now be configured to operate independently from Native Citrix Receiver clients. Settings to manage Receiver integration with the NetScaler Gateway Plug-ins can be configured globally and within session policies.

Disabling Automatic Update for the Windows Gateway Client and EPA Plug-ins

This enhancement adds an option in client Endpoint Analysis (EPA) to prevent automatic client updates by disabling the “EnableAutoUpdate” registry key.

Striped Cluster for Citrix NetScaler Gateway 11 in ICA Proxy Mode

This feature allows administrators to deploy NetScaler Gateway with XenApp and XenDesktop in a striped cluster configuration. Administrators can use existing Gateway configurations and scale seamlessly in a cluster deployment without having to restrict the VPN configuration to a single node.

Note that this feature is limited to ICA Proxy basic-mode virtual servers and does not support SmartAccess.

Clientless VPN support for Outlook Web Access 2013 and SharePoint 2013

NetScaler Gateway has improved support for access to Outlook Web Access 2013 and SharePoint 2013 through Clientless VPN (CVPN) sessions.

WebFront

WebFront is an alternative integration point for XenApp and XenDesktop deployments served by StoreFront. Resident on NetScaler, WebFront uses caching and packet flow optimization in the distribution of user stores. These techniques improve end user experience for Receiver for Web users and speed up single sign-on for native Receiver users. In the NetScaler configuration utility, the WebFront feature is on the Configuration tab at System > WebFront.

ICA Proxy Connection Termination after Session Time Out

Automatic session timeout can be enabled for ICA connections as a VPN parameter. Enabling this parameter forces active ICA connections to time out when a VPN session closes.

Support for Common Gateway Protocol (CGP) over WebSockets

NetScaler Gateway virtual servers have improved intelligence for handling CGP traffic destined for the common CGP port, 2598, over WebSockets. This enhancement allows Receiver for HTML5 user sessions through NetScaler Gateway to support Session Reliability.

SPNEGO Encapsulation for Kerberos Tickets

NetScaler now uses SPNEGO encapsulation on Kerberos tickets that are sent to back-end web applications and servers.

Cross Domain Kerberos Constrained Delegation 

This enhancement adds support for cross-domain Kerberos constrained delegation when both the user and the service realm have a two-way shortcut trust. That is, if the user and service belong to different domains/realms, constrained delegation fails. However, if a user logs on with a user name and password, Kerberos Single Sign-On works for cross-domain access, because the NetScaler Gateway appliance does Kerberos impersonation with the user password. NetScaler Gateway currently does not otherwise support cross-domain constrained delegation.

 

Source

Download Citrix Netscaler Gateway 11 build 55.20 here (requires MyCitrix ID)

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

Citrix Receiver 13 for Linux

Written by Thomas Poppelgaard. Posted in Citrix, HDX, HDX 3D Pro, Linux, Netscaler, Receiver, StoreFront Services, VDI-in-a-box, XenDesktop

Citrix have released Receiver 13 for Linux. This release is an amazine Receiver from Citrix that features lots of new powerfull features. Thin client vendors like Dell Wyse is going to be very happy about this release cause the user experience is truely amazing with this new client.

Check out this cool video Vipin Borkar from Citrix have created, where you see the powerfull new features

http://www.citrix.com/tv/#videos/9555

Whats new in Receiver 13 for Linux

  • Support for XenDesktop 7 features – Receiver supports many of the new features and enhancements in XenDesktop 7, including Windows Media client-side content fetching, HDX 3D Pro, HDX RealTime webcam compression, Server-rendered Rich Graphics, and IPv6 support.
    Note: Link-local network addresses are not supported in IPv6 environments. You must have at least one global or unique-local address assigned to your network interface.
  • VDI-in-a-Box support – You can use Receiver to connect to virtual desktops created with Citrix VDI-in-a-Box.
  • Self-service UI – A new graphical user interface (UI), like that in other Citrix Receivers, replaces the configuration manager, wfcmgr. After they are set up with an account, users can subscribe to desktops and applications, and then start them.
  • Deprecated and removed utilities – The pnabrowse command-line utility is deprecated in favor of the new storebrowse command-line utility. The icabrowse and wfcmgr utilities have been removed.
  • StoreFront support – You can now connect to StoreFront stores as well as Citrix XenApp sites (also known as Program Neighborhood Agent sites).
  • UDP audio support – Most audio features are transported using the ICA stream and are secured in the same way as other ICA traffic. User Datagram Protocol (UDP) Audio uses a separate, unsecured, transport mechanism, but is more consistent when the network is busy. UDP Audio is primarily designed for Voice over IP (VoIP) connections and requires that audio traffic is of medium quality (that is Speex wideband) and unencrypted.
  • Packaging – An armhf (hard float) Debian package and tarball are now included in the download packages. In addition, the Debian package for Intel systems uses multiarch (a Debian feature) for installations on 32- and 64-bit systems. 32-bit binaries are also available in RPM packages.
  • System Flow Control – Video display has been enhanced on low-performance user devices that connect to high-performance servers. In such setups, System Flow Control prevents sessions becoming uncontrollable and unusable.
  • Localization – Receiver is now available in German, Spanish, French, Japanese, and Simplified Chinese.
  • Keyboard improvements – You can now specify which local key combination (Ctrl+Alt+End or Ctrl+Alt+Enter) generates the Ctrl+Alt+Delete combination on a remote Windows desktop. In addition, a new option supports Croatian keyboard layouts.
  • Deferred XSync – While one frame is still on screen, Receiver can now decode tiles for the next frame. This provides a performance improvement compared with previous releases, in which Receiver waited for a frame to finish being displayed before decoding the next frame.
  • Audio and webcam playback improvements – Various changes are implemented that conserve CPU cycles and reduce latency.
  • Audio settings – Several new audio settings are now available in module.ini.

Source

Download Citrix Receiver 13 for Linux here

Vipin Borkar CTX blogpost about Reciever 13 for Linux new features

Citrix VDI-in-a-box 5.4

Written by Thomas Poppelgaard. Posted in Citrix, HDX, HTML5, Hyper-V, Microsoft, Netscaler, Receiver, Server 2012R2, VDI-in-a-box, VMware, vSphere, Windows 8.1, XenServer

Citrix have released a new version of Citrix VDI-in-a-box 5.4

VDI-in-a-Box 5.4 provides support for Windows 8.1 virtual desktops and Windows Server 2012 R2 Hyper-V. It also includes a range of enhancements that increase VDI-in-a-Box’s flexibility and a range of power tools for administrators. If you want to migrate your VDI-in-a-box platform to a XenDesktop 7 platform, there is now a wizard included in VDI-in-a-box 5.4, that lets you easy migrate your images, template configuration and user assignments.

Note !!! – Citrix VDI-in-a-Box does not support HDX3D Pro.

Whats new in Citrix VDI-in-a-box 5.4

  • Windows 8.1 virtual desktops
    Create Windows 8.1 desktops and run them on any supported hypervisor.
  • Windows Server 2012 R2
    Windows Server 2012 R2 Hyper V is now supported. You can also use Windows Server 2012 R2 desktops with HDX connections. Grids running on Windows Server 2012 R2 Hyper V and Windows Server 2012 Hyper V can use shared storage.
  • VMware vSphere ESXi 5.5
    VMware vSphere ESXi 5.5 Hypervisor is now supported.
  • Built-in HTML5 device support
    Use devices running HTML5-capable browsers to access VDI-in-a-Box desktops without StoreFront. This allows devices such as Chromebook to access VDI-in-a-Box desktops without additional server components.
  • Multiple computer domains
    If you use Active Directory as a user database, you can place the computer objects for VDI-in-a-Box desktops in more than one domain. This allows you to separate your users into different domains and meet regulatory or compliance requirements in your organization. For more information, see Use VDI-in-a-Box with Active Directory.
  • StoreFront smart card support
    Users can log on using smart cards when accessing desktops through StoreFront from non-domain-joined Windows devices.
  • SSL certificate multiple host names
    You can specify multiple host names on a single SSL certificate, which is more cost-effective than using a wildcard certificate. This enables you to specify the grid IP FQDN as the common name and add subject alternate names for the FQDNs of the individual vdiManagers. For more information, see Manage SSL certificates.
  • Install existing SSL certificates
    Install existing SSL certificates through the Manage SSL Certificate wizard. For more information, see Manage SSL certificates.
  • Follow-me desktops
    Time-share user devices among multiple user names where each user name is shared by a group of users: in a classroom or lab environment, for example. In previous releases of VDI-in-a-Box this was achieved through setting your entire grid to generic user mode. You now have the flexibility to support shared user accounts and dedicated user accounts in the same VDI-in-a-Box grid just by clearing a check box on an individual template. For more information, see Configure shared user accounts.
    Generic user mode is now reserved solely for avoiding user name verification after the user logs on to a desktop. For more information, see Configure generic user accounts.
  • Image save as
    You can save an existing image under a new name. This gives you the flexibility to easily create backups, or experiment with different image settings.
    If you need to pilot a new version of an image for a pooled desktop, you can update an existing image, save it with a different name, then edit an existing template to use this image. When testing is complete it’s easy to either continue using the updated image, move back to the previous version, or create subsequent versions if you need to continue testing.
    For more information, see Manage images.
  • Change images for pooled-desktop templates
    You can edit an existing template for pooled desktops and base it on a different image, provided the image is compatible with the template properties and existing desktops. This enables you to test new versions of images, as described above. For more information, see Manage templates.
  • Remote Assistance support
    Launch Windows Remote Assistance from the vdiManager console, enabling administrators or support staff to share users’ screens and shadow their sessions. For more information, see Manage user sessions.
  • Wizard-driven migration to Citrix XenDesktop
    If you need to move your entire VDI-in-a-Box deployment to XenDesktop, this easy-to-use wizard exports your images and generates PowerShell scripts that you can run to migrate all template configurations and user assignments to a XenDesktop deployment. For more information see http://support.citrix.com/article/CTX136081.

Source

Download Citrix VDI-in-a-box 5.4 here (Require MyCitrix ID)

Citrix XenDesktop 7.1

Written by Thomas Poppelgaard. Posted in 8.1, Citrix, GRID, HDX, HDX 3D Pro, Microsoft, Netscaler, NVIDIA, Provisioning, Receiver, Server 2012R2, vGPU, vSphere, Windows 7, Windows 8, Windows 8.1, Windows Server 2008R2, Windows Server 2012, XenDesktop, XenServer

Citrix XenDesktop 7.1 is now finally released and vGPU is now in the product and build in with MCS, very very cool. You can configure GPU pass-through with any GPU card or vGPU profiles with NVIDIA GRID, the brilliant thing about this its now build in to the product, you only have to choose a GPU profile and XenDesktop takes care of the High Availability with XenServer and find the resources that free and connects the GPU to the Virtual Machine. Microsoft have just released Windows 8.1 and Server 2012R2 and in this release of Citrix XenDesktop 7.1, Citrix are supporting Microsoft newest Operating System Platforms.

One of the things that have been fixed in the XenDesktop 7.1 Virtual Delivery Agent is following:

  • With HDX 3D Pro enabled, the NVIDIA card might not support certain resolutions. This enhancement introduces support of up to 2560×1600 pixel resolutions.
  • With HDX 3D Pro enabled, client connections to a XenDesktop 5.6 VDA do not support resolutions beyond 1900×1200 pixels. This enhancement introduces support for a wide range of additional resolution ratios, including:
    • 1920×1200
    • 2048×1152
    • 2560×1440
    • 2560×1600

What’s new in XenDesktop 7.1

  • GPU — The Graphical Processing Unit (GPU) capabilities feature provides graphics virtualization, offering a superior experience for users who use graphic-intensive applications and often manipulate 3-D models. The GPU feature also can improve the graphics experience for a large number of users. Administrators can evaluate workflows for the creation of GPU-capable connections and machine catalogs created with an MCS-provisioned master image. If problems are encountered, then Administrators may need to manually create the machines.

When you install Citrix XenDesktop 7.1 on the Controller, you can now choose a GPU type and group which its getting from XenServer.

 

vgpu_option_in_XenServer_-_build_XD

If you have NVIDIA GRID with XenServer, XenDesktop 7.1 takes care of creating a GPU type attached to the GPU group.

vgpu_option_in_XenServer_done_-_build_XD

in above example I am choosing a vGPU type: K140Q. It have 960MB video RAM per VM)

If you have 1 GRID K1 card and choose a K140Q type, you can have maximum 16 virtual machines assigned to this card. If you have 2 GRID K1 and choose  K140Q type, then you can have 32 virtual machines assigned to the GROUP K1, and XenDesktop 7.1/XenServer vGPU takes care of the HA of GPU assignment.

Look at below chart to get an understanding of which vGPU types you can choose in XenDesktop 7.1 with NVIDIA GRID K1 & K2.

Read my blogpost about vGPU profiles

vgpu-profile

The above numbers are from NVIDIA but the vGPU types Citrix have defined in XenDesktop 7.1 are following:

for NVIDIA GRID K1 vGPU options:

  • GRID K100 (256B video RAM per VM)
  • GRID K140Q (960MB video RAM per VM)
  • Passthrough – GK107 GL GRID K1

for NVIDIA GRID K2 vGPU options:

  • GRID K260Q (1920MB video RAM per VM)
  • GRID K240Q (960MB video RAM per VM)
  • GRID K200 (256MB video RAM per VM)
  • Passthrough – GK104GL

 

  • Windows Server 2012 R2 and Windows 8.1 support — Deliver a high-definition user experience on Windows 8.1 virtual desktops and physical machines. HDX 3D Pro has also been upgraded to support Windows 8.1.

vda-platform-support

 

Upgrade XenDesktop 7 components to 7.1

When you run the installer AutoSelect, the wizard checks whether certain Site components (such as the Delivery Controllers, Director, and VDAs), need to be upgraded. If you opt not to upgrade some components during this process, when you run Studio, it performs a component check and notifies you when components need to be upgraded. You cannot proceed to manage your Site until you upgrade these components.

Upgrade Site with components deployed on different machines

The following figure shows the high-level processes involved when upgrading a XenDesktop 7 to XenDesktop 7.1 in which Studio components are deployed on different machines.

Perform the upgrade procedures in the following order.

Check the licenses

Make sure that your Subscription Advantage date for licenses is no earlier than 2013.0522.

Upgrade StoreFront

If StoreFront is deployed on a separate machine, follow the steps described in Upgrade core components from eDocs

Upgrade Director

If Director is deployed on a separate machine, follow the steps described in Upgrade core components from eDocs

Upgrade Provisioning Services

If you are using Provisioning Services, follow the procedures described in Upgrading Provisioning Services from eDocs

Upgrade the Virtual Delivery Agent

For Remote PC Access deployments, Citrix recommends that you upgrade a VDA in a remote PC using a command-line method. For detailed information, see Install using the command line.

  1. Log on to the server using a local administrator account and run the installer by inserting the media or mounting the ISO drive for this release, and double-clickingAutoSelect.
  2. On the Welcome page, click Start. The wizard detects what components need to be upgraded and displays the Upgrade options page, activating the components you can upgrade.
  3. On the Upgrade options page, select:
    • Virtual Delivery Agent for Windows Desktop OS for Desktop OS, and earlier XenDesktop versions
    • Virtual Delivery Agent for Windows Server OS for Server OS
  4. On the Firewall page review the default ports and configure firewall rules.
  5. On the Summary review the prerequisites to be installed and the components to be upgraded then click Upgrade.
  6. On the Finish Upgrade page one of the following messages appears upon completion:
    • Success — Upgrade successful appears when the upgrade completes without errors.
    • Failed — The Upgrade failed appears with a list of failed components. Click Why did this fail to review what you must do to fix the problem. Other components that installed successfully are retained; you do not need to reinstall them.
  7. Click Finish to complete the upgrade.

Upgrade Delivery Controllers

Citrix recommends that you upgrade Delivery Controllers as follows:
  1. Upgrade half of your Site’s Delivery Controllers.
  2. Use the upgraded version of Studio to perform the Site upgrade as described in Upgrade core components.
  3. Upgrade your remaining Delivery Controllers.

Upgrade Databases using Studio

Use Studio to upgrade the Database.

Automatically upgrade Databases

  1. Start Studio. The wizard detects what components need to be upgraded and displays the Mandatory upgrade page.
  2. Select Start the Site upgrade automatically.
  3. At the prompt, select I am ready to upgrade.The wizard displays the upgrade progress. After the upgrade completes, the wizard performs tests. This takes several minutes.
  4. At the Site Upgrade Complete window, you can optionally view a data migration report and then click Finish.
  5. At the Upgrade successful page, click Finish upgrade and return to the Site overview.

Manually upgrade Databases

To minimize Site down time when performing a manual upgrade, it is important that the XenDesktop Administrator closely coordinates with the Database Administrator. This process requires that you run a script that temporarily disables Xendesktop Services while the manual upgrade scripts are run by the Database Administrator using a preferred tool (for example, SQL Server Management Studio). Ideally, immediately after these scripts complete, the XenDesktop Administrator should enable XenDesktop Services and complete the upgrade using Studio.

Manual upgrade requires:

  • Backing up the databases
  • Running the generated scripts in the following order:
  1. DisableServices.ps1 — PowerShell script to be run by the XenDesktop administrator on an XenDesktop Controller.
  2. UpgradeSiteDatabase.sql — SQL script run where the Site databases resides
  3. UpgradeMonitorDatabase.sql — SQL script run where the Monitor databases resides.
  4. UpgradeLoggingDatabase.sql — SQL script run where the Logging database resides.
    Note: You should only run this script if the Logging database changes. For example, run it after applying a hotfix.
  5. EnableServices.ps1 — PowerShell script to be run by the XenDesktop administrator on an XenDesktop Controller.

To upgrade manually

  1. Start Studio. The wizard detects what components need to be upgraded and displays the Mandatory upgrade page.
  2. Select Manually upgrade this site.
  3. The wizard checks for License Server compatibility. Make sure your License Server and license files are compatible with XenDesktop 7.1. Select the confirmation check box and click Continue.
  4. The wizard prompts you to backup the Database. When you have done so, select the confirmation check box and click Continue.
    • The wizard generates the manual upgrade scripts that you must run and displays them in a window
    • The Mandatory Upgrade page changes to display a checklist of the manual upgrade steps
  5. Make sure you have completed the checklist tasks and click Finish upgrade and return to Common Tasks.

Upgrade core components

The installer automatically upgrades core components such as Delivery Controllers, Studio, and Director if they were previously installed.

  1. Log on to the server using a local administrator account and run the installer by inserting the media or mounting the ISO drive for this release, and double-clickingAutoSelect.
  2. On the Welcome page, click Start. The wizard detects what components need to be upgraded and displays the Upgrade options page, activating the components you can upgrade.
  3. Click Delivery Controller.
  4. Accept the license agreement.
  5. Review the upgrade steps, click I’m ready to continue and click Next.
  6. On the Core Components page review the components available for upgrade.
  7. On the Firewall page review the default ports and configure firewall rules.
  8. On the Upgrade page review the prerequisites to be installed and the components to be upgraded and then click Upgrade.
  9. On the Finish Upgrade page one of the following messages appears upon completion:
    • Success — Upgrade successful appears when the upgrade completes without errors.
    • Failed — The Upgrade failed appears with a list of failed components. Click Why did this fail to review what you must do to fix the problem. Other components that installed successfully are retained; you do not need to reinstall them.
  10. Click Finish to complete the upgrade.

Upgrade a Site with components deployed on the same machine

The following figure shows the high-level processes involved when upgrading a Site in which all components are deployed on the same machine.

Upgrade XD7 on a single machinePerform the upgrade procedures in the following order:

  1. Make sure that your Subscription Advantage date for licenses is no earlier than 2013.0522.
  2. Back up the Controller databases.
  3. Optionally back up templates and upgrade Hypervisor.
  4. Upgrade PVS servers and agents as described in Upgrade Provisioning Services from eDocs
  5. Upgrade the core components as described in Upgrade core components from eDocs
  6. Upgrade Virtual Desktop Agents as described in Upgrade the Virtual Delivery Agent from eDocs
  7. Upgrade the Database using Studio as described in Upgrade Databases using Studio from eDocs
  8. Upgrade the remaining Delivery Controllers.

Post upgrade processes

After the upgrade and data migration is complete, you can run environment and configuration tests to make sure that the Site is in functional order.

To test the upgraded site, select Test Site n the Site Configuration pane of the Studio Common Tasks page.

Source

If you want to upgrade your current Citrix XenDesktop 7 environment to XenDesktop 7.1. environment look here

fixes in XenDesktop 7.1 – Virtual Delivery Agent

fixes in XenDesktop 7.1 – Controller 

Download Citrix XenDesktop 7.1 here (Require MyCitrix ID)

Recent Comments

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.

Olivier

|

Thank you! Thats the solution i needed.