Product Documentation

What's new

Feb 26, 2018

What's new in 4.11

Local launch of the application in a double-hop scenario using vPrefer

In earlier releases, you could specify that the instance of an app installed on the VDA (referred to as local instance in this document) must be launched in preference to the published application by setting the KEYWORDS:prefer=”application” attribute in Citrix Studio. 

Starting with this release, in a double-hop scenario (where Citrix Receiver is running on the VDA that is hosting your session), you can now control whether Receiver launches the local instance of an application installed on the VDA (if available as a local app) in preference to launching a hosted instance of the application. 

vPrefer is available on StoreFront Version 3.14 and XenApp 7.17 and later.

When you launch the application, Citrix Receiver for Windows reads the resource data present on the StoreFront server and applies the settings based on the vprefer flag at the time of enumeration. Citrix Receiver for Windows searches for the installation path of the application in the Windows registry on the VDA and, if present, launches the local instance of the application. Otherwise, a hosted instance of the application is launched.
If you launch an application that is not installed on the VDA, the hosted application is launched. For more information on how the local launch is handled on StoreFront, see Control of local application launch on published desktops in StoreFront documentation.

If you do not want the local instance of the application to be launched on the VDA, set the LocalLaunchDisabled to True using the PowerShell on the Delivery Controller. 

This feature helps to launch applications faster, thereby providing a better user experience. You can configure it by using the Group Policy Object (GPO) administrative template. By default, vPrefer is enabled only in a double-hop scenario.

For more information on configuring vPrefer, see Configuring vPrefer launch using the GPO administrative template.

Show or hide the remote language bar

Starting with this release, you can choose to show or hide the remote language bar in an application session using the graphical user interface. The language bar displays the preferred input language in a session.  In earlier releases, you could change this setting using only the registry keys on the VDA. Starting with Citrix Receiver for Windows Version 4.11, you can change the settings using the Advanced Preferences dialog in Citrix Receiver for Windows. The language bar appears in a session by default.

For more information, see Language bar.

Note

This feature is available in sessions running on VDA 7.17 and later.

Support for Visual Studio 2017

Starting with this release, Citrix Receiver for Windows is built with Visual Studio 2017 Compiler.

Note

If you are using a custom Virtual Driver with earlier versions of Virtual Channel SDK, you must recompile it using Visual Studio 2017 and the latest version of Virtual Channel SDK.

Support for Lossless compression codec (MDRLE)

A higher compression ratio MDRLE encoder is added to Thinwire. The MDRLE codec consumes less bandwidth in typical desktop sessions than the 2DRLE codec. If the codec is supported on the server and client sides, it's used instead of 2DRLE. For more information, see the Thinwire article.

In Citrix Receiver for Windows 4.10 and earlier, there were three Thinwire bitmap encoding modes used for server OS and desktop OS VDA graphics remoting:

  • Full-screen H.264
  • Thinwire Plus
  • Thinwire Plus with selective H.264

In a typical desktop session, most of the imagery is simple graphics or text regions. When any of the three bitmap encoding modes listed are used, Thinwire selects these areas for lossless encoding using the 2DRLE codec. Citrix Receiver for Windows decodes these elements using the Citrix Receiver-side 2DRLE decoder for session display.

In Citrix Receiver for Windows 4.11, a higher compression ratio MDRLE encoder is supported that consumes less bandwidth in typical desktop sessions than the 2DRLE codec.

Lower bandwidth usually means improved session interactivity (especially on shared or constrained links) and reduced costs. 

No configuration is required for the MDRLE codec. If Citrix Receiver supports MDRLE decoding, the VDA uses the VDA MDRLE encoding and the Citrix Receiver MDRLE decoding. If Citrix Receiver doesn't support MDRLE decoding, the VDA automatically falls back to 2DRLE encoding.

MDRLE Requirements:

  • XenApp and XenDesktop minimum version 7.17 VDAs.

Browser content redirection

Browser content redirection redirects the contents of a web browser to a client device and creates a corresponding browser embedded within Citrix Receiver. This feature offloads network usage, page processing, and graphics rendering to the endpoint. Doing so improves the user experience when browsing demanding web pages, especially web pages that incorporate HTML5 or Flash video.

For more information see Browser content redirection in XenApp and XenDesktop documentation.