Dell Wyse ThinOS Version 9.1.3129, 9.1.3112, 9.1.2101, and 9.1.1131 Operating System Release Notes

Limitations

• Bluetooth—Supports bluetooth audio paring to one thin client only, due to limitation of bluetooth stack on ThinOS.
• NIC port—ThinOS 9.1 supports only one extended NIC port.
• Captive wireless portal:
  • ThinOS 9.1 only supports HTTP redirect.
  • If an OPT (options) record with DNS resource record (RR) type 41 is available in a received DNS response, the same OPT record must be available in the Additional records section. ThinOS 9.1 does not support the DNS response with a OPT record that is available in the Answer section.
• QUMU—Some QUMU videos cannot playback with BCR enabled in Citrix desktop. For videos to be able to playback, Dell Technologies recommends not to configure BCR to make the video render on server side. However, this impacts the performance of the server.
• Citrix Unified Communications (UC):
  • Microsoft Teams limitations and their workarounds:
    • Sometimes shared screen and incoming video displays a black screen during Microsoft Teams call or meeting—Turn off or turn on the camera. If the issue is not resolved, end the meeting or call and rejoin.
    • Client audio does not work after changing the audio device in Microsoft Teams during a call or a meeting. Switch audio device in Microsoft Teams does not work. This issue occurs as JVDI package is installed—Uninstall the JVDI package. If you must use JVDI, ensure that you select the same headset between all Unified Communications software and client.
    • The Microsoft Teams camera is unavailable for preview at times and is unavailable during meeting—Restart Microsoft Teams.
    • If you hot plug camera in Microsoft teams device window or hot plug camera during meeting or call, the device does not display the camera. This is a Citrix binary issue—Restart Microsoft Teams.
    • Microsoft Teams audio appears to be distorted when the thin client has a dual core CPU.
    • When Microsoft Teams is run on a 32-bit browser like Google Chrome, it fails to receive the incoming video from browser, however, it can turn on the camera and share screen—Dell Technologies recommends you not to use web browser for Microsoft Teams, you may use the Teams app optimization instead.
  • Cisco Webex Meeting VDI limitations and their workarounds:
    • Webex meeting 41.6.1.10 cannot check audio and video statistics.
    • Webex meeting VDI mode is not enabled when you end the meeting and then rejoin the meeting within 5 s—This issue occurs as the previous meeting has not ended entirely. You may have to wait for the current meeting to end. Dell Technologies recommends you to wait for more than 10 s to join the new meeting, or if you encounter the non-VDI mode meeting, you can try to end the meeting and rejoin.
    • Cannot connect to audio or video device in Webex meeting if client time is not correct—Ensure that the client time zone and time is synced and correct.
    • Sometimes audio is not connected when a meeting is started—End the meeting and rejoin.
    • Client USB headset is changed to SST audio in Wyse 3040 Thin Client after ending or rejoining the Webex meeting for several times. This issue occurs as the JVDI package installed—Uninstall the JVDI package, or exit the Jabber application. If you must use JVDI, ensure that you select the same headset between all Unified Communications software and client.
    • When Webex Meeting is run on a 32-bit browser like Google Chrome, it fails to display the video from the browser and send video to other users. Distorted audio occurs during meeting and screen sharing. Share screen delay is also observed—Dell Technologies recommends you not to use web browser for Webex Meeting, you may use the Webex Meeting optimization instead.
    • Webex meeting does not work in optimized mode in Citrix VDI after reinstallation of the Citrix Workspace App— Uninstall WebEx meetings VDI package and reinstall it
  • Cisco WebEx VDI—Webex VDI annotate does not work from the host who is sharing the screen.
  • Cisco JVDI limitations and workarounds:
    • If you install JVDI package in ThinOS, the switched headset does not work in other Unified Communication software. The client audio is changed when you switch headset in Jabber—Dell Technologies recommends you not to install JVDI package if you are not using JVDI.
    • If you want to use JVDI with other Unified Communication software, ensure the headset that is used in Jabber is same as client audio device and with other Unified Communications software also do not change audio device in Jabber. This issue is due to Cisco limitation.
    • Bluetooth headset cannot be detected in JVDI device list from the remote desktop—Use USB or analog headset instead.
    • If you use JVDI on Wyse 5470 All-In-One Thin Client, the default speaker device in JVDI device selector is HD audio 2—Change the audio device from JVDI to your headset manually, or change the thin client audio from HD audio-2 to your headset.
  • Zoom—Zoom annotation stops working during screen sharing in a VDI session.
• VMware Blast Unified Communications (UC):
  • Cisco JVDI:
    • If you install JVDI package in ThinOS, the switched headset does not work in other Unified Communication software. The client audio is changed when you switch headset in Jabber—Dell Technologies recommends not to install JVDI package if you are not using JVDI.
    • If you want to use JVDI with other Unified Communication software, ensure the headset that is used in Jabber is same as client audio device and with other Unified Communications software also do not change audio device in Jabber. This issue is due to Cisco limitation.
    • Bluetooth headset cannot be detected in JVDI device list from the remote desktop—Use USB or analog headset instead.
    • If you use JVDI on Wyse 5470 All-In-One Thin Client, the default speaker device in the JVDI device selector is HD audio 2—Change the audio device from JVDI to your headset manually, or change the thin client audio from HD audio-2 to your headset.
  • Cisco WebEx VDI—Webex VDI annotate does not work from the host who is sharing the screen.
  • Zoom—Zoom annotation stops working during screen sharing in a VDI session.
• Enable Volume Control for Client Volume—The Enable Volume Control for Client Volume option added in Admin Policy Tool/WMS > Personalization > Shortcut Keys can be used to control the ThinOS local volume from the remote session. This option is added to resolve the Citrix limitation. This feature works only if you do not reboot your thin client after upgrading to ThinOS 9.1.3112. However, the functionality does not work across multiple reboots. Full support for this feature is planned for a future release.

• Identity Automation limitations:
  • Tapping card to sign-off broker causes IA app to stop responding with a blank white window.
  • After logging to the broker and locking it using Identity Automation Access, unlocking the broker without badge does not work and the system stops responding at Identity Automation window.
  • When selecting the password authentication method and tapping card in unlock window, unreadable warning message is displayed.
  • API Key is not treated as private and displays plain text in ThinOS GUI, Wyse Management Suite, and Admin Policy Tool.
  • In ThinOS System Tools > Package, double-click Package Identity Auto QwickAccess to see the package detail information. The package detail information is too long and not displayed in a user-friendly manner.
  • When non broker is configured, IA logon does not report notification to user.
  • If card and broker server are in different domain, system reports undefined error.
  • There are too many logs that are printed in system log.