Features in Technical Preview

Features in Technical Preview are available to use in non-production or limited production environments, and to give customers an opportunity to share feedback. Citrix does not accept support cases for features in technical preview but welcomes feedback for improving them. Citrix might act on feedback based on its severity, criticality, and importance.

List of features in Technical Preview

The following table lists the features in technical preview. These features are request-only preview features. To enable and provide feedback for any of these features, fill out the respective forms.

Title	Available from version	Enablement form (Click the icon)	Feedback form (Click the icon)
Enhanced display control with multi-monitor selector	2411	You can configure the feature
Support to share app window during screen sharing	2408	You can configure the feature
Secure HDX	2408	You can configure the feature
Accessibility and TalkBack	2307	You can configure the feature

Enhanced display control with multi-monitor selector

Starting with version 2411, a new Multi-monitor icon has been added to the toolbar, which appears only when more than one screen is connected. The Multi-Monitor Selector (MMS) allows users to choose which displays to use in full-screen mode for desktop sessions only, and not for seamless sessions.

This feature enhances the flexibility and usability of multi-monitor setups in desktop sessions, providing a more tailored and efficient user experience.

Note:

This feature is disabled by default.

Prerequisites

Enable the new toolbar feature. For more information, see Improved in-session toolbar.

Multi-monitor toolbar icon

The Multi-monitor toolbar icon includes three drop-down menu options for desktop sessions in full-screen mode:

• Extend to all displays: The session spans across all the available monitors.

• Custom Layout: This option opens a custom monitor selector displaying the monitor layout. With this feature, you can configure how your session appears across the monitors. Users can click the rectangles in the selector to choose which screens to use and then click Apply to span the session on those monitors. The layout box arrangement depends on how the monitors are connected.

  

• Fullscreen: The session layout changes to full-screen mode in the current monitor.

Known issues in the feature

• In a multi-monitor setup, when you enable Unified Desktop Mode (UDM) and start a desktop session to span across the monitors, the session becomes unresponsive. [RFHTMCRM-14317]

How to configure

You can configure the feature in the following way.

Google Admin Policy

To use this feature, you must enable both the new toolbar and multi-monitor custom layout configurations. For managed devices and users, administrators can enable the 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 JSON strings to the policy.txt file under the engine_settings key.

   Note:

   You can apply this configuration on the following as well:

   • Device > Chrome > Apps and extensions > Users and browsers > Search for the extension > Policy for extensions.
   • Device > Chrome > Apps and extensions > Managed guest sessions > Search for the extension > Policy for extensions.

   Make sure you set the attributes switchToNewToolbar and enableMultiMonitorCustomLayout to true.

   The following is an example of JSON data:

   {
       "settings": {
           "Value": {
               "settings_version": "1.0",
               "engine_settings": {
                   "ui": {
                       "toolbar": {
                           "switchToNewToolbar": true
                       }
                   },
                   "features": {
                       "graphics": {
                           "enableMultiMonitorCustomLayout": true
                       }
                   }
               }
           }
       }
   }
   
    

4. Save the changes.

Limitations

This feature is not supported for sessions launched in Kiosk mode.

Support to share app window during screen sharing

This feature is in technical preview from 2408 release.

Previously, the optimized Microsoft Teams call didn’t support sharing an app window running on the virtual session.

Starting from the 2408 version, optimized Microsoft Teams supports screen sharing of specific apps running in the virtual session rather than the entire desktop, which reduces the exposure of information.

For more information about how to share a specific app, feature limitations and more, see App sharing in the Citrix Virtual Apps and Desktops documentation.

Notes:

• This feature is disabled by default.
• To enable the feature, follow the configuration steps.
• To provide feedback about this feature, click the Google form.
• The minimum VDA version must be at least 2109.

Known limitations in the feature

• This feature might not work in kiosk multi-monitor mode.
• This feature isn’t supported in legacy graphics mode.

How to configure

You can configure the feature in the following way.

Google Admin Policy

For managed devices and users, administrators can enable the 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.

   Note:

   You can apply this configuration on the following as well:

   • Device > Chrome > Apps and extensions > Users and browsers > Search for the extension > Policy for extensions.
   • Device > Chrome > Apps and extensions > Kiosks > Search for the extension > Policy for extensions.
   • Device > Chrome > Apps and extensions > Managed guest sessions > Search for the extension > Policy for extensions.

   Make sure you set the attribute appSharing to true.

   The following is an example of JSON data:

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

4. Save the changes.

Secure HDX

This feature is in technical preview from 2408 release.

Secure HDX is an Application Level Encryption (ALE) solution that prevents any network elements in the traffic path from being able to inspect the HDX traffic. It does this function by providing true End-to-End Encryption (E2EE) at the application level between the Citrix Workspace app (client) and the VDA (session host) using AES-256-GCM encryption.

Prerequisites

The minimum VDA version must be 2402 for this feature to function.

Notes:

• Secure HDX is in technical preview.
• This feature isn’t recommended for use in production environments.
• To request access for this feature, fill out this form.

Configurations

Secure HDX is disabled by default. You can configure this feature using the Secure HDX setting in the Citrix policy:

• Secure HDX: Defines whether to enable the feature for all sessions, only for direct connections, or disable it.

For more information, see Secure HDX in the Citrix DaaS documentation.

Accessibility and TalkBack

This feature is in technical preview from 2307 release.

Citrix Workspace app provides an enhanced user experience with the TalkBack feature. The TalkBack feature helps end users who have difficulty seeing the screen. The narrator reads the screen elements aloud when using the UI.

To use the ChromeOS narrator (ChromeVox), end users must use the keyboard shortcut Ctrl+Alt+Z to turn on the narrator. Use the same key combination to turn off the narrator.

Note:

• By default, this feature is disabled.

How to configure

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

• Configuration.js
• Google Admin Policy

Configuration.js

To enable the accessibility 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 add the accessibility attribute. Set the enable attribute to true.

   The following is an example of JSON data:

   'features' :
   {
       'accessibility': {
             'enable': true
           },
   }
   
    

3. Save the changes.

Google Admin Policy

For managed devices and users, administrators can enable the 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' :
   {
       'accessibility': {
             'enable': true
           },
   }
   
    

4. Save the changes.

Technical Preview to General Availability (GA)