ConfigureWhen using the Citrix Workspace app for Windows, the following configurations allow you to access their hosted applications and desktops. Show
Administrator tasks and considerationsThis article discusses the tasks and considerations that are relevant for administrators of Citrix Workspace app for Windows. Feature flag managementIf 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. 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 via 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
List IP addresses in an allow listIf 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 know 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. LaunchDarkly system requirementsVerify if the apps can communicate with the following services if you have split tunneling on the Citrix ADC set to OFF for the following services:
Disabling LaunchDarkly serviceYou can disable the LaunchDarkly service by using a Group Policy Object (GPO) policy.
You can also disable the LaunchDarkly service using the registry.
Group Policy Object administrative templateWe recommend that you use the Group Policy Object administrative template to configure rules for:
You can use the Citrix recommends using the Windows Group Policy Object (GPO) administrative template to configure Citrix Workspace app. The installation directory includes
If Citrix Workspace app is installed with VDA, the ADMX/ADML files are typically found in the If Citrix Workspace app is installed without the VDA, the ADMX/ADML files are typically found in the See the following table for information about Citrix Workspace app template files and their respective locations.
To add the receiver.admx/adml template files to the local GPO: You can use .adm template files to configure both the Local and the domain-based GPO. Refer to the Microsoft MSDN article about managing ADMX files here. After installing Citrix Workspace app, copy the following template files:
App protection
App protection is an add-on feature that provides enhanced security when using Citrix Virtual Apps and Desktops and Citrix DaaS (formerly Citrix Virtual Apps and Desktops service). The feature restricts the ability of clients to compromise with keylogging and screen capturing malware. App protection prevents exfiltration of confidential information such as user credentials and sensitive information on the screen. The feature prevents users and attackers from taking screenshots and from using keyloggers to glean and exploit sensitive information. App protection requires that you install an add-on license on your License Server. A Citrix Virtual Desktops license must also be present. For information on Licensing, see the Configure section in the Citrix Virtual Apps and Desktops documentation. Requirements:
Prerequisites:
You can include the app protection component with Citrix Workspace app either:
On-premises HDX session protection: Two policies provide anti-keylogging and anti-screen-capturing functionality in a session. These policies must be configured through PowerShell. No GUI is available for the purpose.
For information on app protection configuration on Citrix Virtual Apps and Desktops and Citrix DaaS, see App protection. App protection - Configuration in Citrix Workspace app
During the Citrix Workspace app installation, you can include app protection using one of the following methods:
GUIDuring the Citrix Workspace app installation, use the following dialog to include the app protection component. Select Enable app protection and then click Install to continue with the installation.
Command-line interfaceUse the command-line switch The following table provides information on screens protected depending on deployment:
When you’re taking a screenshot, only the protected window is blacked out. You can take a screenshot of the area outside the protected window. However, if you’re using the PrtScr key to capture a screenshot on a Windows 10 device, you must minimize the protected window. Expected Behavior: The expected behavior depends upon the method by which users access the StoreFront that has the protected resources.
Enhancement to app protection configurationPreviously, the authentication manager and the Self-Service plug-in dialogs were protected by default. Starting with Version 2012, you can configure the anti-keylogging and anti-screen-capturing functionalities separately for both the authentication manager and Self-Service plug-in interfaces. You can configure the functionalities by using a Group Policy Object (GPO) policy.
Configuring app protection for the Self-Service plug-in interface:
Configuring app protection for authentication manager:
App protection error logs: Starting with Version 2103, the app protection logs are collected as part of Citrix Workspace app logs. For more information about log collection, see Log collection. You do not need to install or use a third-party app to collect the app protection logs specifically. However, DebugView can still be continued to be used for log collection. The app protection logs are registered to the debug output. To collect these logs, do the following:
The command indicates the following:
Uninstalling the app protection component: To uninstall the app protection component, you must uninstall Citrix Workspace app from your system. Restart the system for the changes to take effect.
Known issues or limitations:
Application CategoriesApplication Categories allow users to manage collections of applications in Citrix Workspace app. You can create application groups for applications shared across different delivery groups or used by a subset of users within delivery groups. For more information, see Create application groups in the Citrix Virtual Apps and Desktops documentation. Improved ICA file securityThis feature provides enhanced security while handling ICA files during a virtual apps and desktops session launch. Citrix Workspace app lets you store the ICA file in the system memory instead of the local disk when you launch a virtual apps and desktops session. This feature aims to eliminate surface attacks and any malware that might misuse the ICA file when stored locally. This feature is also applicable on virtual apps and desktops sessions that are launched on workspace for Web ConfigurationICA file security is also supported when Citrix Workspace or StoreFront is accessed through the web. Client detection is a prerequisite for the feature to work if it’s accessed through the web. If you’re accessing StoreFront using a browser, enable the following attributes in the web.config file on StoreFront deployments:
When you sign in to the store through the browser, click Detect Workspace App. If the prompt doesn’t appear, clear the browser cookies and try again. If it’s a Workspace deployment, you can find the client detection settings by navigating to Accounts settings > Advanced > Apps and Desktops Launch Preference. You can take extra measures so that sessions are launched only using the ICA file stored on system memory. Use any of the following methods:
Using the GPO: To block session launches from ICA files that are stored on the local disk, do the following:
Using the Global App Config Service: You can use Global App Config Service from Citrix Workspace app 2106. To block session launches from ICA files that are stored on the local disk, do the following: Set the Block Direct ICA File Launches attribute to True. For more information about Global App Config Service, see Global App Config Service documentation. Using workspace for web: To disallow ICA file download on the local disk when using workspace for Web, do the following: Run the PowerShell module. See Configure DisallowICADownload.
Log collectionLog collection simplifies the process of collecting logs for Citrix Workspace app. The logs help Citrix to troubleshoot, and, in cases of complicated issues, provides support. You can collect logs using the GUI. Collecting logs:
HDX adaptive throughputHDX adaptive throughput intelligently fine-tunes the peak throughput of the ICA session by adjusting output buffers. The number of output buffers is initially set at a high value. This high value allows data to be transmitted to the client more quickly and efficiently, especially in high latency networks. Provides better interactivity, faster file transfers, smoother video playback, higher framerate, and resolution results in an enhanced user experience. Session interactivity is constantly measured to determine whether any data streams within the ICA session are adversely affecting interactivity. If that occurs, the throughput is decreased to reduce the impact of the large data stream on the session and allow interactivity to recover. This feature is supported only on Citrix Workspace app 1811 for Windows and later.
Adaptive transportAdaptive Transport is a mechanism in Citrix Virtual Apps and Desktops and Citrix DaaS that allows to use Enlightened Data Transport (EDT) as the transport protocol for ICA connections. For more information, see Adaptive transport section in the Citrix Virtual Apps and Desktops documentation. Advanced Preferences sheetYou can customize Advanced Preferences sheet’s availability and contents present in the right-click menu of the Citrix Workspace app icon in the notification area. Doing so ensures that users can apply only administrator-specified settings on their systems. Specifically, you can:
You can hide the Advanced Preferences sheet by using the Citrix Workspace app Group Policy Object (GPO) administrative template:
Hiding specific settings from the Advanced Preferences sheetYou can hide specific user-configurable settings from the Advanced Preferences sheet by using the Citrix Workspace app Group Policy Object administrative template. To hide the settings:
The following table lists the options that you can select and the effect of each:
You can hide the following specific settings from the Advanced Preferences sheet:
Hiding the Reset Workspace option from the Advanced Preferences sheet using the Registry editorYou can hide the Reset Workspace option from the Advanced Preferences sheet only using the Registry editor.
Hiding Citrix Workspace Updates option from the Advanced Preferences sheet
StoreFront to Workspace URL MigrationThis feature is in Technical Preview. StoreFront to Workspace URL migration enables you to seamlessly migrate your end users from a StoreFront store to Workspace store with minimal user interaction. Consider, all your end users have a StoreFront store Once the setting is detected, Citrix Workspace app adds the mapped Workspace URL To enable the feature, do the following steps:
Once the app config service settings are pushed, the following screen appears: When the user clicks Switch to Citrix Workspace now, the Workspace URL is added to Citrix Workspace app and the authentication prompt appears. Users have a limited option to delay the transition up to three times. Application deliveryWhen delivering applications with Citrix Virtual Apps and Desktops and Citrix DaaS, consider the following options to enhance the user experience:
For more information, see the Create Delivery Groups section in the Citrix Virtual Apps and Desktops documentation. Configure self-service modeBy simply adding a StoreFront account to Citrix Workspace app or configuring Citrix Workspace app to point to a StoreFront site, you can configure self-service mode. The configuration allows users to subscribe to applications from the Citrix Workspace user interface. The enhanced user experience is similar to that of a mobile app store.
In self-service mode, you can configure mandatory, auto-provisioned, and featured app keyword settings as needed. Append keywords to the descriptions you provide for delivery group applications:
Customize the app shortcut location using the Group Policy Object template
Using StoreFront account settings to customize app shortcut locationsYou can set
up shortcuts in the Start menu and on the desktop from the StoreFront site. The following settings can be added in the web.config file in
In the web.config file, add the changes in the XML section for the account. Find this section by locating the opening tab:
The section ends with the </account> tag. Before the end of the account section, in the first properties section:
Properties can be added into this section after the <clear /> tag, one per line, giving the name and value. For example:
An extended example for this section is:
Using per-app settings in Citrix Virtual Apps and Desktops 7.x to customize app shortcut locationsCitrix Workspace app can be configured to automatically place application and desktop shortcuts directly in the Start menu or on the desktop. However, this configuration is similar to the previous Workspace for Windows versions. However, release 4.2.100 introduced the ability to control the placement of the app shortcut using Citrix Virtual Apps per app settings. The functionality is useful in environments with a handful of applications that need to be displayed in consistent locations. Using per app settings in XenApp 7.6 to customize app shortcut locationsTo configure a per app publishing shortcut in XenApp 7.6:
Reducing enumeration delays or digitally signing application stubsCitrix Workspace app provides functionality to copy the .EXE stubs from a network share, if:
This functionality involves several steps:
If RemoveappsOnLogoff and RemoveAppsonExit are enabled, and users are experiencing delays in app enumeration at every logon, use the following workaround to reduce the delays:
Enable a machine to use pre-created stub executables that are stored on a network share:
Example use cases: This topic provides use cases for app shortcuts. If you have dozens or even hundreds of apps, allow users to select the applications to add to Favorite and Start menu:
If a user has a family computer, you might not need or want app shortcuts at all. In such scenarios, the simplest approach is browser access; install Citrix Workspace app without any configuration and browse to workspace for web. You can also configure Citrix Workspace app for self-service access without putting shortcuts anywhere.
If the user has only a few apps, put them all in the Start menu or on the desktop, or in a folder on the desktop.
Per app settings in XenApp 6.5 or 7.xIf you want to set the location of shortcuts so every user finds them in the same place use XenApp per App Settings:
Apps in category folders or in specific foldersIf you want applications displayed in specific folders use the following options:
Remove apps on logoff or exitIf you don’t want users to see apps while another user share the end point, you can remove the apps when the user logs off and exits.
Configuring Local App Access applicationsWhen configuring Local App Access applications:
You can specify the prefer keyword multiple times for an application. Only one match is needed to apply the keyword to an application. The following patterns can be used in any combination:
You can specify the prefer keyword multiple times for an application. Only one match is needed to apply the keyword to an application. The following patterns can be used in any combination:
For information about other keywords, see “Additional recommendations” in Optimize the user experience section in the StoreFront documentation. Virtual display layoutThis feature lets you define a virtual monitor layout that applies to the remote desktop. You can also split a single client monitor virtually into up to eight monitors on the remote desktop. You can configure the virtual monitors on the Monitor Layout tab in the Desktop Viewer. There, you can draw horizontal or vertical lines to separate the screen into virtual monitors. The screen is split according to specified percentages of the client monitor resolution. You can set a DPI for the virtual monitors that is used for DPI scaling or DPI matching. After applying a virtual monitor layout, resize or reconnect the session. This configuration applies only to full-screen, single-monitor desktop sessions, and does not affect any published applications. This configuration applies to all subsequent connections from this client. Starting from Citrix Workspace app for Windows 2106, virtual display layout is also supported for full-screen and multi-monitor desktop sessions. Virtual display layout is enabled by default. In a multi-monitor scenario, the same virtual display layout is applied to all the session monitors if the total number of virtual displays doesn’t exceed eight virtual displays. In case this limit is exceeded, the virtual display layout is ignored and not applied to any session monitor. Multi-monitor enhancement can be disabled by setting the following registry key:
Name: SplitAllMonitors Type: DWORD Values: 1 - Enabled 0 - Disabled Application launch timeUse the session prelaunch feature to reduce application launch time during normal or high traffic periods, thus providing users with a better experience. The prelaunch feature allows to create a prelaunch session. Prelaunch session is created when a user logs on to Citrix Workspace app, or at a scheduled time if the user has signed in. The prelaunch session reduces the launch time of the first application. When a user adds new account connection to Citrix Workspace app for Windows, session prelaunch doesn’t take effect until the next session. The default application ctxprelaunch.exe is running in the session, but it is not visible to you. For more information, see session prelaunch and session linger guidance in the Citrix Virtual Apps and Desktops article titled Manage delivery groups. Session prelaunch is disabled by default. To enable session prelaunch, specify the
The registry locations are:
There are two types of prelaunch:
Configuring prelaunch on a Citrix Virtual Apps server consists of:
You cannot
customize the prelaunch feature using the
HKEY_LOCAL_MACHINE registry values: For 64-bit Windows operating systems: For 32-bit Windows operating systems: Name: UserOverride Type: REG_DWORD Values: 0 - Use the HKEY_LOCAL_MACHINE values even if HKEY_CURRENT_USER values are also present. 1 - Use the HKEY_CURRENT_USER values if they exist; otherwise, use the HKEY_LOCAL_MACHINE values. Name: State Type: REG_DWORD Values: 0 - Disable prelaunch. 1 - Enable just-in-time prelaunch. (prelaunch starts after the user’s credentials are authenticated.) 2 - Enable scheduled prelaunch. (prelaunch starts at the time configured for Schedule.) Name: Schedule Type: REG_DWORD Value: The time (24-hour format) and days of a week for the scheduled prelaunch entered in the following format:
HKEY_CURRENT_USER registry values:
The State and Schedule keys have the same values as for HKEY_LOCAL_MACHINE. Bidirectional content redirectionThe bidirectional content redirection policy allows you to enable or disable client to host and host to client URL redirection. Server policies are set in Studio, and client policies are set from the Citrix Workspace app Group Policy Object administration template. Citrix offers host to client redirection and Local App Access for client to URL redirection. However, we recommend that you use bidirectional content redirection for domain-joined Windows clients. You can enable bidirectional content redirection using one of the following methods:
To enable bidirectional content redirection using the GPO administrative template: Use Group Policy Object administrative template configuration only for a first-time installation of Citrix Workspace app for Windows.
To enable bidirectional content redirection using the registry: To enable bidirectional content redirection, run the
Limitation: No fallback mechanism is present if the redirection fails due to session launch issues. Bi-directional URL support with Chromium-based browsersBidirectional content redirection allows you to configure URLs to redirect from client to server and from server to client using policies on the server and the client. Server policies are set on the Delivery Controller and client policies on Citrix Workspace app. The policies are set using the Group Policy Object (GPO) administrative template. Starting with Version 2106, bidirectional URL redirection support has been added for Google Chrome and Microsoft Edge. Prerequisites:
To register Google Chrome browser to bidirectional URL redirection, run the following command from the Citrix Workspace app installation folder:
To unregister Google Chrome browser from bidirectional URL redirection, run the following command from the Citrix Workspace app installation folder:
For information on configuring URL redirection on Citrix Workspace app, see Bidirectional content redirection. For more information about browser content redirection, see Browser content redirection in the Citrix Virtual Apps and Desktops documentation. To prevent the desktop viewer window from dimming: If you have multiple Desktop Viewer windows, by default the desktops that are not active are dimmed. If users want to view multiple desktops simultaneously, information on them might be unreadable. You can disable the default behavior and prevent the Desktop Viewer window from dimming by editing the Registry editor.
Optionally, instead of controlling dimming, you can define a local policy by creating the same REG_WORD entry in one of the following keys:
Before using these keys, check whether the Citrix Virtual Apps and Desktops and Citrix DaaS administrator has set a policy for this feature. Set the entry to any non-zero value such as 1 or true. If no entries are specified or the entry is set to 0, the Desktop Viewer window is dimmed. If multiple entries are specified, the following precedence is used. The first entry in this list and its value determine whether the window is dimmed:
Citrix CastingThe Citrix Ready workspace hub combines digital and physical environments to deliver apps and data within a secure smart space. The complete system connects devices (or things), like mobile apps and sensors, to create an intelligent and responsive environment. Citrix Ready workspace hub is built on the Raspberry Pi 3 platform. The device running Citrix Workspace app connects to the Citrix Ready workspace hub and casts the apps or desktops on a larger display. Citrix Casting is supported only on Microsoft Windows 10 Version 1607 and later or Windows Server 2016. Citrix Casting feature allows instant and secure access of any app from a mobile device and display on a large screen.
Prerequisites:
Configure Citrix Casting launch
How to use Citrix Casting with Citrix Workspace app
In the Citrix Casting notification dialog, the following options are available:
Self-check listIf Citrix Workspace app cannot detect and communicate with any available workspace hubs in range, ensure that you do the following as part of self-check:
Known issues and limitations
For more information about Citrix Ready workspace hub, see the Citrix Ready workspace hub section in the Citrix Virtual Apps and Desktops documentation. Composite USB device redirectionUSB 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:
When a composite USB device is forwarded, the entire device becomes unavailable to the endpoint. Forwarding also blocks the local usage of the device for all applications on the endpoint, including the Citrix Workspace client needed for an optimized HDX remote experience. Consider a USB headset device with both 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 best experience when the audio is sent through the optimized HDX audio channel unlike the audio sent using host-side audio drivers through generic USB remoting. The behavior is because of the noisy nature of the USB audio protocols. You also notice issues when the system keyboard or pointing device are part of a composite device with other integrated features required for the remote session support. When a complete composite device is forwarded, the system keyboard or mouse becomes inoperable at the endpoint, except within the remote desktop session or application. 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 mechanism ensures that the other child devices are available for use by applications on the client endpoint, including, the Citrix Workspace app that provides optimized HDX experiences, while allowing only the required devices to be forwarded and available to the remote session. Device Rules: As with regular USB devices, device rules set in the policy or client Citrix Workspace app configuration on the end point select the composite devices for forwarding. Citrix Workspace app uses these rules to decide which USB devices to allow or prevent from forwarding to the remote session. Each rule consists of an action keyword (Allow, Connect, or Deny), a colon (:), and zero or more filter parameters that match actual devices at the endpoints USB subsystem. These filter parameters correspond to the USB device descriptor metadata used by every USB device to identify itself. Device rules are clear text with each rule on a single line and an optional comment after a # character. Rules are matched top down (descending priority order). The first rule that matches the device or child interface is applied. Subsequent rules that select the same device or interface are ignored. Sample device rules:
You can use any of the following filter parameters to apply rules to the encountered devices:
The first six parameters select the USB devices for which the rule must be applied. If any parameter is not specified, the rule matches a device with ANY value for that parameter. The USB Implementors Forum maintains a list of defined class, subclass, and protocol values in Defined Class Codes. USB-IF also maintains a list of registered vendor IDs. You can check the vendor, product, release, and interface IDs of a specific device directly in the Windows device manager or using a free tool like UsbTreeView. When present, the last two parameters apply only to USB composite devices. The split parameter determines if a composite device must be forwarded as split devices or as a single composite device.
The intf parameter selects the specific child interfaces of the composite device to which the action must be applied. If omitted, the action applies to all interfaces of the composite device. Consider a composite USB headset device with three interfaces:
The suggested rules for this type of device are:
Enable Device Rules policy: Citrix Workspace app for Windows includes a set of default device rules that filters certain undesirable classes of devices and allow one that customers often encounter. You can check these default device rules in the system registry at either:
However, in the Citrix Workspace app for Window, you can apply USB Device Rules policy to overwrite these default rules. To enable device rules policy for Citrix Workspace app for Windows:
Citrix recommends preserving the default rules shipped with the client when creating this policy by copying the original rules and inserting new rules to alter the behavior as desired. Connecting USB devices: In a desktop session, split USB devices are displayed in the Desktop Viewer under Devices. Also, you can view split USB devices from Preferences > Devices.
In an application session, split USB devices are displayed in the Connection Center. To automatically connect an interface: The CONNECT keyword introduced in Citrix Workspace app for Windows 2109 allows for automatic redirection of USB devices. The CONNECT rule can replace the ALLOW rule if the administrator allows the device or selected interfaces to automatically connect in the session.
Changing USB device auto-connection preferences: Citrix Workspace app automatically connects USB devices tagged with CONNECT action based on the preferences set for the current desktop resource. You can change the preferences in the Desktop viewer toolbar as shown in the following image. The two check boxes at the bottom of the pane controls if the devices must connect automatically or wait for manual connection in the session. These settings are not enabled by default. You can change the preferences if generic USB devices must be connected automatically. Alternatively, an administrator can override the user preferences by deploying the corresponding policies from Citrix Workspace app Group Policy Object administrative template. Both machine and user policies can be found under Administrative Templates > Citrix Components > Citrix Workspace > Remoting client devices > Generic USB Remoting. The corresponding policies are labeled as Existing USB Devices and New USB Devices respectively. Change split device default setting: By default, the Citrix Workspace app for Windows only splits composite devices that are explicitly tagged as Split=1 in the device rules. However, it is possible to change the default disposition to split all composite devices that are not otherwise tagged with Split=0 in a matching device rule.
Limitation: Citrix recommends that you do not split interfaces for a webcam. As a workaround, redirect the device to a single device using Generic USB redirection. For a better performance, use the optimized virtual channel. Bloomberg keyboardsCitrix Workspace app supports the use of Bloomberg keyboard in a virtual apps and desktops session. The required components are installed with the plug-in. You can enable the Bloomberg keyboard feature when installing Citrix Workspace app for Windows or by using the Registry editor. Bloomberg keyboards provide other functionality when compared to standard keyboards, that allows the user to access financial market data and perform trades. The Bloomberg keyboard consists of multiple USB devices built into one physical shell:
In addition to the normal functionality of these devices, the audio device includes support for some keys, control of the keyboard, and keyboard LEDs. To use the specialized functionality inside a session, you must redirect the audio device as a USB device. This redirect makes the audio device available to the session, but prevents the audio device from being used locally. In addition, the specialized functionality can only be used with one session and cannot be shared between multiple sessions. Multiple sessions with Bloomberg keyboards are not recommended. The keyboard operates in a single-session environment only. Configuring Bloomberg keyboard 5: You must configure various interfaces of the Bloomberg keyboard. From Citrix Workspace Application for Windows 2109, a new CONNECT keyword is introduced to allow automatic connection of USB devices at session startup and device insertion. The CONNECT keyword can be used to replace the ALLOW keyword when the user wants a USB device or interface to connect automatically. The following example uses the CONNECT keyword.
This procedure makes the Bloomberg keyboard 5 ready for use. The DENY rules that are mentioned in the steps enforce the redirection of the primary keyboard and audio channel over an optimized channel but not over Generic USB. The CONNECT rules enable automatic redirection of the fingerprint module, special keys on the keyboard, and keys related to audio control. Configure Bloomberg keyboard 4 or 3:
Bloomberg keyboard 3 support is available in the online plug-in 11.2 for Windows and subsequent versions. Bloomberg keyboard 4 support is available for Windows Receiver 4.8 and later versions. Determining if Bloomberg keyboards support is enabled:
Enabling Bloomberg keyboard support:
The support for the Bloomberg keyboard changes the way certain USB devices are redirected to a session. This support is not enabled by default.
Disabling support for the Bloomberg keyboard: You can disable support for the Bloomberg keyboard in the online plug-in as follows:
Using Bloomberg keyboards without enabling support:
Using Bloomberg keyboards after enabling support:
Enabling the Bloomberg keyboard support only affects the specialized Bloomberg keys and the audio device. Because the ordinary keys and fingerprint reader are used in the same way as when the support is not enabled. DPI scalingCitrix Workspace app is DPI aware and supports matching display resolution and DPI scale settings on the Windows client to the virtual apps and desktops session. DPI scaling is mostly used with large size and high-resolution monitors to display applications, text, images, and other graphical elements in a size that can be viewed comfortably. This feature is enabled by default, and it is the recommended setting for all use cases. However, administrators can still configure the DPI scaling using Group Policy Object (GPO) administrative template (per-machine configuration) if necessary. To configure DPI scaling using GPO administrative template: To configure DPI scaling using GPO administrative template:
For information about troubleshooting issues with DPI scaling, see Knowledge Center article CTX230017. Generic client Input Method Editors (IME)
Configuring generic client IME using the command-line interface:
If you have disabled generic client
IME using the command-line interface, you can enable the feature again by running the Toggle: Citrix Workspace app supports toggle functionality for this feature. You can run the Configure generic client IME using the graphical user interface: Generic client IME requires VDA Version 7.13 or later. Generic client IME feature can be enabled by enabling keyboard layout synchronization. For more information, see Keyboard layout synchronization. Citrix Workspace app allows you to configure different options to use generic client IME. You can select from one these options based on your requirements and usage.
The following options are available to support different IME modes:
The changes are applied only for the current session. Enabling hotkey configuration using a registry editor: When generic client IME is enabled, you can use the Shift+F4 hotkeys to select different IME modes. The different options for IME modes appear in the top-right corner of the session. By default, the hotkey for generic client IME is disabled. In the registry editor, navigate to Select AllowHotKey and change the default value to 1. You can use the Shift+F4 hotkeys to select different IME modes in a session. The different options for IME modes appear in the top-right corner of the session while switching using these hotkey combinations. Limitations:
H.265 video encodingCitrix Workspace app supports the use of the H.265 video codec for hardware acceleration of remote graphics and videos. H.265 video codec must be supported and enabled on both the VDA and Citrix Workspace app. If the GPU on the endpoint doesn’t support H.265 decoding using the DXVA interface, the H265 Decoding for graphics policy setting is ignored and the session falls back H.264 video codec. Prerequisites:
In Citrix Workspace app for Windows, this feature is set to Disabled by default. Configuring Citrix Workspace app to use H.265 video encoding using Citrix Group Policy Object (GPO) administrative template:
Configuring H.265 video encoding using Registry editor: Enabling H.265 video encoding on a non-domain joined network on a 32-bit operating system:
Enabling H.265 video encoding on a non-domain joined network on a 64-bit operating system:
Restart the session for the changes to take effect.
Keyboard layout and language barKeyboard layout
Keyboard layout synchronization enables you to switch among preferred keyboard layouts on the client device. This feature is disabled by default. The keyboard layout synchronization allows the client keyboard layout to automatically synchronize to the virtual apps and desktops session. To configure keyboard layout synchronization using the GPO administrative template:
To configure keyboard layout synchronization using the graphical user interface:
To configure keyboard layout synchronization using CLI: Run the following command from the Citrix Workspace app for Windows installation folder. Typically, Citrix Workspace app installation folder is at
Using the client keyboard layout option activates the Client IME (Input Method Editor). If users working in Japanese, Chinese, or Korean prefer to use the Server IME, they must disable the client keyboard layout option by selecting No, or running Sometimes, switching the client keyboard layout does not take effect in an active session. To resolve this issue, log off from Citrix Workspace app and login again. Configuring keyboard sync on Windows VDA
After you enable the keyboard layout on both the VDA and Citrix Workspace app, the following window appears when you switch keyboard layouts. This window indicates that the session keyboard layout is being switched to the client keyboard layout. Configuring keyboard sync on Linux VDALaunch the command prompt and run the following command:
Restart the VDA for the changes to take effect. For more information about the keyboard layout synchronization feature on Linux VDA, see Dynamic keyboard layout synchronization. Hide the keyboard layout switch notification dialog: The keyboard layout change notification dialog lets you know that the VDA session is switching the keyboard layout. The keyboard layout switch needs approximately two seconds to switch. When you hide the notification dialog, wait for some time before you start typing to avoid incorrect character input.
Hide the keyboard layout switch notification dialog using the Registry editor:
Limitations:
Language barThe language bar displays the preferred input language in a session. The language bar appears in a session by default.
Configure the language bar using the GPO administrative template: The language bar displays the preferred input language in an application session.
Configure language bar using the graphical user interface:
Hide the language bar tab from the Advanced Preferences sheet: You can hide the language bar tab from the Advanced Preferences sheet by using the registry.
USB supportUSB support enables you to interact with a wide range of USB devices when connected to a Citrix Virtual Apps and Desktops and Citrix DaaS. You can plug USB devices into their computers and the devices are remote to their virtual desktop. USB devices available for remoting include flash drives, smartphones, PDAs, printers, scanners, MP3 players, security devices, and tablets. Desktop Viewer users can control whether USB devices are available on the Citrix Virtual Apps and Desktops and Citrix DaaS using a preference in the toolbar. Isochronous features in USB devices, such as webcams, microphones, speakers, and headsets are supported in typical low latency or high-speed LAN environments. Such environment allows these devices to interact with packages, like Microsoft Office Communicator and Skype. The following types of device are supported directly in a virtual apps and desktops session, and so does not use USB support:
Specialist USB devices (for example, Bloomberg keyboards and 3-D mice) can be configured to use USB support. For information on configuring Bloomberg keyboards, see Configure Bloomberg keyboards. For information on configuring policy rules for other specialist USB devices, see Knowledge Center article CTX122615. By default, certain types of USB devices are not supported for remoting through Citrix Virtual Apps and Desktops and Citrix DaaS. For example, a user might have a NIC attached to the system board by internal USB. Remoting this device would not be appropriate. The following types of USB device are not supported by default in a virtual apps and desktops session:
USB devices connected to a hub can be remote, but the hub itself cannot be remote. The following types of USB device are not supported by default for use in a virtual apps session:
How USB support works: When a user plugs in a USB device, it is checked against the USB policy, and, if allowed, remoted to the virtual desktop. If the default policy denies a device, it is available only to the local desktop. When a user plugs in a USB device, a notification appears to inform the user about a new device. The user can select which USB devices must be remoted to the virtual desktop each time they connect. Alternatively, the user can configure USB support so that all USB devices plugged in both before and/or during a session is automatically remoted to the virtual desktop that is in focus. Mass storage devicesFor mass storage devices only, in addition to USB support, remote access is available through client drive mapping. You can configure this through the Citrix Workspace app for Windows policy Remoting client devices > Client drive mapping. When you apply this policy, the drives on the user device automatically map to drive letters on the virtual desktop when users log on. The drives are displayed as shared folders with mapped drive letters. The main differences between the two types of remoting policy are:
If you enable both Generic USB and the client drive-mapping policies and insert a mass storage device before a session starts, it is redirected using client drive mapping first, before being considered for redirection through USB support. If it is inserted after a session has started, it will be considered for redirection using USB support before client drive mapping. USB device classes allowed by default: Default USB policy rules allow different classes of USB device. Although they are on this list, some classes are only available for remoting in virtual apps and desktops sessions after additional configuration. Such USB device classes are as follows.
USB devices classes denied by defaultDefault USB policy rules don’t allow the following different classes of USB device:
Update the list of USB devices available for remotingEdit the Citrix Workspace for Windows template file to update the range of USB devices available for remoting to desktops. The update allows you to make changes to the Citrix Workspace for Windows using Group Policy. The file is in the following installed folder:
Alternatively, you can edit the registry on each user device, adding the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Citrix\ICA Client\GenericUSB Type=String Name=”DeviceRules” Value=
The product default rules are stored in: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\GenericUSB Type=MultiSz Name=”DeviceRules” Value= Do not edit the product default rules. For more information about USB devices policy settings, see USB devices policy settings in Citrix Virtual Apps and Desktops documentation. Configuring USB audio
To configure USB audio devices:
vPrefer launchIn earlier releases, you can specify that the instance of an app installed on the VDA (referred to as local instance in this document) must be launched in preference to the published application by setting the KEYWORDS:prefer=”application” attribute in Citrix Studio. Starting with Version 4.11, in a double-hop scenario (where Citrix Workspace app is running on the VDA that hosts your session), you can now control whether Citrix Workspace app launches:
vPrefer is available on StoreFront Version 3.14 and Citrix Virtual Desktops 7.17 and later. When you launch the application, Citrix Workspace app reads the resource data present on the StoreFront server and applies the settings based on the vprefer flag at the time of enumeration. Citrix Workspace app searches for the application’s installation path in the Windows registry of the VDA. If present, launches the local instance of the application. Otherwise, a hosted instance of the application is launched. If you launch an application that is not on the VDA, Citrix Workspace app launches the hosted application. For more information on how StoreFront handled the local launch, see Control of local application launch on published desktops in the Citrix Virtual Apps and Desktops documentation. If you do not want the local instance of the application to be launched on the VDA, set the LocalLaunchDisabled to True using the PowerShell on the Delivery Controller. For more information, see the Citrix Virtual Apps and Desktops documentation. This feature helps to launch applications faster, thereby providing a better user experience. You can configure it by using the Group Policy Object (GPO) administrative template. By default, vPrefer is enabled only in a double-hop scenario.
Limitation:
Workspace configurationCitrix Workspace app for Windows supports configuring Workspace for subscribers, who might be using one or more services available from Citrix Cloud. Citrix Workspace app intelligently displays only the specific workspace resources to which users are entitled. All your digital workspace resources available in Citrix Workspace app are powered by the Citrix Cloud Workspace experience service. A workspace is part of a digital workspace solution that enables IT to securely deliver access to apps from any device. This screenshot is an example of what the workspace experience looks like to your subscribers. This interface is evolving and might look different to what your subscribers are working with today. For example, it might say “StoreFront” at the top of the page instead of “Workspace”. Content Collaboration Service integrationThis release introduces integration of Citrix Content Collaboration Service with Citrix Workspace app. Citrix Content Collaboration enables you to easily and securely exchange documents, send large documents by email, securely handle document transfers to third parties, and 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 from the Citrix Cloud console.
The following image displays example contents of the Files tab of the new Citrix Workspace app: Limitations:
Configure download location for Citrix Files using the Registry editor:
For information about configuring Citrix Files download location using the Advanced Preferences UI, see Configuring download location using Advanced Preferences in Citrix Workspace app for Windows Help documentation. SaaS appsSecure access to SaaS applications provides a unified user experience that delivers published SaaS applications to the users. SaaS apps are available with single sign-on. Administrators can now protect the organization’s network and end-user devices from malware and data leaks. Administrators can achieve this by filtering access to specific websites and website categories. Citrix Workspace app for Windows support the use of SaaS apps using the Citrix Secure Private Access. The service enables administrators to provide a cohesive experience, integrating single sign-on, and content inspection. Delivering SaaS apps from the cloud has the following benefits:
Citrix Workspace app launches the SaaS apps on Citrix Workspace Browser. For information, see Citrix Workspace Browser documentation. Limitations:
For more information about Workspace configuration, see Workspace configuration in Citrix Cloud. PDF printingCitrix Workspace app for Windows supports PDF printing in a session. The Citrix PDF Universal Printer driver allows you to print documents that are launched using hosted applications and desktops running on Citrix Virtual Apps and Desktops and Citrix DaaS. When you select the Citrix PDF Printer option from the Print dialog, the printer driver converts the file to a PDF and transfers the PDF to the local device. The PDF is then launched using the default PDF viewer for viewing and prints from a locally attached printer. Citrix recommends the Google Chrome browser or Adobe Acrobat Reader for PDF viewing. You can enable Citrix PDF printing using Citrix Studio on the Delivery Controller. Prerequisites:
To enable PDF printing:
Restart the Citrix Workspace app session for the changes to take effect. Limitation:
Expanded tablet mode in Windows 10 using Windows ContinuumWindows Continuum is a Windows 10 feature that adapts to the way the client device is used. Citrix Workspace app for Windows supports Windows Continuum, including dynamic change of modes. For touch-enabled devices, the Windows 10 VDA starts in tablet mode when there’s no keyboard or mouse attached. It starts in desktop mode when either a keyboard or a mouse or both are attached. Detaching or attaching the keyboard on any client device or the screen on a 2-in-1 device like a Surface Pro toggles between tablet and desktop modes. For more information, see Tablet mode for touchscreen devices in Citrix Virtual Apps and Desktops documentation. On a touch-enabled client device, the Windows 10 VDA detects the presence of a keyboard or mouse when you connect or reconnect to a session. It also detects when you attach or detach a keyboard or mouse during the session. This feature is enabled by default on the VDA. To disable the feature, modify the Tablet mode toggle policy using Citrix Studio. Tablet mode offers a user interface that is better suited to touchscreens:
Desktop mode offers the traditional user interface where you interact in the same manner as a PC with a keyboard and mouse.
Browser content redirectionBrowser content redirection prevents the rendering of webpages in the allow list on the VDA 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.
Browser content redirection supports the Google Chrome browser in addition to the Internet Explorer browser. Browser content redirection redirects the contents of a web browser to a client device, and creates a corresponding browser embedded within the Citrix Workspace app. This feature offloads network usage, page processing, and graphics appearing at the endpoint. Doing so improves the user experience when browsing demanding webpages, especially webpages that incorporate HTML5 or WebRTC video.
For more information, see Browser content redirection. Citrix AnalyticsCitrix Workspace app is instrumented to securely transmit logs to Citrix Analytics. The logs are analyzed and stored on Citrix Analytics servers when enabled. For more information about Citrix Analytics, see Citrix Analytics. Enhancement to Citrix Analytics ServiceWith this release, Citrix Workspace app is instrumented to securely transmit the public IP address of the most recent network hop to Citrix Analytics Service. This data is collected per session launch. It helps the Citrix Analytics Service to analyze whether poor performance issues are tied to specific geographic areas. By default, the IP address logs are sent to the Citrix Analytics Service. However, you can disable this option on the Citrix Workspace app using the Registry editor. To disable IP address log transmissions, navigate to the following registry path and set the
Citrix Workspace app is instrumented to securely transmit data to Citrix Analytics Service from ICA sessions that you launch from a browser. For more information on how Performance Analytics uses this information, see Self-Service for Performance. Relative mouseThe relative mouse feature determines how far the mouse has moved since the last frame within a window or screen. The relative mouse uses the pixel delta between the mouse movements. When you change, for example, the direction of the camera using mouse controls, the feature is efficient. Apps also often hide the mouse cursor because the position of the cursor relative to the screen coordinates isn’t relevant, when manipulating a 3-D object or scene. Relative mouse support provides an option to interpret the mouse position in a relative rather than an absolute manner. The interpretation is required for applications that demand relative mouse input rather than absolute. You can configure the feature both on a per-user and a per-session basis, which gives more granular control on the feature availability.
Configuring the feature using the Registry Editor or the default.ica file allows the setting to be persistent even after the session is terminated. Configuring relative mouse using the Registry editorTo configure the feature, set the following registry keys as applicable and then restart the session for the changes to take effect: To make the feature available on a per-session
basis: To make the feature available on a per-user basis:
Configuring the relative mouse using the default.ica file
Enabling relative mouse from the Desktop Viewer
Hardware decodingWhen using Citrix Workspace app (with HDX engine 14.4), the GPU can be used for H.264 decoding wherever it’s available at the client. The API layer used for GPU decoding is DirectX Video Acceleration. To enable hardware decoding using Citrix Workspace app Group Policy Object administrative template:
To validate if the policy is set and hardware acceleration is used for an active ICA session, check the following registry entries: Registry Path:
When using the hardware decoding feature, consider the following limitations:
Microphone inputCitrix Workspace app supports multiple client-side microphone inputs. You can use locally installed microphones for:
Citrix Workspace app users can select whether to use microphones attached to their device using Connection Center. Citrix Virtual Apps and Desktops and Citrix DaaS users can also use the Citrix Virtual Apps and Desktops and Citrix DaaS viewer Preferences to disable their microphones and webcams. Client drive-mappingClient drive mapping supports the transfer of data between the host and the client as a stream. The file transfer adapts to the changing network throughput conditions. It also uses any available extra bandwidth to scale up the data transfer rate. By default, this feature is enabled. To disable this feature, set the following registry key and then restart the server: Path: Citrix Workspace app for Windows supports device mapping on user devices so they’re available from within a session. Users can:
Citrix Workspace app informs the server of the available client drives, COM ports, and LPT ports during sign-in. By default, client drives are mapped to server drive letters and server print queues are created for client printers, which make them appear to be directly connected to the session. These mappings are available only for the current user during the current session. They’re deleted when the user logs off and recreated the next time the user logs on. You can use the redirection policy settings to map user devices not automatically mapped at logon. For more information, see the Citrix Virtual Apps and Desktops documentation. Disable user device mappingsYou can configure user device-mapping including options for drives, printers, and ports, using the Windows Server Manager tool. For more information about the available options, see your Remote Desktop Services documentation. Redirect client foldersClient folder redirection changes the way client-side files are accessible on the host-side session. Enabling only client drive mapping on the server, client-side full volumes automatically maps to the sessions as Universal Naming Convention (UNC) links. When you enable client folder redirection on the server and the user configures it on the user device, part of the user specified local volume gets redirected. Only the user-specified folders appear as UNC links inside the sessions, instead of the complete file system on the user device. If you disable UNC links through the registry, client folders appear as mapped drives inside the session. For more information, including how to configure client folder redirection for user devices, see the Citrix Virtual Apps and Desktops documentation. Map client drives to host-side drive lettersClient drive mapping redirects drive letters on the host-side to drives that exist on the user device. For example, drive H in a Citrix user session can be mapped to drive C of the user device running Citrix Workspace app for Windows. Client drive mapping is built into the standard Citrix device redirection facilities transparently. To File Manager, Windows Explorer, and your applications, these mappings appear like any other network mappings. The server hosting virtual desktops and applications can be configured during installation to map client drives automatically to a given set of drive letters. The default installation maps drive letters assigned to client drives starting with V and works backward, assigning a drive letter to each fixed drive and CD-ROM drive. (Floppy drives are assigned their existing drive letters.) This method yields the following drive mappings in a session:
The server can be configured so that the server drive letters don’t conflict with the client drive letters. So, the server drive letters are changed to higher drive letters. In the following example, changing server drives C to M and D to N allows client devices to access their C and D drives directly. This method yields the following drive mappings in a session:
The drive letter used to replace the server drive C is defined during Setup. All other fixed drive and CD-ROM drive letters are replaced with sequential drive letters (for example; C > M, D > N, E > O). These drive letters must not conflict with any existing network drive mappings. If you map the network drive to the same drive letter as a server drive letter, the network drive mapping isn’t valid. Connecting a user device to a server, reestablishes client mappings unless automatic client device mapping is disabled. Client drive mapping is enabled by default. To change the settings, use the Remote Desktop Services (Terminal Services) Configuration tool. You can also use policies to give you more control over how client device mapping is applied. For more information about policies, see the Citrix Virtual Apps and Desktops documentation. HDX Plug and Play USB device redirectionHDX Plug and Play USB device redirection enables dynamic redirection of media devices to the server. The media device includes cameras, scanners, media players, and point of sale (POS) devices. You or the user can restrict the redirection of all or some of the devices. Edit policies on the server or apply group policies on the user device to configure the redirection settings. For more information, see USB and client drive considerations in the Citrix Virtual Apps and Desktops documentation.
A user can set permissions in Citrix Workspace app to allow or reject device redirection always or notify each time a device is connected. The setting affects only devices plugged in after the user changes the setting. To map a client COM port to a server COM port: Client COM port mapping allows devices attached to the COM ports of the user device to be used during sessions. These mappings can be used like any other network mappings. You can map client COM ports at the command prompt. You can also control client COM port mapping from the Remote Desktop (Terminal Services) Configuration tool or using policies. For information about policies, see the Citrix Virtual Apps and Desktops documentation.
To use this COM port in a virtual desktop or application, install your user device to the mapped name. For example, if you map COM1 on the client to COM5 on the server, install your COM port device on COM5 during the session. Use this mapped COM port as you would a COM port on the user device. Multi-monitor supportYou can use up to eight monitors with Citrix Workspace app for Windows. Each monitor in a multiple monitor configuration has its own resolution designed by its manufacturer. Monitors can have different resolutions and orientations during sessions. Sessions can span multiple monitors in two ways:
Citrix Virtual Apps and Desktops and Citrix DaaS: When any desktop in the same assignment (formerly “desktop group”) is launched then, the window setting is preserved and the desktop is displayed across the same monitors. Multiple virtual desktops can be displayed on one device provided the monitor arrangement is rectangular. If the primary monitor on the device is used by the virtual apps and desktops session, it becomes the primary monitor in the session. Otherwise, the numerically lowest monitor in the session becomes the primary monitor. To enable multi-monitor support, check the following:
Check if the setting is large enough (in kilobytes) to provide sufficient graphic memory. If this setting isn’t high enough, the published resource is restricted to the subset of the monitors that fits within the size specified. Using Citrix Virtual desktops on dual monitor:
For calculating the session’s graphic memory requirements for Citrix Virtual Apps and Desktops and Citrix DaaS, see Knowledge Center article CTX115637. PrinterTo override the printer settings on the user device
On-screen keyboard controlTo enable touch-enabled access to virtual applications and desktops from Windows tablets, Citrix Workspace app automatically displays the on-screen keyboard when:
On some devices and in some circumstances, Citrix Workspace app can’t accurately detect the mode of the device. The on-screen keyboard might also appear when you don’t want it to. To suppress the on-screen keyboard from appearing when using a convertible device:
The keys can be set to the following 3 different modes:
Keyboard shortcutsYou can configure combinations of keys that Citrix Workspace app interprets as having special functionality. When the keyboard shortcuts policy is enabled, you can specify Citrix Hotkey mappings, behavior of Windows hotkeys, and keyboard layout for sessions.
Citrix Workspace app support for 32-bit color icons: Citrix Workspace app supports 32-bit high color icons. To provide for seamless applications, it automatically selects the color depth for:
To set a preferred depth, you can add a string registry key named Customizing location for application shortcut using command lineThe start menu integration and desktop shortcut only feature lets you bring published application shortcuts into the Windows Start menu and onto the desktop. Users do not have to subscribe to applications from the Citrix Workspace user interface. Start menu integration and desktop shortcut management provide a seamless desktop experience for groups of users. Also for users who need access to a core set of applications in a consistent way. The flag is called SelfServiceMode and is set to Users and administrators can use several registry settings to customize the way shortcuts are set up. Working with shortcuts
Customizing location for application shortcut using the Registry editor
Manage workspace control reconnectWorkspace control lets applications follow users as they move between devices. For example, workspace control enables clinicians in hospitals to move from workstation to workstation without having to restart their applications on each device. For Citrix Workspace app, you manage workspace control on client devices by modifying the registry. Workspace control can also be done for domain-joined client devices using Group Policy.
Create WSCReconnectModeUser and modify the existing registry key WSCReconnectMode in the Master Desktop Image or in the Citrix Virtual Apps server. The published desktop can change the behavior of the Citrix Workspace app. WSCReconnectMode key settings for Citrix Workspace app:
Disable workspace controlTo disable workspace control, create the following key:
Name: WSCReconnectModeUser Type: REG_SZ Value data: Modify the following key from the default value of
Name: WSCReconnectMode Type: REG_SZ Value data:
Registry keys for 32-bit machinesRegistry key: WSCSupportedValue:
Key path:
Registry key: WSCReconnectAllValue: Key path:
Registry key: WSCReconnectModeValue: Key path:
Registry key: WSCReconnectModeUserValue: Registry isn’t created during installation. Key path:
Registry keys for 64-bit machines: Registry key: WSCSupportedValue: Key path:
Registry key: |
Data collected | Description | What we use it for |
---|---|---|
Configuration and usage data | The Citrix Customer Experience Improvement Program (CEIP) gathers configuration and usage data from Citrix Workspace app for Windows and automatically sends the data to Citrix and Google Analytics. | This data helps Citrix improve the quality, functionality, and performance of the Citrix Workspace app, appropriately allocate resources for product development purposes, and maintain service levels and manage staffing and infrastructure investment. |
Data collected
As noted above, Citrix collects Workspace app configuration and usage data to improve the quality, functionality, and performance of Workspace App, and to allow Citrix to appropriately allocate resources for product development purposes, as well as to maintain service levels and manage staffing and infrastructure investment. The data is used and analyzed in aggregated form only. No user or their machine is singled-out and no analysis is performed on specific end users based on the CEIP data.
The specific CEIP data collected by Citrix are:
Operating system version | Workspace app version | External devices connected | Screen resolution |
Flash version | Desktop Lock configuration | Touch enabled | Authentication configuration |
Session launch method | Graphics configuration | Desktop Viewer configuration | Printing |
Connection error | Time to launch | Workspace app language | VDA information |
SSON state | Installer state | Time to install | Connection protocol |
Internet Explorer version |
The specific CEIP data elements collected by Google Analytics are:
Operating system version* | Workspace app version* | Authentication configuration | Workspace app language |
Session launch method | Connection error | Connection protocol | VDA information |
Installer configuration | Installer state | Client keyboard layout | Store configuration |
Auto-update preference | Connection Center usage | App protection configuration | Reason for the offline banner |
Device Model/Properties | Citrix Virtual Apps and Desktops Session Launch Status | Virtual app/desktop name | Auto-update Status |
Connection Lease Details | StoreFront to Workspace URL Migration Feature Usage | Citrix Workspace Browser Usage | Auto-update channel |
Inactivity Timeout Details | Citrix Workspace Browser Version |
Note:
Starting with version 2206, the Citrix Workspace app doesn’t collect any CEIP data from users located in the European Union (EU), European Economic Area (EEA), Switzerland, and United Kingdom (UK). Update your Workspace app if you wish to take advantage of this functionality.
Data Collection Preferences
Starting with version 2205, both users and administrators can stop sending CEIP data (except for the two data elements which can be blocked as specified in the Note below) by following the below steps.
- Right-click the Citrix Workspace app icon from the notification area.
- Select Advanced Preferences. The Advanced Preferences dialog appears.
- Select Data Collection.
- Select No, Thanks to disable CEIP or to forego participation.
- Click Save.
You can also navigate to the following registry entry as an administrator and set the value as suggested:
Path: HKEY_LOCAL_MACHINE\ SOFTWARE\Citrix\ICA Client\CEIP
Key: Enable_CEIP
Value: False
Note:
Once you select No Thanks or set the
Enable_CEIP
key toFalse
, you can also stop sending the final two CEIP data elements, that is, Operating System and Workspace app version, by navigating to the following registry entry and set the value:
Path: HKEY_LOCAL_MACHINE\ SOFTWARE\Citrix\ICA Client\CEIP
Key: DisableHeartbeat
Value: True
Additional information
Citrix handles your data according to the terms of your contract with Citrix, and protect it as specified in the Citrix Services Security Exhibit. Citrix Services Security Exhibit is available on the Citrix Trust Center.
Regional settings
Citrix Workspace app displays the date, time, and number based on the locale of the browser or endpoint device.
Starting from Citrix Workspace app 2106, you can customize regional date, time, and number formats through Regional Settings. Changes made in these settings are saved for an individual user and applied across all devices.
Note:
This option is available only on Cloud deployments.
For more information, see Regional Settings.
Microsoft Teams
- Screen sharing
- Encoder performance estimator
- Acoustic Echo Cancellation
Upgraded version of WebRTC for the optimized Microsoft Teams
Starting from Version 2209. the version of WebRTC that is used for the optimized Microsoft Teams is upgraded to version M98.
Background blurring or effects for Microsoft Teams optimization with HDX
Citrix Workspace app for Windows now supports background blurring and effects in Microsoft Teams optimization with HDX.
You can either blur or replace the background with a custom image and avoid unexpected distractions by helping the conversation stay focused on the silhouette (body and face). The feature can be used with either P2P or conference calls.
Note:
This feature is now integrated with the Microsoft Teams UI/buttons. MultiWindow support is a prerequisite that requires a VDA update to 2112 or higher. For more information, see Multi-window meetings and chat.
Limitations:
- Admin and user-defined background replacement is not supported.
- The background effect doesn’t persist between sessions. When you close and relaunch Microsoft Teams or VDA is reconnected, the background effect is reset to off.
- 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.
- The device must be connected to the internet while replacing the background image.
Note:
This feature is available only after future update roll-out from Microsoft Teams. When the update is rolled-out by Microsoft, you can check CTX253754 and the Microsoft 365 Public roadmap for the documentation update and the announcement.
Screen sharing
Starting with Version 2006.1, new functionalities in the outgoing screen sharing feature for the Microsoft Teams application that uses HDX optimization are introduced.
The contents shared using Microsoft Teams are limited to the contents of the Desktop Viewer window. Areas outside the Desktop Viewer window (client local desktop, apps) are blacked out.
On a Windows 10 operating system, the following aren’t blacked out when they overlap the Desktop Viewer window:
- Start menu, Search menu, and Task View.
- Notification bar and Notifications that appear at the right-side of the task bar.
- On a multi-monitor set up with different DPI settings, if a local app is overlapping 2 different monitors and its DPI doesn’t match the main monitor DPI which has the Desktop Viewer window.
- App and preview shown when you mouse-hover over the app’s icon in the task bar.
Encoder performance estimator
The HdxRtcEngine.exe
is the WebRTC media engine embedded in Citrix Workspace app that handles Microsoft Teams redirection. Starting from Citrix Workspace app 1912 or higher, HdxRtcEngine.exe
can estimate the best encoding resolution that the endpoint’s CPU can sustain without overloading. Possible values are 240p, 360p, 480p, 720p, and 1080p.
The performance estimation process (also called webrtcapi.EndpointPerformance
) runs when HdxTeams.exe initializes. The macroblock code determines the best
resolution that can be achieved with the particular endpoint. The Codec negotiation includes the highest possible resolution. The Codec negotiation can be between the peers, or between the peer and the conference server.
There are four performance categories for endpoints that have its own maximum available resolution:
Endpoint performance | Maximum resolution | Registry key value |
---|---|---|
fast | 1080p (1920x1080 16:9 @ 30 fps) | 3 |
medium | 720p (1280x720 16:9 @ 30 fps) | 2 |
slow | 360p (either 640x360 16:9 @ 30 fps, or 640x480 4:3 @ 30 fps) | 1 |
very slow | 240p (either 320x180 16:9 @ 30 fps, or 320x240 4:3 @ 30 fps) | 0 |
Registry Path in Citrix Workspace app:
Navigate to the registry path HKEY_CURRENT_USER\SOFTWARE\Citrix\HDXMediaStream and create the following key:
Name | Type | Values | Description |
---|---|---|---|
OverridePerformance | DWORD | 0;1;2;3 | Force desired performance. Value must be in the range between 0 and 3, where 0 indicates slow and 3 fast. |
For information about configuring the endpoint encoder, see Encoder performance estimator.
For more information about Microsoft Teams optimization, see Optimization for Microsoft Teams.
Acoustic Echo Cancellation
Echo cancellation in HdxRtcEngine.exe
can be disabled to troubleshoot audio performance issues or compatibility with peripherals that have built-in AEC capabilities.
Navigate to the registry path HKEY_CURRENT_USER\SOFTWARE\Citrix\HDXMediaStream and create the following key:
Name: EnableAEC Type: REG_DWORD Data: 0 (0 disables AEC. 1 enables AEC. If Regkey
isn’t present, the default behavior in HdxRtcEngine is to enable AEC,
irrespective of the peripheral’s hardware capabilities.)
Enhancements to Microsoft Teams optimization
Starting from Citrix Workspace app 2112.1 for Windows, the following features (MultiWindow and Give/Take Control) are available only after future update roll-out from Microsoft Teams.
When the update is rolled-out by Microsoft, you can check CTX253754 for the documentation update and the announcement.
Multi-window chat and meetings for Microsoft Teams: You can use multiple windows for chat and meetings in Microsoft Teams when optimized by HDX in Citrix Virtual Apps and Desktops (2112 or higher). You can pop out the conversations or meetings in various ways. For details about the pop-out window feature, see Teams Pop-Out Windows for Chats and Meetings on the Microsoft Office 365 site.
If you’re running an older version of Citrix Workspace app or Virtual Delivery Agent (VDA), Microsoft might deprecate the single-window code in the future. However, you can upgrade to the VDA or Citrix Workspace app version that supports multiple windows (2112 or higher), before nine months after the feature is GA.
Give control: You can use the Give control button to give control access of your shared screen to other users participating in the meeting. The other participant can make selections and modify the shared screen through keyboard, mouse, and clipboard input. You’ll both have control of the shared screen and you can take back the control anytime.
Take control: During screen sharing sessions, any participants can request control access through the Request control button. The person sharing the screen can then approve or deny the request. When you’ve the control, you can control the keyboard and mouse input on the screen shared and release the control to stop sharing control.
Limitation:
The Request control option is not available during the peer-to-peer call between an optimized user and a user on the native Microsoft Teams desktop client that is running on the endpoint. As a workaround, users can join a meeting to get the Request control option.
- Dynamic e911: Citrix Workspace app supports dynamic emergency calling. When used in Microsoft Calling Plans, Operator Connect, and Direct Routing, it provides the option to:
- configure and route emergency calls
- notify security personnel
The notification is sent 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.1 for Windows, Microsoft Teams Optimization with HDX is compliant with Ray Baum’s law.
- App sharing: Previously, you weren’t able to share an app using the Screen sharing feature in Microsoft Teams when you enable the HDX 3D Pro policy in Citrix Studio.
Starting with Citrix Workspace app 2112.1 for Windows and Citrix Virtual Apps and Desktops 2112, Screen sharing feature allows you to share app in Microsoft Teams. You can share an app when HDX 3D Pro policy is enabled.
Starting from Citrix Workspace app 2109.1 for Windows, the following features are available:
Support for WebRTC 1.0: Citrix Workspace app 2109.1 for Windows supports WebRTC 1.0 for a better video conferencing experience along with Gallery View.
Screen sharing enhancement: You can share individual applications, windows, or full screen using the screen sharing feature in Microsoft Teams. Citrix Virtual Delivery Agent 2109 is a prerequisite for this feature.
App Protection compatibility: When App Protection is enabled, you can now share content through Microsoft Teams with HDX optimization. With this feature, you can share an application window running in the virtual desktop. Citrix Virtual Delivery Agent 2109 is a prerequisite for this feature.
Note:
Full monitor or desktop sharing is disabled when App Protection is enabled for the delivery group.
Citrix Workspace app 2109.1 for Windows supports the following in an optimized Microsoft Teams on VM hosted apps:
- peer-to-peer audio and video call
- conference call
- screen sharing
- Starting from Citrix Workspace app 2106 for Windows:
- when the Desktop Viewer is in full screen mode, the user can select one from all the screens covered by the Desktop Viewer to share. In window mode, the user can share the Desktop Viewer window. In seamless mode, the user can select one from all the screens to share. When the Desktop Viewer changes the window mode (maximized, restore, or minimize), the screen share stops.
- Starting from Citrix Workspace app 2105 for Windows:
You can configure a preferred network interface for media traffic.
Navigate to
\HKEY_CURRENT_USER\SOFTWARE\Citrix\HDXMediaStream
and create a key calledNetworkPreference
(REG_DWORD).Select one of the following values as required:
- 1: Ethernet
- 2: Wi-Fi
- 3: Cellular
- 5: Loopback
- 6: Any
By default and if no value is set, the WebRTC media engine chooses the best available route.
You can disable the audio device module 2 (ADM2) so that the legacy audio device module (ADM) is used for quad-channel microphones. Disabling ADM2 helps in resolving issues related to microphones in a call.
To disable ADM2, navigate to
\HKEY_CURRENT_USER\SOFTWARE\Citrix\HDXMediaStream
and create a key namedDisableADM2
(REG_DWORD) and set the value to1
.
- Starting from Citrix Workspace app 2103.1 for Windows:
- The VP9 video codec is now disabled by default.
- Enhancement to echo cancellation, auto gain control, noise suppression configurations: If Microsoft Teams configures these options, Citrix-redirected Microsoft Teams honors the values as configured. Otherwise, these options are set to True by default.
DirectWShow
is now the default renderer.To change the default renderer, do the following:
- Launch the Registry editor.
- Navigate
to the following key location:
HKEY_CURRENT_USER\SOFTWARE\Citrix\HDXMediaStream
. Update the following value:
"UseDirectShowRendererAsPrimary"=dword:00000000
Other possible values:
- 0: Media Foundation
- 1: DirectShow (Default)
- Relaunch the Citrix Workspace app.
- Starting from Citrix Workspace app 2012 for Windows:
- Peers can now see the presenter’s mouse pointer in a screen sharing session.
- The
WebRTC
media engine now honors the proxy server configured on the client device.
- Starting from Citrix Workspace app 2009.6 for Windows:
- Microsoft Teams displays previously used peripheral devices in the Preferred devices list.
- The
WebRTC
media engine accurately determines the maximum encoding resolution possible on an endpoint. TheWebRTC
media engine estimates multiple times a day and not only on first launch. - The Citrix Workspace app installer is packaged with the Microsoft Teams ringtones.
- Echo cancellation improvements - Reduced echo level when a peer has a speaker or microphone that generates an echo.
- Screen sharing improvements - when you share your screen, only the Desktop Viewer screen is captured in native bitmap format. Previously, client local windows that overlaid on top of the Desktop Viewer window were blacked out.
- Starting from Citrix Workspace app 2002 for Windows:
- when you share your workspace using Microsoft Teams, Citrix Workspace app displays a red border around the area of the monitor that is currently being shared. You can share only the Desktop Viewer window, or any local window overlaid on top of it. When you minimize the Desktop Viewer window, screen sharing is paused.