Citrix Workspace App package version is updated to 22.9.0.21.3.
NOTE:If you want to install the Citrix Workspace app version 2209 on ThinOS, install this package.
Supports virtual display layout
From ThinOS 2211 and Citrix Workspace App 2209, virtual display layout on VDA is supported. The virtual display configuration interface helps you to define a virtual display layout per session monitor on the VDA, in a live session. This feature allows you to split each session monitor independently into multiple virtual monitors. You can split the session into eight virtual monitors on the remote desktop. Also, you can update the session primary monitor and DPI settings for the displays.
The virtual display configuration is stored per user per client device, which has persisted across session resize, session disconnect or reconnect, and session logoff or login. The configured virtual display layout reset occurs on a session resize and change in the number of session monitors.
Before configuring the virtual display layout on VDA, keep in mind the following points:
Single-session or multisession operating system VDA is supported.
The graphics status indicator policy must be enabled.
VDA version 2019 or later (Dell Technologies qualified VDA 2203 LTSR and 2206).
NOTE:Only desktop sessions can be configured.
Follow these steps to configure your virtual display layout on VDA:
Right-click the graphics status indicator icon from the system tray and select
Configure virtual displays.
The virtual display configuration interface is launched.
Right-click a virtual display to mark it as the primary monitor.
Use the DPI drop-down list to set a preferred scaling factor for the virtual display.
You can draw horizontal or vertical lines to separate the screen into virtual monitors. The screen is split according to specified percentages of the session monitor resolutions.
After defining a virtual display layout, click
OK to save the layout, or
Cancel to discard the changes.
Use
Reset to undo the configuration and restore the original layout.
Log in to Citrix ADC using MFA with SAML, OKTA as IDP, and Citrix FAS for SSO to VDA
From ThinOS 2211 and Citrix Workspace App 2209, you can log in to Citrix Application Delivery Controller (ADC) through Multiple Factors Authentication (MFA) with Security Assertion and Markup Language (SAML), using OKTA as the identity provider, and Citrix FAS for Single Sign-On (SSO) to VDA.
From the desktop menu, go to
System setup >
Remote Connections.
The Remote Connections dialog box is displayed.
Click the
Broker Setup tab and select
Citrix Virtual Apps and Desktops from the
Broker Type drop-down list.
Enter the Citrix ADC gateway server URL in the
Broker Server field. You can also configure other options.
Click
OK.
The NetScaler gateway Webview login window is displayed and, you are redirected to Okta IDP for authentication.
Enter the user credentials with UPN format and password.
If you have not registered your phone with Okta Verify, you are prompted to setup MFA.
Select
Enter a code or
Get a push notification security method using Okta Verify application.
Launch the Okta Verify application on your phone.
If you selected
Enter a code previously, enter the code in the Citrix ADC login window and click
Verify.
If you selected
Get a push notification, approve the push notification on your phone once you get it.
If the authentication is successful, you are logged into Citrix ADC.
NOTE:ThinOS does not support Okta Single Sign-On (SSO) with Certificate Authentication.
Support for extended keyboard layouts
From ThinOS 2211 and Citrix Workspace App 2209, Japanese 106 keyboard, Portuguese ABNT/ABNT2 keyboards, and Multimedia keyboards are supported in Citrix VDI sessions. The Scancode keyboard input mode supports the extended keyboard layouts along with all keyboard layout synchronization modes.
This feature is disabled by default. To enable the extended keyboard layouts in Citrix VDI session, ensure that the Scancode keyboard input mode is configured, and do the following:
In
Admin Policy Tool or Wyse Management Suite policy settings, go to
Advanced >
VDI Configuration Editor >
Citrix Configuration Editor.
In
Citrix INI Settings, click
Add Row.
From the
File drop-down list, select
wfclient.ini.
From the
Operation drop-down list, select
Add or Update.
In the
Section field, enter
WFClient.
In the
Key field, enter
KeyboardEventMode.
In the
Value field, enter
Scancode.
Sign out or restart the device for the settings to take effect.
NOTE:Ensure that the setting
Enabled Volume Control for Client Volume is disabled in Admin Policy Tool or Wyse Management Suite policy. Otherwise, the Multimedia keyboards do not work.
Citrix Workspace App Limitations
In the server operating system VDA desktop (such as Windows server 2016, 2019, and 2022), if audio and video devices are required to be redirected into a session, ensure that the following registry settings are configured in session:
HKLM\Software\Citrix\PortICA\GenericUSB key and REG_DWORD value
UsbAudioEnabled is set to 1.
HKLM\Software\Citrix\PortICA\GenericUSB key and REG_DWORD value
UsbVideoEnabled is set to 1.
If audio and video devices redirection in server operating system VDA is not required, ensure
UsbAudioEnabled and
UsbVideoEnabled is set to 0.
For thin clients that have the default time zone as
UTC+0(UTC) in ThinOS 2208 and earlier versions, the Windows 11 VDA session may face display flickering issues after upgrading to ThinOS 2211. To resolve this, change the time zone or set the UTC+0 (UTC) time zone to
others and then set it back to
UTC+0 (UTC) from Admin Policy Tool or Wyse Management Suite policy.
Relative mouse feature does not work in Citrix Workspace App on ThinOS.
Citrix webview auto login does not work after rebooting the client, when the user credentials are configured through Wyse Management Suite.
The following new features from Citrix Workspace App 2209 are not supported in ThinOS:
Microsoft Teams enhancements: Enhancements to high DPI support
Keyboard input mode enhancements
Support for authentication using FIDO2
Known issues in Linux Citrix Workspace app binary
Multimedia Redirection (MMR) video stops responding, and there is no audio with Citrix VDA 2203 and VDA 2206.
When playing videos in Windows Media Video (WMV) version 9 or version 7 format, the wallpaper of the VDI session is displayed in the video.
If the Microsoft Teams optimization option is disabled, the audio and video devices in Microsoft Teams device settings are displayed as
None.
Microsoft LifeCam Cinema camera name is displayed as
Generic in
Citrix toolbar >
Devices >
Manage devices.
When trying to play .WMP format 4 K videos in Citrix, there are audio issues and no video is displayed.
Audio issue with Microsoft Teams during audio or video calls when using a browser.
Mouse cursor is not displayed correctly in Word in ICA Windows 2022 desktop.
Invert cursor is not working in ICA Windows 2022 desktop.
Dual monitor setup does not work when RDP client is published using Citrix application.
The webview login screen stops responding, and a white screen is displayed after network connection is lost.
The integrated audio speakers on Wyse 5470 thin clients emit an echo during calls or meeting. As a workaround, use a USB headset.
If there is a Microsoft Teams call or meeting happening between a Wyse 5470 thin client and a thin client that is or is not Wyse 5470 thin client, you may encounter audio issues when you enable the camera. You can change the default settings to troubleshoot the audio issues by doing the following:
In the Citrix JSON Settings, click
Add Row.
From the
File drop-down list,
select hdx_rtc_engine/config.json.
From the
Operation drop-down list, select
Add or Update.
In the
Key field, enter
EnableAEC.
In the
Value field, enter
0.
Follow steps one to three again.
In the
Key field, enter
EnableAGC.
In the
Value field, enter
0.
Follow steps one to three again.
In the
Key field, enter
EnableNS.
In the
Value field, enter
0.
Sign out or restart the device for the settings to take effect.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\