Dell Wyse ThinOS Version 9.0 Operating System Release Notes

In this release, the Citrix session printer support has been expanded to support all the client printer redirection functionality that is available in ThinOS v8.6. Based on the Citrix Host Printer Policy settings, ThinOS 9.0 supports the following:

• Device-Specific Printer Driver support—This method allows Citrix hosts to automatically create client redirected printer queues based on the peripheral management printers settings of the ThinOS client. The following details are used by the host print manager to automatically create the printer queues:

  • Name—Printer queue name
  • Printer ID (Printer Identification)—Printer driver name
• Citrix Universal Print Driver support—This method allows Citrix hosts to automatically create printer queues based on the peripheral management printers settings of the ThinOS client. The following details are used by the host print manager to automatically create the printer queues:
  • Name—Printer queue name
  • Class—Printer class that is associated by the Citrix host registry to a printer-specific driver name
  NOTE ThinOS 8.6 supports the association of PS, PCL5, and PCL4 classes. However, ThinOS 9.0 associations are limited to the PS class only.

Limitations

• The ThinOS solution to support the client printer redirection functionality is limited to Type 3 printers only. However, the solution is subject to changes in the future according to the changes made by Citrix.
• After you connect a USB printer to the thin client, the Printer ID information is not automatically displayed in the ThinOS client Peripheral Management Printer settings menu. This limitation will be resolved in future ThinOS releases.
• ThinOS supports only PS class when using the Citrix Universal Print Driver policy to automatically create ThinOS client redirected printers. PCL5 and PCL4 classes are not supported. This is a Citrix limitation.

In Citrix Workspace app, the Keyboard Dynamic synchronization mode functions differently on a Linux client from a Windows client. In general, on a Linux client, the keyboard output follows the client keyboard layout, which is different from the Windows VDA layout. Windows clients follow Windows VDA layout which is same as the Windows client keyboard layout. If a Linux client keyboard is synchronized to VDA, users may observe unpredictable output when working in a Windows VDA with a keyboard output that follows the Linux client keyboard layout. Also, in dynamic synchronization mode, Citrix Workspace app for Linux does not support VDA users to switch the keyboard layout inside a VDA session.

In the server default mode, both Linux and Windows use the session (VDA) side keyboard layout with predictable output. In this release, ThinOS has a customized Citrix package where the keyboard layout is set to server default mode, for the predictable output. The keyboard layout that you select on the thin client is not automatically synchronized in the VDA session. VDA users must select or switch the keyboard layout inside the VDA session using the Windows Input Method Editor (IME) language bar.

As a VDA administrator, you must configure the VDA desktop with the required keyboard language layout options. The IME language bar must be enabled on the Windows lock screen. This enables the VDA user to select the appropriate keyboard language layout on the Windows lock screen.

In scenarios such as opening a new application in a VDA session, locking, or unlocking the VDA session, the keyboard layout falls back to the VDA default layout. For example, EN_US. This is a known issue for a Linux client in the server default mode.

You can customize VDA registry settings for a consistent keyboard layout in the VDA session.

• For a desktop operating system VDA, the feature is enabled by default.
• For a server operating system VDA, you can enable the feature using the system registry.
  1. In the system registry of VDA, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout.
  2. Create a DWORD entry IgnoreRemoteKeyboardLayout=1.

     By default, the IgnoreRemoteKeyboardLayout entry is unavailable. The default keyboard is set to ENG, irrespective of the Control Panel setting.

     For example, open an application, lock, or unlock the session, the keyboard is set to ENG. To resolve this issue, ensure that you set IgnoreRemoteKeyboardLayout=1.

For information about the Keyboard Layout Modes and Keyboard Layout rules in Citrix Workspace app, see the Citrix Virtual Apps and Desktops keyboard and IME configurations article at www.citrix.com/blogs.

VDA settings for Server Default mode

When set to server default mode, the keyboard layout falls back to the VDA default layout. For example, EN_US. This issue can be related to Citrix Workspace app or Windows server operating system 2016/2019. All workarounds may require you to modify registry keys on the server side. For more information about workarounds, see the Citrix articles CTX269153 and CTX223316 at support.citrix.com. If you do not want to modify registry keys, contact the Citrix support team or the Microsoft support team.

Limitations—Keyboard shortcut keys such as Ctrl+Alt+Down, Ctrl+Alt+Left, and Ctrl+Alt+Right do not work inside the VDI session. To resolve this issue, press the Ctrl+Alt key combination inside the session. This is a Citrix limitation.

For information related to keyboard layout issues that are fixed in this release, see the Fixed issues section.

• Video call and share screen features are not recommended on Wyse 3040 Thin Clients due to client resource limitations.
• Video call and share screen features are recommended on Wyse 5070 Thin Clients, 5470 Thin Clients, and Wyse 5470 All-in-One Thin Clients. The following are the known issues:
  • Teams audio can be choppy when sharing the screen between a thin client and a laptop or personal computer that uses a native Microsoft Teams during the meeting. There is no workaround right now and the issue is being worked on.
  • During a Teams meeting, the audio can be choppy when the presenter has enabled the camera, or shared the screen and all participants are on mute. The issue is being worked on.

    Workaround—Ensure that at least one participant is unmuted when the presenter has enabled the camera or shared the screen.

  • Teams audio may sound robotic when sharing the screen between Dell Wyse 5070 and 5470 devices.
  • Teams audio can be choppy when playing back BCR html5 videos on a shared screen.
  • Teams audio can be choppy when browsing a website with multiple images on a shared screen.
  • Teams audio can be choppy on a thin client with dual core CPU.
• Citrix Workspace app Teams optimization issues:
  • Depending on your network bandwidth latency, the audio quality may fluctuate. To avoid this issue, ensure that your network bandwidth is adequate for audio or video call. Citrix recommends 200 kbps or higher network speed for a single client.
  • Switching cameras during a Microsoft Teams call in not recommended. This is a known Citrix Workspace App limitation [Case #80109986].
  • Session termination or abrupt disconnect may result in unexpected HdxRtcEngine.exe processing exits. This is a known Citrix Workspace Application limitation [RFLNX-5885].
  • If you are using Microsoft Teams (or Zoom), do not install the Cisco JVDI package. This issue is due to Cisco limitation.
  • When using a headset, you cannot answer or end the call using headset buttons. This issue is due to a limitation of Microsoft Teams.