Configure

Multi-touch mode

About this feature

Citrix Workspace app for ChromeOS allows you to set Multi-touch as the default mode through the Google Admin Console. Multi-touch mode controls whether to enable multi-touch gestures.

You can toggle between Panning mode and Multi-touch mode. Earlier, panning mode was set as the default mode.

When you launch a session in a touch-enabled device, the gestures by default are handled in panning mode. You can switch to multi-touch mode using the toolbar. This feature provides a better user experience.

How to configure

To set the feature as the default, edit the Google Admin Console policy and set the value of defaultMode to multitouch.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                        "engine_settings": {
                            "ui": {
                                "touch" : {
                                    "defaultMode" : "multitouch"
                                    }
                               }
                            }
                         }
                    }
                 }

<!--NeedCopy-->

Support for Touch

About this feature

Citrix Workspace app for ChromeOS now enhances touch support by allowing you to run sessions on touch-enabled Chrome devices in tablet mode. This feature includes support for gestures, multi-touch, and soft keyboard functionality.

The Open keyboard icon now appears on the session toolbar when a Chrome device is in tablet mode. When you use this feature or do a three-finger tap, the soft keyboard appears.

Gesture enhancements on touch devices

Starting with the 23.4.0 release, Citrix Workspace app enhances end user experience related to gestures, multi-touch, and soft keyboard functionality (Tablet mode). In your Citrix Workspace app sessions, you can use all the familiar multi-touch gestures, including the tap, swipe, and drag.

Following is the gesture guide:

Automatic Keyboard display

About this feature

You can enable automatic keyboard display on a server by using the floating keyboard button that appears in an input field. For the automatic keyboard display feature to be available, verify that the server-side setting is enabled.

Feature limitations:

• Doing a three fingers tap to fetch the soft keyboard does not work in multi-touch mode. It works only in panning mode.

• For the soft keyboard to work properly, always close it using the Open Keyboard icon on the session toolbar rather than the system-soft keyboard. If you close the soft keyboard using the system-soft keyboard, the soft keyboard might behave unexpectedly.

How to configure

To enable the server-side setting, complete these steps:

1. On the Delivery Controller, open Citrix Studio.
2. Select Policies.
3. Click Create Policy.
4. Search for Automatic Keyboard Display and select Allowed.

Asset ID

About this feature

Citrix Workspace app uses an Asset ID that administrators set through the Google Admin Console as a client name for sessions that are launched from enrolled Chromebooks.

How to configure

By default, Citrix Workspace app continues to generate a unique client ID for enrolled Chromebooks, which is similar to earlier versions. To use this feature, you must set a policy for Citrix Workspace app.

The data value that you enter can’t have more than 15 characters. Values longer than 15 characters are truncated to 15 characters.

Configuring Asset ID

1. Log on to the Google Admin Console.

2. Go to Device Management > Chrome > Devices Console and add Asset ID for the device.

3. Edit the Google Admin Console policy and set the value of useAssetID to true. By default, the useAssetID is set to false.

   {
   "settings": {
   "Value": {
     "settings_version": "1.0",
     "engine_settings": {
       "uniqueID": {
         "useAssetID": true
                   }
               }
           }
       }
   }
   
   <!--NeedCopy-->
   

Feature limitations:

• You must have a Google Admin policy that can be pushed. Otherwise, the current method of generating a unique client ID for managed Chromebooks remains in use.

• Do not enter a value more than 15 characters. Values longer than 15 characters are truncated to 15 characters.

Customer Experience Improvement Program (CEIP)

How to configure

Additional Information

Citrix handles your data in line with the terms in your contract. Citrix protects your data as specified in the Citrix Services Security Exhibit available on the Citrix Trust Center.

Citrix uses Google Analytics to collect certain data from Citrix Workspace app as part of CEIP. You can either disable or block CEIP data. Review how Google handles data collected for Google Analytics.

Note:

No data is collected for the users in European Union (EU), European Economic Area (EEA), Switzerland, and United Kingdom (UK).

Disabling CEIP

You can disable sending CEIP data to Citrix and Google Analytics. To do that, use one of the following methods:

• Disable CEIP using Google Admin Policy
• Disable CEIP using configuration.js

Note:

When you disable CEIP for version 2203 and later, minimal information about the Citrix Workspace app version that is installed is uploaded. This minimal information is valuable to Citrix because it provides the distribution of different versions used by customers.

To disable CEIP using Google Admin Policy

Note:

Administrator-level credentials are required to do this procedure.

1. Log on to the Google Admin Console.
2. Go to Device management > Chrome Management > User Settings.
3. Add the strings shown after Step 4 to the policy.txt file under the engine_settings key.
4. Click Save.

For more information on google policy, see Knowledge Center article CTX141844.

For Version 1907 and earlier, set the enabled attribute under ceip to false.

"ceip":{
    "enabled":false,
}
<!--NeedCopy-->

For Version 1908 and later, set the enabled attribute under analytics to false. However, the analytics key is backward compatible with the ceip key.

"analytics":{
    "enabled":false,
}
<!--NeedCopy-->

To disable CEIP using configuration.js

The configuration.js file is in the ChromeApp root folder. Edit this file to configure Citrix Workspace app for ChromeOS.

Note:

• Citrix recommends that you back up the configuration.js file before making changes.
• Citrix recommends using this method only if Citrix Workspace app for ChromeOS is repackaged for users.
• Administrator-level credentials are required to edit the configuration.js file.

For Version 1907 and earlier, set the enabled attribute under ceip to false in the configuration.js file.

"ceip":{
    "enabled":false,
}
<!--NeedCopy-->

For Version 1908 and later, set the enabled attribute under analytics to false in the configuration.js file.

"analytics":{
    "enabled":false,
}

<!--NeedCopy-->

Blocking CEIP

For Version 2007 and later, administrators are allowed to block CEIP through the configuration.js file and Google Admin Policy.

For Version 2203 and later, end users are allowed to block CEIP through the GUI.

This configuration takes precedence over the configuration made through the GUI and Google Admin Policy, and CEIP data isn’t sent to Citrix.

To block CEIP using Google Admin Policy

Note:

Administrator-level credentials are required to do this procedure.

1. Log on to the Google Admin Console.
2. Go to Device management > Chrome Management > User Settings.
3. Add the strings shown after Step 4 to the policy.txt file under the engine_settings key.
4. Click Save.

"analytics":{
    "connectionEnabled":false,
                }
<!--NeedCopy-->

To block CEIP using configuration.js

1. Open the configuration.js file.

2. Add the connectionEnabled attribute, and set the attribute to false:

   "analytics":{
   "connectionEnabled":false,
               }
   
   <!--NeedCopy-->
   

To block CEIP using GUI

Note:

Only the end user can modify the CEIP settings using the GUI.

1. Launch Citrix Workspace app for ChromeOS.
2. Select Settings > General.
3. Clear Help improve Citrix Workspace by sending anonymous usage statistics option.

Relaunch Citrix Workspace app for the changes to take effect.

Specific CEIP data

The specific CEIP data elements collected by Google Analytics are:

Content Collaboration Service integration

About this feature

Citrix Content Collaboration enables you to:

• Exchange documents easily and securely.
• Send large documents by email
• Securely handle document transfers to third parties.
• Access a collaboration space.

Citrix Content Collaboration provides many ways to work, including a web-based interface, mobile clients, desktop apps, and integration with Microsoft Outlook and Gmail.

You can access Citrix Content Collaboration functionality from the Citrix Workspace app using the Files tab displayed within Citrix Workspace app. You can view the Files tab only if Content Collaboration Service is enabled in the Workspace configuration in the Citrix Cloud console.

Note:

Citrix Workspace app does not support Citrix Content Collaboration on Windows Server 2012 and Windows Server 2016. This exclusion is because of a security option set in the operating system.

The following image displays sample contents of the Files tab of the new Citrix Workspace app:

Feature limitations:

• Resetting Citrix Workspace app does not cause Citrix Content Collaboration to log off.
• Switching stores in Citrix Workspace app does not cause Citrix Content Collaboration to log off.

To enable Citrix Workspace app for ChromeOS for users to access resources hosted on Citrix Virtual Apps and Desktops, you must create a StoreFront store. You must also enable:

• WebSocket connections on Citrix Gateway
• Citrix Virtual Apps
• Citrix Virtual Apps and Desktops as required

Graphics and H.264

How to configure

To configure graphics and H.264 protocol support, use the Google admin policy by including the following. By default, H.264 protocol support is enabled. To disable it, set the enabled attribute to false.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                     "ui": {
                        "features": {
                            "graphics": {
                                "jpegSupport": true,
                                "h264Support" : {
                                     "enabled": true,
                                     "losslessOverlays": true,
                                     "dirtyRegions": true,
                                     "yuv444Support": false
                                }
                            }
                        }
                     }
                }
        }
   }
}

<!--NeedCopy-->

List of graphics options with their descriptions:

• “jpegSupport”: JPEG capability in Graphics (Thinwire).
• “h264Support”: H.264 protocol support.
• “enabled”: H.264 support capability in Thinwire.
• “losslessOverlays”: Loss less overlays capability in Thinwire.
• “dirtyRegions”: Dirty regions capability in Thinwire.
• “yuv444Support”: Yuv444 support capability in Thinwire.

Note:

We recommend setting the Legacy Graphics Mode to Disabled.

Selective H.264

How to configure

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

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

1. Open the web.config file for Citrix Receiver for Web site. This file is in the C:\inetpub\wwwroot\Citrix\<Storename> Web folder, where Storename is the name that is 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 in the ChromeApp root folder. Edit this file to modify Citrix Workspace app according to your requirement.

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

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.

   

Note:

• Citrix recommends that you back up the configuration.js file.
• Citrix recommends using this method only when Citrix Workspace app for ChromeOS is repackaged for users.
• Administrator-level credentials are required to edit the configuration.js file; after editing the file, repackage the app for the changes to take effect.

Other (H.264)

How to configure

To configure H.264, use the Google admin policy by including the following. By default, the option under the other section is disabled. To enable it, set the disabled attribute h264nonworker to true.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                    "other": {
                        "h264nonworker" : false
                        }
                }
        }
    }
}

<!--NeedCopy-->

List of options with their descriptions:

• “h264nonworker”: Enable the option to decode an H.264 frame in the main thread.

Full-screen mode

How to configure

To configure your desktop session to always open in full-screen mode, edit the Google Admin Policy by including the following:

{

      "settings": {

                     "Value": {
                     "settings\_version": "1.0",
                     "engine\_settings": {
                     "ui": {
                     "sessionsize": {
                     "windowstate": "fullscreen"
                              }
                                      }
                                               }
                            }
                }
}
<!--NeedCopy-->

Window state on session launch

How to configure

To open desktop sessions in full-screen mode, edit the Google admin policy by including the following. By default, desktop sessions open in maximized windows, where the “window state” value is set to “maximized”.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
            "engine_settings": {
            "ui": {
                "sessionsize": {
                    "windowstate": "fullscreen"
                    }
                }
            }
        }
    }
}

<!--NeedCopy-->

Session size

How to configure

The session size setting lets you customize resolutions for a session. Edit the Google admin policy by including the following:

{
    "settings": {
      "Value": {
            "settings_version": "1.0",
            "engine_settings": {
            "ui": {
                "sessionsize" : {
                    "minwidth" : 240,
                    "minheigh" : 120,
                    "available" : {
                            "default" : "Fit_To_Window",
                            "values" : [
                                            "Fit_To_Window",
                                            "Use_Device_Pixel_Ratio",
                                            "1280x800",
                                            "1440x900",
                                            "1600x1200"
                                       ]
                        }
                    }
                }
            }
        }
    }
}

<!--NeedCopy-->

List of various resolution options and their descriptions:

• “minwidth”: 240: The minimum width for sessions.
• “minheight”: 120: The minimum height for sessions.
• “available”: Options to set resolution preferences for sessions.

  • “default”: The value that you set applies to the default resolution. By default, the value is set to “Fit_To_Window”. You can change the default value as follows:

    • “values”: Other resolution values are:
      • “Fit_To_Window”: The default resolution value available. It matches the window size to emulate various screen resolutions.
      • “Use_Device_Pixel_Ratio”: Scales sessions to match the DPI of the device.
      • “1280x800”: Sets the session size to 1280 * 800 pixels.
      • “1440x900”: Sets the session size to 1440 * 900 pixels.
      • “1600x1200”: Sets the session size to 1600 * 1200 pixels.

Store settings

How to configure

To create a store, you identify and configure communications with the servers. You can provide the resources that you want to make available in the store. Then, optionally, you configure remote access to the store through Citrix Gateway. To configure store settings, edit the Google admin policy by including the following:

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
            "store_settings": {
                "name": "SampleStore",
                "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"
                }
            }
        }
    }
}

<!--NeedCopy-->

List of store setting options and their descriptions:

• “name”: Enter the Store name.

• “gateways”: Gateway URLs.

  Add gateway URLs in the format https://gateway.domain.com or https://yourcompany.gateway.com and click Add on the utility page.

  You can set a default gateway if two or more gateway URLs are added.

  To make a gateway the default, set the “is_default” flag to true. Otherwise, set the flag to false.

  For example:

  
       {
           "settings": {
               "Value": {
               "settings_version": "1.0",
               "store_settings": {
                   "name": "RTST",
                       "gateways": [{
                           "url": "https: //yourcompany.gateway.com",
                           "is_default": true
                   },
                   {
                           "url": "https://gateway2.domain.com",
                           "is_default": false
                   }]
               }
          }
      }
   }
  
   <!--NeedCopy-->
  

• “internal”: Determines whether Citrix Workspace app connects to StoreFront directly or it connects through a gateway. For example, https://storefront.domain.com.
• “external”: Determines whether the specified network interface is available and allows traffic. For example, https://citrix.com.
• “rf_web”: Store URL.

Support for multiple stores

Starting with the 2305 release, IT administrators can assign multiple stores to end users. Now, it’s easy for end users to switch between multiple stores without needing to remember the exact store URL. This feature improves the user experience when accessing multiple stores.

How to configure

To configure multiple stores, IT administrators can edit the Google admin policy. Following is an example of JSON data:

{
      "settings_version": "1.0",
      "store_settings": {
            "name": "SampleStore",
            "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"
            },
            "secondary_stores": [{
                  "name": " SampleStore",
                  "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 "
                  }
            }, {
                  "rf_web": {
                  "url": " http: //yourcompany.storefrontstoreweb.net "
                  }
            }]
      }
}
<!--NeedCopy-->

The attribute, secondary_stores allows you to configure multiple stores. An administrator can use the JSON structure multiple times. For more information on how to customize Citrix Workspace app for ChromeOS see, Configuration utility tool.

Multiple StoreFront

About this feature

You can change the Store address without having to restart Citrix Workspace. Existing Citrix Workspace sessions, if any, continue to run uninterrupted.

To add stores:

1. Click Settings in Citrix Workspace app for ChromeOS, and select the Account tab.
2. Enter the StoreFront URL or email address in the Store URL or Email address field.

3. Click Apply to save the new store.

   

To switch stores, select a store from the Select a store URL list.

To delete a store from the list, click the Delete icon next to the store address you want to delete and confirm deletion.

Awake setting

About this feature

Citrix Workspace app for ChromeOS keeps managed Chromebook devices awake even when the users aren’t active.

The awake setting feature is disabled by default.

How to configure

To enable the feature, edit the Google Admin Console policy and set the value of the keep_awake_level property under power_settings to either “system” or “display” and then restart the session.

The “system” level keeps the system awake, but allows the screen to be dimmed or turned off. The “display” level keeps the system awake and active.

{
 "settings": {
     "Value": {
         "settings_version": "1.0",
         "power_settings": {
             "keep_awake_level": ”system” or “display”
             }
           }
        }
    }
<!--NeedCopy-->

List of power setting options with their descriptions:

• “keep_awake_level”: Keeps devices awake even when users aren’t active. You can choose either of the two values:

  • “system”: Keeps the system awake, but allows the screen to be dimmed or turned off.
  • “display”: Keeps the system awake and active.

Note:

For Kiosk mode, make sure that the Allow app to manage power setting in the Google Admin console is disabled.

Virtual channels

About this feature

A virtual channel consists of a client-side virtual driver that communicates with a server-side application. Virtual channels are a necessary part of the remote computing experience with Citrix Virtual Apps and Desktops servers.

Virtual channels are used for:

• Printing
• Serial port mapping
• Clipboard
• Audio
• Multimedia
• Control channel
• EUEM
• USB
• File transfer
• Mobility
• Multi-touch
• Smart card.

How to configure

All virtual channels are enabled by default. To disable a particular virtual channel, use the Google admin policy by including the following. Select the feature name under “vc_channel” and click Add on the utility page. For example:

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                        "vc_channel": {
                            "<vc_name1>": false,
                            "<vc_name2>": false,
                            "<vc_name3>": false,
                            "<vc_namen>": false
                                        }
                                  }
        }
    }
}

<!--NeedCopy-->

To enable a particular “vc_channel”, select the feature and click Remove on the utility page.

Note:

The names can be from 1 to n. The last name “n” can’t have a comma after setting it to true or false.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                    "vc_channel": {
                        "CTXCPM ": false,
                        "CTXCAM ": false,
                        "CTXGUSB": false
                                    }
                                   }
        }
    }
}

<!--NeedCopy-->

List of virtual channel options with their descriptions:

• “CTXCPM”: PDF printing.
• “CTXCCM”: Client serial port mapping.
• “CTXCLIP”: Clipboard operations from session to VDA and from VDA to session.
• “CTXCAM”: Client audio mapping.
• “CTXMM”: Citrix multimedia redirection.
• “CTXCTL”: Citrix control virtual channel.
• “CTXEUEM”: End user experience monitoring.
• “CTXGUSB”: Redirect USB devices to session.
• “CTXFILE”: Secure file transfer happens between a user device and a Citrix Virtual Apps and Desktops and Citrix DaaS (formerly Citrix Virtual Apps and Desktops service) session. You can upload and download files to and from a session and seamlessly access data.
• “CTXMTCH”: Multi-touch remotes all gestures to the virtual session. The app behaves based on the gestures that it supports.
• “CTXSCRD”: Smart card support.

CustomVC

About this feature

Virtual Channel SDK for Chrome enables third-party Chrome apps to write custom virtual channels. These channels are initialized with the app and desktop sessions that are launched using Citrix Workspace app or using the HDX SDK for Chrome.

In addition, the virtual channel SDK gives an easy way to write and receive data from the third-party Chrome app and the app and desktop.

How to configure

To configure custom virtual channels, use the Google admin policy by including the following.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                    "customVC": [
                        {
                    "appId": "xyz",
                    "streamName": "abc"
                        }
                    ]
                }
        }
    }
}

<!--NeedCopy-->

List of CustomVC options with their descriptions:

• “appId”: ID of the chrome app that is implementing custom virtual channels.
• “streamName”: The virtual channel name.

Net promoter score

About this feature

Citrix Workspace app for ChromeOS prompts you periodically for Net Promoter Score (NPS) feedback. The prompt asks you to rate your experience with Citrix Workspace app for ChromeOS. We use NPS feedback as a tool to measure customer satisfaction and to further improve the app.

You can rate your experience on a scale of 1–5, with 5 indicating that you’re satisfied.

How to configure

To configure NPS, use the Google admin policy by including the following. If the option is set to true, the user can provide the rating.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                    "ui": {
                        "netPromoters": true
                          }
                }
        }
    }
}

<!--NeedCopy-->

Multi-monitor display

About this feature

Multi-monitor supports up to two external monitors. By default, the multi-monitor feature is set to enabled.

UI dialogs and toolbars appear only on the primary monitor. However, USB and smart card authentication dialogs span across monitors.

How to configure

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

Note:

• If you’re using Citrix Workspace app 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 the primary monitor. However, USB and smart card authentication dialogs span across monitors.

To disable enhanced multi-monitor display in kiosk mode

Enhanced multi-monitor display in kiosk mode is enabled by default.

To disable the feature in kiosk mode, edit the configuration.js file or the Google Admin Console policy and set the value of kioskMultimonitor to false.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
            "engine_settings": {
                "features": {
                    "graphics": {
                        "multiMonitor": true,
                        "kioskMultimonitor": true
                  }
              }
           }
       }
    }
 }

<!--NeedCopy-->

Note:

To launch a session in kiosk mode, you must enable Unified Desktop mode.

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 Unified Desktop mode

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 performance

About this feature

Citrix Workspace app for ChromeOS improves the overall performance and stability of sessions in multi-monitor scenarios. In earlier versions, when a session was running on multiple monitors, you experienced sluggish performance.

How to configure

Multi-monitor display in kiosk mode

Enhanced multi-monitor display in kiosk mode is enabled by default.

To disable kiosk mode, edit the configuration.js file or the Google Admin Console policy and set the value of kioskMultimonitor to false.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
            "engine_settings": {
                "features": {
                    "graphics": {
                        "kioskMultimonitor": false
                  }
              }
           }
       }
    }
 }

<!--NeedCopy-->

Note:

To launch a session in kiosk mode, you must enable Unified Desktop mode.

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 Unified Desktop mode 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.

To disable multi-monitor feature

By default, multi-monitor is enabled.

1. Launch Citrix Workspace app for ChromeOS.
2. Select Settings > General.

3. Clear Use all the monitors to span display.

   

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

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

4. Windowed mode: The desktop session displays in single monitor mode.

5. Full-screen mode: When a desktop session is switched to full-screen mode, the session displays in multi-monitor mode only when Use all the monitors to span display is selected.

   For the display to span across monitors in a desktop session, select Use all the monitors to span display option and click full-screen mode when the two monitors are connected.

   In an application session, when two monitors are connected and Use all the monitors to span display option is selected, the session automatically displays in a multi-monitor mode.

Using Citrix Virtual Desktops on dual monitors:

1. Click Multimonitor in the toolbar.

   The screen is now extended to both the monitors.

Feature limitations:

• Citrix Workspace app for ChromeOS does not support full-screen H.264 graphics mode for multiple monitors.

• The limit of the number of monitors isn’t hard-coded. The total resolution to be managed and rendered affects the limitation.

  • This feature supports two monitors. If you launch a session with the total screen resolution greater than [2 x (1920x1080)] pixels, you might experience screen lags. Monitor resolution limits can cause screen lags to occur.
  • The built-in screen of the latest Chromebooks supports a resolution greater than 1920x1080 pixels. The feature hasn’t been tested on such devices.

• In multi-monitor mode, full-screen H264 is disabled because of issues found during testing.

  • When you use one single, large external monitor, the issue does not occur and H264 remains running. Selective H264 also runs in this scenario.

• When you use screens with different resolutions, you might experience performance issues.

• When you use built-in monitors with higher resolution and external monitors whose resolution is low, performance issues might occur.

Microsoft Teams optimization

You can now use the following features of Microsoft Teams for virtual desktop and virtual app sessions:

• Optimized audio calls

• Optimized video calls

• Optimized screen sharing

It’s supported only on VDA versions 1906 and later.

Notes:

• By default, screen sharing allows sharing of the entire screen. However, you can limit screen sharing to Citrix Workspace app content only. For more information, see Limit screen sharing of Citrix Workspace app content. To enable the screen sharing feature through the Google admin policy, see Microsoft Teams optimization settings.

• To troubleshoot, and to change Microsoft Teams to optimized from unoptimized within your client session, see Troubleshooting for Microsoft Teams optimization.

• During screen sharing using Microsoft Teams optimization, the red border around the shared window does not appear.

• App sharing isn’t supported.

• Microsoft Teams optimization for audio calls, video calls, and screen sharing is generally available from release 2105.5 and later. We recommend that you update to the latest version of Citrix Workspace app for ChromeOS.

Video calls and screen sharing on external monitors

On your external monitor, you can now use the following features of Microsoft Teams during calls.

• Optimized video
• Optimized screen sharing

These features are available for Microsoft Teams calls within virtual desktops. They’re also available for calls made through the Microsoft Teams virtual app, when you place the Microsoft Teams windows on an external monitor.

Notes (ChromeOS version 96 update)

• To avoid any impact of ChromeOS version 96 update on Microsoft Teams functioning, do the following before you update the ChromeOS:
• For users on a repackaged version of Citrix Workspace app, see Knowledge Center article CTX331648 and implement the steps.
• For all other users of Citrix Workspace app for ChromeOS, version 2110 and earlier, see Knowledge Center article CTX331653.

Microsoft Teams optimization settings

To enable screen sharing

To enable screen sharing using the Google admin policy (see Google policies), change the screen sharing value to true for msTeamsOptimization as follows:

{
  "settings": {
     "Value": {
       "settings_version": "1.0",
          "engine_settings": {
             "features":{
                "msTeamsOptimization":{
                "screenSharing" : true
                  }
               }
            }
         }
     }
  }

<!--NeedCopy-->

To enable screen sharing for Bring your own device (BYOD) users (only for those using on-premises StoreFront):

Follow the steps in Get started - Using webconfig and add the chromeAppPreferences value as follows:

For example:

chromeAppPreferences = '{"features":{"msTeamsOptimization":{"screenSharing":true }}}'

Note:

Ensure that the following setting is allowed in Google Admin Console for screen sharing optimization to work: In Google Admin Console, under Devices > Chrome > Settings > Select Allow sites to prompt the user to share a video stream of their screen under Screen Video Capture for all three categories: User & Browser Settings, Device Settings and Managed Guest Session Settings (or an appropriate category)

Limit screen sharing of Citrix Workspace app content

For Microsoft Teams optimization, administrators can limit screen sharing of apps and desktops that are opened only through Citrix Workspace app on managed Chrome devices. When administrators turn this feature on, the end users can’t share resources that aren’t opened from Citrix Workspace app.

This feature is applicable to Chrome version M98 and later.

To configure the settings, use Google policies as follows:

1. Navigate to the Google Admin console > Settings > User & browser settings.
2. Go to Screen video capture allowed by sites > Allow tab video capture (same site only) by these sites and enter the Citrix Workspace app for ChromeOS app ID -haiffjcadagjlijoggckpgfnoeiflnem.

Now, the end users can select the tab and share content that is opened through Citrix Workspace app only.

Troubleshooting for Microsoft Teams optimization

To change Microsoft Teams to optimized from an unoptimized state within your client sessions, do the following:

• Quit Microsoft Teams by right-clicking the Microsoft Teams icon, then click Quit. Relaunch Microsoft Teams.
• If quitting does not work, log off from the session and log back on.
• If logging off and logging back on does not work, clear the cache in the directory C:\Users\Administrator\AppData\Roaming\Microsoft\Teams on the VDA, then restart Microsoft Teams.

For more information, see Troubleshooting.

For troubleshooting on the shim library version, see Microsoft Teams optimization logs section.

Support for dynamic e911

Citrix Workspace app supports dynamic emergency calling. When used in Microsoft Calling Plans, Operator Connect, and Direct Routing, it provides the capability to:

• configure and route emergency calls
• notify security personnel

The notification is provided based on the current location of the Citrix Workspace app that runs on the endpoint, instead of the Microsoft Teams client on the VDA.

Ray Baum’s law requires the 911 caller’s dispatchable location to be transmitted to the appropriate Public Safety Answering Point (PSAP). Starting from Citrix Workspace app 2112 for ChromeOS, Microsoft Teams Optimization with HDX is compliant with Ray Baum’s law.

Background blurring and effects in Microsoft Teams optimization

Starting with the 2303 release, Citrix Workspace app for ChromeOS supports background blurring and effects in Microsoft Teams optimization for video calls. You can either blur or replace the background effects povided by Microsoft Teams to avoid unexpected distractions by helping the conversation stay focused on the silhouette (body and face). This feature can be used with P2P and conference calls.

Notes:

• By default, this feature is disabled.
• This feature is now integrated with the Microsoft Teams UI. Multi-window support is a prerequisite that needs a VDA update to 2112 or higher. For more information, see Multi-window meetings and chat.

Limitations

• Administrator and user-defined background replacement aren’t supported.
• When you enable this feature, you might observe performance issues.
• After the ICA session is reconnected, the effect is off. However, the Microsoft Teams UI shows that the previous effect is still On by a tick mark. Citrix and Microsoft are working together to resolve this issue.

How to configure

You can enable the background effect feature in one of the following ways:

• Configuration.js
• Google Admin Policy
• Global App Configuration service

Configuration.js

To configure background blurring and effects using the configuration.js file, do the following:

1. Locate the configuration.js file in the ChromeApp root folder.

   Notes:

   • Citrix recommends that you back up the configuration.js file before making changes.
   • Citrix recommends editing the configuration.js file, only if the Citrix Workspace app for ChromeOS is repackaged for users.
   • Administrator-level credentials are required to edit the configuration.js file.

2. Edit the configuration.js file and set the default value of backgroundEffects to true.

   Following is an example of JSON data:

   "features" :
   {
       "msTeamsOptimization" : {
           "backgroundEffects" : true
       }
   }
   <!--NeedCopy-->
   

3. Save the changes.

Google Admin Policy

On the on-premises deployment, administrators can enable the background effect feature using the Google Admin Policy as follows:

1. Sign in to the Google Admin Policy.
2. Go to Device management > Chrome Management > User Settings.

3. Add the following strings to the policy.txt file under the engine_settings key. Following is an example of JSON data:

   "features" :
   {
       "msTeamsOptimization" : {
           "backgroundEffects" : true
       }
   }
   <!--NeedCopy-->
   

4. Save the changes.

Global App Configuration service

On the cloud setup, administrators can enable the background effect feature by setting the backgroundEffects attribute to True in the Global App Configuration service.

For more information, see Global App Configuration service documentation.

Feature flag management

About this feature

If an issue occurs with Citrix Workspace app in production, we can disable an affected feature dynamically in Citrix Workspace app even after the feature is shipped. To do so, we use feature flags and a third-party service called LaunchDarkly.

How to configure

You do not need to make any configurations to enable traffic to LaunchDarkly, except when you have a firewall or proxy blocking outbound traffic. In that case, you enable traffic to LaunchDarkly through specific URLs or IP addresses, depending on your policy requirements.

You can enable traffic and communication to LaunchDarkly in the following ways:

Enable traffic to the following URLs

• events.launchdarkly.com
• app.launchdarkly.com

List IP addresses in an allow list

If you must list IP addresses in an allow list, for a list of all current IP address ranges, see LaunchDarkly public IP list. You can use this list to ensure that your firewall configurations are updated automatically in keeping with the infrastructure updates. For details about the status of the infrastructure changes, see the LaunchDarkly Status page.

Provision to disable LaunchDarkly service

You can disable LaunchDarkly service on both on-premises and cloud stores.

On the cloud setup, administrators can disable the LaunchDarkly service by setting the enableLaunchDarkly attribute to False in the Global App Configuration Service.

For more information, see Global App Configuration Service documentation.

On the on-premises deployment, administrators can disable the LaunchDarkly service using the Google Admin Policy as follows:

1. Sign in to the Google Admin Console.
2. Go to Device management > Chrome Management > User Settings.

3. Add the following strings to the policy.txt file under the engine_settings key.

   "thirdPartyServices": {
   
     "enableLaunchDarkly": false
   
   },
   
   <!--NeedCopy-->
   

4. Click Save.

Note:

• By default, the LaunchDarkly service is enabled if the enableLaunchDarkly attribute isn’t present.

On the on-premises deployment, administrators can disable the LaunchDarkly service using the configuration.js file as follows:

Note:

• Administrator-level credentials are required to edit the configuration.js file; after editing the file, repackage the app for the changes to take effect.

1. Open the configuration.js file.

2. Add the enableLaunchDarkly attribute and set the attribute to false.

   "thirdPartyServices": {
   
       "enableLaunchDarkly": false
   
        },
   <!--NeedCopy-->
   

3. Click Save.

Note:

• By default, the LaunchDarkly service is enabled if the enableLaunchDarkly attribute isn’t present.

Webcam redirection for 64-bit

About this feature

Webcam redirection is available for both 32-bit and 64-bit applications. Support for webcam redirection with both 32-bit and 64-bit apps is limited to built-in webcams.

You can now use external webcams within Citrix Workspace app for ChromeOS virtual desktop and app sessions. The Workspace app detects newly connected external webcams and makes them available for use dynamically.

How to configure

Configure for webcam redirection for 64-bit as follows:

Configuring the webcam by using the configuration.js file and the Google Admin Console

For Versions 2010 and earlier:

Configure webcam redirection using the following path: HTML5_CONFIG > appPrefs > chromeApp > nacl > video

For Versions 2101 and later:

Configure webcam redirection using the following path: HTML5_CONFIG > features > video

Note:

We recommend that you use the HTML5_CONFIG > features > video path to configure webcam redirection. The other path continues to work for some time and will be removed in a future release.

Recommendations for webcam redirection

• Set the Citrix Delivery Controller Audio Quality policy to Low or Medium. When using low-powered Chromebooks, audio lags might occur if you do not set the Audio Quality policy.
• For best performance, we recommend using high-end Chromebooks and low-latency networks with good bandwidth connections.
• When you use the speaker of a system during a video conference call, you might hear an echo. As a workaround, use a headset.

• Set the following registry key on a VDA:

  HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\HdxRealTime

  Name: OfferH264ToApp

  Type: REG_DWORD

  Value: 1

Note:

This setting applies to the current user setting. For new users, set the registry key through the Windows Group Policy Object (GPO) Editor.

DISCLAIMER: Caution! Using the Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix can’t guarantee that problems resulting from the incorrect use of the Registry Editor can be solved. Use the Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Serial COM port redirection

About this feature

By default, Citrix Workspace app for ChromeOS maps COM5 as a preferred serial COM port for redirection.

How to configure

To configure serial COM port redirection, enable the feature by applying Citrix Virtual Apps and Desktops and Citrix DaaS port redirection policy settings. For more information on port redirection, see Port redirection policy settings.

Note:

By default, Citrix Workspace app for ChromeOS maps COM5 as a preferred serial COM port for redirection.

After enabling serial COM port redirection policy settings on the VDA, configure Citrix Workspace app for ChromeOS using one of the following methods:

• Google Admin Policy
• 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 Citrix Workspace app for ChromeOS is repackaged.

Edit the Google Admin Policy by including the following:

    {
      "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.                                                   }
                                      }
                                      }
                                      }
                                      }
                                     }

 <!--NeedCopy-->

List of serial COM port name options and their descriptions:

• “portname”: Port number for the COM (serial) virtual channel. By default, the value is COM5.

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"

}
<!--NeedCopy-->

Note:

Citrix recommends using the configuration.js file method to configure serial port redirection only when Citrix Workspace app for ChromeOS 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. Run the following command in an active ICA session:

    net use COM4 : \\Client\COM5
<!--NeedCopy-->

Tip:

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

Citrix Universal Print Driver

About this feature

The Citrix PDF Universal Printer driver enables users to print documents opened with hosted applications or applications that run 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.

When printing a document opened with a hosted application or an application that runs on a virtual desktop, you can print the document to PDF. You can transfer the PDF to the local device to view and print from a locally attached printer. The file isn’t stored in Citrix Workspace app for ChromeOS.

Important

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

How to configure

Requirements

To access the Citrix Workspace app for ChromeOS download page, you need a MyCitrix account.

Download the Citrix PDF Printer from the Citrix downloads 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 VDA machine that delivers desktops or apps for Citrix Workspace app 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 policy or edit an existing policy.

   For more information about configuring Citrix Virtual Apps and Desktops policies, see Policies.

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

Support for network printers

Previously, the Citrix PDF Printer option was used to print from the virtual desktop session. The print driver converted the file to PDF and transferred the PDF to the local device. The PDF was then opened in a new window for viewing and printing.

Starting with the 2305 release, Citrix Workspace app for ChromeOS supports network printing. End users can view the list of printers that are connected to their Chromebook inside the session. Users can select a printer directly without generating intermediate PDF files on the local device. This feature is supported on:

• VDA versions 2112 and later.
• ChromeOS version 112 and later.

Note:

• By default, this feature is enabled, and only the PDF format of metafile printing is supported.

For more information, see the following articles:

• Manage printers and print drivers in your environment in the Citrix Virtual Apps and Desktops documentation.

• Knowledge Center article on How to use Citrix Policy to Set a Default Session Printer - CTX232031.

• Knowledge Center article on Citrix Printing Quick Start Guide and Default configuration - CTX227534.

Configuration

You can disable this feature in one of the following ways:

• Configuration.js
• Google Admin Policy

Note:

• As a prerequisite, the IT administrator must enable the Auto-create generic universal printer policy on the Delivery Controller (DDC). For more information, see Client printers policy settings in the Citrix Virtual Apps and Desktops documentation.

Configuration.js

To disable this feature using the configuration.js file, do the following:

1. Locate the configuration.js file in the ChromeApp root folder.

   Notes:

   • Citrix recommends that you back up the configuration.js file before making changes.
   • Citrix recommends editing the configuration.js file, only if the Citrix Workspace app for ChromeOS is repackaged for users.
   • Administrator-level credentials are required to edit the configuration.js file.

2. Edit the configuration.js file and set the default value of networkPrinting to false. Following is an example of JSON data:

   {
     "features": {
        " networkPrinting ": {
             "enable": false
                        }
       }
   }
   <!--NeedCopy-->
   

3. Save the changes.

Google Admin Policy

IT administrators can disable this feature using the Google Admin Policy as follows:

1. Sign in to the Google Admin Policy.
2. Go to Device management > Chrome Management > User Settings.

3. Add the following strings to the policy.txt file under the engine_settings key. Following is an example of JSON data:

   {
      "features": {
           " networkPrinting ": {
               "enable": false
                   }
           }
   }
   <!--NeedCopy-->
   

4. Save the changes.

Google Drive access

About this feature

With Google drive support, users can open, edit, and save Windows file types from a Chrome device that runs Citrix Workspace. While running a Google Chrome device, 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 Citrix Virtual Apps hosted application. The file can be viewed, edited, and saved to Google Drive.

How to configure

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 downloads page.

To enable Google Drive access from Citrix Workspace

1. Install FileAccess.exe on each Citrix Virtual Apps or Citrix Virtual Apps and Desktops and Citrix DaaS VDA.
2. Configure the appropriate FTAs for published applications in Citrix Studio.
3. On the Citrix Virtual Apps or Citrix Virtual Apps and Desktops and Citrix DaaS 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 Workspace. To open a file from Google Drive, right-click and open the file using Citrix Workspace.

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

Proxy connection support

The Citrix Workspace app for ChromeOS supports opening documents from Google drive using published applications through the unauthenticated proxy servers.

How to configure:

To enable the proxy connection, configure the proxy setting in the internet options.

To disable Google Drive access from Citrix Workspace

In the manifest.json file, replace:

"file_handlers" : {
      "all-file-types" : {
         "extensions" : [
            "*"
         ]
      }
   },
<!--NeedCopy-->

with:

    "file_handlers" : {
          "cr-file-type" : {
             "extensions" : [
                "cr",
               "ica"
             ]
          }
       },
<!--NeedCopy-->

Auto-launch of ICA sessions

About this feature

Citrix Workspace app for ChromeOS supports auto-launch of ICA (Independent computing architecture) sessions on Google managed devices or users.

With this feature, you can access resources remotely from Citrix Workspace for the web. The downloaded ICA file starts automatically, with the Citrix Workspace app for ChromeOS, if it has been installed on the device. Previously, you were able to only download ICA files and open the files manually to start resources. Also, the ICA file wasn’t deleted when opened and remained on the device. Now, the ICA file is automatically deleted from the device - once it’s used to auto-launch the session.

How to configure

To configure the auto-launch of ICA sessions, log in as an administrator and do these steps:

1. Log on to the Google Admin console.
2. In the Google Admin console, select Devices > Chrome > Settings.
3. Then, under Settings, select Users & Browsers, Device, and Managed Guest Session Settings (as appropriate), set Auto-open downloaded files and add ica under Auto-open file types for User & Browser Settings, Device Settings, and Managed Guest Session Settings as appropriate (for managed users and managed devices).

Then, ask your users to associate the ICA file with the Citrix Workspace app for ChromeOS on their ChromeOS devices as follows:

1. Open File manager and navigate to the previously downloaded ICA file.
2. Click the ICA file.
3. On the right side of the navigation bar, click Open and select the arrow beside it.
4. Then, select Change default.
5. A list of available apps appears.
6. Select Citrix Workspace.

Kiosk mode

About this feature

Citrix Workspace app for ChromeOS kiosk mode provides the ability to run all apps in the same window. Using this feature, you can run Citrix Workspace 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.

How to configure

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 Citrix Workspace app to run in kiosk mode on managed and non-managed Chrome devices.

If you’re deploying a Citrix Workspace 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.

    <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>

<!--NeedCopy-->

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

    {
    "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 "
    }
    }
    }
    }
    }
<!--NeedCopy-->

Excel shortcuts

How to configure

Keyboard shortcuts are configured with the sendAllKeys attribute.

For all Excel shortcuts to work, configure as follows: HTML5_CONFIG > features > sendAllKeys

The sendAllKeys attribute defaults to true. To change the default, open the configuration.js file (see Google Policies), add the sendAllKeys attribute, and set the attribute to false.

Clipboard

About this feature

Support for copying image clips

Using the standard keyboard shortcuts, you can copy and paste image clips between your local device and your virtual desktop and app sessions. You can use the standard keyboard shortcuts for copying and pasting. As an example, you can use apps such as Microsoft Word, Microsoft Paint, and Adobe Photoshop. Previously, this functionality was available only for text.

Note:

• Due to network bandwidth constraints, sessions might become unresponsive when you try to copy and paste an image clip larger than 2 MB.
• You can select and press Ctrl + C and Ctrl + V to copy and paste. The right-click functionality to copy or paste is also supported.
• We’ve tested this feature with BMP, PNG, JPEG, and GIF formats.

How to configure

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 and 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 the Registry Editor incorrectly can cause serious problems that can require you to reinstall the operating system. Citrix can’t guarantee that problems resulting from incorrect use of the Registry Editor can be solved. Use Registry Editor at your own risk. Make sure you back up the registry before you edit it.

The clipboard feature has resolved many issues. For additional information, see Knowledge Center article CTX086028.

Support for HTML data format

Starting with the version 2207, you can use HTML format for clipboard operations between the virtual desktop and the endpoint device. When you copy and paste the HTML data, the source content format is copied and when you paste the data, the destination content carries the formatting as well. In addition, HTML format provides better look and feel.

For more information on how to set the policies, see Client clipboard write allowed formats in the Citrix Virtual Apps and Desktops documentation.

Shortcuts

About this feature

You can use standard Windows shortcuts to copy data, that includes text, tables, and images, between hosted applications. The hosted applications can be:

• within the same session
• within different sessions

Only Unicode plain text can be copied and pasted between hosted applications and the local clipboard on the device.

Users can use standard Windows keyboard shortcuts with Citrix Workspace app for ChromeOS because these shortcuts are passed from ChromeOS to hosted applications. Similarly, shortcuts specific to particular applications can also be used, provided they do not conflict with any ChromeOS shortcuts. However, the Windows key must also be pressed for function keys to be recognized. So, an external keyboard is required. For more information about using Windows keyboards with ChromeOS, see https://support.google.com/chromebook/answer/1047364. Citrix-specific shortcuts, such as those for switching between sessions and windows, cannot be used with Citrix Workspace app for ChromeOS.

Support for Microsoft Windows logo key and shortcut keys

Note:

• In Chromebooks, use the Search key to map the Microsoft Windows logo key.

Starting with the version 2108 release, we’re supporting the Microsoft Windows logo key and shortcut keys on your Citrix Workspace app for ChromeOS sessions.

We’ve added support for the following key combinations:

• Windows + R
• Windows + D
• Windows + E
• Windows + M
• Windows + S
• Windows + CTRL + S
• Windows + T
• Windows + U
• Windows + Number
• Windows + X
• Windows + K

USB device redirection

About this feature

Citrix Workspace app for ChromeOS supports a wide range of USB peripherals. With this added functionality, you can create a Google policy to identify the PID/VID of the device to enable its use in Citrix Workspace. This support extends to new USB devices, including the 3D Space mouse, other composite devices, Bloomberg keyboards, and the UC-Logic Tablet WP5540U.

How to configure

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

Automatic redirection of USB devices in Kiosk mode

About this feature

In kiosk mode, USB devices are redirected automatically inside a session without any manual intervention. In user and public modes, for the first time, you must manually redirect the USB device into the session from the toolbar or the Connection Center. This manual USB redirection is done to grant permission to the Chrome operating system for accessing the USB device. When a USB device is inserted, it’s redirected into the session automatically.

Important:

• If you insert a USB device when multiple sessions are running, USB redirects into the session that is in focus.
• If there are no sessions in focus, the USB device isn’t redirected into any session.
• If a single session is running and if it isn’t in focus when you insert the USB device, the USB device redirection might fail.

To redirect the USB device to a new session

Note:

To redirect the USB device to a new session, it’s required to remove the USB device from the previous session.

1. Right-click the Citrix Workspace icon and select Connection Center. The Connection Center window appears.
2. Select a session or an application.
3. Click Devices.
4. Navigate to the USB section.
5. Click Release All.

Double hop

Starting with the 2301 version, Citrix Workspace app supports double-hop scenarios. This feature is an enhancement to USB redirection.

For more information, see Double hop in the Citrix Virtual Apps and Desktops documentation.

File transfer

About this feature

Citrix Workspace app for ChromeOS provides secure file transfer functionality between a user device and a Citrix Virtual Apps and Desktops and Citrix DaaS 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 Citrix Virtual Apps and Desktops and Citrix DaaS sessions.
• Download files from their Citrix Virtual Apps and Desktops and Citrix DaaS sessions. You can download files 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.

Feature 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. However, the functionality is based on the policy setting. If both policies are set to Disabled, the Upload and Download icons aren’t displayed in the toolbar.

How to configure

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.

To configure file transfer using configuration.js file

The configuration.js file is in the ChromeApp root folder. Edit this file directly to modify Citrix Workspace app to suit your requirent.

Note:

Citrix recommends that you back up the configuration.js file before modifying it. Administrator level credentials are required to edit the configuration.js file; After editing the file, repackage the app to make more modifications to toolbar elements.

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

Open the configuration.js file and configure the settings as follows:

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

Note:

When there’s 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.

To configure file transfer using the Google admin policy

By default, the file transfer feature is enabled.

To disable it, set the enabled attribute to false.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                    "ui": {
                         "features": {
                            "filetransfer" : {
                                    "allowupload": true,
                                    "allowdownload": true,
                                    "maxuploadsize": 2147483647,
                                    "maxdownloadsize": 2147483647
                            }
                        }
                    }
                }
        }
    }
}

<!--NeedCopy-->

List of file transfer options with their descriptions:

• “allowupload”: Allows file uploads from device to remote session.
• “allowdownload”: Allows downloads from device to remote session.
• “maxuploadsize”: The maximum file size, in bytes, that can be uploaded. By default, set to 2,147,483,648 bytes (2 GB).
• “maxdownloadsize”: The maximum file size, in bytes, that can be downloaded. By default, set to 2,147,483,648 bytes (2GB).

Taskbar icons

About this feature

Applications and desktops that are configured using Citrix Virtual Apps and Desktops and Citrix DaaS in an active session are displayed as separate apps in the taskbar (shelf) on a Chrome device. This feature applies to published applications and desktops. The functionality and behavior of this feature is similar to the taskbar experience that is provided by the Windows Operating system.

By default, this feature is enabled.

How to configure

Configuring taskbar icons using Google Admin policy

Note:

Citrix recommends using this method only when Citrix Workspace app for ChromeOS is repackaged for users.

1. Log on to the Google Admin Console.

2. Go to Device management > Chrome Management > User Settings.

3. Add the following strings to the policy.txt file.

   

4. Click Save and close the file.

Configuring taskbar icons using the Web.config in StoreFront

Note:

Citrix recommends that you use the web.config file method for configuration purposes only. You can use this method when the store version of Citrix Workspace app for ChromeOS is being used.

1. Open the web.config file for the Citrix Receiver for Web site. This file is in C:\inetpub\wwwroot\Citrix\<Storename>Web, where the 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=’{“seamless”:{“showInShelf”:false}}

Configuring taskbar icons using the configuration.js file

The configuration.js file is in the ChromeApp root folder. Access this file directly to modify Citrix Workspace app.

Note:

Administrator-level credentials are required to edit the configuration.js file; after editing the file, repackage the app for the changes to take effect.

To change the ChromeOS taskbar using the configuration.js file:

1. Open the configuration.js file and set the showInShelf attribute to true.

For example:

Feature limitations:

1. When more than one instance of the same application is launched, the app icon isn’t stacked and appears as two separate icons. For example, two instances of Notepad display two icons of Notepad in the taskbar.
2. App pinning isn’t supported.

In-session toolbar and dialogs

About this feature

The in-session toolbar is a floating toolbar that can be moved anywhere on the screen. The toolbar has Citrix Workspace app icon embedded on it. A customized toolbar improves the user experience. This enhancement provides new options that are accessible from the toolbar to ease common tasks, such as:

• switching to full-screen mode
• uploading or downloading files
• Copy content from an active session to the clipboard to enable sharing between sessions
• accessing more options

Note:

On the touch-enabled devices, the Citrix Workspace app icon appears at the top center to indicate the floating toolbar during desktop sessions. On non-touch-enabled devices, a menu button indicating the floating toolbar transforms to the Workspace icon when you move your cursor towards it.

How to configure

The toolbar is enabled by default.

To hide or customize individual toolbar items, edit the Google admin policy by including the following:

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                "ui" : {
                    "toolbar" : {
                            "menubar" :true,
                            "usb": true,
                            "fileTransfer":true,
                            "about":true,
                            "lock":true,
                            "disconnect":true,
                            "logoff":true,
                            "fullscreen":true,
                            "multitouch":true,
                            "preferences":true,
                            "gestureGuide":true
                                 }
                     }
                }
        }
    }
}

<!--NeedCopy-->

List of in-session toolbar options and their descriptions:

• “menubar”: Toolbar appears when set to true, and is hidden when set to false.
• “usb”: Opens the USB devices dialog box. Contains the list of devices that can be redirected into the session. To redirect a USB device, select an appropriate device and click Connect.
• “fileTransfer”: Secure file transfer functionality between a user device and a Citrix Virtual Apps and Desktops and Citrix DaaS session. You can upload and download files to and from a session and seamlessly access data.
• “about”: Displays the third-party licenses page and provides the version number.
• “lock”: Sends “Ctrl+Alt+Del” to the session.
• “disconnect”: Disconnects the session.
• “logoff”: Logs off from the session.
• “fullscreen”: Adjusts the session to full-screen mode. If the session is connected with multiple monitors, the multi-monitor icon appears on the menu bar rather than a full-screen icon. A Restore icon appears on the menu bar while in full-screen mode. To restore maximized mode, click Restore in the toolbar UI.
• “multitouch”: Remotes all gestures to the virtual session, and the app behaves based on the gestures it supports.
• “preferences”: Provides options to customize CEIP and display resolution settings.
• “gestureGuide”: Provides the guide for gestures in touch mode.

To hide the toolbar configuration using the configuration.js file:

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

1. Open the configuration.js file and set the menubar attribute to false.

You can also hide an individual icon to prevent it from displaying in the toolbar. For example, to hide the Ctrl+Alt+Del button in the toolbar:

1. Open the configuration.js file and set the lock attribute to false.

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 for the changes to take effect.

App switcher

About this feature

Shows the apps that are launched inside a session.

Note:

This option is only for kiosk mode.

The app switcher enables users to switch between multiple apps running in the same session. The app that is in focus is highlighted.

How to configure

To configure an app switcher, use the Google admin policy by including the following:

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                    "ui": {
                        "appSwitcher": {
                            "showTaskbar": true,
                            "showIconsOnly": false,
                            "autoHide": false
                                        }
                          }
                   }
        }
    }
}

<!--NeedCopy-->

List of appSwitcher options with their descriptions:

• “showTaskbar”: If set to true, the taskbar appears at the bottom of the session. To hide the taskbar, set this option to false.
• “showIconsOnly”: If set to true, the taskbar icons appear. By default, the option is set to false.
• “autoHide”: If set to true, the taskbar is automatically hidden. By default, the option is set to false.

Assistive cursor

About this feature

When a cursor isn’t visible inside a desktop session, you can enable an assistive cursor. Requires a session restart.

How to configure

The assistive cursor feature is disabled by default. To enable the assistive cursor feature, use the Google admin policy by including the following.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
            "engine_settings": {
                "ui": {
                    "assistiveCursor": true
                    }
                }
            }
        }
}

<!--NeedCopy-->

Note:

• If an administrator enables the assistive cursor as described earlier, the corresponding check box on the client-side setting is selected by default. To disable the feature, clear the check box.

• If an administrator disables the assistive cursor as described earlier, the check box is cleared and the feature is disabled.

Splash screen

About this feature

Citrix Workspace app displays a splash screen on the first launch with the text “Citrix Workspace app extends the capabilities of Citrix Receiver.”

How to configure

To configure the display of the splash screen, use the Google admin policy by including the following. It’s enabled by default. To disable, set the enabled attribute under the splash screen to false.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
            "engine_settings": {
                "ui": {
                    "splashScreen": true
                    }
                }
            }
        }
}

<!--NeedCopy-->

List of splash screen options with their descriptions:

• “splash screen”: If set to true, the splash screen appears.

DPI scaling

About this feature

Citrix Workspace app for ChromeOS allows the operating system to control the resolution of app and desktop sessions and supports DPI client scaling for app sessions on a single monitor.

Citrix Workspace app for ChromeOS supports DPI scaling by allowing you to set the VDA resolution on monitors that have a high pixel ratio.

The High DPI Scaling feature is disabled by default for app and desktop sessions. For better resolution on high DPI enabled devices, go to Settings and select the High DPI Scaling check box.

How to configure

You can configure the High DPI Scaling setting using the Google Admin policy only.

The DPI scaling feature Scale the session for monitors with high device pixel ratio is enabled by default.

To set the resolution for desktop sessions, go to the session toolbar. Select Preferences > Display Resolution > Use device pixel ratio for the correct resolution to be set on the VDA. When the resolution is set properly on the VDA, blurry text becomes crisper.

To enable or disable the feature, edit the Google Admin Console policy and set the value of scaleToDPI to true or false.

For example, to disable the feature, set scaleToDPI property to false.

{
    "settings": {
               "Value": {
                        "settings_version": "1.0",
                              "engine_settings": {
       "features" : {
       "graphics" : {
                "dpiSetting": {
                                "scaleToDPI": false
                                }
                             }
                       }
                    }
                }
            }
         }


<!--NeedCopy-->

Assistive cursor

About this feature

When a cursor isn’t visible inside a desktop session, you can enable an assistive cursor. Launch the next session for the setting to take effect.

How to configure

The assistive cursor feature is disabled by default.

To enable the feature, edit the Google Admin Console policy and set the value of the assistiveCursor property under ui to true and then restart the session.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
            "engine_settings": {
                "ui": {
                    "assistiveCursor": true
                    }
                }
            }
        }
    }

<!--NeedCopy-->

Note:

• If an administrator enables the assistive cursor as described earlier, the corresponding check box in the client-side setting is selected by default. To disable the feature, clear the check box.
• If an administrator disables the assistive cursor as described earlier, the check box is cleared and the feature disabled.

Native client

About this feature

Allows running native codes safely from a web browser that is independent of the user’s operating system. This functionality allows web apps to run at near-native speeds.

How to configure

To configure a native client, use the Google admin policy by including the following. By default, the native client option is enabled. To disable it, set the enabled attribute under the native client to false.

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                    "ui": {
                            "Nacl" : {
                                 "supportNacl" : true,
                                 "graphics": {
                                         "enable": true,
                                         "config": {
                                                "acceleration": 2
                                                    }
                                            },
                                 "video":    {
                                            "enable": true
                                             },
                                 "audio":    {
                                            "enable": true
                                             }
                            }
                    }
                }
        }
    }
}

<!--NeedCopy-->

List of native client options with their descriptions:

• “supportNacl”: Supports native client.
• “graphics”: Enables native client graphics module.
• “config”: Selects h264 hardware or software decoder.
  • Software = 0
  • Hardware = 1
  • Hardware with fallback = 2
  • AutoDetect = 3
• “video”: Enables webcam redirection.
• “audio”: Enables audio input or microphone redirection.

Unique ID and Asset ID

About this feature

A unique ID is applied as a prefix to the client name.

Citrix Workspace app uses an asset ID that administrators set through the Google Admin console as a client name for the sessions launched from enrolled Chromebooks.

How to configure

To configure an asset ID using the GUI, go to Device Management > Chrome > Devices Console, and add the Asset ID for the device.

To configure an asset ID and a unique ID manually, use the Google admin policy by including the following:

{
    "settings": {
        "Value": {
            "settings_version": "1.0",
                "engine_settings": {
                        "uniqueID" : {
                                 "prefixKey" : "CR-",
                                 "restrictNameLength" : true,
                                 "useAssetID": false
                                     }
                                  }
        }
    }
}

<!--NeedCopy-->

List of uniqueID options and their descriptions:

• “prefixKey”: The prefix to be used before the client name. The default value is CR.
• “restrictNameLength”: Enables or disables the name length of the prefixKey.
• “useAssetID”: Asset ID that is set as a client name for sessions that are launched from enrolled Chromebooks.

Feature limitations:

• You must have a Google admin policy that can be pushed. Otherwise, the current method of generating a unique client ID for managed Chromebooks remains in use.

• Do not enter a value that has more than 15 characters. Values longer than 15 characters are truncated to 15 characters.

Connection Center

About this feature

Connection Center helps application management in seamless sessions. This is done by providing a taskbar that lists all opened applications.

To launch the Connection Center, right-click the Citrix Workspace icon and then select Connection Center.

Using the Connection Center, you can select an application and:

1. Display devices.
2. Send a Ctrl+Alt+Del command.
3. Disconnect from a session.
4. Logoff from the session.

You can also terminate an app using the Connection Center by selecting the radio button of the corresponding application and clicking Terminate.

Seamless window integration

About this feature

Citrix Workspace app for ChromeOS improves the user experience by adding seamless integration of multiple apps hosted in separate windows within an active session. Using this functionality, Citrix Workspace app for ChromeOS enables you to launch applications in an independent user interface compared as opposed to launching all apps for a session in a single window.

Seamless applications can be hosted in separate windows. With this functionality, remote applications are run natively on the client device.

Feature limitations:

• Extra entries appear in the Chrome task bar. Click any of the entries to bring the selected session to the front.
• All opened apps in an active session run in a single window. Focusing on one app in an active session brings that window into focus along with all other apps belonging to that session.

Use the seamless app icon on the taskbar to quickly move between apps:

Tip:

All apps in one session run in a single window. When moving an app to a second monitor, all apps that are part of that session move to the second monitor.

Reload store

About this feature

In Citrix Workspace app for ChromeOS window, a button is added for reload operation. When you click the button, the cookies of the store get cleared and the store page is reloaded.

Audio

About this feature

You can use a USB headset within a session to speak and to listen. You can also use buttons on the USB headset (such as mute and skip). The user experience is enriched by providing smooth audio output.

Adaptive audio

With Adaptive audio, you don’t need to configure the audio quality policies on the VDA. Adaptive audio optimizes settings for your environment. It replaces legacy audio compression formats to provide an excellent user experience.

For more information, see Adaptive Audio in the Citrix Virtual Apps and Desktops documentation.

Feature attributes

There are two feature attributes:

• EnableAdaptiveAudio: Set the value to true to enable the adaptive audio feature. Set the value to false to disable the feature.

• EnableStereoRecording: Stereo recording is an optional feature. By default, this feature is disabled. Set the attribute EnableStereoRecording value to true to enable stereo recording or set the value to false to disable the feature. This feature can be supported only when the adaptive audio feature is enabled. When the EnableStereoRecording attribute is set to true, the stereo recording is supported with echo cancellation disabled.

How to configure

You can configure the adaptive audio feature in the following ways:

• Configuration.js
• Google Admin Policy

Configuration.js

To configure adaptive audio using the configuration.js file, do the following:

1. Locate the configuration.js file in the ChromeApp root folder.

2. Edit this file to configure the adaptive audio feature.

   Notes:

   • Citrix recommends that you back up the configuration.js file before making changes.
   • Citrix recommends editing the configuration.js file, only if the Citrix Workspace app for ChromeOS is repackaged for users.
   • Administrator-level credentials are required to edit the configuration.js file.

3. Set the default value of EnableAdaptiveAudio to true. Set the default value of EnableStereoRecording to false.

   Following is an example of JSON data:

   "features" : {
       "audio" : {
       "EnableAdaptiveAudio": true
               }
   }
   
   "features" : {
       "audio" : {
           "EnableStereoRecording": false
               }
   }
   <!--NeedCopy-->
   

4. Save the changes.

Note:

• To disable the feature, set the EnableAdaptiveAudio attribute to false.

Google admin policy

On the on-premises deployment, administrators can enable the adaptive audio feature using the Google Admin Policy as follows:

1. Sign in to the Google Admin Policy.
2. Go to Device management > Chrome Management > User Settings.

3. Add the following strings to the policy.txt file under the engine_settings key.

   Following is an example of JSON data:

   "features" : {
       "audio" : {
           "EnableAdaptiveAudio": {
               "type": "boolean"}
                       }
                   }
   
   "features" : {
       "audio" : {
           "EnableStereoRecording": {
               "type": "boolean"}
                   }
               }
   <!--NeedCopy-->
   

4. Save the changes.

Plug and play audio device support

Previously, only a single audio playback and recording device was supported and displayed as Citrix HDX Audio irrespective of the real device name.

Starting with the 2301 version, we support multiple audio devices and redirect them to VDA. Now, when you redirect USB audio devices, you can view the real name of the audio device under the Sound settings > Playback and Sound settings > Recording on the VDA. The list of devices on the VDA is dynamically updated whenever an audio device is plugged in or removed.

Note:

By default, this feature is enabled.

Configuration

You can configure this feature in one of the following ways:

• Configuration.js
• Google Admin Policy

Configuration.js

To disable plug and play audio device support using the configuration.js file, do the following:

1. Locate the configuration.js file in the ChromeApp root folder.

2. Edit the file to configure the plug and play audio device support feature.

   Notes:

   • Citrix recommends that you back up the configuration.js file before making changes.
   • Citrix recommends editing the configuration.js file, only if the Citrix Workspace app for ChromeOS is repackaged for users.
   • Administrator-level credentials are required to edit the configuration.js file.

3. Set the value of AudioRedirectionV4 to false. Following is an example of JSON data:

       "features" : {
           "audio" : {
             "AudioRedirectionV4": false
                   }
           }
   <!--NeedCopy-->
   

4. Save the changes.

Google admin policy

On the on-premises deployment, administrators can disable the plug and play audio device feature using the Google Admin Policy as follows:

1. Sign in to the Google Admin Policy.
2. Go to Device management > Chrome Management > User Settings.

3. Add the following strings to the .txt file under the engine_settings key.

   Following is an example of JSON data:

       "features" : {
           "audio" : {
             "AudioRedirectionV4": false
                   }
           }
   <!--NeedCopy-->
   

4. Save the changes.

Known Limitations

• On the VDA, the name of the built-in audio device is in English only. The issue occurs when you use ChromeOS-based devices. [RFHTMCRM-8667]

Webcam

About this feature

Citrix Workspace app for ChromeOS provides an enhancement to webcam redirection functionality. H.264 hardware encoding for webcam input helps reduce CPU load and increases battery efficiency for Chromebook devices. These devices have encoders for H.264, which uses Intel functionality through the PPB_VideoEncoder API.

Citrix Workspace app for ChromeOS supports webcam redirection for both 32-bit and 64-bit applications.

Session sharing

About this feature

For session sharing, the applications must be hosted on the same machine and must be configured in seamless window mode with the same settings for parameters, such as window size, color depth, and encryption. Session sharing is enabled by default when a hosted application is made available.

Host to client redirection

About this feature

Content redirection allows you to control whether users access information by:

• using applications that are published on servers or
• running applications locally on user devices.

Host to client redirection is one type of content redirection. It’s supported only on Server OS VDAs (not Desktop OS VDAs) with Citrix XenApp and XenDesktop versions 7.15 LTSR and later.

For more information, see Host to client redirection - XenApp and XenDesktop in the XenApp and XenDesktop documentation.

When host to client redirection is enabled, URLs are intercepted on the server VDA and sent to the user device. Citrix Workspace app for ChromeOS displays a dialog prompting the user to select whether to open the URL within the session or on the local device. The dialog appears for every URL.

When host to client redirection is disabled, users open the URLs with web browsers or multimedia players on the server VDA. When host to client redirection is enabled, users can’t disable it.

Host to client redirection was previously known as server to client redirection.

For more information, see General content redirection in the Citrix Virtual Apps and Desktops documentation.

Enhancements to URL redirection

Previously, when host-to-client redirection was enabled, URLs were intercepted on the server VDA and sent to the user’s device. Citrix Workspace app for ChromeOS displayed a dialog box asking the user to select whether to open the URL within the session or on the local device. The dialog box appeared for every URL.

Starting with 2305, administrators can configure the URL redirection to open the links in the local device without additional dialog boxes. This enhancement improves the user experience.

Note:

• By default, this feature is disabled.

How to configure

You can enable this feature in one of the following ways:

• Configuration.js
• Google Admin Policy

Configuration.js

To enable this feature using the configuration.js file, do the following:

1. Locate the configuration.js file in the ChromeApp root folder.

   Notes:

   • Citrix recommends that you back up the configuration.js file before making changes.
   • Citrix recommends editing the configuration.js file, only if the Citrix Workspace app for ChromeOS is repackaged for users.
   • Administrator-level credentials are required to edit the configuration.js file.

2. Edit the configuration.js file and set the default value of forceOpenInClient to true. Following is an example of JSON data:

   {
   "features": {
           "UrlRedirection": {
           "forceOpenInClient": true
               }
       }
   }
   <!--NeedCopy-->
   

3. Save the changes.

Google Admin Policy

On the on-premises deployment, administrators can enable this feature using the Google Admin Policy as follows:

1. Sign in to the Google Admin Policy.
2. Go to Device management > Chrome Management > User Settings.

3. Add the following strings to the policy.txt file under the engine_settings key. Following is an example of JSON data:

    {
      "features": {
        "UrlRedirection": {
           "forceOpenInClient": true
                     }
               }
   }
   <!--NeedCopy-->
   

4. Save the changes.

Security settings

How to configure

Citrix recommends using stores that are secure. Besides, it’s a good practice to have HTTP strict transport security (HSTS) setting enabled for secure stores.

Do the following steps to enable the HSTS setting:

1. In Citrix StoreFront, under Stores, click the link of the particular store to enable the security settings.
2. The Manage Receiver for Web Sites dialog box appears.
3. Click Configure.
4. The Edit Receiver for Web site dialog box appears.
5. Click the Advanced Settings tab and select Enable strict transport security.

Battery status indicator

The battery status of the device appears in the notification area within the virtual desktop session. Previously, the battery status indicator wasn’t visible in the session, which sometimes led to a loss of productivity when the laptop shuts down after the battery runs out.

This feature is supported only on VDA versions 7.18 and later.

Note:

• With Microsoft Windows 10 VDA, the battery status indicator might take about 1 or 2 minutes to appear.

Support for virtual desktops in multiple-monitor setups

You can now use your virtual desktop in full-screen mode across a subset of available monitors. Previously when you selected multi-monitor mode from the toolbar, the virtual desktop spanned across all available monitors. You can now drag your virtual desktop to span two monitors (out of more than two) and then select multi-monitor mode. A typical use case for this scenario is, when you choose to run a video conferencing app on your native device monitor and want to view your virtual desktop contents in full-screen across your other two monitors during the call.

Note:

• To use this feature, under General settings > Multi-monitor settings > select Use all the monitors to span display option.

Support for Dual Tone Multi Frequency (DTMF) with Microsoft Teams

Citrix Workspace app now supports Dual Tone Multi Frequency (DTMF) signaling interaction with telephony systems (for example, PSTN) and conference calls in Microsoft Teams. This feature is enabled by default.

Workspace with intelligence

With this release, Citrix Workspace app is optimized to take advantage of the Workspace intelligence features. This version unifies user workflows and provides an activity feed displaying relevant information. The microapps streamline end user workflows and approvals. For more information, see Workspace Intelligence Features - Microapps.

Troubleshooting enhancement

Citrix Workspace app supports log collection for ongoing virtual desktop and app sessions. Previously, you can collect logs only for sessions launched after selecting Start Logging during an ongoing session. Now, the logs are collected for the ongoing and later sessions until you select Stop Logging.

Email-based store discovery

You can now use your email ID to access the Citrix Workspace app without the need to memorize the Store URL. The stores assigned to your account are automatically populated. Navigate to Accounts > Store URL or Email address drop-down menu to view the list of stores associated with your email.

Note:

You can still use the store URL to sign in.

As an administrator, to maintain and auto-populate the store accounts, see Citrix Cloud API Overview as a prerequisite.

For more information, see Global App Configuration Service.

Generic client IME for east asian languages

The Generic Client Input Method Editor (IME) feature enhances the input and display experience with Chinese, Japanese, and Korean (CJK) language characters. This feature allows you to compose CJK characters at the cursor position when you are in a session. The feature is available for the Windows VDA and Linux VDA environments.

Generally, IME displays user interface (UI) components such as a candidate window and a composition window. The composition window includes the composition characters and composition UI elements. For example, underline and background color. The candidate window displays the candidate list.

The composition window enables you to choose between the confirmed characters and the composing characters. The composition window and the candidate window move with the input cursor. As a result, the feature gives an enhanced input of characters at the cursor location in the composition window. In addition, it gives an improved display in the composition and the candidate window.

Prerequisites:

• For Linux VDA, enable Client keyboard layout sync and IME improvement policy.
• For Windows VDA, enable Unicode Keyboard Layout Mapping, Client Keyboard Layout Sync, and IME Improvement policies.
• Use Citrix Linux VDA version 2012 and later. For Citrix Windows VDA, all the currently available Windows VDA versions support the generic client IME feature.
• The browser language must be Japanese, Chinese (Simplified), Chinese (Traditional), or Korean.
• Use Google Chrome or Mozilla Firefox.

Feature limitation:

• Character composition is unsuccessful within the Microsoft Excel cell. The issue happens when the cell is selected using a mouse click. [RFHTMCRM-6086]
• Multi-monitor sessions don’t support the Generic client IME feature. Instead, use Server IME. To enable the Server IME:
  1. Change the VDA or the server keyboard language to Chinese, Japanese or Korean (CJK) as wished.
  2. Change the client or the Chromebook keyboard language to English.

Known Issue in the feature:

• When Citrix IME isn’t added to the VDA desktop session, you might be unable to type the IME characters. The issue happens intermittently on VDA versions 2202 and earlier. [HDX-36748]

Configuration:

Starting with version 2209, the Generic Client IME feature is enabled by default.

As an administrator, you can disable the feature using the configuration.js file on the StoreFront server usually at ProgramFiles%\Citrix\Receiver StoreFront\HTML5Client. To disable the feature, navigate to appPrefs > chromeApp > feature > ime > set genericIME to false.

For example,

    "appPrefs":{
        "chromeApp":{
            "features" : {
                    "ime" : {
                    "genericIME": false
                }
      }
    }
    }
<!--NeedCopy-->

• As an administrator, you can disable the feature using the Google Admin Policy console by setting genericIME to false. For example,

    {
    "settings": {
    "Value": {
      "settings_version": "1.0",
      "engine_settings": {
        "features": {
          "ime": {
            "genericIME": false
          }
        }
      }
    }
    }
}
<!--NeedCopy-->

Service continuity

Service continuity removes or reduces the dependency on the availability of components that are involved in the connection process. You can launch the Citrix Virtual Apps and Desktops and Citrix DaaS regardless of the health status of the cloud services. In other words, service continuity allows you to connect to the DaaS apps and desktops during outages. As a prerequisite, your device must maintain a network connection to a resource location.

For more information, see the Service continuity section in the Citrix Workspace documentation.

Browser content redirection

Browser Content Redirection (BCR) redirects the remote browser’s content to the client’s device. BCR is a frameless-borderless web browser that runs within the remote desktop window and covers (overlays) the remote (VDA) browser’s content area.

BCR redirects the contents of a web browser to a client device, and creates a corresponding browser embedded within Citrix Workspace app. This feature offloads network usage, page processing, and graphics rendering to the endpoint. Doing so improves the user experience when browsing demanding webpages, especially webpages that incorporate HTML5 or WebRTC. Only the viewport (the user’s visible area of a webpage) is redirected to the endpoint. Browser content redirection doesn’t redirect the user interface (the address bar, toolbar, and so forth) of the browser on the VDA.

In other words, BCR provides the ability of rendering webpages in the allow list on the client side. This feature uses Citrix Workspace app to instantiate a corresponding rendering engine on the client side, which fetches the HTTP and HTTPS content from the URL.

For more information on how to set up the allow list see:

• Browser content redirection Chrome extension
• Browser content redirection policy settings

Known issues in the feature

• On BCR overlay, when you open a website link in a new tab, it opens in the client browser instead of the session browser. [HDX-43206]

Known limitations in the feature

• This feature doesn’t support:

  • Server fetch and client render scenario.
  • Integrated Windows Authentication (IWA) webserver.
  • Multimonitor feature.
• When you upload or download a file to some of the BCR-redirected websites, the ChromeOS file picker appears instead of a VDA session file picker. [HDX-43207]
• Printing is not supported from BCR-redirected pages.

Composite USB redirection

Previously, when a composite USB device was connected to the local device, it could only be used as a single device through USB redirection. The disadvantage was that the interfaces like audio and video also got redirected through USB, despite optimized channels. The interfaces weren’t separate and due to this incapability, administrators could not decide which component to redirect through USB and which ones to redirect through the optimized virtual channel (like audio interface) to achieve the best performance.

Starting from the 2211 release, administrators can configure if certain interfaces of the device are redirected to the session through USB redirection or not. The end user can now select and redirect a specific constituent interface of a composite USB device to the Citrix Workspace app session through USB redirection.

About composite USB redirection

USB 2.1 and later supports the notion of USB composite devices where multiple child devices share a single connection with the same USB bus. Such devices employ a single configuration space and shared bus connection where a unique interface number 00-ff is used to identify each child device. Such devices are also not the same as a USB hub which provides a new USB bus origin for other independently addressed USB devices for connection.

Composite devices found on the client endpoint can be forwarded to the virtual host as either:

• a single composite USB device, or
• a set of independent child devices (split devices)

When a composite USB device is forwarded, the entire device becomes unavailable to the local device. Forwarding also blocks the local usage of the device for all applications on the local device, including the Citrix Workspace app.

Consider a USB headset device with both an audio device and HID button for mute and volume control. If the entire device is forwarded using a generic USB channel, the device becomes unavailable for redirection over the optimized HDX audio channel. However, you can achieve a better performance when the audio is sent through an optimized HDX audio channel when compared to a generic channel.

To resolve these issues, Citrix recommends that you split the composite device and forward only the child interfaces that use a generic USB channel. Such a mechanism ensures that the other child devices are available for use by applications on the local device, including, the Citrix Workspace app that provides optimized HDX experiences. This method allows the required devices to be forwarded and available to the remote session.

How to enable this feature

You can enable this feature in the following ways:

• Configuration.js
• Global App Configuration service
• Google Admin Policy

Configuration.js

To configure composite USB redirection using the configuration.js file, do the following:

1. Locate the configuration.jsfile in the ChromeApp root folder.

2. Edit the configuration.js file to configure the composite USB redirection feature.

   Notes:

   • Citrix recommends that you back up the configuration.js file before making changes.
   • Citrix recommends editing the configuration.js file, only if the Citrix Workspace app for ChromeOS is repackaged for users.
   • Administrator-level credentials are required to edit the configuration.js file.

3. Set enableCompositeDeviceSplit to true.

Following is an example of JSON data:

```
{
    "features": {
        "usb": {
            "enableCompositeDeviceSplit": true
        }
    }
}
<!--NeedCopy--> ```

1. Save the changes.

Note:

• To disable the feature, set the enableCompositeDeviceSplit attribute to false.

Global App Configuration service

On the cloud setup, administrators can enable the composite USB redirection feature by setting the enableCompositeDeviceSplit attribute to True in the Global App Configuration service.

For more information, see Global App Configuration service documentation.

Google admin policy

On the on-premises deployment, administrators can enable the composite USB redirection feature using the Google Admin Policy as follows:

1. Sign in to the Google Admin Policy.
2. Go to Device management > Chrome Management > User Settings.

3. Add the following strings to the policy.txt file under the engine_settings key. Following is an example of JSON data:

   {
       "features": {
           "usb": {
               "enableCompositeDeviceSplit": true
           }
       }
   }
   <!--NeedCopy-->
   

4. Save the changes.

Configuration

Prerequisites:

• White list USB Devices with VID:PID values and enable policy for USB device redirection on Delivery Controller. For more information, see the knowledge center article CTX200825.
• This feature works on managed devices and not on BYOD.

To enable the auto-detection of the USB:

1. Go to Google Admin Policy settings.
2. Select the WebUSB API allowed devices option.
3. Enter the Citrix Workspace app for the ChromeOS extension ID. For example, chrome-extension://haiffjcadagjlijoggckpgfnoeiflnem.

4. Add the VID and PID of the device as follows:

   

   After adding the VID and PID values, the Citrix Workspace app can now automatically detect the devices in the session.

5. Apply the Google Admin Policy. Following is an example of JSON data:

   {
   "settings": {
           "Value": {
           "settings_version": "1.0",
               "device_settings": {
                   "deviceRules": {
                               "allow": [{
                                       "vid": "046D",
                                       "pid": "C31C",
                                       "split": true,
                                       "interfaceClass": ["video", "hid"]
                                       },
                                       {
                                       "vid": "04E8",
                                       "pid": "A051",
                                       "split": true
                                       }],
                                   "deny": [{
                                       "vid": "0911",
                                       "pid": "0C1C",
                                       "split": true,
                                       "interfaceClass": ["audio"]
                                       }],
                                   "autoRedirect": [{
                                       "vid": "47F",
                                       "pid": "C053",
                                       "split": true,
                                       "interfaceClass": ["hid"]
                                       }]
                                   }
                           }
                   }
           }
   }
   <!--NeedCopy-->
   

6. Save the changes.

Device rules

Citrix Workspace app uses the device rules to decide, which USB devices to allow or prevent from forwarding to the remote session.

Following are the explanation of the keywords:

• allow: This section includes the list of devices and their child interfaces that can be redirected to the session.
• deny: This section includes the list of devices and their child interfaces that can’t be redirected to the session.

• autoRedirect: This section includes the list of devices and their child interfaces that can be auto-redirected to the session through USB redirection.

  Note:

  • Each object represents a device with mandatory ‘vid’ and ‘pid’ values of the USB device. It is optional to have ‘split’, and ‘interfaceClass’ values.

• vid, pid (mandatory): Represents Vendor ID (VID) and Product ID (PID) of the USB device. Enter the values in Hexa decimal format.
• split (optional): Expects a boolean value that indicates whether the device to be split into child interfaces or not.
• interfaceClass (optional): Represents USB interface class. The allowed values are audio, video, hid, printer, storage, and so on.

Following is an example of JSON data:

"deviceRules": {

    "allow": [
        {"vid": "11","pid": "22",  "split":true, "interfaceClass":["audio","video"]} //split device and allow redirection of 'audio' & 'video' interfaces.
    ],

    "deny": [
        {"vid": "33","pid": "44"},  //deny redirection of this whole device with vid= 33 & pid = 44, including all of its interfaces.
        {"vid": "77","pid": "88","split":true,"interfaceClass":["audio"]}    //split device and deny the redirection of 'audio' interface only; remaining interfaces(if any) are redirected through USB.
    ],

    "autoRedirect": [
    {"vid": "55","pid": "66"}, //auto redirect the device when it's connected.
    {"vid": "55","pid": "66","split":true,"interfaceClass":["hid"]} //split device and auto redirect only the 'hid' interface when the device is connected.
    ]
}
<!--NeedCopy-->

How to use this feature

To use the composite USB redirection feature:

1. Click the USB icon from the toolbar.

   

   If there are no USB devices connected, the following pop-up appears:

   

2. Connect a USB device to your local machine. The following pop-up might appear:

   

3. Click USB Devices to view and redirect the USB constituent. After a successful connection, the Citrix Workspace app detects the USB. For each USB constituent interface, you see a drop-down menu. The two options are:

   • In-session and local machine access (Optimized): select this option if you want to access the USB on your device and in a session.
   • In-session access (Generic): select this option if you want to access the USB only in the session. For better performance, select In-session and local machine access (Optimized) option.

   

4. Select Connect for redirecting the interface.

   

   Upon successful redirection, the status changes to Connected.

Notes:

• To add a USB device manually, click Add Device. The Chrome picker dialog appears that lists the USB devices. You can select the device from the list.

• If a USB device connection is denied, the following error message appears:

  “Your administrator has blocked the newly inserted device. Contact your organization’s administrator for assistance.

How to transfer the USB interface between the sessions

When you click the USB icon from the toolbar, a list of USB devices that are connected to your sessions appears. If the USB device is already in use in a different session you can see that the USB constituent shows Connected to another session status.

To redirect to the current session, select Connect which is placed opposite to the USB constituent. The status changes accordingly.

Composite USB automatic redirection settings

Previously, there was no option related to USB automatic redirection settings to set the end user preferences. As administrators control these policies, the end user has to manually redirect required USB devices on every session launch.

Starting with the 2301 version, the end user can select a preference for auto-redirection for any USB device within a Virtual Desktop session. Citrix Workspace app now provides app-level settings, where the end user can control the USB auto-redirection. The end user can set preferences and can save the setting across session launches.

There are two options: one at the session launch and the other while the session is ongoing.

Note:

• This feature supports on-premises and cloud deployments and is available only for managed Chrome users.