Product Documentation

Configuring Citrix Receiver for Chrome

Nov 01, 2017

To enable Citrix Receiver for Chrome users to access resources hosted on XenDesktop and XenApp, you must create a StoreFront store. You must also enable WebSocket connections on NetScaler Gateway, XenApp, and XenDesktop, as required. 

Configuring Selective H.264

Configuring Selective H.264 using the web.config in StoreFront

To change the Selective H.264 configuration using the web.config file:

  1. Open the web.config file for Citrix Receiver for Website.
    This file is typically located in the C:\inetpub\wwwroot\Citrix\<Storename>Web folder, where Storename is the name specified for the store when it was created.
  2. Locate the chromeAppPreferences field and set its value with the configuration as a JSON string; for example:
    chromeAppPreferences='{"graphics":{" selectiveH264":false}}

Configuring Selective H.264 using the configuration.js file

The configuration.js file is located in the ChromeApp root folder. Edit this file to make changes to Citrix Receiver for Chrome.

 By default, selective H.264 is set to true.

Note: Citrix recommends that you back up the configuration.js file before making any changes to it.

Note: Citrix recommends using this method only when Citrix Receiver for Chrome is repackaged for users.

Note: Administrator -level credentials are required to edit the configuration.js file; after editing the file, repackage the app to make additional modifications to toolbar elements.

To disable the Selective H.264 configuration using the configuration.js file:

1. Open the configuration.js file and set the selectiveH264 attribute to false.
For example:  

localized image

Configuring multi-monitor display

Multi-monitor display can be configured in two ways.

By default, the multi-monitor feature is set to enabled.

Note

  • If you are using Citrix Receiver for Chrome running on XenApp 6.5, set the shadowing policy to Disabled to use the multi-monitor feature.
  • In a desktop session, when the window is set to full screen, the Display Resolution option in Preferences is deactivated.
  • UI dialogs and toolbars appear only on primary monitor. However, USB and smart card authentication dialogs span across monitors.

To configure multi-monitor display using the Chrome browser:

  1. Launch a web browser and enter the following command:
    chrome://flags
  2. From the list of flags, search for UnifiedDesktopMode and set it to Enabled.

To configure multi-monitor display using Google Admin Policy

  1. Log on to the Google Admin Console.
  2. Go to Device management > Chrome Management > User Settings.
  3. Set the Unified Desktop policy to Make Unified Desktop mode available to user.
  4. Click Save.

Multi-monitor display is available for both desktops and applications.

When using multi-monitor display, the desktop session can span across multiple monitors in two ways:

  1. Windowed mode: The desktop session displays in single monitor mode.
  2. Full-screen mode: When the desktop session is switched to full-screen mode, the session displays in multi-monitor mode.

In an application session, when two monitors are connected and the UnifiedDesktopMode is set to Enabled as described above, the session automatically displays in a multi-monitor mode.

Note

When unified desktop mode is enabled, the Citrix Receiver for Chrome home page appears only on the primary monitor.

HDX SDK for Chrome (Experimental API)

Procedure to consume the API in the third-party Chrome app

  1. Install the latest version of Citrix Receiver for Chrome. See Citrix downloads page for details.
  2. Whitelist the third-party Chrome app by adding the policy file for Citrix Receiver for Chrome using Chrome management settings.
    For more details, see Manage Chrome Apps by organizational unit on Google support. 
    The Sample policy.txt file to whitelist the third-party Chrome app is as below:
command Copy

{

                "settings": {

                                "Value": {

                                                "settings_version": "1.0",

                                                "store_settings": {

                                                                "externalApps": [“<3rdParty_App1_ExtnID>”,“<3rdParty_App2_ExtnID>”]

                                                }

                                }

                }

}

Note

<3rdParty_App1_ExtnID> is used as an example for the name of externalApps and can send messages to Citrix Receiver for Chrome. Get your appid from the chrome://extensions site.

3. Launch the application or desktop session in Citrix Receiver for Chrome by following the steps below:

  • Get the receiverId

    var receiverId = " haiffjcadagjlijoggckpgfnoeiflnem "; // 

Note: In this example, receiverId indicates the store version of Citrix Receiver for Chrome. If you are using a repackaged version of Citrix Receiver for Chrome, use the appropriate receiverId.

  • Convert ICA data from INI to JSON format.

    Note: Typically, the ICA file is retrieved from StoreFront as an INI file. Use the following helper function to convert a ICA INI file into JSON.

//Helper function to convert ica in INI format to JSON
function convertICA_INI_TO_JSON(data){
var keyVals = {};
if (data) {
var dataArr;
if(data.indexOf('\r')==-1){
dataArr = data.split('\n');
}else{
dataArr = data.split('\r\n');
}
for (var i = 0; i < dataArr.length; i++) {
var nameValue = dataArr[i].split('=', 2);
if (nameValue.length === 2) {
keyVals[nameValue[0]] = nameValue[1];
}
// This is required as LaunchReference will contain '=' as well. The above split('=',2) will not provide
// the complete LaunchReference. Ideally, something like the following should be used generically as well
// because there can be other variables that use the '=' character as part of the value.
if (nameValue[0] === "LaunchReference") {
var index = dataArr[i].indexOf('=');
var value = dataArr[i].substr(index + 1);
keyVals[nameValue[0]] = value;
}
}
console.log(keyVals);//to remove
return keyVals;
}
return null;
}

  • Send an ICA message from the third-party Chrome app to Citrix Receiver for Chrome.

    var icaFileJson = {...}; // ICA file passed as JSON key value pairs.
    var message = {
    "method" : "launchSession",
    "icaData" : icaJSON
    };
    chrome.runtime.sendMessage(receiverId, message, function(launchStatus) {
    if (launchStatus.success) {
    // handle success.
    console.log("Session launch was attempted successfully");
    } else {
    // handle errors.
    console.log("error during session launch: ", launchStatus.message);
    }
    });

Configuring Citrix Receiver for Chrome

This section includes information about:

  • Google Admin Policy
  • Web.config in StoreFront
  • default.ica
  • configuration.js

Configuring Citrix Receiver for Chrome using Google Admin Policy

Before Version 2.1, only store/beacon related configurations could be pushed through Google Admin Policy. For additional information about this policy, see the Knowledge Center article CTX141844.

With Citrix Receiver for Chrome Version 2.1, other Chrome configurations can also be pushed through the Google Admin Policy.

Note

Citrix recommends using this method only when Citrix Receiver for Chrome is repackaged for users.

For more information, see the sample policy text below:

command Copy

{

                  "settings": {

                                    "Value": {

                                                      "settings_version": "1.0",

                                                      "store_settings": {

                                                                        "name": "RTST",

                                                                        "gateways": [

                                                                                    {

                                                                                                 "url":“https://yourcompany.gateway.com",

                                                                                                  "is_default": true

                                                                                     }

                                                                        ],

                                                                        "beacons": {

                                                                                          "internal": [

                                                                                                     {

                                                                                                                "url":

                                 “http://yourcompany.internalwebsite.net"

                                                                                                            }

                                                                                          ],

                                                                                          "external": [

                                                                                                            {

                                                                                                               "url":

                                 “http://www.yourcompany.externalwebsite.com"

                                                                                                            }

                                                                                          ]

                                                                        },

                                                                        "rf_web": {

                                                                                          "url": “http://yourcompany.storefrontstoreweb.net”

                                                                        }

                                                      },

                                                      "engine_settings":{

                                                                        "ui":{

                                                                                          "sessionsize": {

                                                                                                            "windowstate": "fullscreen",

                                                                                                            "available" : {

                                                                                                                              "default" : "Fit_To_Window",

                                                                                                                              "values" : ["Fit_To_Window", "Use_Device_Pixel_Ratio","1280x800","1440x900","1600x1200"]                 

                                                                                                            }

                                                                                          },

                                                                                          "toolbar": {

                                                                                                            "menubar":true,

                                                                                                            "usb": true,

                                                                                                            "fileTransfer":true,

                                                                                                            "about":true,

                                                                                                            "lock":true,

                                                                                                            "disconnect":true,

                                                                                                            "logoff":true,

                                                                                                            "fullscreen":true,

                                                                                                            "multitouch":true,

                                                                                                            "preferences":true,

                                                                                                            "gestureGuide":true

                                                                                          }

                                                                        },

“features”:{

 

“com”:{

                                                                                                                “portname” :”COM5”

                                                                                                },

                                                                                          "graphics" : {

                                                                        "features" : {

                                                                                          "graphics" : {

                                                                                                            "jpegSupport" : true,

                                                                                                            "h264Support" : {

                                                                                                                              "enabled" : true,

                                                                                                                              "losslessOverlays" : true,

                                                                                                                              "dirtyRegions" : true,

                                                                                                                              "yuv444Support" : false

                                                                                                            }

                                                                                          },

                                                                                          "filetransfer" : {

                                                                                                            "allowupload" : true,

                                                                                                            "allowdownload" : true,

                                                                                                            "maxuploadsize"               : 2147483647,

                                                                                                            "maxdownloadsize" : 2147483647

                                                                                          }

                                                                        },

                                                                        "nacl" : {

                                                                                          "supportNacl" : true,

                                                                                          "graphics": {

                                                                                                            "enable": true

                                                                                          },

                                                                                          "video": {

                                                                                                            "enable": true

                                                                                          },

                                                                                          "audio": {

                                                                                                            "enable": true

                                                                                          }

                                                                        }

                                                      }

                                    }

                  }

 }

Configuring Receiver for Chrome using Web.config in StoreFront

To change the configuration using the Web.config file:

  1. Open the web.config file for the Citrix Receiver for Website. This file is typically located in C:\inetpub\wwwroot\Citrix\storenameWeb, where storename is the name specified for the store when it was created.
  2. Locate the chromeAppPreferences field and set its value with the configuration as a JSON string.
For example:
chromeAppPreferences = '{"ui": {"toolbar": {"menubar": false}}}'

Note

Citrix recommends that you use the web.config file method for configuration purposes only when a store version of Citrix Receiver for Chrome is being used.

Configuring Receiver for Chrome using the default.ica file

To change the configuration using the default.ica file:

  1. Open the default.ica file typically located at C:\inetpub\wwwroot\Citrix\<site name>\conf\default.ica for Web interface customers, where sitename is the name specified for the site when it was created.
    In case of Storefront customers, default.ica file is typically located at C:\inetpub\wwwroot\Citrix\<Storename>\App_Data\default.ica, where storename is the name specified for the store when it was created.
  2. Add a new key at the end of the file, chromeAppPreferences with its value set to configuration as the JSON object.
For example:
chromeAppPreferences={"ui":{"toolbar": {"menubar": false}}}

Note

Citrix recommends that you use the default.ica file method for configuration purposes only for Web Interface users.

A sample default.ica file might resemble:

;

; ICA Override File

;

; Add ICA file settings that you want to be sent to client devices

; to this file.  Settings contained in this file override any

; settings generated by Delivery Services.

;

 

[WFClient]

Version=2

RemoveICAFile=yes

ProxyTimeout=30000

ProxyFavorIEConnectionSetting=Yes

ProxyUseFQDN=Off

 

[ApplicationServers]

Application=

 

[Application]

TransportDriver=TCP/IP

DoNotUseDefaultCSL=On

BrowserProtocol=HTTPonTCP

LocHttpBrowserAddress=!

WinStationDriver=ICA 3.0

ProxyTimeout=30000

AutologonAllowed=ON

;EncryptionLevelSession=RC5 (128 bit)

 

[EncRC5-0]

DriverNameWin16=pdc0w.dll

DriverNameWin32=pdc0n.dll

 

[EncRC5-40]

DriverNameWin16=pdc40w.dll

DriverNameWin32=pdc40n.dll

 

[EncRC5-56]

DriverNameWin16=pdc56w.dll

DriverNameWin32=pdc56n.dll

 

[EncRC5-128]

DriverNameWin16=pdc128w.dll

DriverNameWin32=pdc128n.dll

 

[Compress]

DriverNameWin16=pdcompw.dll

DriverNameWin32=pdcompn.dll

chromeAppPreferences={"ui" : {"toolbar" : { "menubar" : false}}}

Configuring Citrix Receiver for Chrome using the configuration.js file

The configuration.js file is located in the ChromeApp root folder. Access this file directly to make changes to Citrix Receiver for Chrome.

Note

  • Citrix recommends that you back up the configuration.js file before making any changes to it.
  • Administrator-level credentials are required to edit the configuration.js file; after editing the file, repackage the app to make additional modifications to toolbar elements.
  • In Kiosk mode, the toolbar is hidden by default. When editing the configuration.js file to enable the toolbar, ensure that Kiosk mode is disabled. Citrix recommends that you use one of the alternative methods (for example, the default.ica file) to enable the toolbar.

Enabling smart card authentication

Receiver for Chrome provides support for USB smart card readers with StoreFront. You can use smart cards for the following purposes:

  • Smart card logon authentication to Receiver for Chrome.
  • Smart card-aware published apps to access local smart card devices.
  • Applications such as Microsoft Word and Outlook that are launched in ICA sessions can access smart cards for signing documents and email.
Supported smart cards include:
  • PIV cards
  • common access cards
Prerequisites:
  • StoreFront versions 3.6 or later

Important

For smart card authentication to StoreFront 3.5 or earlier, users require a custom script to enable smart card authentication. Contact Citrix Support for details.

  • XenDesktop 7.6 or later
  • XenApp 6.5 or later

To configure smart card support on your Chrome device:

1.  Install the smart card connector application. Note that the smart card application is required for PCSC support on the Chrome device. This application reads the smart card using the USB interface. You can install this application from the Chrome website.

2.  Install the middleware application. Note that a middleware application (for example, Charismathics, or CACKey) is required because it serves as an interface that communicates with the smart card and other client certificates.

  • To install the Charismathics smart card extention or CACKey, see the instructions on the Chrome website.
  • For more information about middleware applications and smart card authentication, see the Google support site

3.  Configure smart card authentication using NetScaler Gateway. For more details, see Configuring Smart Card Authentication in NetScaler Gateway documentation.

Important

Mandatory client authentication is required when a session launches. To prevent this from occurring, see the instructions in the Third reduction (one PIN prompt) section in the NetScaler product documentation.

Smart card authentication support has the following limitations:

  • The smart card certificate is cached even after the smart card is removed from the Chrome device. This is a known issue that exists in Google Chrome. Restart the Chrome device to clear the cache.
  • When Receiver for Chrome is repackaged, administrators should get the appID whitelisted by Google to ensure that the smart card connector application passes through.
  • Only one smart card reader is supported at a time.

Configuring serial COM port redirection

To configure serial COM port redirection, enable the feature by applying XenApp/XenDesktop port redirection policy settings. For more information on port redirection, see Port redirection policy settings.

Note

By default, Receiver for Chrome maps COM5 as a preferred serial COM port for redirection.

After enabling serial COM port redirection policy settings in XenApp or XenDesktop, configure Citrix Receiver for Chrome using one of the following methods:

  • Google Admin Policy
  • Using the configuration.js file
  • Changing the default mapping by issuing a command in an active ICA session.
Using Google Admin Policy to configure COM port redirection
Use this method to redirect the serial COM port by editing the policy file.

Tip

Citrix recommends that you configure the COM port using the policy file only when Receiver for Chrome is repackaged.

Edit the Google Admin Policy by including the following:

command Copy

{

                "settings": {

                                "Value": {

                                                "settings_version": "1.0",

                                                "store_settings": {

                                                                "rf_web": {

                                                                                "url": "<http://YourStoreWebURL>"

                                                                }

                                                },

                                                "engine_settings":{

                                                                                "features" : {

                                                                                "com" : {

                                                                                                "portname" : "<COM4>", where COM4 indicates the port number that is set by the administrator.                                                                                }

                                                                }

                                                }

                                }

                }

 

}

Using the configuration.js file to configure COM port redirection

Use this method to redirect the serial COM port by editing the configuration.js file. Locate the portname field in the configuration.js file and edit the value by changing the port number.

For example:

"com" :{

"portname" : "COM4"

}

Note

Citrix recommends using the configuration.js file method to configure serial port redirection only when Receiver for Chrome is repackaged and republished from StoreFront.

Issuing a command in an ICA session to configure COM port redirection

Use this method to redirect the serial COM port by executing the following command in an active ICA session:

command Copy

net use COM4 : \\Client\COM5

Tip

In the example above, COM4 is the preferred serial port used for redirection.

Configuring Single Sign-on (SSON) with Google and Citrix using SAML authentication

To configure Single Sign-on:

  1. Set up the third-party Identity provider (IdP) for SAML authentication if it is not already configured (for example, ADFS 2.0). For more information, see Knowledge Center article CTX133919
  2. Setup Single Sign-on with Google Apps using SAML IdP; this enables users to leverage third-party identity to use Google apps instead of the Google Enterprise account. For more information, see Set up Single Sign-On (SSO) for Google Apps accounts using third-party identity providers on Google support.
  3. Configure Chrome devices to log on via SAML IdP.This enables users to log on to Chrome devices using a third-party identity provider. For more information, see Configure SAML Single Sign-On for Chrome devices on Google support.
  4. Configure NetScaler Gateway to log on via SAML IdP. This enables users to log on to NetScaler Gateway using a third-party identity provider. For more information, see Configuring SAML Authentication.
  5. Configure XenApp and XenDesktop for Federated Authentication to allow logons to XenApp and XenDesktop sessions using dynamically generated certificates after the SAML logon process instead of typing username/password combinations. For more information, see Federated Authentication.
  6. Install and configure SAML SSO for Chrome app extension on Chrome devices. For more information, see the Google website. This extension retrieves SAML cookies from the browser and provides them to Citrix Receiver. This extension must be configured with the following policy to allow Receiver to get SAML cookies.
command Copy

{

    "whitelist" : {

        "Value" : [

            {

            "appId" : "haiffjcadagjlijoggckpgfnoeiflnem",

            "domain" : "saml.yourcompany.com"

            }

        ]

     }

}

If you are repackaging Citrix Receiver for Chrome, change the appId accordingly. In addition, change the domain to your company's SAML IdP domain.

7.  Configure Receiver to use NetScaler Gateway configured for SAML logon. This enables users to use the NetScaler Gateway configured for SAML logon. For more information on Chrome configuration, see Knowledge Center article CTX141844.

Enabling Google Cloud printing and the Citrix Universal Print Driver

The Citrix PDF Universal Printer driver enables users to print documents opened with hosted applications or applications running on virtual desktops delivered by XenDesktop 7.6 and XenApp 7.6 or later. When a user selects the Citrix PDF Printer option, the driver converts the file to PDF and transfers the PDF to the local device. The PDF then opens in a new window for viewing and printing through Google Cloud Print.

Important

Local PDF printing is supported only on XenApp and XenDesktop 7.6 or later.

Requirements

To access the Citrix Receiver for Chrome download page, you need a MyCitrix account.

Download the Citrix PDF Printer from the Citrix Receiver for Chrome download page.

To enable users to print documents opened with hosted desktop and applications:

  1. Download the Citrix PDF Printer and install the Citrix PDF Universal Printer driver on each machine that delivers desktops or apps for Receiver for Chrome users. After installing the printer driver, restart the machine.
  2. In Citrix Studio, select the Policy node in the left pane and either create a new policy or edit an existing policy.

    For more information about configuring XenDesktop and XenApp policies, see Citrix policies.

  3. Set the Auto-create PDF Universal Printer policy setting to Enabled.

Enabling and disabling access to Google Drive

With Google drive support your users can open, edit, and save Windows file types from a Chrome device running Citrix Receiver. While running a Google Chrome device, your users can seamlessly use existing Windows-based applications (for example, Microsoft Word) and access the files residing on Google Drive

For example, if a user opens a file in Google Drive (for instance, a .DOC file attachment downloaded from Gmail), edits it, and saves it to Google Drive, the file can be accessed in a XenApp hosted application. The file can be viewed, edited, and saved to Google Drive.

Prerequisites

To enable Google Drive access, you must install the Citrix File Access component (FileAccess.exe) on your VDA and enable file type associations in Citrix Studio. You can download Citrix File Access from the Citrix Receiver for Chrome download page.

To enable Google Drive access from Citrix Receiver

  1. Install FileAccess.exe on each XenApp or XenDesktop VDA.
  2. Configure the appropriate FTAs for published applications in Citrix Studio.
  3. On the XenApp/XenDesktop VDA https://accounts.google.com and https://ssl.gstatic.com have to be trusted and cookies from these sites should be enabled.

Only files from Google Drive can be opened using Citrix Receiver. To open a file from Google Drive, right-click and and open the file using Citrix Receiver.

Citrix recommends that you associate one file type with only one published application.

To disable Google Drive access from Citrix Receiver

In the manifest.json file, replace:

"file_handlers" : {

      "all-file-types" : {

         "extensions" : [

            "*"

         ]

      }

   },

with:

Code Copy

"file_handlers" : {

      "cr-file-type" : {

         "extensions" : [

            "cr",

           "ica"

         ]

      }

   },

Enabling and configuring KIOSK mode

Citrix Receiver for Chrome kiosk mode provides the ability to run all apps in the same window. Using this feature, you can run Citrix Receiver apps in kiosk mode, and then launch any Windows app or desktop using the same mode. In addition, kiosk mode allows you to publish remote apps or desktops as a dedicated Chrome package using a persistent URL.

You can control this feature by adjusting the kiosk settings in the Chrome admin panel for managed Chrome devices.

See the Google support site for instructions on enabling the Receiver app to run in kiosk mode on managed and non-managed Chrome devices.

If you are deploying a Receiver app, you should publish using the visibility options set to Public/unlisted to ensure interoperability with KIOSK mode. Go to the Chrome Web Store Developer Dashboard.

The store URL is read-only when kiosk mode is active and cannot be edited using the Account settings screen. However, you can change this setting by either repackaging the app with the .cr file or through Google Policy Management using the Google Admin Console.

.cr file example Copy

<Services version="1.0">

<Service>

<rfWeb>http://your_RfWebURL_or_persistenturl</rfWeb>

<Name>Mystore</Name>

<Gateways>

<Gateway>

<Location>https://yourcompany.gateway.com</Location>

</Gateway>

</Gateways>

<Beacons>

<Internal>

<Beacon>http://yourcompany.internalwebsite.net</Beacon>

</Internal>

<External>

<Beacon>http://www.yourcompany.externalwebsite.com</Beacon>

</External>

</Beacons>

</Service>

</Services>

If you are using the Google Admin Console, edit the policy.txt file containing the Receiver configuration. Replace the value of “url” under “rf_web” with a persistent URL.

example Copy

{

"settings": {

"Value": {

"settings_version": "1.0",

"store_settings": {

"beacons": {

"external": [

{

"url": "http://www.yourcompany.externalwebsite.com"

}

],

"internal": [

{

"url": "http://yourcompany.internalwebsite.net"

}

]

},

"gateways": [

{

"is_default": true,

"url": "https://yourcompany.gateway.com"

}

],

"name": "mystore",

"rf_web": {

"url": " http://your_RfWebURL_or_persistenturl "

}

}

}

}

}

Session reliability

With session reliability, the session remains active on the server if connectivity is lost temporarily. To indicate that connectivity is lost, the user’s display becomes unresponsive until connectivity resumes. The user continues to access the display during the interruption and can resume interacting with the application when the network connection is restored.
Session Reliability reconnects users without reauthentication prompts.

Note

You can use session reliability with Transport Layer Security (TLS).

Using session reliability policies

The session reliability connections policy setting allows or prevents session reliability.

The session reliability time-out policy setting has a default of 180 seconds, or three minutes. Though you can extend the amount of time the session reliability keeps a session open, this feature is designed to be convenient to the user and it does not, therefore, disconnect the session.

Tip

As you extend the amount of time a session is kept open, chances increase that a user might get distracted and walk away from the user device, potentially leaving the session accessible to unauthorized users.

Incoming Session Reliability connections use port 2598- unless you change the port number defined in the session reliability port number policy setting.

Note

Session reliability is enabled by default on the server. To disable this feature, configure the policy managed by the server.

Configuring session reliability

By default, session reliability is enabled.

To disable session reliability:

  1. Launch Citrix Studio.
  2. Open the Session Reliability connections policy.
  3. Set the policy to Prohibited.
localized image

Configuring session reliability time-out

Note

Session reliability time-out policy can be configured only with XenApp/XenDesktop 7.11 or later.

To modify session reliability time-out:

By default, session reliability time-out is set to 180 seconds.

  1. Launch Citrix Studio.
  2. Open the Session Reliability time-out policy.
  3. Edit the time-out value.
  4. Click OK.

Configuring the Reconnect user interface transparency level

The Session User Interface is displayed during a session reliabilitySession Reliability reconnect attempts. The transparency level of the user interface can be modified using Studio policy.

By default, Reconnect UI transparency is set to 80%.

To modify the Reconnect user interface transparency level:

  1. Launch Citrix Studio.
  2. Open the Reconnect UI transparency level policy.
  3. Edit the value.
  4. Click OK
For XenApp and XenDesktop Version 7.11 or earlier, use the default.ica file in StoreFront to modify the connection time-out for session.

Setting

Example

Default

SessionReliabilityTTL

SessionReliabilityTTL=120

180

How session reliability works

When session reliability is enabled consider the following:

  • A session window is grayed out when a reconnection is in progress. When a session is timed out, it is disconnected. 
localized image

Note

You can alter the grayscale brightness used for an inactive session using Desktop Studio. By default, this value is set to 80. The maximum value cannot exceed 100 (indicates a transparent window) and the minimum value can be set to 0 (a fully blacked out screen).

localized image

Enhanced clipboard support

Citrix Receiver for Chrome supports HTML format in addition to plain text between the client and the VDA in a session. This support is useful when using Microsoft Office apps and browsers. Enhanced clipboard support is available only on Chrome and Safari browsers.

Configuring clipboard

You can copy HTML content and retain formatting when copying a link in Chrome. An <img> tag is added in HTML format, which allows you to copy images as well as text. This feature is richer than plain text.

To enable this feature, add the following registry entry to the VDA:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\Virtual Clipboard\Additional Formats\HTML Format
"Name"="HTML Format"

Warning

Using Registry Editor incorrectly can cause serious problems that can require you to reinstall the operating system. Citrix cannot guarantee that problems resulting from incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Make sure you back up the registry before you edit it.

Note

For additional information about the issues resolved by the introduction of this feature, see Knowledge Center article CTX112063 and CTX086028.

Configuring USB device redirection

Citrix Receiver for Chrome supports a wide range of USB peripherals. With this added functionality, administrator can create a Google policy to identify the PID/VID of the device to enable its use in Citrix Receiver. This support extends to new USB devices, including 3D Space mouse, additional composite devices, and Bloomberg keyboard.

For more information on configuring USB devices, see the Knowledge Center article CTX200825.

File transfer policies

Citrix Receiver for Chrome provides secure file transfer functionality between a user device and a virtual XenDesktop session. This feature uses a file transfer virtual channel instead of client drive mapping.

By default, users can:

  • Upload files from a local download folder or attached peripheral
  • Seamlessly access data from their XenDesktop sessions.
  • Download files from their XenDesktop sessions to a local folder or a peripheral on their user device.

Administrators can configure file transfer, uploads, and downloads using policies in Citrix Studio.

Prerequisites

  • XenApp or XenDesktop 7.6 or later, with:
    • Hotfix ICATS760WX64022.msp on server OS VDAs (Windows 2008 R2 or Windows 2012 R2)
    • Hotfix ICAWS760WX86022.msp or ICAWS760WX64022.msp on client OS VDAs (Windows 7 or Windows 8.1)
  • To change file transfer policies: Group Policy Management (GPM) hotfix GPMx240WX64002.msi or GPMx240WX86002.msi on machines running Citrix Studio.

Limitations

  • A user can upload or download a maximum of 10 files at a time.
  • Maximum file size:
    • For uploads: 2147483647 bytes (2 GB)
    • For downloads: 262144000 bytes (250 MB)
  • If either the ‘Upload file to Desktop’ or the ‘Download file from Desktop’ policy is set to Disabled, the toolbar still displays both the Upload and the Download icons but the functionality is based on the policy setting. However, if both policies are set to Disabled, the Upload and Download icons are not displayed in the toolbar.

Configuring file transfer policies

To configure file transfer using a Citrix Studio policy

By default, file transfer is enabled.

Use Citrix Studio to change the following policies, located under User Setting > ICA > File Redirection.

CITRIX STUDIO POLICY DESCRIPTION
Allow file transfer between desktop and client To enable or disable the file transfer feature
Upload file to Desktop To enable or disable file upload in the session. Requires the “allow file transfer between desktop and client” policy to be set to true.
Download file from Desktop To enable or disable file download from the session. Requires the “allow file transfer between desktop and client” policy to be set to true.

To configure file transfer using configuration.js file

The configuration.js file is located in the ChromeApp root folder. Edit this file directly to make changes to Citrix Receiver for Chrome.

Note: Citrix recommends that you back up the configuration.js file before making any changes to it.

Note: Administrator- level credentials are required to edit the configuration.js file; After editing the file, repackage the app to make additional modifications to toolbar elements.

To change the file transfer configuration using the configuration.js file:

  1. Open the configuration.js file and configure the settings as below:
FILE TRANSFER CLIENT SETTINGS DESCRIPTION
AllowUpload To enable or disable upload from client-side. By default set to true (enabled).
AllowDownload To enable or disable download from the client-side. By default set to true (enabled).
MaxUploadSize To set the maximum size of the file that can be uploaded in bytes. By default set to 2147483648 bytes (2GB)
MaxDownloadSize To set the maximum size of the file that can be downloaded in bytes. By default set to 2147483648 bytes (2GB).

Following are the behavior cases when the policy set in Citrix Studio and the client are different.

Citrix Studio Policy
Upload / Download
Client- side setting 
Upload / Download
Resulting Behavior
DISABLED ENABLED DISABLED
DISABLED DISABLED DISABLED
ENABLED DISABLED DISABLED
ENABLED ENABLED ENABLED

Note

When there is a conflicting value set for Maximum File Size upload or download in the registry and in the client-side settings, the minimum size value among the two is applied.

File transfer logs:

The file transfer logs can be retrieved from both the client and the server.

To retriever file transfer logs from the client:

  1. Launch a browser.
  2. Go to the following URL to start logging:
    <storefronturl>/clients/html5client/src/viewlog.html
    where <storefronturl> is the FQDN or IP address of the StoreFront server where the store is configured.

For more information on file transfer, see Receiver for HTML5 and Chrome File Transfer Explained.