Dell Wyse 3040 Thin Client Administrator's Guide PDF

Dell Wyse ThinOS 2205, 2208, and 2211 Administrators Guide

November 2022 Rev. A06

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid

the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

2022 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

Chapter 1: Introduction................................................................................................................ 11 Supported platforms.......................................................................................................................................................... 11

Chapter 2: What's new in ThinOS 2211......................................................................................... 12

Chapter 3: What's new in ThinOS 2208........................................................................................ 15

Chapter 4: What's new in ThinOS 2205....................................................................................... 20

Chapter 5: Upgrading the ThinOS firmware.................................................................................22 Before you upgrade.......................................................................................................................................................... 24

Important notes........................................................................................................................................................... 24 Register ThinOS devices to Wyse Management Suite.............................................................................................24

Register ThinOS devices using Wyse Device Agent........................................................................................... 24 Register ThinOS devices by using secure DHCP option tags.......................................................................... 25 Register ThinOS devices by using legacy DHCP option tags........................................................................... 26 Register devices using secure DNS records.........................................................................................................26 Register devices using legacy DNS records..........................................................................................................27

Enable Live Update........................................................................................................................................................... 27 Download the ThinOS firmware, BIOS, and application packages........................................................................ 28

File naming convention.............................................................................................................................................. 30 Upgrade ThinOS 9.x to later versions using Wyse Management Suite............................................................... 30 Upgrade ThinOS 9.x to later versions using Admin Policy Tool..............................................................................31 Convert Ubuntu 20.04 with DCA to ThinOS 2205 or later versions.....................................................................31 Convert WES to ThinOS 2211.........................................................................................................................................33 Add ThinOS application packages to the repository.................................................................................................33 Enhancements to the Application Package Updates category.............................................................................. 34 Upload and push ThinOS 9.x application packages using Groups and Configs on Wyse Management

Suite................................................................................................................................................................................. 35 Upload and install ThinOS 9.x application packages using Admin Policy Tool....................................................35 Firmware installation using Dell Wyse USB Imaging Tool........................................................................................ 35 Upgrade BIOS.....................................................................................................................................................................36 Edit BIOS settings.............................................................................................................................................................36 Delete ThinOS application packages.............................................................................................................................37 Downgrading the ThinOS firmware...............................................................................................................................37

Chapter 6: Getting started with ThinOS ..................................................................................... 38 End User License Agreement......................................................................................................................................... 38 Configure ThinOS using First Boot Wizard................................................................................................................. 38 Configure account privileges for ThinOS.................................................................................................................... 43

Configure account privileges using Admin Policy Tool....................................................................................... 44 Configure account privileges using Wyse Management Suite......................................................................... 44

Enable PCoIP Activation License...................................................................................................................................44 Connect to a remote server........................................................................................................................................... 45

Contents

Contents 3

Connecting a display.........................................................................................................................................................45 Connecting a printer.........................................................................................................................................................45 Configure WMS settings on the client GUI................................................................................................................ 45 Desktop overview..............................................................................................................................................................46 Modern interactive desktop features...........................................................................................................................46

Enable modern desktop mode.................................................................................................................................. 47 Modern toolbar or float bar.......................................................................................................................................47 List of connections......................................................................................................................................................48

Classic desktop features................................................................................................................................................. 48 Desktop guidelines...................................................................................................................................................... 48 Enable classic desktop mode....................................................................................................................................49 Using the taskbar........................................................................................................................................................ 49 Using the shortcut menu............................................................................................................................................51 Using the desktop menu.............................................................................................................................................51 Configure the Connection Manager....................................................................................................................... 52

Configuring thin client settings and connection broker settings...........................................................................52 Configure ThinOS using Admin Policy Tool.................................................................................................................53

Configure the Admin Policy Tool............................................................................................................................. 53 Feature list of Admin Policy Tool.............................................................................................................................53

Locking the thin client......................................................................................................................................................56 Shut down and restart.....................................................................................................................................................56 Scheduled Shutdown....................................................................................................................................................... 56 Scheduled Reboot.............................................................................................................................................................56 Enable or disable shutdown............................................................................................................................................ 57 Battery information...........................................................................................................................................................57 Login dialog box features................................................................................................................................................ 58 View the system information..........................................................................................................................................58 Sleep mode......................................................................................................................................................................... 59

Enable sleep manually.................................................................................................................................................59 Import certificates to ThinOS from Admin Policy Tool or Wyse Management Suite....................................... 59 ThinOS system variables................................................................................................................................................. 60 Manual override................................................................................................................................................................. 60

Chapter 7: Configuring the global connection settings................................................................ 62

Chapter 8: Configuring connectivity............................................................................................64 Configuring the network settings................................................................................................................................. 64

Configure the general settings.................................................................................................................................64 Configure the DHCP options settings....................................................................................................................65 Configure the ENET settings....................................................................................................................................67 Configure the WLAN settings.................................................................................................................................. 69 Configure the proxy settings.....................................................................................................................................71 Configure the SNMPV3 settings............................................................................................................................. 73

Configuring the remote connections............................................................................................................................ 74 Configure the broker setup....................................................................................................................................... 74 Configure the General Options.................................................................................................................................74

Configuring the central configurations........................................................................................................................ 75 Configure the Wyse Management Suite settings................................................................................................75

Configure the VPN Manager.......................................................................................................................................... 77

4 Contents

Configure VNC services...................................................................................................................................................78

Chapter 9: Configuring connection brokers................................................................................. 80 Configuring Citrix.............................................................................................................................................................. 80

Configure the Citrix broker setup............................................................................................................................80 Citrix ADC......................................................................................................................................................................84 Citrix Cloud services................................................................................................................................................... 89 Automatically configure using DNS for email discovery ................................................................................... 90 Citrix HDX Adaptive transport (EDT)..................................................................................................................... 91 HDX Adaptive Display V2........................................................................................................................................... 91 Browser content redirection.....................................................................................................................................92 HTML5 Video Redirection......................................................................................................................................... 92 Windows Media Redirection..................................................................................................................................... 93 QUMU Video Optimization Pack for Citrix............................................................................................................93 Citrix Self-Service Password Reset........................................................................................................................94 Citrix SuperCodec....................................................................................................................................................... 95 Anonymous logon........................................................................................................................................................ 95 Enable UDP audio in a Citrix session...................................................................................................................... 96 Keyboard layout synchronization in VDA...............................................................................................................96 Cursor pattern in ICA session................................................................................................................................. 103 Citrix multiple virtual channels................................................................................................................................103 Configure the Citrix session properties................................................................................................................105 Using multiple displays in a Citrix session............................................................................................................ 106 USB Printer Redirection........................................................................................................................................... 107 USB device redirection using Citrix Desktop Viewer........................................................................................ 107 Configure the Citrix UPD printer .......................................................................................................................... 108 Configure the device-specific printer driver....................................................................................................... 108 Invert cursor color..................................................................................................................................................... 109 Echo cancellation for Microsoft Teams............................................................................................................... 109 Multiwindow chat and meetings for Microsoft Teams......................................................................................110 UDP audio through Citrix Gateway .......................................................................................................................110 Multiple audio redirection.......................................................................................................................................... 111 Smart card reader plug and play..............................................................................................................................111 HDX RealTime Webcam Video Compression for 32-bit apps.......................................................................... 112 HDX RealTime Webcam Video Compression for 64-bit apps.......................................................................... 113 Export Citrix Workspace App logs..........................................................................................................................114 Configure multifarm................................................................................................................................................... 114 Configure multilogon..................................................................................................................................................115 Virtual Display Layout................................................................................................................................................ 115 Extended keyboard layouts ..................................................................................................................................... 116

Configuring VMware........................................................................................................................................................116 Configure the VMware broker connection........................................................................................................... 116 VMware Real Time Audio-Video..............................................................................................................................117 High Efficiency Video Coding.................................................................................................................................. 118 Enable Scanner Redirection..................................................................................................................................... 118 Enable Serial Port Redirection.................................................................................................................................119 Enable Session Collaboration................................................................................................................................... 119 Enable Battery State Redirection........................................................................................................................... 119 Relative mouse............................................................................................................................................................ 119 Configure Workspace ONE Mode..........................................................................................................................120

Contents 5

Unified Access Gateway.......................................................................................................................................... 120 Configure the VMware integrated printing settings.......................................................................................... 121 USB Redirection in a VDI session...........................................................................................................................122 Enable Multimedia Redirection in Blast session..................................................................................................123 Smartphone sync....................................................................................................................................................... 123 VMware Horizon Kiosk Mode..................................................................................................................................124

Special Peripheral Support............................................................................................................................................ 124 Bloomberg keyboard support.................................................................................................................................. 124 Confirm the USB interface redirection.................................................................................................................126 Nuance PowerMic II-NS...........................................................................................................................................129 Olympus RecMic DR-2200...................................................................................................................................... 132 Philips SpeechMike III............................................................................................................................................... 135 Wacom One................................................................................................................................................................. 138 Topaz Signature Tablet............................................................................................................................................ 139 Wacom Signature Tablet..........................................................................................................................................140 Wacom Intuos Pro M tablet..................................................................................................................................... 141

Configuring Azure Virtual Desktop.............................................................................................................................. 143 Enable printer in Azure Virtual Desktop............................................................................................................... 143 Log in to Azure Virtual Desktop using Active Directory Federation Services............................................. 144 Use camera redirection in an RDP session.......................................................................................................... 144

Configuring Microsoft Remote Desktop Services................................................................................................... 145 Enable Terminal Services Gateway....................................................................................................................... 145 Configure the Remote Desktop Services collection..........................................................................................145 Add a Remote Desktop Protocol connection......................................................................................................146 Log in to RDP session using Remote Desktop Gateway.................................................................................. 148 Log in to RDP session using Remote Desktop Gateway from Wyse Management Suite or Admin

Policy Tool............................................................................................................................................................... 150 Change the display mode for RDP connection using shortcut keys............................................................. 150

Configuring the Amazon WorkSpaces broker connection.....................................................................................150 Configure the Teradici Cloud Access broker connection....................................................................................... 151

Teradici PCoIP licensing........................................................................................................................................... 152 Configuring PCoIP connections using Teradici Remote Workstation card..................................................153 USB Redirection in a Teradici PCoIP session......................................................................................................154

Enable ThinOS to check the server certificate common name............................................................................154 Configure the Select Group feature to log in to different brokers..................................................................... 154 VDI Configuration Editor................................................................................................................................................155

Citrix Configuration Editor.......................................................................................................................................155 Horizon Blast Configuration Editor........................................................................................................................ 157 Zoom Plugin Configuration Editor..........................................................................................................................157

Configure the VDI settings............................................................................................................................................160 Authenticate the domain controller (NTLM) with None Broker agent ............................................................. 160

Chapter 10: Unified Communications optimization with ThinOS................................................. 162 Citrix HDX RealTime Optimization Pack for Skype for Business......................................................................... 162

Install the Citrix Workspace app package on ThinOS....................................................................................... 163 Set up the Skype for Business application.......................................................................................................... 163 Using the Skype for Business application............................................................................................................ 163 Verify the Skype for Business connection status.............................................................................................. 164 Citrix RTME call statistics....................................................................................................................................... 165

VMware Horizon Virtualization Pack for Skype for Business............................................................................... 165

6 Contents

Install the Horizon package on ThinOS................................................................................................................ 165 Setting up the Skype for Business in VMware Blast session..........................................................................165 Optimized mode and Fallback mode..................................................................................................................... 166 Change Optimized mode to Fallback mode......................................................................................................... 166

Cisco Jabber Softphone for VDI.................................................................................................................................. 167 Install the JVDI package on ThinOS...................................................................................................................... 168 Setting up the Cisco Jabber Softphone for VDI................................................................................................ 168 Using Cisco Jabber....................................................................................................................................................168 Using Device Selector...............................................................................................................................................169 Verify the Cisco Jabber connection status......................................................................................................... 169

Cisco Webex Teams for VDI......................................................................................................................................... 170 Install the Cisco Webex Teams package on ThinOS......................................................................................... 170 Setting up the Cisco Webex Teams for VDI.........................................................................................................171 Cisco Webex Teams optimization on Citrix Workspace app feature matrix.................................................171 Cisco Webex Teams optimization on VMware feature matrix........................................................................ 172 Verify the Cisco Webex Teams connection status............................................................................................ 173

Cisco Webex Meetings for VDI.....................................................................................................................................173 Install the Cisco Webex Meetings package on ThinOS.................................................................................... 174 Setting up the Cisco Webex Meetings for VDI...................................................................................................175 Cisco Webex Meetings optimization feature matrix......................................................................................... 175 Verify the Cisco Webex Meetings connection status....................................................................................... 176 Cisco Webex Meetings optimization known issues .......................................................................................... 177

Zoom Meetings for VDI.................................................................................................................................................. 177 Install the Zoom package on ThinOS.....................................................................................................................178 Setting up the Zoom Meetings for VDI................................................................................................................ 178 Zoom optimization feature matrix..........................................................................................................................178 Verify the Zoom connection status....................................................................................................................... 179

Microsoft Teams Optimization from Citrix Workspace app.................................................................................. 180 Microsoft Teams Optimization from VMware Horizon........................................................................................... 181

Enable the optimization by using a Group Policy Editor...................................................................................182 Microsoft Teams optimization feature matrix.................................................................................................... 182 Microsoft Teams optimization limitations and known issues.......................................................................... 183

RingCentral........................................................................................................................................................................184 ControlUp.......................................................................................................................................................................... 184

Chapter 11: Configuring third-party authentication settings...................................................... 185 Configure the Imprivata OneSign server................................................................................................................... 185 VDI selection on ThinOS................................................................................................................................................ 186

OMNIKEY readers......................................................................................................................................................186 Configure the VDI settings on OneSign server........................................................................................................ 186 Configure objects on Imprivata Server.......................................................................................................................186 Use smart card as proximity card................................................................................................................................ 188 Enroll a proximity card with Imprivata OneSign....................................................................................................... 188 Imprivata Bio-metric Single Sign-On...........................................................................................................................189 Imprivata Virtual Channel in PCoIP session from ThinOS ProveID Web............................................................189 Grace period to skip second authentication factor................................................................................................. 189 Imprivata OneSign ProveID Embedded...................................................................................................................... 189

Configure the OneSign Admin Console................................................................................................................. 191 Install the Imprivata PIE package on ThinOS.......................................................................................................191 Enable PIE mode on ThinOS....................................................................................................................................192

Contents 7

Uploading OneSign appliance SSL certificate.....................................................................................................192 Import the OneSign appliance SSL certificate automatically..........................................................................192 Import OneSign appliance SSL certificate manually..........................................................................................193 Configure Fast User Switching on ThinOS..........................................................................................................193

Configure Imprivata fingerprint reader for Citrix ICA and PCoIP sessions........................................................193 Configure Imprivata fingerprint reader for Blast sessions..................................................................................... 194 Identity Automation.........................................................................................................................................................194

Configure the Identity Automation........................................................................................................................ 194 Install the Identity Automation QwickAccess app package on ThinOS........................................................ 195 Identity Automation support matrix...................................................................................................................... 195 Enroll a proximity card with Identity Automation on ThinOS.......................................................................... 195 Use a proximity card for sign-on with Identity Automation on ThinOS........................................................195 Use a proximity card to secure the remote session with Identity Automation on ThinOS...................... 196 Use a proximity card to tap-over another user session with Identity Automation on ThinOS............... 196 PIN Reset.....................................................................................................................................................................196 Identity Automation feature matrix....................................................................................................................... 197

Chapter 12: Configuring the thin client local settings.................................................................198 Configuring the system preferences.......................................................................................................................... 198

Configure the general system preferences......................................................................................................... 198 Set the time and date............................................................................................................................................... 199 Set the custom information....................................................................................................................................200 Configuring power and sleep mode...................................................................................................................... 200

Configure the display settings..................................................................................................................................... 202 Using the On-Screen Display (OSD).................................................................................................................... 204 Port preferences on the Wyse 5470 Thin Client...............................................................................................204 Display limitation on Dell WD19 docking station................................................................................................ 204 Vertical Synchronization..........................................................................................................................................204 Configure the external touch screen settings................................................................................................... 205

Configuring the peripherals settings..........................................................................................................................205 Configure the keyboard settings...........................................................................................................................205 Configure the mouse settings................................................................................................................................207 Configure the touchpad settings.......................................................................................................................... 208 Configure the audio settings..................................................................................................................................208 Configure the serial settings................................................................................................................................... 210 Configure the camera device...................................................................................................................................211 Configure the Bluetooth settings........................................................................................................................... 211 Secure Digital cards...................................................................................................................................................212 Storage formats......................................................................................................................................................... 213 Configure the Jabra Xpress headset settings.................................................................................................... 213 Configure the EPOS headset settings..................................................................................................................213

Configure the HID Fingerprint reader settings......................................................................................................... 214 Configuring the printer settings...................................................................................................................................215

Configure the ports settings...................................................................................................................................216 Configure the LPDs settings...................................................................................................................................216 Configure the SMBs settings..................................................................................................................................217 Using the printer setup options..............................................................................................................................218 Using the Help............................................................................................................................................................ 219

Reset to factory defaults...............................................................................................................................................219 Resetting to factory defaults using G-Key reset..................................................................................................... 219

8 Contents

Recovery mode using R-Key.........................................................................................................................................219

Chapter 13: Using the system tools............................................................................................ 221 Simplified Certificate Enrollment Protocol................................................................................................................223

Request the certificate manually...........................................................................................................................223 Request the certificate automatically using Wyse Management Suite....................................................... 225 About Default Certificates......................................................................................................................................225

Trusted Platform Module version 2.0........................................................................................................................ 228

Chapter 14: Using Wyse Management Suite............................................................................... 229 Functional areas of Wyse Management Suite console.......................................................................................... 229 Managing groups and configurations.........................................................................................................................229

Create a default device policy group....................................................................................................................229 Create a user policy group.......................................................................................................................................231 Edit an unmanaged group....................................................................................................................................... 233 Remove a group........................................................................................................................................................ 233 Create and import bulk device exception file.....................................................................................................234

Edit the ThinOS 9.x policy settings............................................................................................................................ 237 Managing devices............................................................................................................................................................237

Search a device using filters on the Devices page........................................................................................... 238 View the display parameters.................................................................................................................................. 239

View the BIOS details.................................................................................................................................................... 239 Managing Jobs.................................................................................................................................................................239

Schedule a device command job........................................................................................................................... 240 Managing rules................................................................................................................................................................. 241

Editing a registration rule.........................................................................................................................................241 Create unmanaged device auto assignment rules ............................................................................................ 241 Edit an unmanaged device auto assignment rule.............................................................................................. 242 Disable or delete a rule.............................................................................................................................................242 Save the rule order................................................................................................................................................... 242 Create a rule for alert notification.........................................................................................................................242 Edit an alert notification rule.................................................................................................................................. 243

Managing Events.............................................................................................................................................................243 Search an event or alert using filters................................................................................................................... 243

Managing users................................................................................................................................................................244 Add a new admin profile.......................................................................................................................................... 244 Create a WMS custom role in Wyse Management Suite................................................................................ 245 Create auto assignment rules for unmanaged devices....................................................................................246 Add a user................................................................................................................................................................... 246 Bulk import end users.............................................................................................................................................. 246 Configure end user policy....................................................................................................................................... 246

Portal administration...................................................................................................................................................... 247 Adding the Active Directory server information................................................................................................ 247 Wyse Management suite Active Directory group feature matrix..................................................................249 Import unassigned users or user groups to public cloud through active directory....................................251 Access Wyse Management Suite file repository............................................................................................... 252

Chapter 15: Troubleshooting your thin client............................................................................. 254 Capture an HTTP log using ThinOS........................................................................................................................... 256

Contents 9

System crashes, freezes or restarts abruptly..........................................................................................................256 Broker agent login failure..............................................................................................................................................256 Citrix desktop and application crashes abruptly......................................................................................................256 Unified Communications software call failure..........................................................................................................257 Request a log file using Wyse Management Suite.................................................................................................. 257 View audit logs using Wyse Management Suite...................................................................................................... 257 System log and trace information...............................................................................................................................258

Chapter 16: Frequently Asked Questions................................................................................... 260 ThinOS-related questions............................................................................................................................................. 260

What should I do if the package installation fails?............................................................................................260 Is Wyse Management Suite the only way to manage ThinOS 9.x?.............................................................. 260 How to verify third-party binary versions on your ThinOS client?............................................................... 260 Is USB Imaging Tool method a possible option for upgrading to ThinOS 9.x?.......................................... 260 Can ThinOS be installed on a PCoIP device?.....................................................................................................260 Does ThinOS support zero desktop?................................................................................................................... 260 Does ThinOS 9.x support ThinOS configurations using INI files?................................................................. 260 iPhone cannot be redirected to the Citrix Desktop session........................................................................... 260 Android smartphone is not displayed in the session when redirected or mapped..................................... 261 Does Citrix Workspace app replace Citrix Receiver on ThinOS?...................................................................261 What is Workspace mode on ThinOS?................................................................................................................. 261 Can I enable Flash content to be rendered using a local Flash Player on ThinOS?...................................261 How do I verify if HDX Enlightened Data Transport Protocol is active?..................................................... 261 How do I check if HTML5 Video Redirection is working?............................................................................... 261 How do I check if QUMU Multimedia URL Redirection is working?.............................................................262 How do I check if Windows Media Redirection is working?...........................................................................262 How to check if Multimedia Redirection is working?.......................................................................................262 Is persistent logging supported in ThinOS 9.x?.................................................................................................262 Is tls.txt file included in network traces on ThinOS 9.x?.................................................................................262 Will ThinOS device reboot automatically when the system crashes?..........................................................262

Wyse Management Suite-related questions.............................................................................................................263 What takes precedence between Wyse Management Suite and ThinOS UI when conflicting

settings are enforced?........................................................................................................................................ 263 How do I import users from a .csv file?.............................................................................................................. 263 How do I use Wyse Management Suite file repository?..................................................................................263 How do I check the version of Wyse Management Suite............................................................................... 264

10 Contents

Introduction Thin clients running Dell Wyse ThinOS firmware are designed solely for optimal thin client security and performance. These efficient purpose-built thin clients offer ultrafast access to applications, files, and network resources within Virtual Desktop Infrastructure (VDI) environments. With zero attack surface, unpublished API, and encrypted data Wyse ThinOS is virus and malware resistant.

Wyse ThinOS requires a management software to configure, operate, and update thereby eliminating the need for IT support to visit or touch the physical devices. Dell Wyse Management Suite is the next generation management solution that enables you to centrally configure, monitor, manage, and optimize your ThinOS-based thin clients. As the number of devices grows, the Wyse Management Suite offers process automation and helps lower costs for large deployments of thin clients. With secure HTTPS-based communications and active directory authentication for role-based administration, Wyse Management Suite keeps your thin clients always up-to-date. The mobile application enables IT to view critical alerts, notifications on the dashboard, and send real-time commands.

This guide is intended for administrators of thin clients running Wyse ThinOS and using Wyse Management Suite to manage thin clients. It provides information and detailed system configurations to help you design and manage a ThinOS environment using Wyse Management Suite.

Supported platforms The Dell Wyse ThinOS firmware is supported on the following Dell Wyse thin clients:

Wyse 3040 Thin Client Wyse 5070 Thin Client Wyse 5470 Thin Client Wyse 5470 All-in-One Thin Client OptiPlex 3000 Thin Client Latitude 3420 OptiPlex 5400 All-in-One

NOTE: Wyse 3040 Thin Client is for users who work mostly on tasks with limited multimedia requirements. It is not

applicable for using multimedia such as BCR, HTML 5 video redirection, Window multimedia redirection, RTOP video

call, JVDI video call, enable video or share screen with Microsoft Teams, Webex Meetings, Webex Teams or Zoom. It is

recommended to use other platforms for high multimedia requirements.

1

Introduction 11

What's new in ThinOS 2211 Citrix Workspace app updates

Citrix Workspace App package version is updated to 22.9.0.21.2. Supports virtual display layoutFrom ThinOS 2211 and Citrix Workspace App 2209, virtual display layout on VDA is

supported. See Virtual Display Layout on page 115 Log in to Citrix ADC using MFA with SAML, OKTA as IDP, and Citrix FAS for SSO to VDASee Log in to Citrix

ADC using MFA with SAML, OKTA as IDP, and Citrix FAS for SSO to VDA. Support for extended keyboard layoutsJapanese 106 keyboard, Portuguese ABNT/ABNT2 keyboards, and

Multimedia keyboards are supported in Citrix VDI sessions. See Extended keyboard layouts. Microsoft Teams enhancementsFrom ThinOS 2211 and Citrix Workspace App 2209, App sharing is enabled in

Microsoft Teams optimization mode. You can share an application using the Screen sharing feature in Microsoft Teams. Microsoft RDP and AVD

SmartCard redirectionFrom ThinOS 2211 and AVD package version 1.9, SmartCard can be redirected in RDP and AVD sessions.

Printer update in RDP/AVD sessionIf you want to map a printer to the RDP/AVD session, install the specific driver in the RDP/AVD session before mapping. The printer supports only PostScript (PS) drivers in RDP/AVD session.

Teradici updatesTeradici version is updated to 22.07.3.16 in ThinOS 2211.

If USB or Bluetooth headsets do not work properly in PCoIP sessions, you can deploy the Teradici virtual audio driver in the PCoIP session.

Horizon Blast updates Horizon package version is updated to Horizon 2209 in ThinOS 2211. Supports Multi-session for a published applicationWhen multi-session mode is enabled for a published application,

you can use multiple sessions of the same published application when you log in to the server from different client devices.

Imprivata updatesThinOS Imprivata_PIE_7.9.000.0023.1162.pkg is supported against OneSign server 7.9.000.11 in ThinOS 2211.

Identity Automation updates Identity automation package is updated to 2.0.3.1. Supports PIN ResetYou can reset your PIN from the ThinOS login window by clicking Forgot your PIN. See PIN

Reset. Cisco WebEx Meetings VDI update

Cisco WebEx Meetings VDI version is updated to 42.10.5.15.3. Added meeting action soundsA sound is played for participants joining a meeting, leaving a meeting, raising hand,

receiving a message, and waiting in the lobby. Cisco WebEx VDI update

Cisco WebEx VDI package version is updated to 42.10.0.23814.5. Added new features:

Preview of shared content. Choose the skin tone for your reactions. See more in thumbnail videos. Maximize what you see when content is shared. Identify whether a meeting participant is internal, external, or unverified. Hosts can set a stage view for all meeting participants.

Cisco Jabber updateCisco Jabber version is updated to 14.1.2.307144.7. Zoom update

Zoom Citrix and Horizon package version is updated to 5.11.9.21750.8. Zoom AVD package is also supported in 5.11.9.21750.5.

RingCentral updateRingCentral package version, RcApp_VMwareplugin_22.2.30.44745.1, is supported in ThinOS 2211. See RingCentral.

ControlUp updateControlUp package version is updated to 1.0.0.1.21. See ControlUp. ThinOS updates

2

12 What's new in ThinOS 2211

Admin mode login event on Wyse Management Suite 4.0 serverIf you enable admin mode in Wyse Management Suite policy by going to Privacy & Security > Account Privileges and then log in, a login event is recorded. This event is recorded in Wyse Management Suite 4.0 server, whether the login is successful or not.

Fail to change BIOS settings event on Wyse Management Suite 4.0 serverIf you publish the BIOS policy from Wyse Management Suite 4.0 server with a wrong BIOS password, a failure event is recorded. This event is recorded in Wyse Management Suite 4.0 server.

Supports new MIB tree in SNMPV3 ThinOS supports MIB tree 1.3.6.1.4.1.714.1.2.6.1.2.0 to send message to client, and the message character count is raised to 255 characters. ThinOS also supports MIB tree 1.3.6.1.4.1.714.1.2.6.1.1.0 to reboot the client.

LPD printer serviceA thin client can be configured to provide Line Printer Daemon (LPD ) services, making the thin client a printer server on the network. The LPD printer service is applied with LPT printer and SMB printer.

Performance RetrospectiveWhen you click Performance Retrospective in the General tab of the Troubleshooting dialog box, CPU, Memory, and Disk data is displayed. When you click Networking, Network data like ENET and WLAN is displayed, and the data starts from terminal boot. Five-minute data is displayed by default, and you can select a time span in the list by using Prev and Next buttons.

VDI with Web Authentication updates Tested scenariosIn case any other (or custom) web authentication pages are used, correct caching of the

credentials, which results in behavior similar to ThinOS 2208 or earlier versions, cannot be guaranteed . The tested scenarios are as follows: - Citrix Federated Authentication Service SAML with Microsoft Azure Active Directory - Citrix ADC Native OTP - Citrix ADC MFA with SAML using OKTA as IDP and Citrix FAS for SSO to VDA - Horizon Workspace One Mode (On-premises) - Horizon Workspace One Mode (WS1 Access) - Horizon Workspace One Mode (WS1 Access) with OKTA IDP - VMware Unified Access Gateway with OKTA IDP - VMware Unified Access Gateway with Microsoft Azure IDP - Azure Virtual desktop Broker agent

Web Authentication Auto Login updateAfter setting the default credentials in Remote Connections > General Option, when you connect to a VDI Broker agent that uses Web Authentication, the default credentials passes through to the web page automatically.

Lock/Unlock Terminal when using Web Authentication method - In ThinOS 2208 (9.3.2102), after logging into a VDI Broker agent with Web Authentication and locking the ThinOS

session, you must set a temporary password to unlock the system. - From ThinOS 2211 (9.3.3096) onwards, a temporary password is not required. You can use the password that is

used at the time of logging in to unlock the system directly. Updated the First Boot Wizard import configuration password character limit from eight to nineWhen importing

the system settings configuration in First Boot Wizard, the minimum password character limit is nine characters. VPN UpdateGlobalProtect with .pfx certificate feature is added. Supports Enable SD card in OptiPlex 5400 All-in-One. Admin Policy Tool and Wyse Management Suite policy updates

NOTE: Wyse Management Suite 4.0 is required for Admin Policy Tool and Wyse Management Suite policy updates.

WINS Server Added new option WINS Server in Network Configuration > DNS Settings. If you disable Only use DNS configuration set in DHCP, you can set WINS Server.

NOTE: ThinOS only supports one WINS server.

SNMP Server ListAdded a new option SNMP Server List in Network Configuration > SNMPV3 Settings. TLS ControlAdded new options TLS Min Protocol, TLS Max Protocol, and Select Ciphers to disable in Privacy

& Security > Security Policy. Reason For RDP/AVD Session Disconnect is displayedThe default value is Enable in Session Settings > RDP

and AVD Session Settings. When an RDP/AVD session gets disconnected, a dialog box displays the reason for disconnection.

Hide TaskbarAdded a new option Hide Taskbar in Personalization > User Experience Settings > System Mode. Manual Override for Closing the LidAdded a new option Manual Override in System Settings > Power Sleep

Settings > Closing the Lid (MTC only). Manual Override Login SettingsAdded Manual Override Login Settings in Advanced > Login Experience >

Login Settings > Default Credentials. By default, the option is disabled.

What's new in ThinOS 2211 13

Unified Communication Virtual Channel Settings are added in Citrix Session Settings, Blast Session Settings, and RDP and AVD Session Settings. For more information, see Dell Wyse ThinOS 2205, 2208, and 2211 Release Notes at www.dell.com/support.

Supports showing picture from File Server optionYou can configure this option in WMS/ATP > Personalization > Screen Saver Settings > Showing Pictures > File Server option. If File server option is enabled, the client can download the screensaver images from the IIS file server.

Supports enabling LPD Service setting in printerTo configure this setting go to WMS/ATP > Peripheral Management > Printer > Local Printer Settings and SMB Printer Settings > Enable LPD Service. If enabled, the client can be configured to provide Line Printer Daemon (LPD ) services, that is, the client can work as a printer server on the network.

NOTE: LPD service for LPT and SMB is not supported in AVD/RDP sessions.

Secure MQTT connection for the Wyse Management Suite cloud serverWhen the client checks in to the Wyse Management Suite cloud server, the MQTT connection is routed to a secure MQTT connection. If the secure MQTT connection fails, the cloud server falls back to a nonsecure MQTT connection.

SCEP renewal interval updateIf the client fails to renew the certificate, the SCEP renewal interval changes from 20 s to 12 hours.

SMB printer update If the SMB printer credentials field is left empty, the client uses the login credentials (not the web login authentication credentials) as the SMB printer credentials.

Enable Group Change NoticeAdded Enable Group Change Notice in Services > WDA Settings. If this option is enabled, a dialog box is not displayed when changing the group on the thin client.

Enable Performance Retrospective Added Enable Performance Retrospective in APT/WMS > Advanced > Services > Troubleshooting Settings. By default, the option is disabled. When enabled, you must first specify the device for performance retrospective and the Performance Retrospective button, which is in Troubleshooting window of the General tab, can be enabled.

NOTE: As part of the upcoming ThinOS release, the implementation method of library dependencies for third-party

packages is going to change. Third-party packages that are released as part of ThinOS 2208 or earlier, are going to be

uninstalled from your ThinOS device when upgrading to the future ThinOS release. All third-party ThinOS packages (Zoom,

Cisco WebEx, Cisco jVDI, and so on) that are part of ThinOS 2211 are interoperable with the upcoming library dependency

changes. It is recommended that you upgrade all third-party packages to the versions that are launched as part of ThinOS

2211.

14 What's new in ThinOS 2211

What's new in ThinOS 2208 Citrix Workspace app updates

Citrix Workspace App package version is updated to 22.7.0.20.2. RTME (Citrix HDX Realtime Media Engine) is updated to 2.9.500-2802. Multi-window chat and meetings for Microsoft TeamsFrom ThinOS 2208 and Citrix Workspace App 2207

onwards, multi-window chat and meetings for Microsoft Teams is supported. Webcam redirection for 64-bit applicationsFrom ThinOS 2208 and Citrix Workspace App 2207 onwards, Webcam

redirection or HDX RealTime Webcam Video Compression is supported for 64-bit applications. Keyboard layout Dynamic Sync mode enhancementSee Keyboard layout Dynamic Sync mode enhancement. USB device redirection with Citrix Desktop ViewerSee USB device redirection using Citrix Desktop Viewer.

Azure Virtual Desktop updates AVD auto loginSet the default credentials in Remote Connections > General Option, and enable the Azure Virtual

Desktop Broker agent. When you reboot the client, you need not enter the credentials again, as the client automatically logs in using the AVD Broker agent

AVD auto connect listEnter the name of the connection that is displayed in Connection Manager to automatically connect after you log in the AVD Broker agent. You can enter more than one connection name. Each connection name is separated by a semicolon and is case-sensitive.

Teradici updates Teradici version is updated to 22.04.2.13 in ThinOS 2208. Support for PCoIP display real time refreshThere is no need to disconnect and reconnect to PCoIP session to

have a new display setting take effect. The PCoIP session adjusts the display settings in real time when changed. Imprivata updateAVD session supports Imprivata virtual channels with this release. When you log in to an AVD session

using Imprivata PIW or Imprivata PIE, you can enroll using a proximity card and fingerprint in the Imprivata agent in AVD session.

Cisco WebEx Meetings VDI updateSupports Virtual Background/Blur image feature. Cisco WebEx VDI updateSupports WebEx Teams VDI: Remove someone from a conference call feature. Zoom update Supports Gesture Recognition feature. Administrators can enable users to seamlessly provide reactions to

the people who are speaking by using hand gesture recognition during meetings. ThinOS local updates

Supports ET2201L IntelliTouch ZB (Worldwide) - E382790 and ET1717L AccuTouch ZB Black Anti-glare (Worldwide) - E649473 ELO touch monitors.

Supports OptiPlex 5400 All-in-One Improvements on Latitude 3420

Supports integrated microphone. Supports Dell DA310 7-in-1 USB-C Multiport Adapter. Supports DellWD19 docking station. Supports Type-C port display audio.

NOTE: Do not hot plug monitors on the WD19 docking station as this may cause a black screen issue. You can

hot plug the WD19 docking station.

NOTE: Display audio through WD19 docking station do not work if you hot plug the docking station. You must

reboot the device with the WD19 docking station connected, to use display audio. Display audio can only work

with one monitor on the WD19 docking station.

NOTE: Latitude 3420 supports display audio through one port only. If displays are connected using both HDMI

and Type-C, the Type-C display audio takes priority.

Power adapter is required to complete operating system firmware, application packages, or BIOS firmware installation Operating system firmware, application packages, or BIOS firmware cannot be installed without power adapter, and an error message Skip upgrade since AC power is not connected or disk space is not enough is displayed in the event log

Light theme for Modern modeThe theme can be enabled in Wyse Management Suite policy by going to Personalization > Experience Settings > Color scheme for Modern mode.

3

What's new in ThinOS 2208 15

Removed local ThinOS window icons from modern mode floatbarIn the previous release, few ThinOS local windows have icons on the modern mode floatbar, such as the System Information window. These icons are removed, and only VDI icons are displayed on the floatbar.

Added transparency in classic mode. Default desktop background Image is changed. SNMPV3 is supportedSNMPV3 in ThinOS requires security level with both authentication and privacy. This setting

can be configured in Wyse Management Suite policy by going to Network Configuration > SNMPV3 Settings. ThinOS supports MIB tree 1.3.6.1.2.1 but not 1.3.6.1.2.1.10, 1.3.6.1.2.1.4.20.1.5, and 1.3.6.1.2.1.4.21.1.10.

NOTE: ThinOS 2208 supports only Set and Get operations.

Updated the settings in System Preferences > Power and SleepIf the thin client does not support sleep mode, Sleep option is not displayed in the drop-down list and the default value is Power off with the timer Disabled.

Changed DNS SRV record to DNS/DHCP DiscoverThe name DNS SRV record is renamed to DNS/DHCP Discover in Central Configuration of the client menu. There is no change in the fuctionality.

Changed the order of options in LPDsIn Printer Setup > LPDs of the client menu, the order of the options are changed.

Changed the audio device priority when manual override is enabledWhen manual override is enabled, audio device priority does not change. To give priority to an audio device, select the audio device from the dropdown list manually. If the audio device is already selected in the dropdown list, choose another audio device in the list and change it back to the first audio device.

In the Import Configuration page during first boot, a drop-down list is added. The following two Wyse Management Suite URLs are shown by default: us1.wysemanagementsuite.com eu1.wysemanagementsuite.com

Updated the password policy when exporting logsWhen exporting logs from Troubleshooting, the password must include upper and lower case letters, numbers, and one or more special characters in !@#$%^&*-_. The minimum length of the password should be nine characters.

Lock Terminal enhancementA new group is created in Wyse Management Suite or Admin Policy Tool for Lock Terminal.

Figure 1. Lock Terminal in Wyse Management Suite

This group contains below parameters: 1. Enable Lock TerminalThis option enables the thin client to be locked. The default value of this parameter is ON.

The previous name of this parameter was Lock Terminal under the group Login Experience. NOTE: If the lock terminal option is disabled from ThinOS policy, the local terminal command from Wyse

Management Suite ignores this option and locks the thin client.

2. Sign Off instead of LockWhen web authentication or an anonymous user signs in, you can configure the thin client to sign off instead of lock. The default value of this parameter is OFF. The previous name of this parameter is Sign Off Automatically when Lock Terminal under group Screen Saver Settings

NOTE: If Enable Lock Terminal is OFF, this parameter is not shown and configured.

3. Enable Choose Lock BehaviorsWhen web authentication or an anonymous user signs in, you can configure the thin client to display a dialog box to set the unlock password, sign off, or cancel lock. The default value of this parameter is ON.

16 What's new in ThinOS 2208

NOTE: If Sign Off instead of Lock is ON, this parameter is not shown and configured. This parameter does not

take effect when no web authentication or anonymous login is detected.

4. Auto Sign Off Timer: You can set auto sign-off timer from 10 s to 600 s. The default value of this parameter is 60.

NOTE: If Enable Choose Lock Behaviors is OFF, this parameter is not shown and configured.

Enable Lock Terminal: If Enable Lock Terminal is ON, the Lock Terminal option is displayed and selected in ThinOS shutdown menu. If Enable Lock Terminal is OFF, the Lock Terminal option is disabled in the ThinOS shutdown menu. You cannot lock the terminal from ThinOS shutdown menu or using the ThinOS system shortcut Ctrl + Alt + Left/Right.

Lock Terminal on Web Authentication and Anonymous Logon user cases: ThinOS supports None broker agent Logon and various Web Authentication scenarios in VDI Logon. After ThinOS 2208 release, Lock Terminal will be supported in the following user cases: - Broker is None - Login AVD broker - Horizon Workspace One Mode - Horizon Anonymous Login - Horizon Kiosk mode - Horizon Azure + UAG broker - Horizon OKTA + UAG broker - Citrix Storefront Anonymous Login - Citrix Azure AD broker - Citrix OTP broker - Citrix Cloud with Web authentication

New features of Lock Terminal in Web Authentication and None broker agent login - After selecting Lock Terminal in ThinOS shutdown menu or using the ThinOS system shortcut Ctrl + Alt +

Left/Right, the Unable to Lock Account window is displayed.

Figure 2. Unable to Lock Account window - Once the countdown is over, terminal signs off. - When the Cancel button is clicked, the Lock Terminal operation is cancelled. - After the Set Password button is clicked, the Set Unlock Password window is displayed. You can follow the

password complexity requirements to set a one-time password, which can be used to unlock the terminal.

NOTE: Instead of Sign Off if Lock is ON, the terminal signs off when selecting Lock Terminal option from ThinOS

shutdown menu or using the ThinOS system shortcut Ctrl + Alt + Left/Right.

NOTE: If Enable Choose Lock Behaviors is OFF, the Lock Terminal function is disabled. Lock Terminal is

disabled in ThinOS shutdown menu. The ThinOS system shortcut Ctrl + Alt + Left/Right does not work either.

SMB printer credentials update for the VDI logon credentials and variablesIf there is an SMB printer configuration on the WMS, then the WMS SMB printer configuration always has high priority than the local SMB printer configuration. To always pass the VDI logon credentials to the SMB credentials, use $UN, $PW, $DN as the SMB printer username,

password, and domain on the WMS server or Local UI if there is no WMS configuration. If you leave SMB printer username, password, and domain empty on the WMS server or Local UI and if there is no

WMS configuration, the client VDI logon credentials will not pass to the SMB printer credentials after the VDI logs on to the client.

To use the same SMB printer credentials for all client users, configure the SMB printer common credentials (non- variables) on the WMS server or Local UI if there is no WMS configuration.

NOTE: After configuring $UN, $PW, $DN as the SMB printer username, password, and domain on the WMS

server, ensure that on the client the SMB printer credentials are empty before the VDI logon.

Wyse Management Suite and Admin Policy Tool updates

What's new in ThinOS 2208 17

DNS/DHCP DiscoverChange the option name from DNS Discover to DNS/DHCP Discover in Services > WDA Settings. The option can enable or disable ThinOS clients ability to discover Wyse Management Suite settings from both DNS and DHCP.

Force DiscoverAdded a new option Force Discover in Services > WDA Settings. If the option is enabled, ThinOS client can discover Wyse Management Suite settings from DNS/DHCP and register the client even if it is already registered to Wyse Management Suite. Enable DNS/DHCP Discover for this option to take effect.

Color scheme for Modern modeAdded a new option Color scheme for Modern mode in Personalization > Experience Settings. The Light theme is applied when Light option is selected.

Sleep ModeAdded a new option Sleep Mode in System Settings > Power Sleep Settings. If disabled, the sleep function is disabled on the ThinOS client, and the sleep option is removed on all the ThinOS local windows. If you publish sleep policies from Wyse Management Suite on the ThinOS client in System Preferences > Power and Sleep the value is set as Power off and the Timer is set as Disabled.

Firmware Update Logic Added a new option Firmware Update Logic in Firmware > OS Firmware Updates. When Any different firmware is selected, the client upgrades or downgrades to another operating system version. When New firmware only is selected, the client upgrades to a newer operating system version and cannot downgrade to an older operating system version.

Deep Sleep Control for OptiPlex 3000 Thin ClientAdded a new option Deep Sleep Control in BIOS > Dell OptiPlex 3000 Thin Client. If you set the value to Disabled, you can wake the client on LAN from the power off status. If set to other values, you cannot wake the client on LAN from the power off status.

BIOS settings page for OptiPlex 5400 AIOAdded a BIOS settings page to control the BIOS options for OptiPlex 5400 All-in-One.

Added Keyboard Error Detection, Fastboot, Extend BIOS POST time optionsAdded new options Fastboot and Extend BIOS POST time in BIOS for all platforms and added Keyboard Error Detection in BIOS for non-laptop platforms.

SNMPV3 SettingsAdded SNMPV3 Settings in Network Configuration. Enable SNMP Enable and set validate settings to make the ThinOS client an SNMPV3 agent.

RDS Web LoginAdded a new option RDS Web Login in Broker Settings > Microsoft Remote Desktop Settings. The default value is disabled. If enabled, Remote Desktop Service authentication uses the web login method instead of NTLM.

Automatically connect to sessionsAdded a new input box Automatically connect to sessions in Broker Settings > Azure Virtual Desktop Settings. Specify Connection Name is displayed in Connection Manager or on the client desktop to connect automatically.

NOTE: The name of the connection is case-sensitive. Use a semicolon to separate multiple connections to be

launched automatically.

Hold key audio warnings countdown Added a new option Hold key audio warnings countdown in Peripheral Management > Keyboard > Keyboard Settings. An audio beep is played on the current playback device when the timeout value (in milliseconds) has been reached after long pressing a key on the keyboard. Supported values are 0 to 20000, where 0 means disabled.

Hold key audio warnings beep repeat timeAdded a new option Hold key audio warnings beep repeat time in Peripheral Management > Keyboard > Keyboard Settings. You can specify the interval in milliseconds when the repetitive beeps are played. The supported values are 0 to 5000, where 0 means no beep repetition.

Added Single Button Connect settingsYou must set the default username, password, or domain and then enable Single Button Connect under the policy Login Experience > Login Settings > Default Credentials. The client does not log in to the VDI Broker agent automatically, but the default username, password, or domain is populated. After clicking the login button, the client logs in to the VDI Broker agent. The below four configurations are hidden and do not take effect: Disable Default User on Login Console Disable Default password on Login Console Disable Default Domain on Login Console Clear User

Added Single Connection settingThe Single Connection setting is added in Advanced Settings > Global Session Settings page. By default, the setting is disabled. If enabled, the client is limited to one active desktop. If you try to launch the second or more desktops, the event log displays an error message. If there is an auto connection list that contains multiple desktops, only one desktop is allowed to autoconnect. Logging off or disconnecting the active desktop and connecting another desktop is allowed, but you can only launch one desktop simultaneously. This setting is only applicable for desktop sessions and there is no restriction for published applications. When Single Connection is enabled or disabled from Admin Policy Tool or Wyse Management Suite policy, signing off from the Broker agent or restarting the client makes the setting take effect.

Added Only Show and Launch the OnDesktop Session Type settingOnly Show and Launch the OnDesktop Session Type setting is added in Advanced Settings > Global Session Settings > Display Settings page. The

18 What's new in ThinOS 2208

setting enables the launch of OnDesktop defined session type in Connection Manager with Classic mode or on the menu bar with Modern mode. The setting is enabled by default.

Application Package updates categoryClick Browse to upload application packages. All application packages are in the same drop-down list before. From ThinOS 2208, categories are added to improve the application packages visibility.

Added Edit Screen Saver in System PreferencesThe option can be displayed by going to Admin Policy Tool > Privacy & Security > Account Privileges, selecting Customize from privilege level drop down list, and enabling System Preferences. If System Preferences is enabled,Edit Screen Saver is enabled by default. If Edit Screen Saver is disabled, you cannot change and configure the screen saver settings from the client menu System Preferences.

Add default 5900 to the VNC service VNCD TCP Port text fieldGo to Service > VNC Service, and 5900 is displayed in the VNCD TCP Port text field. From ThinOS 2208, the default value is displayed as 5900.

Data validation on Proxy Server URLGo to Network Configuration > Proxy Settings, add a proxy row. The Proxy Server URL text field has data validation and cannot be saved if you cannot pass data validation.

DHCP option 42 enableAdded a new option DHCP option 42 enable in Network Configuration > DHCP Settings. Enable this option and the time server that is defined in DHCP server option 42 takes effect. After reboot each time, the event log displays Use DHCP NTP Servers: xxxxxx, Update time: xxxxxx, where the date and time syncs with the time server.

NOTE: When this option is enabled, the time server that is defined in DHCP server option 42 takes priority.

Changed the default value from enabled to disabled for the Map Disks In Session Settings > Global Session Settings > Local Resources and USB Redirection > Map Disks, the default value has been changed from enabled to disabled.

NOTE: If you do not change Map Disks default value on the last ConfigUI, you must enable the Map Disks option

again after upgrading to the ThinOS 2208 ConfigUI.

Lock TerminalLock Terminal group is new added under Login Settings in Login Experience. There are four settings in this group: Enable Lock TerminalThis setting was in the Login Experience group and now it is moved to Lock Terminal

group. Sign off instead of LockThis setting was called Sign Off Automatically when Lock Terminal in Personalization

> Screen Saver. Now its moved to Lock Terminal group. Enable Choose Lock BehaviorsThis setting is newly added. When WebAuth or anonymous user log in, it configures

to show a dialog to set unlock password, sign off, or cancel lock. Auto Sign Off TimerThis setting is newly added. Set auto sign-off timer from 10-600 seconds if auto sign off dialog

is triggered. For limitations, workaround, and known issues, see the individual sections in the Release Notes of your ThinOS version at www.dell.com/support.

What's new in ThinOS 2208 19

What's new in ThinOS 2205 Citrix Workspace app updates

From ThinOS 2205 and Citrix Workspace App 2203, Citrix Workspace app displays all available local audio devices in a session with their names. For more information, see Multiple audio redirection.

From ThinOS 2205 and Citrix Workspace app 2203, a user is allowed to disable smart card plug-and-play functionality. VMware Horizon updates

From the current release, VMware Horizon logs in automatically if the Kiosk Mode account Client Mac is configured as the ThinOS default user. See, VMware Horizon Kiosk Mode.

In virtual desktop sessions, the Real-Time Audio-Video feature displays the actual names of redirected devices with (VDI) appended. See, VMware Real Time Audio-Video.

Client users can use touch screen gestures in remote desktop and application sessions. Teradici updates

Teradici PCoIP version 22.01.5 is supported in ThinOS 2205. Updated USB redirection in a PCoIP section. See, USB Redirection in a Teradici PCoIP session.

Imprivata updateProximity card readers IMP-82-BLE and IMP-82 are supported in ThinOS 2205. For limitations and known issues, see the Release Notes of your ThinOS version at www.dell.com/support.

Unified Communications updates Cisco WebEx Meetings VDI package is updated to version 42.2.6.11.3. Cisco WebEx Teams VDI is updated to version 41.12.0.20899.3. Zoom package is updated to version 5.9.6.20931.7. Cisco JVDI package is updated to version 14.1.0.306686.4.

ThinOS local updates Added ThinOS Activation devices license in Wyse Management Suite. Latitude 3420 is supported from ThinOS 2205. MJPEG format is supported in the camera. Added wireless IP address info on Wi-Fi icon tooltips. On the import your ThinOS configuration page, WMS Prefix and Group key values are hidden. Click the eye icon to

display or hide values. Updated the peripherals list description in Devices tab. Added support for ELO ET2202L-2UWA-0-BL-G touch monitor. Added two new items to WMS server drop-down list on THINOS client menu Central Configuration. The new items are

us1.wysemanagementsuite.com and eu1.wysemanagementsuite.com. SMB Printer behavior updateWhen you log in to a Broker agent, the SMB credentials are taken from the Broker

agent login credentials, and these credentials are used for printing.

NOTE: The Broker agent sign-in credentials are expected to have priority over Wyse Management Suite credentials.

Wyse Management Suite and Admin Policy Tool updates Enable PcoIP Activation LicenseAdded Enable PCoIP Activation License option in Services > WDA Settings.

See, Enable PCoIP Activation License. Enable On screen option in RDP settings.Login to RDP session using Remote Desktop Gateway from Wyse

Management Suite or Admin Policy Tool. Manual Override Camera DeviceAdded Manual Override Camera Device in Advanced > Peripheral

Management > Camera > Camera Settings. If this option is enabled, the camera that is selected by user in the local UI on ThinOS, takes priority. It prevents Camera Settings from the WMS Server to overwrite the locally configured camera device until the option is disabled. The setting change only affects the Camera device option.

Default Camera optionAdded the option to set default camera in Advanced > Peripheral Management > Camera > Camera Settings. You can use full camera label, VID:PID, substring, or any valid regex. The setting tries to match the best available camera based on the substring. The option disables the user camera selection on local user interface if a default camera is found. Manual override is disabled.

Added MJPEG in the Camera Format list. Float bar activation delayChanged the input value scope of Delay Floatbar Activation in Milliseconds in

Advanced > Personalization > User Experience Settings to 70 - 60000.

4

20 What's new in ThinOS 2205

Turn Off DisplayTurn Off Display option is added in Advanced > Personalization > Screen Saver to turn off the display after a few minutes when the screensaver starts.

GUI change in VNC service to match the actual behaviorGo to Advanced > Services > VNC Service, turn on the option Enable VNC Daemon and then turn on the option Enable VNC Prompt. For the option Select Timeout Type, change the default value from Accept to Reject and for the option Timeout, change the default value from 0 to 10. This is only a GUI change and there is no change in the functionality.

DHCP option 252 enableAdded DHCP option 252 enable in Network Configuration > DHCP Settings. Enable or disable this option to enable or disable the proxy settings from DHCP option 252.

BIOS settings page for Latitude 3420Added BIOS settings page to control the BIOS options for Latitude 3420. NOTE: If you publish BIOS settings policy from Wyse Management Suite on Latitude 3420, the policy does not sync

to Admin Policy Tool. It takes effect in BIOS Setup directly.

Login Expire TimeChange the value range of Login Expire Time in Broker Settings > Citrix Virtual Apps and Desktops Settings. The new range is from 0 to 18446744073709551615 where 0 means follow server timeout policy.

NOTE: This policy only works when you log in to Citrix storefront server or Citrix NetScaler server with LDAP

authentication.

Disable Default Password on Login ConsoleAdded the option Disable Default Password on Login Console in Login Experience > Login Settings to disable the default password field in the login window.

NOTE: MFA token and Smartcard PIN are not impacted with this option.

The Username field in Peripheral Management > Printers > SMB Printer supports special characters such as $UN. The accepted length of Amazon WorkSpaces registration code is updated from 255 to 1023 characters in Wyse

Management Suite, Local Admin Policy Tool, and ThinOS local user interface. Enable logging levelRemoved 4, 5 from Login Experience > 3rd Party Authentication > 3rd Party

Authentication Settings > Enable logging level drop-down list. Hide On StartupAdded Hide On Startup in Peripheral Management > Mouse. If you enable this option, mouse

pointer will be hidden until you move the mouse, after you reboot the client. For limitations, workaround, and known issues, see the individual sections in the Release Notes of your ThinOS version at www.dell.com/support.

What's new in ThinOS 2205 21

Upgrading the ThinOS firmware It is recommended to use the Wyse Management Suite version 3.7 or later to upgrade your ThinOS firmware to the latest 9.x version. You can also use the USB Imaging Tool version 3.4.0 or later to install the ThinOS Merlin image on your thin client.

The overall upgrade process using Wyse Management Suite includes the following tasks:

1. Register your thin client to Wyse Management Suite. Register ThinOS devices using Central Configuration. See Register ThinOS devices using Wyse Device Agent. Register ThinOS devices using DHCP option tags. See Register devices by using DHCP option tags.

2. Download the ThinOS operating system image. See Download the ThinOS firmware. 3. Upgrade BIOS on your device to the current version mentioned in the BIOS details table in this section. 4. Upgrade the ThinOS firmware from 9.x to later versions. See Upgrade ThinOS 9.x to later versions. 5. Deploy the application packages. See Upload and push ThinOS 9.x application packages.

The following firmware upgrade scenarios are supported for upgrading to the latest ThinOS version:

ThinOS 9.1.3129 or later versions > ThinOS YYMM

From ThinOS version 9.1.6108, the following changes are made in the installation process:

The pop-up window for new firmware or application package is prompted before downloading the file. After you click Install Now, the download is initiated.

Once a file is downloaded, it gets installed before the next file is downloaded. After the installation of the downloaded file is finished, the next download is initiated.

ThinOS image is downloaded and installed first. The client reboots after the image is installed. After the reboot, the download and installation of other packages are initiated.

If you change the WMS server or group in the Central Configuration window when there is a notification window with a new available firmware or application package upgrade, a pop-up window is displayed to notify that the upgrade will be terminated.

For detailed information about the upgrade process, see the latest Migration Guide at www.dell.com/support.

Table 1. Firmware images

Platform ThinOS firmware image for upgrading from 9.x to later versions

Wyse 3040 Thin Client ThinOS_YYMM_version.pkg

Wyse 5070 Thin Client ThinOS_YYMM_version.pkg

Wyse 5470 Thin Client ThinOS_YYMM_version.pkg

Wyse 5470 All-in-One Thin Client ThinOS_YYMM_version.pkg

OptiPlex 3000 Thin Client ThinOS_YYMM_version.pkg

OptiPlex 5400 All-in-One ThinOS_YYMM_version.pkg

Latitude 3420 ThinOS_YYMM_version.pkg

Table 2. Ubuntu 20.04 to ThinOS conversion image

Platform ThinOS firmware image for converting from Ubuntu 20.04

Latitude 3420 ThinOS_YYMM_version_Ubuntu_Conversion.zip

OptiPlex 5400 All-in-One ThinOS_YYMM_version_Ubuntu_Conversion.zip

Table 3. Package information

Name Description Package installation

Citrix_Workspace_App The package supports Citrix Workspace app with RTME client integrated.

Upload the new package using Wyse Management Suite or Admin Policy Tool.

5

22 Upgrading the ThinOS firmware

Table 3. Package information (continued)

Name Description Package installation

Teradici_PCoIP The package supports the Teradici PCoIP connection.

Upload the new package using Wyse Management Suite or Admin Policy Tool.

VMware_Horizon The package supports VMware Blast. Upload the new package using Wyse Management Suite or Admin Policy Tool.

Imprivata_PIE The package supports Imprivata with ProveID Embedded feature.

Upload the new package using Wyse Management Suite or Admin Policy Tool.

Cisco_Jabber The package supports Cisco Jabber. Upload the new package using Wyse Management Suite or Admin Policy Tool.

Zoom_Horizon The package supports Zoom Meetings for VMware Horizon.

Upload the new package using Wyse Management Suite or Admin Policy Tool.

Zoom_Citrix The package supports Zoom Meetings for Citrix. Upload the new package using Wyse Management Suite or Admin Policy Tool.

Zoom_AVD The package supports

Zoom Meetings for AVD.

Upload the new package using Wyse Management Suite or Admin Policy Tool.

Cisco_WebEx_Meetings The package supports Cisco Webex Meetings. Upload the new package using Wyse Management Suite or Admin Policy Tool.

Cisco_WebEx_VDI The package supports Cisco Webex VDI. Upload the new package using Wyse Management Suite or Admin Policy Tool.

Microsoft_AVD The package supports Azure Virtual Desktop. Upload the new package using Wyse Management Suite or Admin Policy Tool.

Jabra The package supports Jabra headsets. Upload the new package using Wyse Management Suite or Admin Policy Tool.

EPOS_Connect The package supports EPOS Connect. Upload the new package using Wyse Management Suite or Admin Policy Tool.

HID_Fingerprint_Reader The package supports HID Fingerprint Reader. Upload the new package using Wyse Management Suite or Admin Policy Tool.

Identity_Automation_Qwi ckAccess

The package supports Identity Automation Upload the new package using Wyse Management Suite or Admin Policy Tool.

ControlUp_VDI_Agent The package supports

ControlUp.

Upload the new package using Wyse Management Suite or Admin Policy Tool.

RingCentral_App_VMwar e_Plugin

The package

Supports RingCentral.

Upload the new package using Wyse Management Suite or Admin Policy Tool.

NOTE: If the package fails to update, or if the thin client does not work after upgrading to the new firmware, remove all

packages and reboot the thin client. Reinstall the package after the reboot.

NOTE: To optimize security, application performance, and stability, a design change has been made in ThinOS 2205 when

installing third-party applications, like Citrix Workspace App, VMware Horizon, and Microsoft AVD. Third-party applications

released as part of ThinOS 2205 use a different shared library search path than older third-party package versions. Because

of this optimization, third-party packages that are released before ThinOS 2205 are no longer supported with ThinOS 2205

or later versions. Install the latest version of the required third-party application after you upgrade to ThinOS 2205 or later

versions.

NOTE: Third-party packages released before ThinOS 2205 can be downloaded but installation fails on the first attempt.

After that, the packages cannot be downloaded anymore.

Upgrading the ThinOS firmware 23

Table 4. BIOS details

Platform name BIOS version

Wyse 3040 Thin Client 1.2.5

Wyse 5070 Thin Client 1.18.0

Wyse 5470 All-in-One Thin Client 1.14.1

Wyse 5470 Thin Client 1.15.0

OptiPlex 3000 Thin Client 1.2.0

Latitude 3420 1.18.0

OptiPlex 5400 All-in-One 1.0.9

If Secure Boot is disabled, and the BIOS password is set as the default value or if there is no BIOS password, the Secure Boot option is automatically enabled after the next reboot.

Before you upgrade If you are using earlier versions of ThinOS 9.x, you must upgrade to ThinOS 9.1.3129 or later versions before upgrading to the

latest version of ThinOS 9.x. If you are using ThinOS 8.x, you must upgrade to ThinOS 9.1.3129 or later versions before upgrading to the latest version of

ThinOS 9.x. NOTE: From ThinOS 2205, there's no image to upgrade to the latest ThinOS version from ThinOS version 8.x directly

due to image file size limitation.

Your system must be powered on and the sleep mode must be disabled on the system. If the system has entered the sleep mode, you must send the WOL command using Wyse Management Suite before using any real-time commands. To use the WOL command, ensure that the Wake-On-LAN (WOL) option is enabled in BIOS.

Important notes

You cannot boot into ThinOS when you perform any of the following operations in BIOS setup: Disable the on-board Network Interface Card (NIC), Trusted Platform Module (TPM), or Platform Trust Technology

(PTT). Clear TPM or PTT. Reset BIOS to factory default settings

If you power off the ThinOS client by force, a counter in the TPM starts from one. When the counter reaches 32, the client encounters a Fatal Error. If the error is displayed, do the following: For ThinOS 2205 and older versions, you must reimage the device. For ThinOS 2208 and later versions, each time the TPM counter reaches 32 and encounters the issue, manually reboot to

recover the client.

Register ThinOS devices to Wyse Management Suite

NOTE: DHCP and DNS configurations for Wyse Management Suite work when the ThinOS client is not registered yet..

Register ThinOS devices using Wyse Device Agent

Steps

1. From the desktop menu of the thin client, go to System Setup > Central Configuration. The Central Configuration window is displayed.

2. Enter the Group Registration Key as configured by your administrator for the wanted group.

3. Select the Enable WMS Advanced Settings check box.

24 Upgrading the ThinOS firmware

4. In the WMS server field, enter the Wyse Management Server URL.

5. To verify the setup, click Validate Key. If the key is not validated, verify the group key and Wyse Management Suite server URL which you have provided. Ensure that ports mentioned are not blocked by the network. The default ports are 443 and 1883.

NOTE: If the Group Token parameter is not specified, the device is moved to the unmanaged group or quarantine group.

6. Enable or disable CA validation based on your license type. For public cloud, select the Enable CA Validation check box, and for private cloud, select the Enable CA Validation check box if you have imported certificates from a well-known certificate authority into your Wyse Management Suite server.

To enable the CA validation option in the private cloud, you must install the same self-signed certificate on the ThinOS device as well. If you have not installed the self-signed certificate in the ThinOS device, do not select the Enable CA Validation check box. You can install the certificate to the device by using Wyse Management Suite after registration, and then enable the CA validation option.

7. Click OK. The device is registered to Wyse Management Suite.

Register ThinOS devices by using secure DHCP option tags

About this task

You can register the devices by using the following secure DHCP option tags:

NOTE: Do not set secure DHCP option tags if your current ThinOS version is earlier than 9.1.6108.

Table 5. Registering device by using secure DHCP option tags

Option Tag Description

NameWMS

Data TypeString

Code201

DescriptionSecure WMS Server

The tag specifies the secure Wyse Management Suite server.

NameMQTT

Data TypeString

Code202

DescriptionSecure Group Token

The tag directs the device to fetch the secure Group Registration Key for Wyse Management Suite.

NameCA Validation

Data TypeString

Code167

DescriptionCertificate Authority Validation

You can enable or disable CA validation option if you are registering your devices with Wyse Management Suite on private cloud.

Enter True, if you have imported the SSL certificates from a well-known authority for https communication between the client and the Wyse Management Suite server.

Enter False, if you have not imported the SSL certificates from a well-known authority for https com@Wedding2020munication between the client and the Wyse Management Suite server.

NOTE: CA Validation is optional for Wyse Management Suite 2.0 and later versions. However, Dell Technologies recommends to configure this option tag.

NOTE: If you use both secure DHCP option tags and legacy DHCP option tags to register devices, secure DHCP option

tags take priority over legacy.

To get secure Wyse Management Suite server and secure Group Registration Key, do the following:

Upgrading the ThinOS firmware 25

Steps

1. Go to WMS Server > Portal Administration > Console Settings > WMS Discovery.

2. Enter the group token.

3. Select DHCP from the Discovery Type drop-down list.

4. Click Generate Details.

Register ThinOS devices by using legacy DHCP option tags

About this task

You can register the devices by using the following legacy DHCP option tags:

Table 6. Registering device by using legacy DHCP option tags

Option Tag Description

NameWMS

Data TypeString

Code165

DescriptionWMS Server FQDN

This tag points to the Wyse Management Suite server URL. For example, wmsserver.acme.com, where wmsserver.acme.com is fully qualified domain name of the server where Wyse Management Suite is installed.

NOTE: HTTPS:// is not required in the Wyse Management Suite URL.

NameMQTT

Data TypeString

Code166

DescriptionMQTT Server

This tag directs the device to the Wyse Management Suite Push Notification server (PNS). For a private cloud installation, the device gets directed to the MQTT service on the Wyse Management Suite server. For example, wmsservername.domain.com:1883. WDA automatically fetches the MQTT details when devices check in for the first time.

NOTE: MQTT is optional for Wyse Management Suite 2.0 and later versions.

NameCA Validation

Data TypeString

Code167

DescriptionCertificate Authority Validation

You can enable or disable CA validation option if you are registering your devices with Wyse Management Suite on private cloud.

Enter True, if you have imported the SSL certificates from a well-known authority for https communication between the client and the Wyse Management Suite server.

Enter False, if you have not imported the SSL certificates from a well-known authority for https com@Wedding2020munication between the client and the Wyse Management Suite server.

NOTE: CA Validation is optional for Wyse Management Suite 2.0 and later versions. However, Dell Technologies recommends to configure this option tag.

NameGroup Registration Key

Data TypeString

Code199

DescriptionGroup Registration Key

This tag directs to the Group Registration Key for the Wyse Management Suite agent. For example, in SCDA-DTos91SalesGroup, for the second part of the Group registration key, you must use 8-31 characters, with at least 1 upper, 1 lower, 1 number, 1 special character. However, special characters such as \(backslash), "(double quotes), '(single quote) are not allowed.

NOTE: Group Token is optional for Wyse Management Suite 2.0 and later versions on private cloud. However, there is a known issue that if you do not provide the group token, the device is not moved to unmanaged group. Therefore, It is recommended to configure the Group Token key.

Register devices using secure DNS records

Steps

1. On the Wyse Management Suite server, go to Portal Administration > WMS Discovery.

26 Upgrading the ThinOS firmware

2. Specify the Wyse Management Suite URL, Group Token, select DNS as the Discovery Type and click Generate Details to get the Wyse Management Suite URL and Group Token encrypt strings.

3. In the DNS server, go to DNS > DNS Server Host Name > Forward Lookup Zones > Domain and right-click the domain.

4. Click Other New Records.

5. Select Text (TXT), click Create Record, and do the following: To create the Wyse Management Suite Server record, enter the following values, and click OK.

Record name_WMS_MGMTV2. TextWyse Management Suite URL encrypt strings from Step 2.

To create the Wyse Management Suite Group Token record, enter the following values, and click OK. Record name_WMS_GROUPTOKENV2. TextGroup token encrypt strings from Step 2.

To create the Wyse Management Suite CA validation record, enter the following values, and then click OK. Record name_WMS_CAVALIDATION TextTRUE/FALSE

If you have not registered your ThinOS client to Wyse Management Suite and if you have set the DNS server with records, the device will automatically register to Wyse Management Suite.

NOTE: If both secure DNS records and legacy DNS records are set in the DNS server, the secure DNS records take

priority.

Register devices using legacy DNS records

Steps

1. In the DNS server, go to DNS > DNS Server Host Name > Forward Lookup Zones > Domain > _tcp, and right-click the _tcp option.

2. Click Other New Records. The Resource Record Type window is displayed.

3. Select the Service Location (SRV), click Create Record, and do the following: To create Wyse Management Suite server record, enter the following details and click OK: Service_WMS_MGMT Protocol_tcp Port number443 Host offering this serviceFQDN of WMS server

4. Go to DNS > DNS Server Host Name > Forward Lookup Zones > Domain, and right-click the domain.

5. Click Other New Records.

6. Select Text (TXT), click Create Record, and do the following: To create Wyse Management Suite Group Token record, enter the following values, and click OK:

Record name_WMS_GROUPTOKEN TextWMS Group token

To create Wyse Management Suite CA validation record, enter the following values, and then click OK: Record name_WMS_CAVALIDATION TextTRUE/FALSE

Enable Live Update

Steps

1. Open the Admin Policy Tool on your thin client or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. Click the Advanced tab.

3. Expand Services, and click WDA Settings.

4. Enable or disable Enable Live Update.

If enabled, the thin client starts downloading the firmware and package immediately. If the Live Update option is disabled, the thin client cannot download and install any firmware or package until the next reboot. However, the firmware or packages are downloaded in the following scenarios even when the Live Update option is disabled:

Upgrading the ThinOS firmware 27

When you register the thin client to Wyse Management Suite manually. When you power on the thin client from a power off state. When you change the Wyse Management Suite group.

5. Click Save & Publish.

Download the ThinOS firmware, BIOS, and application packages

About this task

This section describes the steps to download the ThinOS firmware, BIOS, and application packages from Dell support site.

Steps

1. Go to www.dell.com/support.

2. In the Enter a Service Tag, Serial Number, Service Request, Model, or Keyword field, type the model number of your device.

3. Select the product from the searched results to load the product page.

4. On the product support page, click Drivers & downloads.

5. Select the operating system as ThinOS .

6. Locate the ThinOS image entry and download the image.

Table 7. ThinOS 2211 image

Scenario ThinOS image title

Upgrade your ThinOS 9.1.3129 or later versions to 2211 (9.3.3096)

ThinOS 9.1.3129 or later to ThinOS 2211 (9.3.3096) Image file for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, Dell OptiPlex 3000 Thin Client, Dell Latitude 3420, and Dell OptiPlex 5400 All-in-One with ThinOS

Ubuntu to ThinOS 2211 conversion image ThinOS 2211 Ubuntu conversion image for Latitude 3420 and OptiPlex 5400 All-in-One.

WES to ThinOS 2211 conversion image ThinOS 2211 WES conversion image for Wyse 5070 Thin Client, Wyse 5470 Mobile Thin Client, and Wyse 5470 All-in- One Thin Client.

Table 8. ThinOS 2208 Image

Scenario ThinOS image title

Upgrade your ThinOS 9.1.3129 or later versions to 2208 (9.3.2102).

ThinOS 9.1.3129 or later to ThinOS 2208 (9.3.2102) Image file for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, and Dell OptiPlex 3000 Thin Client.

Ubuntu to ThinOS 2208 conversion image

ThinOS 2208 conversion image for Latitude 3420 and OptiPlex 5400 All-in-One.

Table 9. ThinOS 2205 Image

Scenario ThinOS image title

Upgrade your ThinOS 9.1.3129 or later versions to 2205 (9.3.1129).

ThinOS 9.1.3129 or later to ThinOS 2205 (9.3.1129) Image file for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, and Dell OptiPlex 3000 Thin Client.

Ubuntu to ThinOS 2205 conversion image

ThinOS 2205 conversion image for Latitude 3420

NOTE: If you are using the Dell Wyse USB Imaging Tool to install the ThinOS image on a single client, you must

download the ThinOS 2205 (9.3.1129) Merlin image.

28 Upgrading the ThinOS firmware

7. If you want to use ThinOS packages, locate a package and download the package to your device.

NOTE: For a given ThinOS release, you can install only the supported packages mentioned in the corresponding ThinOS

Release Notes available at www.dell.com/support.

Table 10. ThinOS packages

ThinOS packages ThinOS image title

Citrix_Workspace_App ThinOS YYMM Citrix package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

VMware_Horizon ThinOS YYMM VMware Horizon package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Teradici_PCoIP ThinOS YYMM Teradici PCoIP package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Microsoft_AVD ThinOS YYMM Microsoft AVD package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Imprivata_PIE ThinOS YYMM Imprivata package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Zoom_Horizon ThinOS YYMM Zoom Horizon package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Zoom_Citrix ThinOS YYMM Zoom Citrix package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Jabra ThinOS YYMM Jabra headsets package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

EPOS_Connect ThinOS YYMM EPOS Connect package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Cisco_WebEx_VDI ThinOS YYMM Cisco Webex VDI package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Cisco_WebEx_Meetings ThinOS YYMM Cisco Webex Meetings package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Cisco_Jabber ThinOS YYMM Cisco Jabber package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

HID_Fingerprint_Reader ThinOS YYMM HID Fingerprint Reader package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Identity_Automation_Qwic kAccess

ThinOS YYMM Identity Automation QwickAccess package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Zoom_AVD ThinOS YYMM Identity Automation QwickAccess package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

Upgrading the ThinOS firmware 29

Table 10. ThinOS packages (continued)

ThinOS packages ThinOS image title

ControlUp_VDI_Agent ThinOS YYMM ControlUp VDI Agent package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

RingCentral_App_VMware _Plugin

ThinOS YYMM RingCentral App VMWare Plugin package for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients, OptiPlex 3000 Thin Client, OptiPlex 5400 All-in-One, and Latitude 3420

8. If you want to install the latest BIOS package, locate the package entryThinOS BIOS package for your thin client model and click the download icon.

NOTE: After you upgrade the client, install the Citrix Workspace app package first, and then reinstall the Citrix-related

application packages such as Cisco WebEx Meeting or HID.

NOTE: For more information about BIOS installation, see BIOS Installation.

NOTE: To optimize security, application performance, and stability, a design change has been made in ThinOS 2205

when installing third-party applications, like Citrix Workspace App, VMware Horizon, and Microsoft AVD. Third-party

applications released as part of ThinOS 2205 use a different shared library search path than older third-party package

versions. Because of this optimization, third-party packages that are released before ThinOS 2205 are no longer

supported with ThinOS 2205 or later versions. Install the latest version of the required third-party application after you

upgrade to ThinOS 2205 or later versions.

File naming convention

ThinOS application packages, ThinOS firmware, and BIOS packages support the following characters in their file names:

Uppercase letter Lowercase letter Numeric character Special charactersperiod (.), hyphen-minus (-), and underscores (_)

If you use other characters in file names, the package installation fails.

Upgrade ThinOS 9.x to later versions using Wyse Management Suite

Prerequisites

Ensure that you are running 9.1.3129 or later versions on your thin client. Create a group in Wyse Management Suite with a valid group token. Use this group token to register the ThinOS 9.x devices. Register your thin client to Wyse Management Suite.

Steps

1. Go to the Groups & Configs page, and select a group.

2. From the Edit Policies drop-down menu, click ThinOS 9.x. The Configuration Control | ThinOS window is displayed.

3. Click Advanced.

4. In the Firmware field, select OS Firmware Updates.

5. Click Browse to browse and upload the firmware. The EULA details of the package and the name of the vendors are displayed.

6. Click the vendor names to read the license agreement of each vendor and then click Accept to upload the package.

You can select the Do not show this again if you do not want to see the EULA details of the same vendor again.

30 Upgrading the ThinOS firmware

NOTE: If you upload multiple packages, the EULA details of each package are displayed. You must accept the license

agreement of the packages individually. The firmware is not uploaded if you click Decline.

7. From the Select the ThinOS Firmware to deploy drop-down menu, select the uploaded firmware.

8. Click Save & Publish. The thin client downloads the firmware and restarts. The firmware version is upgraded.

Upgrade ThinOS 9.x to later versions using Admin Policy Tool The firmware upgrade using Admin Policy Tool is supported on ThinOS 9.x.

Prerequisites

Ensure that you are running ThinOS 9.1.3129 or later versions on your thin client.

Steps

1. Go to the Admin Policy Tool on the ThinOS client.

2. In the Configuration Control | ThinOS window is displayed. Click Advanced.

3. In the Firmware field, select OS Firmware Updates.

4. Click Browse to browse and upload the firmware from USB drive.

5. From the Select the ThinOS Firmware to deploy drop-down menu, select the uploaded firmware.

6. Click Save & Publish. The thin client downloads the firmware and restarts. The firmware version is upgraded.

Convert Ubuntu 20.04 with DCA to ThinOS 2205 or later versions Supported platforms to convert Ubuntu 20.04 with DCA to ThinOS 2205 or later versions are Latitude 3420 and OptiPlex 5400 All-in-One.

Prerequisites

If you have a Ubuntu device that is running Ubuntu 20.04 operating system, ensure that DCA-Enabler 1.5.0-14 or later versions are installed. For details on how to install DCA-Enabler in Ubuntu operating system and upgrade it, see Dell Wyse ThinOS 2205, 2208, and 2211 Migration Guide at www.dell.com/support.

NOTE: The Ubuntu device must have a factory-installed Ubuntu 20.04 operating system. If you have custom installed

the Ubuntu operating system, you cannot convert it to ThinOS 2205 or later versions.

NOTE: There are some languages that do not support the conversion from Ubuntu to ThinOS 2205. Dell Technologies

recommends you to set Ubuntu to English language for the conversion process.

Wyse Management Suite version 3.7 or later versions must be used to convert to ThinOS 2205 or later versions. Ensure that you have connected the device to the external power source using the power adapter. Ensure you have enough ThinOS Activation devices licenses on Wyse Management Suite 3.7 or later versions. Create a group in Wyse Management Suite with a group token. The ThinOS Activation devices license number of Wyse Management Suite must be larger than the Ubuntu device number. If

it is not, you cannot create the Advanced Policy for conversion. The Ubuntu 20.04 devices must be registered to Wyse Management Suite as generic clients. For details on how to register

generic clients to Wyse Management Suite, see Dell Wyse ThinOS 2205, 2208, and 2211 Migration Guide at www.dell.com/ support.

Ensure you have downloaded the Ubuntu 20.04 to ThinOS conversion image. Extract the Ubuntu 20.04 to ThinOS conversion image to get the Conversion Installer file DTOS_Ubuntu_Installer_x.x-

dtosx-amd64_signed.tar.gz and ThinOS image ThinOS_YYMM_9.x.pkg.

NOTE: The ThinOS image ThinOS_YYMM_9.x.pkg can be used for downgrading in the future.

Upgrading the ThinOS firmware 31

Steps

1. Go to Apps & Data > App Inventory > Generic Client, and click Add Package file.

2. Upload the Conversion Installer file DTOS_Ubuntu_Installer_x.x-dtosx-amd64_signed.tar.gz

3. Go to Apps & Data > OS Image Repository > ThinOS 9.x, and click Add Firmware file.

4. Upload the ThinOS image ThinOS_YYMM_9.x.pkg.

5. Go to Apps & Data > App Policies > Generic Client, and click Add Advanced Policy.

6. Enter the policy name, select the group in which Ubuntu device has been registered, and select Generic Client as OS type.

7. Click Add app, and select the Conversion Installer file that was uploaded before from the drop-down menu.

8. Click Add app again, and select the ThinOS image file that was uploaded before from the drop-down menu.

9. Select all the platform that you want to convert in the Platform Filter drop-down menu.

10. Click Save.

NOTE: Ensure that the Apply Policy Automatically option is set to Do not apply automatically.

11. In the pop-up window, click Yes to schedule a job.

12. Select Immediately in the Run drop-down menu on App Policy Job window, and click Preview.

13. Click Schedule. The Conversion Installer file downloads and installs first followed by the ThinOS image on Ubuntu device. After installation, the device restarts automatically.

NOTE: After you register the converted ThinOS device to Wyse Management Suite, the ThinOS activation devices

license is consumed automatically.

NOTE: After conversion, ThinOS is in the factory default status. ThinOS must be registered to Wyse Management Suite

manually or using DHCP/DNS discovery.

NOTE: If the conversion has failed, you can refer to the error log table below and reschedule the job. Go to Jobs >

Schedule APP Policy to reschedule the job.

If there is /usr/dtos folder in the Ubuntu 20.04 device, then you can use command cat /var/log/ dtos_dca_installer.log to get error log. If there is no /usr/dtos folder present in the device that runs Ubuntu 20.04, go to the Jobs page in Wyse Management Suite server to check the error messages.

Table 11. Error log

Error Log Resolution

No AC plugged in Plug in power adapter, re-schedule job

Platform Not Supported This hardware platform is not supported

Error mounting recovery partition The Ubuntu image is not a factory image. Re-install the factory image.

No DHC/ThinOS package in recovery partition Cannot find the ThinOS image, re-schedule job

Error in extracting DHC/ThinOS Future packages Failed to extract the ThinOS image, re-schedule job

Error copying the DHC/ThinOS Future packages to recovery partition

Failed to copy the ThinOS image, re-schedule job

ThinOS package verification failed ThinOS image is not correct, re-schedule job with the correct ThinOS image

Not enough space in Recovery Partition Clear the recovery partition

The free space of Recovery Partition is not enough Clear the recovery partition

32 Upgrading the ThinOS firmware

Convert WES to ThinOS 2211 Supported platforms that can convert WES to ThinOS 2211 are Wyse 5070 Thin Client, Wyse 5470 Mobile Thin Client, and Wyse 5470 All-in-One Thin Client.

Prerequisites

Ensure you are running Windows 10 Enterprise LTSC 2019 version 10.04.08.05.22.00. Ensure that you are running Wyse Management Suite 4.0 or later versions. Ensure that there are enough ThinOS Activation licenses on devices with Wyse Management Suite 4.0 or later versions. Create a group in Wyse Management Suite with a group token. You must be registered to Wyse Management Suite. Ensure that you have downloaded WES to ThinOS 2211 conversion image.

Steps

1. Extract the conversion image .zip file to get the exe file and copy this file to the Wyse Management Suite 4.0 or later version server repository.

The path to upload the conversion image is Repository Location > repository > osImages > zipped.

2. On the Wyse Management Suite page, go to Portal Administration > File Repository, select the repository, and click Sync Files. Wait for the synchronization to complete.

3. Ensure that the conversion image is in the repository by going to Apps & Data > OS Image Repository > WES/ThinLinux.

4. Go to Apps & Data > OS Image Policies > WES/ThinLinux, click Add Policy.

5. Enter the policy name.

6. Select the group that WES devices are registered to and select WES as OS type.

7. Select WIE10 as OS Subtype Filter.

8. Select the conversion image as OS Image.

9. Select Force this version as Rule.

10. In the Apply Policy Automatically drop-down list, select Do not apply automatically.

11. Click Save. A dialog box is displayed to schedule a job.

12. Click Yes to schedule a job.

13. Select Immediately from the Run drop-down list in the App Policy Job dialog box.

14. Click Preview.

15. Click Schedule when the next dialog box is displayed.

The WES device downloads and installs the conversion image. After installation, the device reboots automatically to ThinOS.

NOTE: After conversion, ThinOS is in factory default status. You must register ThinOS to Wyse Management Suite

manually or by DHCP/DNS discovery.

NOTE: After you register the converted ThinOS devices to Wyse Management Suite, the ThinOS Activation devices

license is consumed.

Add ThinOS application packages to the repository

Steps

1. Log in to Wyse Management Suite using your tenant credentials.

2. In the Apps & Data tab, under OS Image Repository, click ThinOS 9.x.

3. Click Add Package file. The Add Package screen is displayed.

4. To select a file, click Browse and go to the location where your file is located. If the EULA is embedded in the package, the EULA details of the package and the name of the vendors are displayed.

You can click the vendor names to read the license agreement of each vendor. Click Accept to upload the package. You

Upgrading the ThinOS firmware 33

can select the Do not show this again if you do not want to see the EULA details of the same vendor again. You must accept the license agreement of the packages individually. The package is not uploaded if you click Decline.

If the EULA is not embedded in the package, go to step 5.

5. Click Upload.

NOTE: The operator can upload the package from operator account and is visible to all the tenants. Tenants cannot

delete or modify these files.

Enhancements to the Application Package Updates category When you click Browse to upload the application packages, all the application packages are available in the same drop-down list before. From ThinOS 2208, categories are added to improve the visibility of the application packages. The following are the defined categories:

1. Citrix Citrix Workspace App

2. VMware VMware Horizon

3. Microsoft Microsoft AVD

4. Zoom Zoom Citrix Zoom Horizon Zoom AVD

5. Cisco Cisco Jabber Cisco WebEx Meetings VDI Cisco WebEx VDI

6. Dell Security Addon Hotfix

7. Third Party Teradici PCoIP Imprivata PIE Jabra EPOS Connect HID Fingerprint Reader Identity Automation QwickAccess ControlUp VDI Agent RingCentral App VMware Plugin

8. Other Application packages are not predefined yet.

For each category, there is one switch option INSTALL/UNINSTALL on the left and one drop-down list Not Selected by default on the right. Click the drop-down list, and the uploaded versions of the application package is displayed. You can select only one version in the list and the drop-down list title changes to the package name and repository.

NOTE: For Other category, you can select multiple application packages and versions, as the application packages are

not predefined yet. Once you have the application packages in Other category, it is recommended you upgrade the

Wyse Management Suite configUI. The new Wyse Management Suite configUI sets the application packages in the new

category.

If the switch option is set to INSTALL, the selected application package version in the drop-down list is published to the ThinOS client to install.

If the switch option is set to Uninstall, the application package drop-down list is disabled, and the application package is uninstalled from the ThinOS client.

34 Upgrading the ThinOS firmware

Upload and push ThinOS 9.x application packages using Groups and Configs on Wyse Management Suite

Prerequisites

Create a group in Wyse Management Suite with a group token. Use this group token to register the ThinOS 9.x devices. Register the thin client to Wyse Management Suite.

Steps

1. Go to the Groups & Configs page, and select a group.

2. From the Edit Policies drop-down menu, click ThinOS 9.x. The Configuration Control | ThinOS window is displayed.

3. Click Advanced.

4. In the Firmware field, click Application Package Updates.

5. To select a file, click Browse and go to the location where your file is located. If the EULA is embedded in the package, the EULA details of the package and the name of the vendors are displayed.

You can click the vendor names to read the license agreement of each vendor. Click Accept to upload the package. You can select the Do not show this again if you do not want to see the EULA details of the same vendor again. If you upload multiple packages, the EULA details of each package is displayed. You must accept the license agreement of the packages individually. The package is not uploaded if you click Decline.

If the EULA is not embedded in the package, go to step 6.

NOTE: You can upload and deploy multiple firmware packages from the remote repository, tenant cloud repository or

operator cloud repository.

6. Expand the category of the package and select it.

7. Verify and ensure that the switch option of the category is INSTALL.

8. Click Save & Publish. The application package is installed and the thin client restarts.

Upload and install ThinOS 9.x application packages using Admin Policy Tool

Steps

1. Go to the Admin Policy Tool on the ThinOS client. The Configuration Control | ThinOS window is displayed.

2. Click Advanced.

3. In the Firmware field, click Application Package Updates.

4. Browse and upload the packages from USB drive.

5. Expand the category of the package and select it.

6. Verify and ensure that the switch option of the category is INSTALL.

7. Click Save & Publish. The application packages are installed and the thin client restarts.

Firmware installation using Dell Wyse USB Imaging Tool Use the Dell Wyse USB Imaging Tool version 3.4.0 or later versions to install the latest version of ThinOS 9.x Merlin image on your thin client. For information about installation instructions, see the Dell Wyse USB Imaging Tool version 3.4.0 or later User's Guide.

Upgrading the ThinOS firmware 35

If you install the merlin image on the following thin clients, the installation may stop at 100% and does not display the completion status:

Wye 3040 Thin Client with hard disk size larger than 8 GB Wyse 5070 Thin Client with hard disk size larger than 16 GB Wyse 5470 Thin Client with hard disk size larger than 16 GB Wyse 5470 All-in-One Thin Client with hard disk size larger than 16 GB

However, you can force reboot the thin client as the image is already installed.

Upgrade BIOS

Prerequisites

Depending on your thin client model, download the relevant BIOS file from www.dell.com/support. If you are upgrading BIOS using Wyse Management Suite, register your thin client to Wyse Management Suite.

NOTE: On thin clients that run ThinOS versions earlier than ThinOS 9.1.6108, you must upgrade the OS image first,

and then upgrade the BIOS after the OS image is successfully upgraded. Do not upgrade the BIOS and the OS image

together. If you upgrade the BIOS and the OS image together, the BIOS upgrade is ignored, and you cannot upgrade the

BIOS to the ignored version anymore. You must upgrade the BIOS to another version.

Steps

1. Open the Admin Policy Tool on the thin client or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. On the Configuration Control | ThinOS window, click the Advanced tab.

3. Expand Firmware and click BIOS Firmware Updates.

4. Click Browse and select the BIOS file to upload.

5. From the Select the ThinOS BIOS to deploy drop-down list, select the BIOS file that you have uploaded.

6. Click Save & Publish.

The thin client restarts. BIOS is upgraded on your device.

NOTE: BIOS upgrade requires a display screen (integrated or external) without which the update fails. In this case, you

cannot install the BIOS package again. You must install another BIOS version.

Edit BIOS settings

Prerequisites

If you are using Wyse Management Suite, ensure that you have registered the thin client and synchronize the BIOS admin password. For more information about using the Sync BIOS Admin Password option, see the latest Dell Wyse Management Suite Administrator's Guide at www.dell.com/support.

NOTE: If you have not synced the BIOS password in the Wyse Management Suite server, you can enter the current

BIOS password in the Current BIOS Admin Password field to publish the BIOS settings. If you have synced the BIOS

password in the Wyse Management Suite server, this field is ignored. Wyse Management Suite server uses the synced

BIOS password to publish BIOS settings.

If you are using the Admin Policy Tool, ensure that you enter the current BIOS admin password in the Advanced > BIOS section.

Steps

1. Open the Admin Policy Tool on the thin client or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. In the Configuration Control | ThinOS window, click the Advanced tab.

3. Expand BIOS and select your preferred platform.

4. In the System Configuration section, modify the USB ports and audio settings.

5. In the Security section, modify the administrator-related configurations.

6. In the Secure Boot section, enable the secure boot option. If enabled, you cannot disable it using Admin Policy Tool or Wyse Management Suite. Secure Boot can be disabled only in the BIOS setup window.

36 Upgrading the ThinOS firmware

7. In the Power Management section, modify the power-saving options.

8. In the POST Behavior section, enable or disable the MAC Address Pass-Through feature. This option is applicable only to mobile thin clients.

9. Click Save & Publish

NOTE: If the thin client does not have a BIOS admin password, you can set the password using Admin Policy Tool or

Wyse Management Suite. In this scenario, the client reboots first to apply the BIOS admin password and other BIOS

settings take effect after the second reboot.

NOTE: Changing BIOS password using Select Group requires a reboot to take effect.

NOTE: If you enable Set Admin Password, set new BIOS password and then reboot, the new BIOS password is synced

to WMS server automatically. If you first enable Set Admin Password, set the new BIOS password, and then disable

Set Admin Password, the BIOS password is cleared to empty. On the thin client, the Current BIOS Admin Password

option is always blank, and Set Admin Password option is always disabled. These options do not have any impact on

the functionality.

Delete ThinOS application packages You can use the ThinOS local UI or the Wyse Management Suite to delete one or more ThinOS packages.

About this task

This section describes steps to delete ThinOS packages using the ThinOS local UI.

Steps

1. Log in to the ThinOS client.

2. From the system menu, go to System Tools > Packages. All the installed ThinOS packages are listed.

3. Select a package that you want to delete and click Delete.

NOTE: To delete all the packages, click Delete all.

4. Click OK to save your settings.

For information about how to delete or uninstall application packages using Wyse Management Suite, follow all steps in Upload and push ThinOS 9.x application packages using Groups and Configs on Wyse Management Suite, except Step 7, where you must switch to UNINSTALL

Downgrading the ThinOS firmware If you are downgrading to ThinOS 8.6, ThinOS 9.0, or ThinOS 9.1 versions that are older than 9.1.3129, you must use the Dell Wyse USB Imaging Tool to install the ThinOS 8.x or 9.x Merlin image that is posted to www.dell.com/support. Before you downgrade, ensure that you disable the secure boot option in the BIOS. If you want to downgrade to ThinOS 9.0, you must clear Trusted Platform Module (TPM) or Platform Trust Technology (PTT) in BIOS too. Else, ThinOS resets to factory settings after each reboot. If you are running the latest version of ThinOS, you can downgrade to ThinOS 9.1.3129 or later versions using Wyse Management Suite.

Upgrading the ThinOS firmware 37

Getting started with ThinOS This chapter helps you to quickly learn the basics and get started with your ThinOS -based thin client. From ThinOS 2205, ThinOS Activation devices license is added in Wyse Management Suite. Devices that are converted from other operating systems must have the ThinOS Activation devices license to enable the VDI function. The license is automatically added when registering to Wyse Management Suite. You cannot log in to any Broker agent from the client without ThinOS Activation devices license. You can add the license to enable PCoIP function on non-PCoIP devices that are converted from ThinOS 8.6 by enabling the Enable PCoIP Activation License option from Services > WDA Settings.

NOTE: Once ThinOS Activation devices licenses are consumed, you cannot restore them anymore. The licenses are

permanently applied on the ThinOS clients. ThinOS activation licenses are not cleared when you reset the ThinOS clients

to factory default. However, if you recover ThinOS clients using ISO images or merlin images, the licenses are cleared. You

must register the devices to the same Wyse Management Suite server that you applied licenses previously, to re-active

them. If you register the devices to the same Wyse Management Suite server, the clients can use the same licenses,

and they do not consume new licences. For Non-PCoIP ThinOS clients, you must also enable Enable PCoIP Activation

Licenseoption in ThinOS 9.x policy to re-active licenses.

End User License Agreement End User License Agreement (EULA) is added to ThinOS. EULAs must be read and accepted to continue using ThinOS. By default, Dell EULA and HID EULA are added to ThinOS. The third-party EULAs are displayed on the EULA screen depending on the ThinOS application packages that you install on the thin client.

The EULA screen is displayed during the following instances:

When you boot the thin client for the first time. When you reset a thin client that runs ThinOS 9.x to factory settings.

Configure ThinOS using First Boot Wizard A First Boot Wizard application runs the first time when you start a thin client with ThinOS. The thin client starts the First Boot Wizard application before you enter the ThinOS desktop. Use this application to perform tasks, such as, configuring system preferences, setting up the Internet connectivity, loading USB configurations, configuring management software, and configuring broker connections.

Prerequisites

If you are an existing thin client user, and you have upgraded to the ThinOS version 9.x, reset your thin client to factory default settings to enter the First Boot Wizard.

NOTE: If DHCP contains the Wyse Management Suite configurations, the ThinOS desktop is loaded without entering the

First Boot Wizard and you cannot view the End User License Agreement.

About this task

This section describes how to configure ThinOS using First Boot Wizard.

Steps

1. Connect your thin client to an Ethernet using a wired connection.

NOTE: If you want to use a wireless connection, you can connect to Wi-Fi on the How do You Connect? screen at a

later stage.

2. Turn on your thin client.

6

38 Getting started with ThinOS

The thin client checks for a wired network connection. If the network connection is successful, a welcome screen is displayed followed by the EULA screen. For more information about the EULA screen, see End User License Agreement.

NOTE: When you reset the device to factory default settings without a network connection, a message Device is

waiting for WMS information from network auto discovery is displayed. Press on the welcome

screen to go to next screen.

3. Click Dell EULA or HID EULA from the right pane to read the respective EULAs. If you have installed the ThinOS application packages, ensure that you read the respective EULAs of the third-party applications.

NOTE: The EULA screen may different depending on the client installed pkgs.

Figure 3. EULA screen

4. Select the Click here to accept all EULAs check box and click Accept.

5. On the Select Your Language screen, select a language from the Language drop-down list to start ThinOS in the regional language.

Getting started with ThinOS 39

Figure 4. Select Your Language

6. Click .

7. On the Select Your Keyboard screen, select a keyboard layout from the list.

Figure 5. Select Your Keyboard

8. Click .

9. On the Select Your Time Zone screen, select a time zone from the list to set the time zone for your thin client.

The time server with IP addresses or host names is also displayed.

40 Getting started with ThinOS

Figure 6. Select Your Time Zone

10. Click .

11. On the How do You Connect? screen, do either of the following: Local network (Ethernet)Click this option if you have connected the thin client to an Ethernet using a wired

connection. Wi-Fi NetworkClick this option if you want to select a wireless network. From the list, select a wireless network, and

click Connect.

NOTE: The option to define a wireless connection is not available on thin clients without a WLAN module.

My computer does not connect to the InternetClick this option if you do not want to establish a network connection using the First Boot Wizard screen. You can connect to either wired or wireless connection after you boot to the ThinOS desktop.

Figure 7. How do You Connect?

12. Click .

13. On the How would you like to import your ThinOS configurations? screen, do either of the following:

Getting started with ThinOS 41

From Wyse Management SuiteClick this option if you want to use Wyse Management Suite to manage your thin clients.

To register your thin client to Wyse Management Suite, enter the group registration key and the Wyse Management Suite server URL. Select the CA validation check box if you want to enable the CA validation feature. The CA validation is required when you import certificates into your Wyse Management Suite server. By default, the CA Validation check box is selected to improve the security when using the Wyse Management Suite cloud. While typing, you can click the eye icon next to Prefix and Group Key to display the masked values. Click the icon again to hide the values.

From USBClick this option if you want to import system settings from the USB drive. Do not import a configurationClick this option if you do not want to import any ThinOS configurations using the

First Boot Wizard screen.

Figure 8. How would you like to import your ThinOS configurations?

14. Click .

15. On the Connect to VDI broker screen, configure your preferred broker type from the following options: Citrix Virtual Apps and Desktops VMware Horizon Azure Virtual Desktop Microsoft Remote Desktop Services Amazon WorkSpaces Teradici Cloud Access

42 Getting started with ThinOS

Figure 9. Connect to VDI broker

16. Click . The Done screen is displayed.

Figure 10. Done

The device exists from the First Boot Wizard mode, and the ThinOS desktop is displayed.

Configure account privileges for ThinOS Account privilege is used to control the user permission to access Admin Policy Tool and System Menu options. You can change a user privilege to High, Customize, or None from the Admin Policy Tool or the Wyse Management Suite console. When you set the user privilege to Customize, you can manually select and enable or disable the options in the ThinOS system menu.

The Administrator Mode menu in the Admin Policy Tool is disabled by default. You can enable the administrator mode in the Admin Policy Tool or the Wyse Management Suite server, and configure an Administrator username and password.

Getting started with ThinOS 43

Configure account privileges using Admin Policy Tool

About this task

This section describes how to configure account privileges using Admin Policy Tool.

Steps

1. From the desktop menu, click System Setup > Admin Policy Tool. The Configuration Control || ThinOS window is displayed.

2. Click the Standard tab or the Advanced tab.

3. Expand Privacy & Security.

4. Click Account Privileges.

5. Click the Enable Admin Mode slider switch if you want to enable the Administrator mode. When enabled, you must specify the Admin username and password.

6. From the Privilege Level drop-down list, select a privilege levelNone, Customize, or High.

When you set the user privilege to Customize, you can manually select the options that you want to enable or disable in the ThinOS system menu. In ThinOS 9.1.4097 and ThinOS 9.1.4234, DHCP and Granular Control of Peripherals options are added. The DHCP option is only available after you enable Network Setup and Granular Control of Peripherals option is only available after you enable Peripherals. From Granular Control of Peripherals, you can select the tabs that you want to be displayed in the Peripherals window. If no tabs are selected, all tabs will be visible in the Peripherals window by default.

7. Click Save & Publish.

Configure account privileges using Wyse Management Suite

About this task

This section describes how to configure account privileges using Wyse Management Suite.

Steps

1. Go to the Groups & Configs tab and select your desired group.

2. Click Edit Policies.

3. Select ThinOS 9.x from the drop down list. The Configuration Control | ThinOS window is displayed.

4. Click the Standard tab or the Advanced tab .

5. Expand Privacy & Security.

6. Click Account Privileges.

7. Click the Enable Admin Mode slider switch if you want to enable the Administrator mode. When enabled, you must specify the Admin username and password.

8. From the Privilege Level drop-down list, select a privilege levelNone, Customize, or High.

When you set the user privilege to Customize, you can manually select the options that you want to enable or disable in the ThinOS system menu. In ThinOS 9.1.4097 and ThinOS 9.1.4234, DHCP and Granular Control of Peripherals options are added. The DHCP option is only available after you enable Network Setup and Granular Control of Peripherals option is only available after you enable Peripherals.

9. Click Save & Publish.

Enable PCoIP Activation License

About this task

You can enable PCoIP Activation License to enable the PCoIP function on Non-PCoIP Thin clients.

Steps

1. Open the ThinOS 9.x policy settings on Wyse Management Suite.

44 Getting started with ThinOS

2. Click the Advanced tab

3. Expand Services, and click WDA Settings.

4. Under WDA Settings, enable PCoIP Activation License.

By default this option is disabled.

5. Click Save & Publish.

Connect to a remote server

About this task

This section describes how to manually connect to a remote server.

Steps

1. From the desktop menu, click System Setup > Remote Connections. The Remote Connections dialog box is displayed.

2. Click the Broker Setup tab and configure the respective VDI broker.

3. Click OK and restart the thin client. After the thin client restarts, the Login dialog box is displayed.

4. Enter the username, password, and domain. After authentication is successful, your desktop is presented with your assigned connection that is defined by the broker server.

Connecting a display Depending on your thin client model, connections to displays can be made using VGA (analog) port, DisplayPort (digital), Mini DisplayPort, USB Type-C port, HDMI, and the proper Dell monitor cables/splitters/adapters.

For more information about ports and connectors, see the hardware documentation of the respective thin clients.

Connecting a printer To connect a local printer to your thin client, ensure that you obtain and use the correct adapter cables. Before use, you may need to install the driver for the printer by following the printer driver installation instructions. For information about connecting to a printer, see Configuring the printer setup.

Configure WMS settings on the client GUI

Steps

1. Open the Admin Policy Tool on your thin client or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. Click the Advanced tab.

3. Expand Services, and click WMS Settings.

4. Click Enable WMS.

The option is enabled by default.

5. Enable Show Advanced Configuration to display the advanced configuration options.

6. Fill the following fields:

Group prefixThis field is mandatory. Group tokenThis field is mandatory. ServerThis field is mandatory.

NOTE: If you disable, and then enable Show Advanced Configuration, all the values that you enter in the mandatory

fields are cleared.

Getting started with ThinOS 45

7. Enable or disable CA Validation.

8. Click Save & Publish.

Desktop overview ThinOS boots to the modern desktop screen. This screen is the default screen that is displayed after you log in to the thin clientwithout autostart of any connections or applications.

Figure 11. Modern desktop

The ThinOS modern desktop consists of the following screen elements:

Floatbar or taskbarContains the system tray area that displays the system icons. Broker login windowEnables you to log in to the Broker agent session using your login credentials.

Modern interactive desktop features The modern desktop mode (formerly zero desktop) has a Dell default background with the floating toolbar or floatbar on the screen.

NOTE: Citrix Workspace mode is not supported on the modern desktop.

Table 12. Modern desktop shortcuts

Action Press

Open a selection box for toggling between the desktop and currently-active connections

Ctrl+Alt+DownArrow

Lock the thin client Ctrl+Alt+LeftArrow

or

Ctrl+Alt+RightArrow

Capture the full desktop to the clipboard Print Screen

Capture the active window to the clipboard Alt+PrintScreen

46 Getting started with ThinOS

Enable modern desktop mode

Steps

1. Go to ThinOS 9.x policy settings on Wyse Management Suite or the Admin Policy Tool on ThinOS.

2. Click the Advanced tab and expand Personalization.

3. Click User Experience Settings.

4. From the System Mode drop-down list, select Modern.

5. From the Color scheme for Modern mode, select the color that you want.

6. From the Show Floatbar when mouse drop-down list, select the way that you want to show floatbar when it is hidden.

7. From the Floatbar Location on Screen drop-down list, select the location of floatbar on the screen.

8. In the Screen ID field, enter the Screen ID on which floatbar should be shown. You must enter a number 0 to 6. 0 specifies the main screen.

9. Click Save & Publish.

Modern toolbar or float bar

The modern toolbar or float bar appears at the left or right corner of the modern desktop. However, depending on administrator configurations, the float bar can be removed or hidden. The toolbar is displayed when a user moves the mouse pointer over the left or right edge of the desktop screen.

NOTE: If you set the Show Floatbar option to Fly Over on either Admin Policy Tool or Wyse Management Suite, you must

quickly move the mouse pointer on the desktop.

NOTE: If you set the Show Floatbar when mouse option to Delay and the Delay Floatbar Activation in Milliseconds

to 0, the modern float bar is disabled in a full screen session. If you press Ctrl+Alt+down key combination to switch to the

ThinOS desktop, the float bar is not displayed. If you change the mouse pointer size to a number greater than 3 in a Blast

session, you must use Ctrl+Alt to exit the session and view the floating bar on the ThinOS modern desktop.

Table 13. Toolbar icons

Icon Description

VDI menu Opens the list of available connections.

System Info Displays thin client system information.

Settings Opens the System Settings menu to configure thin client system settings and perform diagnostics.

Shutdown Click the Shutdown Terminal icon to use the Shutdown options available on the thin client.

Wireless network Displays the wireless connection mode. Clicking the wireless icon displays the SSID scan list. You can directly connect to your preferred WiFi. You can view the wireless IP address information in the Wi-Fi icon tooltip.

Wired network Displays the wired connected mode.

Volume or Sound Click this icon to increase or decrease the speaker volume or mute the speaker.

PNA menu Displays the Citrix connection options such as Refresh, Disconnect, Reconnect, Logoff, and Manage Security Question.

NOTE: The PNA menu button is displayed only after you log in to the Citrix Broker agent.

PCoIP Displays the active PCoIP sessions. This icon is applicable only for PCoIP-enabled clients. You can select a session from the menu, and enable or disable the following PCoIP options in real time: Relative Mouse Audio or Video synchronization

Battery indicator Hover over the battery indicator to view the remaining battery percentage. This option is applicable only to the Wyse 5470 Thin Client.

Getting started with ThinOS 47

Table 13. Toolbar icons (continued)

Icon Description

Smart Card Self-Service Click this icon to open the smart card self service window. You can use this window to view the smart card details, change PIN, and unlock PIN. This icon is displayed when you connect a smart card reader to the ThinOS client.

List of connections

On the modern toolbar, you can click the VDI menu icon to open your list of assigned connections and published applications. Sometimes, the list contains only default connections.

NOTE: The connection options may be available for use, depending on the user privileges.

Table 14. Connection options

Option Description

Name of the connection Opens the connection you want to use.

Gear icon Displays the sub menu.

Add Connection Allows you to configure or add new connections.

Global Connection Settings Use the Global Connection Settings dialog box to configure settings that affect all the connection in the list.

Search bar Enables you to search for a particular connection from the list.

Classic desktop features This section includes information about desktop guidelines, shortcut menu, desktop menu, and Connection Manager.

Desktop guidelines

The classic desktop has a Dell Wyse default background with a horizontal taskbar at the bottom of the screen.

Figure 12. Classic Desktop

48 Getting started with ThinOS

Use the following guidelines:

Icons representing available server connections and published applications are displayed on the desktop. If you pause the mouse pointer over an icon, the information about the connection is displayed. Right-click an icon to open the Properties dialog box that displays additional information about the connection. The number of icons that can be displayed on the desktop depends on the desktop resolution and administrator configuration.

A server connection and published application can be opened by double-clicking a desktop icon. You can also go to the desktop icon by using the tab key and press Enter to initiate the connection.

Right-clicking on the desktop provides a shortcut menu. Clicking the desktop menu button, or clicking anywhere on the desktop, opens the desktop menu.

Enable classic desktop mode

Steps

1. Go to ThinOS 9.x policy settings on Wyse Management Suite or the Admin Policy Tool on ThinOS.

2. Click the Advanced tab and expand Personalization.

3. Click User Experience Settings.

4. From the System Mode drop-down list, select Classic.

5. If you want to hide the taskbar when ThinOS is not logged in or if there is a maximized window, enable Hide Taskbar.

6. Click Save & Publish.

Using the taskbar

Use the taskbar to view the date, time, system information, wireless information, volume icon, PNAmenu button, and switch to the desktop screen.

Figure 13. Taskbar

1. System Information 2. Volume or Sound 3. Battery 4. Wireless network 5. Wired network 6. Smart card self-service 7. Citrix PNA menu 8. Date and time 9. Show desktop

The following table lists the taskbar elements:

Table 15. Taskbar - System tray elements

Element Description

Date and time Displays the date and time.

Battery Displays the battery percentage. This option is applicable for Wyse 5470 Thin Client.

Show desktop Click this icon to hide or restore VDI sessions.

Getting started with ThinOS 49

Table 15. Taskbar - System tray elements (continued)

Element Description

Volume or Sound Click this icon to increase or decrease the speaker volume or mute the speaker.

System Information Click this icon to view the system information such as general system details, copyright, event logs, Wyse Management Suite status, network connections, and so on.

NOTE: From ThinOS version 9.1.6108, Energy Star logo is added to the System Information window of factory shipped OptiPlex 3000 Thin Clients.

Wireless icon Displays the wireless connection mode. Clicking the wireless icon displays the SSID scan list. You can directly connect to your preferred WiFi. You can view the wireless IP address information in the Wi-Fi icon tooltip.

Wired icon Displays the wired connected mode.

Citrix PNA menu Click this icon to use the following options: Refresh Disconnect Reconnect Logoff Manage Security QuestionThis option is available when you enable SSPR at

the server end.

NOTE: The PNA menu button is displayed only after you log in to the Citrix broker.

Smart card self service Click this icon to open the smart card self service window. You can use this window to view the smart card details, change PIN, and unlock PIN. This icon is displayed when you connect a smart card reader to the ThinOS client.

PCoIP Click this icon to view the active PCoIP sessions. This icon is applicable only for PCoIP-enabled clients. You can select a session from the menu, and enable or disable the following PCoIP options in real-time: Relative Mouse Audio/Video synchronization

Taskbar icons are added for all ThinOS windows except the login window and the Admin Policy Tool window. You can use the taskbar icons to minimize and restore the windows.

Table 16. Taskbar - ThinOS local windows icons

Element Taskbar icon

Network Setup

Remote Connections

Central Configuration

VPN Manager

System Preferences

Display

Peripherals

Printer

50 Getting started with ThinOS

Table 16. Taskbar - ThinOS local windows icons (continued)

Element Taskbar icon

System Information

System Tools

Troubleshooting

Connection Manager

Using the shortcut menu

About this task

This section describes how to use the shortcut menu on your thin client.

Steps

1. Right-click on your desktop. The shortcut menu is displayed.

2. On the shortcut menu, you can view and use the following options:

a. Administrator ModeLets you enter the administrator mode. This option is disabled by default. You must enable the option from Wyse Management Suite server or Admin Policy Tool.

b. Hide all windowsBrings the full desktop to the foreground. c. Copy to clipboardCopies an image of the full screen, current window, or event log to the clipboard. The clipboard

contents can be pasted to an Independent Computing Architecture (ICA) session. You can copy the full screen or current window to clipboard, and can export the screenshots using the Export Screenshot option in the Troubleshooting dialog box.

d. Purge clipboardDiscards the contents of the clipboard to free up memory. If there are no contents in the clipboard, the Purge clipboard option is disabled.

e. Lock TerminalPuts the thin client in a locked state when the user has logged in to the system with a password. The thin client can only be unlocked using the same password.

f. Performance MonitorOpens the performance monitor.

Using the desktop menu

About this task

This section describes how to use the desktop menu on your thin client.

Steps

1. Click or click anywhere on your desktop. The desktop menu is displayed.

2. On the desktop menu, use the following options to configure the thin client:

System SetupProvides access to the following local system setup dialog boxes: Network SetupAllows selection of DHCP or manual entry of network settings, and server locations. Remote ConnectionsAllows you to configure the Broker agent connection. Central ConfigurationAllows you to configure the Wyse Management Suite server settings. VPN ManagerAllows you to configure the VPN connection. System PreferencesAllows you to configure general settings such as screensaver, locale, and time and date. DisplayAllows you to configure the monitor resolution and rotation. PeripheralsAllows you to select the peripherals settings such as audio, keyboard, mouse, serial, camera, and

Bluetooth settings.

Getting started with ThinOS 51

Printer SetupAllows you to configure network printers and local printers that are connected to the thin client. Admin Policy ToolAllows you to configure all the ThinOS settings similar to configuring settings using Wyse

Management Suite. System InformationProvides the device information. System ToolsProvides information about devices, certificates, and packages. TroubleshootingDisplays the performance monitor graphs, trace and event log settings, and other options that are

useful for troubleshooting your thin client. ShutdownAllows you to shut down the system, or restart the operating system.

Configure the Connection Manager

The Connection Manager has a list of connection entries and command buttons available for use with the connections.

About this task

This section describes how to configure the Connection Manager settings.

Steps

1. Go to System Setup > Remote Connections, and configure the Broker agent setup.

2. Log in to the Broker agent connection.

3. On the taskbar, click . The Connection Manager dialog box is displayed.

NOTE: Nonprivileged users cannot view the Connection Manager.

4. In the Connection Manager dialog box, and use the following guidelines:

Select a connection from the list, and click Connect to establish the VDI connection. Click Properties to open the Connection Settings dialog box for the selected connection.

All users can view and edit definitions for the selected connection. Edits are not permanently retained when the user signs-off.

Click Sign-off to log off from the thin client. If you want to reset a selected virtual connection, select a connection from the list, and click Reset VM. Click the Global Connection Settings tab to open and configure settings that affect all the connections available in the

list. Click Add to create an RDP or a PCoIP connection. Click Delete to remove the created connection from the list.

Configuring thin client settings and connection broker settings You can either use the ThinOS local UI or the Wyse Management Suite to do the following:

Set up your thin client hardware, look and feel, and system settings For configuring these settings using ThinOS local UI, see Configuring connectivity and Configure the thin client local

settings. For configuring these settings using Wyse Management Suite, see Edit the ThinOS 9.x policy settings.

Configure the connection broker settings For configuring these settings using ThinOS local UI, see Configuring the connection brokers. For configuring these settings using Wyse Management Suite, see Edit the ThinOS 9.x policy settings.

52 Getting started with ThinOS

Configure ThinOS using Admin Policy Tool ThinOS 9.x does not support FTP, HTTP, HTTPS file server, and INI parameter settings. You can configure these settings using a local management tool called Admin Policy Tool.

NOTE: After you reset the thin client to factory default settings, the device starts the First Boot Wizard application by

default. You can use the Admin Policy Tool to change the default settings for First Boot Wizard.

Configure the Admin Policy Tool

Steps

1. From the desktop menu, click System Setup > Admin Policy Tool. The Configuration Control | ThinOS window is displayed.

2. Click the Standard tab or the Advanced tab.

The Standard tab lists all the common settings. The Advanced tab lists all the advanced settings.

3. Expand the options that you want to configure.

4. In the respective fields, click the option that you want to configure.

5. Click Save & Publish.

Feature list of Admin Policy Tool

The following table displays the list of features that are supported by the Admin Policy Tool in ThinOS.

Table 17. Admin Policy Tool

Feature Subfeature Restart required

Region & Language Settings

Region & Language No

Privacy & Security Account Privileges No

Privacy & Security Certificates No

Privacy & Security Security Policy Yes, you must restart the client for all changes to take effect.

Privacy & Security SCEP No

Privacy & Security Device Security Yes, you must restart the client for all changes to take effect.

Broker Settings Global Broker Settings

No

Broker Settings Citrix Virtual Apps and Desktops Settings

No

Broker Settings VMware Horizon Settings

No

Broker Settings Azure Virtual Desktop Settings

No

Broker Settings Microsoft Remote Desktop Settings

No

Broker Settings Amazon WorkSpaces Settings

No

Broker Settings Teradici Cloud Access Settings

No

Getting started with ThinOS 53

Table 17. Admin Policy Tool (continued)

Feature Subfeature Restart required

Session Settings Global Session Settings

No

Session Settings Citrix Session Settings

No

Session Settings Blast Session Settings

No

Session Settings PCoIP Session Settings

No

Session Settings RDP and AVD Session Settings

No

VDI Configuration Editor Citrix Configuration Editor

Yes, you must restart the client for all changes to take effect.

VDI Configuration Editor Horizon Blast Configuration Editor

Yes, you must restart the client for all changes to take effect.

VDI Configuration Editor Zoom Plugin Configuration Editor

Yes, you must restart the client for all changes to take effect.

Login Experience 3rd Party Authentication

No

Login Experience Smart card Settings Yes, you must restart the client for all changes to take effect.

Login Experience Login Settings No

Login Experience Session Settings No

Personalization Shortcut Keys Yes, you must restart the client for all changes to take effect.

Personalization Device Info No

Personalization Desktop Yes, you must restart the client for all changes to take effect.

Personalization Screen Saver No

Personalization User Experience Settings

No

Peripheral Management RFIdeas Reader No

Peripheral Management Printers No

Peripheral Management Audio Yes, you must restart the client for all changes to take effect.

Peripheral Management Touch No

Peripheral Management Serial Port Yes, you must restart the client for all changes to take effect.

Peripheral Management USB Redirection No

Peripheral Management Monitor No

Peripheral Management Mouse No

Peripheral Management Camera No

Peripheral Management Keyboard No

Peripheral Management Device Headset Settings

Yes, you must restart the client for all changes to take effect.

Peripheral Management CCID Yes, you must restart the client for all changes to take effect.

Firmware OS Firmware Updates

No

54 Getting started with ThinOS

Table 17. Admin Policy Tool (continued)

Feature Subfeature Restart required

Firmware Application Package Updates

No

Firmware BIOS Firmware Updates

No

System Settings Power and Sleep Settings

No

System Settings Scheduled Reboot Settings

No

System Settings Scheduled Shutdown Settings

No

System Settings Device Settings No

Network Configuration Ethernet Settings No

Network Configuration DHCP Settings No

Network Configuration DNS Settings No

Network Configuration VPN Settings No

Network Configuration Bluetooth Settings Yes, you must restart the client for all changes to take effect.

Network Configuration Proxy Settings No

Network Configuration Wireless Captive Portal requires a reboot to take effect.

Network Configuration Common Settings No

Network Configuration SNMPV3 Settings No

Services VNC Service No

Services WMS Settings No

Services Troubleshooting Settings

No

BIOS Dell Wyse 3040 Yes, you must restart the client for all changes to take effect.

BIOS Dell Wyse 5070 Yes, you must restart the client for all changes to take effect.

BIOS Dell Wyse 5470 Yes, you must restart the client for all changes to take effect.

BIOS Dell Wyse 5470 AIO Yes, you must restart the client for all changes to take effect.

BIOS Dell OptiPlex 3000 Yes, you must restart the client for all changes to take effect.

BIOS Dell Latitude 3420 Yes, you must restart the client for all changes to take effect.

BIOS Dell OptiPlex 5400 AIO

Yes, you must restart the client for all changes to take effect.

Important information

If you are using the Device Security Allow List Policy setting, you must first specify Hub, HID in the Class field by adding a row in Advanced > Device Security section in Admin Policy Tool. If you do not add Hub, HID to the Allow list, all USB devices are inaccessible when connected to the thin client. You must restart the thin client for changes to take effect.

It is not recommended to set Vendor and Product ID and Class simultaneously in one row. However, if you configure both options simultaneously, the device first checks the Vendor and Product ID followed by the Class list.

When you configure the Bluetooth, VNCD server, Bluetooth, VNC Server, NetID License, Serial Port, and Device Security settings using the Admin Policy Tool, ensure that you restart the thin client for the settings to take effect.

Getting started with ThinOS 55

Locking the thin client ThinOS enables you to lock your thin client so that credentials are required to unlock and use the thin client again. This option is enabled by default. To disable the option, go to Advanced > Login Experience > Login Settings from the Admin Polity Tool or the Wyse Management Suite Policy Settings, and disable Lock Terminal.

NOTE: A lock terminal command from Wyse Management Suite takes priority over the settings and locks the thin client

even if the setting is disabled.

Shut down and restart

About this task

This section describes how to use the Shutdown dialog box to either shut down the system or restart the system.

Steps

1. From the desktop menu, click Shutdown. The shutdown dialog box is displayed.

2. Click any of the following options: Shutdown the systemEnables you to shut down the system. Restart the systemEnables you to restart the operating system.

3. Click OK to save settings.

Scheduled Shutdown Using this option, you can specify a time and a day to shut down the device automatically.

Steps

1. Open the Admin Policy Tool on your thin client or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. Click the Advanced tab.

3. Expand System Settings, and click Scheduled Shutdown Settings.

4. Click the Enable Auto Shutdown toggle switch to enable the feature.

5. You can use the following settings:

Shutdown after Idle TimeThe client shuts down only if it is left idle for the time that you specify here. Scheduled Shutdown TimeSet a time window for the client to shut down. Specify the time in 24-hour format. Shutdown DaySpecify the days when you want the shutdown to happen. Shutdown Week No.Use this option to select a minimum time period to trigger a shutdown from the last shutdown.

6. Click Save & Publish.

NOTE: If you change the time zone on the local client, Scheduled Shutdown Settings take effect only after a reboot.

Scheduled Reboot Using this option, you can specify a time and a day to reboot the device automatically.

Steps

1. Open the Admin Policy Tool on your thin client or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. Click the Advanced tab.

3. Expand System Settings, and click Scheduled Reboot Settings.

4. Click the Enable Auto Reboot toggle switch to enable the feature.

5. You can use the following settings:

56 Getting started with ThinOS

Reboot after Idle TimeThe client reboots only if it is left idle for the time that you specify here. Scheduled Reboot TimeSet a time window for the client to reboot. Specify the time in 24-hour format. Reboot DaySpecify the days when you want the reboots to happen. Reboot Week No.Use this option to select a minimum time period to trigger a reboot from the last reboot.

6. Click Save & Publish.

NOTE: If you change the time zone on the local client, Scheduled Reboot Settings take effect only after a reboot.

Enable or disable shutdown This option disables the Shutdown option in the ThinOS Shutdown window, and also disables the physical shutdown button on the thin client.

Steps

1. Open the Admin Policy Tool on your thin client or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. Click the Advanced tab.

3. Expand Login Experience, and click Login Settings.

4. Click the Disable Shutdown toggle switch under Login Experience to enable or disable the shutdown.

5. Click Save & Publish.

Battery information This section is only applicable to mobile thin clients. The battery indicator is displayed on the system tray.

The following table contains the battery indicators:

Table 18. Battery indicators

Battery status Icon

While charging with the AC adapter

Battery 90% - 100% without connecting the AC adapter

Battery 50% - 89% without connecting the AC adapter

Battery 25% - 49% without connecting the AC adapter

Battery 9% - 24% without connecting the AC adapter

Battery 0% - 8% without connecting the AC adapter

NOTE: The battery icons are updated from ThinOS 9.1.6108.

When the battery is lower than 12%, a notification is displayed at the right-bottom with the remaining percentage. Plugging in the AC adapter to charge the device increases brightness by 10% and disconnecting the AC adapter decreases

brightness by 10%. By default, the critical battery level is 5%. When the battery reaches the critical level, ThinOS is turned off automatically.

You must plug in the AC power to power on the thin client.

Getting started with ThinOS 57

Login dialog box features The Login dialog box enables you to do the following tasks:

Log in broker to the configured server connection. Change or reset your own password, and unlock your account.

View the system information Use the System Information dialog box to view the system information. You can either click System Information from the desktop menu or the System Information icon on the taskbar.

The System Information dialog box includes the following elements:

General tabDisplays the following information: System version Terminal name Serial number System Up Time Memory size Memory Usage CPU Speed SSD sizethe storage size of the SSD/eMMC on which ThinOS is installed. CPU Utilization Monitor Main Resolution Parallel ports Serial ports Batterymobile thin clients only Remaining timemobile thin clients only

Copyright tabDisplays the software copyright and patent notices.

Click the Acknowledgments button to view the information that is related to third-party software.

Event Log tabDisplays the thin client start-up steps beginning from system version to checking firmware or error messages that are helpful for debugging issues. The number of displays and USB devices that are connected to the thin client, and the Bluetooth initialization are also displayed.

ENET tabDisplays information about wired network connections. WLAN tabDisplays information about wireless network connections. About tabDisplays the following information:

Platform name Operating system Build name Build version BIOS name BIOS version Citrix Workspace App version Teradici PCoIP VMware Horizon AVD WMS status MQTT server

NOTE:

Kernel modeThe components are implemented in Kernel according to the specification. The version is displayed

as [max].[min], which is the base version of protocol or server or client of the component.

User modeThe components are from the source, or binaries from third-party software that are compiled or

integrated into the ThinOS operating system. The version is displayed as [max].[min].[svn_revision]. The [max] and

[min] is the base version of the third component, and the [svn_revision] is the source control revision of ThinOS.

58 Getting started with ThinOS

Using the ThinOS specified version, you can identify the changes between different revisions. For example, the Citrix

Workspace App version is 19.12.0.19. The components are matched to the installed packages. If the packages are

removed, the field remains empty in the About tab.

Sleep mode The sleep mode enables the power-saving state and quickly resumes full power operations without loss of data.

The sleep mode feature is supported on the following platforms:

Wyse 5070 Thin Client Wyse 5470 Thin Client Wyse 5470 All-in-One Thin Client OptiPlex 3000 Thin Client

The USB interface is closed in sleep mode. All USB devices such as USB drives, Bluetooth, audio devices, video devices, and camera are reinitialized after resuming from sleep mode.

The wired network, wireless network, and VPN are disconnected in sleep mode. However, the network configurations are saved.

All the ThinOS configurationsVDI configuration, network configuration, and so onare saved automatically in sleep mode. If you are signed on to broker agent, all the windows are closed automatically and signed off when entering sleep mode. If you are not signed on to broker agent, the windows are not closed when entering sleep mode.

Enable sleep manually

To enable the Sleep option manually, use either of the following options:

ThinOS lock windowTo enter sleep mode using the ThinOS lock window, do the following: 1. Lock your thin client. 2. In the ThinOS lock window, click Sleep. 3. Click OK.

Shutdown dialog boxTo enter sleep mode using the Shutdown dialog box, do the following: 1. Open the Shutdown window. 2. Click Sleep, and then click OK.

You can wake the thin client from sleep mode by pressing the power button, any key on the keyboard, or by clicking the mouse button. To use the USB keyboard or mouse to wake your thin client, you must enable wake on USB in BIOS.

Wyse 5470 Thin ClientThe AC power must be connected to wake the Wyse 5470 Thin Client using the USB keyboard or mouse. You can also wake the Wyse 5470 Thin Client by opening the lid.

Import certificates to ThinOS from Admin Policy Tool or Wyse Management Suite

Steps

1. Open the Admin Policy Tool on your thin client or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. On the Configuration Control | ThinOS window, click the Advanced tab.

3. Expand Privacy & Security, and click Certificates.

4. Click the Auto Install Certificates slider switch to enable autoinstall of certificates on ThinOS.

5. Browse and select the certificate that you want to upload.

NOTE: Admin Policy Tool supports the .cer, .crt, .pfx, .der, and .pem certificate file types. Wyse Management

Suite supports .cer, .crt,.pfx, .der, and .pem certificate file types.

6. From the Select Certificates to Upload drop-down list, select the certificate that you have uploaded.

7. Click Save & Publish. The certificate is installed on your thin client.

Getting started with ThinOS 59

ThinOS system variables ThinOS uses system variables or part of a system variable when defining command values. System variables are often used to define unique values for fields such as terminal name or default user. For example, if the client has an IP address 123.123.123.022, ACC&Right($FIP,3) results in a value of ACC022. Using system variables makes it easier to manage groups of devices that require a unique terminal name or default user.

NOTE: System variables are case sensitive. For example, you cannot use $ip instead of $IP.

The following are the ThinOS system variables:

Table 19. ThinOS system variables

Variable Description

$IP IP address

$IPOCT4 The fourth octet of IP Address. For example, if IP is 10.151.120.15, the value is 15.

$UN Sign-on username

$DN Sign-on domain name

$DHCP (extra_dhcp_option) Extra DHCP options for Windows CE unit, including 169, 140, 141, 166, 167.

For example, set a string test169 for option tag 169 in DHCP server, and set TerminalName=$DHCP(169) in the Wyse Management Suite server. After the thin client checks in to the Wyse Management Suite server, check the terminal name in GUI, and the terminal name is changed to test169. 166 and 167 is default for CCM MQTT Server and CCM CA Validation in ThinOS. So you need to remap the options from GUI if you want to use $DHCP(166)/ $DHCP(167).

$MAC MAC address

$CMAC MAC address with colon

$UMAC MAC address with uppercase letters is used.

$TN Terminal name

$SUBNET Subnet notation, the format is {network_address}_{network_mask_bits} For example, if the ip address is 10.151.120.15, network mask is 255.255.255.0, 10.151.120.0_24 is used.

$FIP IP Address with xxx.xxx.xxx.xxx, for example,123.123.123.022

$SN Serial number

$VN Version number

Right($xx, i) or and Left($xx, i) Specifies that the variable is to be read from left or right. The $xx is any of above parameters and the parameter i specifies the digits for the offset of right or left.

Manual override

The manual override feature enables users to prevent the Wyse Management Suite configured policies from applying to the device after a particular action is performed on the local ThinOS device. When the manual override feature is enabled, and the user performs the required action on the ThinOS local device, the configured policies from Wyse Management Suite for these settings are not applied to the ThinOS device.

Table 20. Manual override support matrix

Settings Action to be performed on the ThinOS local device

Default value

DHCP Settings Click the OK button in the Network Setup window

Disabled

60 Getting started with ThinOS

Table 20. Manual override support matrix (continued)

Settings Action to be performed on the ThinOS local device

Default value

DNS Settings Click the OK button in the Network Setup window

Disabled

Proxy Settings Click the OK button in the Network Setup window

Disabled

Ethernet Settings Click the OK button in the Network Setup window

Disabled

Wireless Settings Click the OK button in the Network Setup window

Disabled

VPN Settings Add a new VPN, edit a VPN, or remove a VPN Disabled

Printers Click the OK button in the Printer Setup window Disabled

Audio Change the audio configuration Disabled

Mouse Click the OK button in the Peripherals window Enabled

Keyboard Change the configuration under the Keyboard tab in the Peripherals window, and click the OK button

Enabled

Touch pad Click the OK button in the Peripherals window Enabled

Monitor Click the Test button and then click OK in the Display Setup window

Disabled

Region & Language - Region Settings

Change the region configuration and click the OK button

Disabled

Region & Language - Language Settings

Change the language configuration and click the OK button

Disabled

Closing the Lid (Mobile Thin Clients only)

Change When I close the lid configuration and click OK

Disabled

Login Settings Change the default credentials in the General Options tab in Remote Connections

Disabled

Getting started with ThinOS 61

Configuring the global connection settings About this task

This section describes how to use the Global Connection Settings dialog box to configure the connection settings for ICA, Horizon, RDP and PCoIP.

Steps

1. Configure the Broker agent connection on ThinOS. See, Configure the Broker Setup.

2. On the desktop taskbar, click

(Connection Manager) and then click Global Connection Settings. The Global Connection Settings dialog box is displayed.

3. Click the Session tab and configure the following options: Settings common to all sessionSelect the check boxes to enable options that are applied to all sessions. The

available options are: Launch only onceSelect the check box if you want the session to be launched only once at the same time. Re-connect after disconnectSelect the check box if you want the session to launch again after the connection is

disconnected. Mount disks as read-onlySelect the check box if you want to disable write access for storage disks. Enable Imprivata VCSelect the check box if you want the Imprivata VC to be redirected to the remote session. If

this option is not selected, RFIDEAS or Fingerprint reader can be redirected into the remote session. Auto connect to local devicesSelect the check boxes to automatically connect to local devices, such as printers,

serials, smart cards, audio devices, and disks at system startup.

If you want to use the Disks option to connect to sessions automatically, ensure that:

More than one disk can be used simultaneously. However, the maximum number of USB drives including different subareas is 12.

You save all data and sign off from the session before removing the USB drive. USB device redirectionSelect this check box to allow USB devices to be redirected to the remote session. The

available options are: Exclude disk devicesSelect the check box if you do not want disk devices to be redirected to the remote session. Exclude printer devicesSelect the check box if you do not want printer devices to be redirected to the remote

session. Exclude audio devicesSelect the check box if you do not want audio devices to be redirected to the remote

session. Exclude video devicesSelect the check box if you do not want video devices to be redirected to the remote

session.

4. Click the ICA tab, and do the following:

a. Select the check boxes to enable the options that are applied to all sessions. The available options are:

Seamless window modeSelect this check box if you want to launch applications and desktops seamlessly. Desktop with fullscreen modeSelect this check box if you want to launch the desktop session in fullscreen. Enable HDX/MMRSelect the check box if you want to enable the Multimedia Redirection feature. When this

option is enabled, the audio and video is rendered on the user device instead of the server. Enable session reliabilitySelect the check box if you want the session to remain active when the network

connection is unstable. Enable UDP audioSelect the check box if you want the Citrix connections to use audio over User Datagram

Protocol (UDP).

b. From the Audio Quality drop-down list, select an audio quality optimized for your connection.

5. Click the Horizon tab, and select the check boxes to enable the options that are applied to all sessions. The available options are:

7

62 Configuring the global connection settings

Allow H.264 decodingSelect the check box if you want to enable the H.264 decoding in Horizon Client. Enabling this option improves the performance of high-end applications. H.264 is disabled by default.

Allow High Color AccuracySelect the check box if you want to allow Horizon Client to use a superior color fidelity when H.264 decoding is enabled.

Allow High Efficiency Video DecodingSelect ths check box to enable High Efficiency Video Coding (HEVC). For more information, see High Efficiency Video Coding

NOTE: HEVC in Blast Extreme requires both the ESXi hosts that supports the virtual desktops, and RDSH servers

to have NVIDIA Tesla or newer graphics cards to offload its encoding. HEVC does not work with only ESXi CPU

encoding. If there are no supported graphics cards present, the H.264 or JPEG/PNG encoding is used.

6. Click the RDP tab, and do the following:

a. Select the check boxes to enable the options that are applied to all sessions. The available options are:

Force SpanSelect the check box if you want to span the session horizontally across two displays. This option enables you to use two displays as one large display.

Record from LocalSelect the check box if you want to enable recording from a local microphone.

NOTE: Enable NLA option is always enabled and you cannot disable it.

b. In the Desktop Scale Factor box, enter the DPI value in percentage. This option enables you to define the desktop DPI remotely. The Desktop Scale Factor is only applicable for the RDP connection. Setting this option does not impact the display scale of the thin client locally. The DPI range is 100500. If you enter a nonnumeric character, the value is automatically set to 100. If you enter a value less than 100, the value is automatically set to 100. If you enter a value higher than 500, the value is automatically set to 500

7. Click OK to save your settings.

Configuring the global connection settings 63

Configuring connectivity This chapter helps you understand various configuration settings for a secure connection. To configure the settings on the classic desktop, click System Setup from the desktop menu, and use the configuration tabs.

Configuring the network settings Use the network options to configure the network connection based on your requirement.

From ThinOS 9.1.4097and ThinOS 9.1.4234, you can enable or disable IPv6 from Advanced > Network Configuration > Common Settings > Enable IPv6 in Wyse Management Suite policy settings or the Admin Policy Tool. IPv6 is enabled by default for both wired and wireless networks.

Configure the general settings

About this task

This section describes how to configure the general network settings on your thin client.

Steps

1. From the desktop menu, click System Setup > Network Setup. The Network setup dialog box is displayed.

2. Click the General tab, and do the following:

Figure 14. General tab

NOTE: If network interfaces are in the same subnet, connection to the same subnet is prioritized last by the interface to

fetch the IP address. Connections to the other subnets are prioritized in the order ENET0, ENET1, and WLAN.

a. To set a default gateway, select the type of network interface from the Select Network Interface as the Default Gateway drop-down list.

8

64 Configuring connectivity

ThinOS supports the dual IPv6 network interface. The following network combinations are supported: Wired connection 1 + Wireless connection 1 Wired connection 1 + Wired connection 2

NOTE: The limitation of the dual network is that the device cannot automatically determine which connection to use

among the two.

b. Use Static Name ServersBy default, this check box is not selected, and the thin client fetches the server IP address from DHCP. To manually assign the static IP addresses, select the Use Static Name Servers check box and do the following:

NOTE: If name servers are changed, the details are displayed in event logs. In dynamic mode, the DNS can be

merged from Ethernet and wireless, or from Ethernet 0 and Ethernet 1.

NOTE: From ThinOS 9.1.3112 onwards, you can upload the host file using the Wyse Management Suite policy

settings or the Admin Policy Tool. To upload the file, go to Advanced > System Settings > Device Settings from

the Wyse Management Suite policy settings or the Admin Policy Tool, and click Browse... next to Select Host File.

ANSI or UTF-8 encoding is supported, and the maximum supported file size is 10 KB.

i. Enter the URL address of the DNS domain in the DNS Domain field.

NOTE: From ThinOS 9.1.5067 onwards, you can use multiple DNS domain suffixes. Use ; to separate values.

ii. Enter the IP address of the DNS server in the DNS Server field.

However, the use of DNS is optional. DNS enables you to specify remote systems by their host names rather than IP addresses. If a specific IP address (instead of a name) is entered for a connection, it is used to make the connection. Ensure that you use the DNS domain and the network address of an available DNS server. The function of the DNS domain entry is to provide a default suffix that is used to resolve the name. The values for these two fields may be supplied by a DHCP server. If the DHCP server supplies these values, they replace any locally configured values. If the DHCP server does not supply these values, the locally configured values are used.

On ThinOS, error tips are displayed when you set an invalid DNS server. A window with the error message is displayed when you click save the invalid DNS server.

NOTE: You can enter the server addresses, each separated by a semicolon. The character limit is 256. The first

address is for the primary DNS server, and the rest are secondary DNS servers or backup DNS servers.

c. Enter the IP address of the WINS server in the WINS Server field.

NOTE: Only one WINS server is supported.

However, the use of WINS is optional. You must specify the network address of an available WINS name server. WINS enables you to specify remote systems by their host names rather than IP addresses. If a specific IP address (instead of a name) is entered for a connection, it is used to make the connection. These entries can be supplied through DHCP, if DHCP is used. DNS and WINS provide essentially the same name resolution. If both DNS and WINS are available, the thin client attempts to resolve the name using DNS first and then WINS. You can enter a single WINS Server address.

d. Enter the digit multiplier of 30 s in the TCP Timeout box to set the time-out value of a TCP connection. The value must be either 1 or 2 which means the connection time-out value is from 1 x 30 = 30 s to 2 x 30 = 60 s. Setting the time-out period retransmits the sent data and tries to connect to the server again until the connection is established.

3. Click OK to save your settings.

Configure the DHCP options settings

About this task

This section describes how to configure the DHCP options settings on your thin client.

Steps

1. From the desktop menu, click System Setup > Network setup. The Network setup dialog box is displayed.

2. Click the Options tab, and do the following:

Configuring connectivity 65

Figure 15. Options tab

a. Interpret DHCP Option IDsEnter the supported DHCP options. Each value can only be used one time after you reset your device to factory default settings.

Table 21. DHCP option tags

Option Description Additional information

165 Wyse Management Suite server Optional string. Specifies the IP address of the Wyse Management Suite server.

166 Wyse Management Suite MQTT server

Optional string. Specifies the IP address of the MQTT server.

167 Wyse Management Suite CA Validation

Optional string. Specifies the CA validation.

181 PNAgent/ PNLite server list Optional string. The thin client uses the server to authenticate the credentials of the user. The device obtains a list of ICA published applications valid for the validated credentials. The user supplies those credentials when logging in to the thin client.

182 NT domain list for PNAgent/ PNLite

Optional string. The thin client creates a drop-down list of domains from the information that is supplied in the option tag. The list is available during thin client login in the order that is specified in the DHCP option. For example, the first domain that is specified becomes the default option. The selected domain is the one which must authenticate the user ID and password. Only the selected domain is used in the authentication process. If the domain list is incomplete and if the user credentials must be verified against a domain not in the list, you can type a different domain name during login. This is based on the assumption that the server in option 181 can authenticate against a domain that is not available in the list.

199 Wyse Management Suite group registration key

Optional string. Specifies a Wyse Management Suite group registration key for the Wyse Management Suite agent. When Wyse Management Suite is disabled, and the group key of Wyse Management Suite is null, this option takes effect. Wyse Management Suite uses the optional string as the group registration key. If the Wyse Management Suite

66 Configuring connectivity

Table 21. DHCP option tags (continued)

Option Description Additional information

server or the MQTT server is null, the Wyse Management Suite agent sets the values to the default server values.

b. Interpret DHCP Vendor-Specific InfoSelect this check box for automatic interpretation of the vendor information. c. DHCP Vendor IDDisplays the DHCP vendor ID when the Dynamically allocated over DHCP/BOOTP option is

selected. d. DHCP UserClass IDDisplays the DHCP user class ID when the Dynamically allocated over DHCP/BOOTP option is

selected.

3. Click OK to save your settings.

NOTE: The User Class option for DHCP standard is RFC 2132.

Configure the ENET settings

About this task

This section describes how to configure the Ethernet settings on your thin client.

Steps

1. From the desktop menu, click System Setup > Network setup. The Network setup dialog box is displayed.

2. Click the ENET tab, and do the following:

Figure 16. ENET tab

a. From the Ethernet Select drop-down list, select a wired network connection.

Configuring connectivity 67

NOTE: For Wyse 5070 Thin Client without SFP or RJ45 module, the ENET0 option is selected by default. For

Wyse 5070 thin client with SFP or RJ45 module and Wyse 5470 Thin Client that is connected to Dell WD19 docking

station, select either ENET0 or ENET1 based on your network preference.

b. From the Ethernet Speed drop-down list, select a value for the Ethernet speed. The default value is Auto-Detect. If your network equipment does not support the automatic negotiation, select any of the following values:

10 MB Half-Duplex 10 MB Full-Duplex 100 MB Half-Duplex 100 MB Full-Duplex 1000 MB Full-Duplex

NOTE: The 10 MB Full-Duplex value can be selected locally. However, this mode can be negotiated through

Auto-Detect.

c. Click the IPv4 button, and then click Properties to configure the following options:

Dynamically allocated over DHCP/BOOTPSelect this option to enable your thin client to automatically receive information from the DHCP server. The network administrator must configure the DHCP server by using DHCP options to provide information. Any value that is entered locally in the Options tab is replaced by the DHCP value. If the DHCP server fails to provide replacement values, the locally entered value is used.

Statically specified IP AddressSelect this option to manually enter the IP address, subnet mask, and default gateway. IP AddressEnter a valid network address in the server environment. The network administrator must provide

this information. Subnet MaskEnter the value of the subnet mask. A subnet mask is used to gain access to machines on other

subnets. The subnet mask is used to differentiate the location of other IP addresses with two choicessame subnet or other subnet. If the location is a different subnet, messages that are sent to that address must be sent through the default gateway. This does not depend on the value that is specified through local configuration or through DHCP. The network administrator must provide this value.

Default GatewayUse of gateways is optional. Gateways are used to interconnect multiple networksrouting or delivering IP packets between them. The default gateway is used for accessing the Internet or an intranet with multiple subnets. If no gateway is specified, the thin client can only address other systems on the same subnet. Enter the address of the router that connects the thin client to the Internet. The address must exist on the same subnet as the thin client as defined by the IP address and the subnet mask. If DHCP is used, the address can be supplied through DHCP.

d. Click the IPv6 button, and on the Properties tab, configure the following options:

NOTE: The limitation of the dual IPv6 network is that the device cannot automatically determine which connection

to use among the two.

Select the Dynamically allocated over DHCP/BOOTP option to enable your thin client to automatically receive information from the DHCP server. The network administrator must configure the DHCP server (using DHCP options) to provide information. Any value that is entered locally in the Options tab is replaced by the DHCP value. If the DHCP server fails to provide replacement values, the locally entered value is used.

Select the Statically specified IP Address option to manually enter the IP address, subnet mask, and default gateway. IP AddressEnter a valid network address in the server environment. The network administrator must provide

this information. Subnet Prefix LenEnter the prefix length of the IPv6 subnet. Default gatewayUse of gateways is optional. For more information, see various IPv4-supported options in this

section.

e. Select the Enable the IEEE 802.1x authentication check box, and from the EAP type drop-down list, select TLS, LEAP, PEAP or FAST.

TLSSelect this option, and click Properties to configure the Authentication Properties dialog box. Select the Validate Server Certificate check box because it is mandatory to validate your server certificate.

NOTE: The CA certificate must be installed on the thin client. The server certificate text field supports a

maximum of approximately 255 characters, and supports multiple server names.

Select the Connect to these servers check box, and enter the FQDN of the server. Click Browse to find and select the client certificate file and the private key file you want.

NOTE: Ensure that you select the PFX file only.

Select either User Certificate or Machine Certificate, base on your choice.

68 Configuring connectivity

LEAPSelect this option, and click Properties to configure the Authentication Properties dialog box. Be sure to use the correct username and password for authentication. The maximum length for the username or the password is 31 characters.

PEAPSelect this option, and click Properties to configure the Authentication Properties dialog box. Be sure to select either EAP_GTC or EAP_MSCHAPv2, and then use the correct username, password, and domain. Validate Server Certificate is optional.

FASTSelect this option, and click Properties to configure the Authentication Properties dialog box. Be sure to select either EAP_GTC or EAP_MSCHAPv2, and then use the correct username, password, and domain.

NOTE: During the initial connection with EAP-FAST, when there is a request for a Tunnel PAC from the

authenticator, the PAC is used to complete the authentication. The first-time connection always fails, and

the subsequent connections succeed. Only automatic PAC provisioning is supported. The user/machine PAC

provisioning that is generated with CISCO EAP-FAST utility is not supported.

When EAP-MSCHAPV2 or EAP-GTC is selected for PEAP or FAST authentication, an option to hide the domain is available. Username and password boxes are available for use, but the domain text box is disabled. When EAP- MSCHAPV2 or EAP-GTC is selected for PEAP or FAST authentication, a check box to enable the single sign-on feature is available.

3. Click OK to save your settings.

Configure the WLAN settings

About this task

This section describes how to configure the wireless settings on your thin client.

NOTE: On the Wyse 5070 Thin Client with an optional SFP module or RJ45 module, you cannot configure the wireless

settings.

Steps

1. From the desktop menu, click System Setup > Network setup.

The Network Setup dialog box is displayed.

2. Click the WLAN tab, and configure the following options:

Figure 17. WLAN tab

Configuring connectivity 69

AddUse this option to add and configure a new SSID connection. You can configure the SSID connection from the available security type options. After you configure the SSID connection, the added SSID connection is listed on the WLAN tab.

RemoveUse this option to remove an SSID connection from the list. ScanUse this option to allow your thin client to scan and identify a wireless network connection. ConnectUse this option to join a wireless network from the list.

NOTE: From ThinOS 9.1.5067 onwards, when you enter a correct password to connect to the WPA and WPA2

personal wireless connection, the new password is saved and you do not need to enter the password again after you

restart the system.

PropertiesUse this option to view and configure the authentication properties of an SSID connection that is displayed in the list.

IPv4 ConfigClick this option to configure the IPv4 settings for the wireless connection.

To set IPv4 connection using either DHCP or static IP address, configure any one of the following options: If you want to enable your thin client to automatically receive information from the DHCP server, click Dynamically

allocated over DHCP/BOOTP. If you want to manually configure the IP address, click Statically specified IP Address, and provide the IPv4 details.

IPv6 ConfigClick this option to configure the IPv6 settings for the wireless connection. a. To enable the wireless IPv6, click the IPv6 slider switch. b. To set IPv6 connection using either DHCP or static IP address, configure any one of the following options:

If you want to enable your thin client to automatically receive information from the DHCP server, click Dynamically allocated over DHCP/BOOTP.

If you want to manually configure the IP address, click Statically specified IP Address, and provide the IPv6 details.

Disable Wireless DeviceSelect this check box to disable a wireless device. AlwaysClick this radio button if you want to keep the wireless options always disabled. EnetUpClick this radio button if you want to disable the wireless device whenever the wired network is connected.

3. Click OK to save your settings.

NOTE: If you have connected to Wi-Fi on a ThinOS device that is connected to the Dell WD19 docking station, you

may not be able to connect to Wi-Fi again after the ThinOS firmware update is installed and your device is automatically

restarted. To resolve this issue, you must restart the ThinOS client again.

Enable captive portal detection for wireless

When you attempt to connect to WiFi, a web page is displayed to verify the authenticated users, before Internet access is granted. ThinOS supports a captive portal that is based on HTTP redirect. Any captive portal that is based on DNS redirect or ICMP redirect is not supported in the current ThinOS release. 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 does not support the DNS response with an OPT record that is available in the Answer section.

Steps

1. Open the Admin Policy Tool on ThinOS or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. Click the Advanced tab and expand Network Configuration.

3. Click Wireless.

4. On the Global Wireless Settings page, click the Enable Captive Portal Detection toggle switch. Enabling this feature allows the ThinOS client to display the captive portal web page when you attempt to connect to WiFi.

5. In the Captive Portal Detection Interval Time field, specify the session timeout.

6. Click the Allow HTTP protocol redirection toggle switch if you want to use the HTTP protocol for redirecting to the captive portal web page.

7. Specify the captive portal detection URL. If the URL is not configured, the system default URL is used.

8. Restart your thin client for settings to take effect.

NOTE: If your thin client is connected to a wired network, you must set the default gateway to WLAN0.

70 Configuring connectivity

Configure the proxy settings

About this task

This section describes how to configure the proxy settings on your thin client.

Steps

1. From the desktop menu, click System Setup > Network setup. The Network setup dialog box is displayed.

Table 22. Supported protocols

Component Supported protocols Additional information

Wyse Management Suite HTTPS, and SOCKS5 N/A

Citrix RealTime Media Engine (RTME)

HTTP N/A

Azure Virtual Desktop (AVD) HTTP N/A

Horizon HTTP N/A

2. Click the Proxy tab, and configure the following options:

Proxy TypesYou can use HTTP proxy, HTTPS proxy and SOCKS5 proxy types. The proxy type enables the thin client to connect to the application such as Wyse Management Suite.

Proxy valuesYou can enter values for the HTTP proxy, HTTPS proxy and SOCKS5 proxy types. Adding proxy values enable the thin client to connect to the proxy server.

A new app list value HORIZON is added. For the VMware Broker agent logon to use the proxy, you should specify the Apply proxy server on field as HORIZON. Unauthenticated proxy is accepted when using HORIZON. Username and password are ignored.

A new proxy app list value called MTOP is added for Microsoft Teams in an ICA session.

Configuring connectivity 71

Figure 18. Proxy tab

Use the following guidelines:

a. Configure the proxy servers based on your requirement.

Enter the HTTP proxy port number or HTTPS proxy port number, username, and password in the respective fields. However, credential pass through ($UN/$PW) is not recommended because it starts before user sign on.

Wyse Management Suite uses both HTTP/HTTPS and MQTT protocols to communicate with the WMS/MQTT server. However, the HTTP proxy cannot redirect TCP packages to the MQTT server which requires a SOCKS5 proxy server. If there is only the HTTP server available, the real-time command that requires MQTT does not work.

NOTE: The HTTP/HTTPS proxy default port is 8080.

Enter the SOCKS5 proxy port number, username, and password in the respective fields. If SOCKS5 proxy is configured, Wyse Management Suite proxy uses the SOCKS5 only. If SOCKS5 is not configured, then Wyse Management Suite proxy searches for alternative protocols, for example, HTTP in the configuration.

NOTE: The SOCKS5 proxy default port is 1080.

Select the Use the first proxy server for all protocols check box to enable all the protocols to use the same server in the HTTP Proxy fields. Both HTTP and HTTPS proxy use the same host and port, and SOCKS5 proxy agent uses HTTP host with default Socks5 port (1080).

b. Specify the supported applications as Wyse Management Suite, Azure Virtual Desktop (AVD), and RTME separated by a semicolon in the Apply proxy server on field.

3. Click OK to save your settings.

ThinOS supports the usage of DHCP option tag 252. This option enables the device to fetch the proxy information from the DHCP server when the device is reset to factory default settings or when you restart the thin client. For example, http://x.x.x.x/proxy.pac. The proxy settings from DHCP option 252 are not displayed on the ThinOS GUI.

Proxy is enabled only for configured applications regardless of the availability of DHCP option 252. If you configure an empty value on the ThinOS local user interface, proxy is enabled for all supported applications by default. If you configure an empty value in the Wyse Management Suite policy settings or the Admin Policy Tool, proxy is not enabled for any applications. If DHCP option 252 is available and is supported by the configured application, WPAD (DHCP 252) takes priority. If DHCP 252 is available, WMS is enabled to go through proxy even if it is not configured in the Proxy Application List configuration.

72 Configuring connectivity

Table 23. VDI logon or session launch that goes through proxy

Component Features PAC proxy GUI proxy

Citrix http broker log in No No

http broker session launch

No No

https broker log in Yes Yes (RTME value added in the Apply proxy server on application list field)

https broker session launch

Yes Yes (RTME value added in the Apply proxy server on application list field)

VMware broker log in Yes Yes (HORIZON value added in the Apply proxy server on application list field)

session launch Yes Yes (HORIZON value added in the Apply proxy server on application list field)

Azure Virtual Desktop broker log in Yes Yes (AVD value added in the Apply proxy server on application list field)

session launch No No

Microsoft Remote Desktop Services

broker log in No No

session launch No No

Amazon WorkSpaces broker log in No No

session launch No No

Teradici Cloud broker log in No No

session launch No No

Wyse Management Suite Wyse Management Suite connection

Yes Yes (WMS value added in the Apply proxy server on application list field)

User scenario

1. Configure the HTTPS proxy server host and port. 2. Configure the user credentials according to the proxy server settings.

After you restart your system, the client checks in to the Wyse Management Suite server through the HTTPS proxy server.

Configure the SNMPV3 settings

SNMPV3 in ThinOS requires a security level with both authentication and privacy. This setting can be configured in Wyse Management Suite policy by going to Network Configuration > SNMPV3 Settings . ThinOS supports MIB tree 1.3.6.1.2.1 but not 1.3.6.1.2.1.10, 1.3.6.1.2.1.4.20.1.5, and 1.3.6.1.2.1.4.21.1.10. ThinOS supports private MIB tree 1.3.6.1.4.1.714 as below:

Table 24. Private MIB tree

Serial Number 1.3.6.1.4.1.714.1.2.6.2.1

Undefined yet 1.3.6.1.4.1.714.1.2.6.2.2

Undefined yet 1.3.6.1.4.1.714.1.2.6.2.3

Network speed 1.3.6.1.4.1.714.1.2.6.2.4

Network Gateway 1.3.6.1.4.1.714.1.2.6.2.5

DHCP setting (1 as enabled, 0 as disabled) 1.3.6.1.4.1.714.1.2.6.2.6

DNS setting (1 as static, 0 as dynamic) 1.3.6.1.4.1.714.1.2.6.2.7

DNS server 1.3.6.1.4.1.714.1.2.6.2.8

Configuring connectivity 73

Table 24. Private MIB tree (continued)

Send message to client 1.3.6.1.4.1.714.1.2.6.1.2.0

Reboot client 1.3.6.1.4.1.714.1.2.6.1.1.0

NOTE: Set 1.3.6.1.4.1.714.1.2.6.1.2.0 to send message to client. The message character count is increased to 255

characters.

Set 1.3.6.1.4.1.714.1.2.6.1.1.0 to reboot the client. Reboot client behaviors are as below:

Set to 0: Reboot immediately Set to x: Reboot after x minutes (x is integer) Set to -1: Cancel reboot

NOTE: If you set 1.3.6.1.4.1.714.1.2.6.1.1.0 to reboot the client, you cannot set another value to change the reboot timer

directly. You must set the value to -1 to cancel the reboot first, and then set another value to reboot again.

Configuring the remote connections Use the Remote Connections dialog box to configure the connection broker settings, general connection options, and authentication settings.

Configure the broker setup

About this task

This section describes how to configure the broker setup on your thin client.

Steps

1. From the desktop menu, click System Setup > Remote Connections. The Remote Connections dialog box is displayed.

2. On the Broker Setup tab, select a VDI broker from the Broker type drop-down list, and configure the broker settings.

3. Click OK to save your settings.

NOTE: ThinOS enables you to log in to a VDI broker using only a smartcard certificate. To enable this feature, go

to Advanced > Login Experience > Login Settings from the Wyse Management Suite policy settings or the Admin

Policy Tool, and enable the Login Use Smartcard Certificate Only option under Login Experience. When the option

is enabled, other certificates such as user certificates are ignored.

Configure the General Options

About this task

This section describes how to configure the general options on your thin client.

Steps

1. From the desktop menu, click System Setup > Remote Connections. The Remote Connections dialog box is displayed.

2. Click the General Options tab, and do the following:

74 Configuring connectivity

Figure 19. General options

a. Click one of the following options to set the action that the thin client should perform after you exit all sessions:

NoneBy default, None is selected and the thin client automatically returns to the terminal desktop. Sign-off automatically Shutdown the system automaticallyIf you select this option, you must specify a time period after which the thin

client shuts down. Restart the system automaticallyIf you select this option, you must specify a time period after which the thin

client restarts.

NOTE: You can enable or disable the privilege to cancel shutdown or restart. From the Wyse Management Suite

policy settings or Admin Policy Tool, go to Advanced > Privacy & Security > Account Privileges > Previlige

Level, and select Customize from the drop-down list. Enabled or disable the Allow to Stop Forced Reboot/

Shutdown option. If the option is disabled, when all sessions are ended, users cannot click the Cancel button on the

reboot or shutdown countdown window to stop the process.

b. Enter the default username in the Default Sign-on Username field. c. Enter the default password in the Default Sign-on password field. d. Enter the default domain in the Default Sign-on Domain field.

3. Click OK to save your settings.

Configuring the central configurations Use the Central Configuration dialog box to configure the Wyse Management Suite server settings.

Configure the Wyse Management Suite settings

About this task

This section describes how to configure the Wyse Management Suite settings on your thin client.

Configuring connectivity 75

Steps

1. From the desktop menu, click System Setup > Central Configuration. The Central Configuration dialog box is displayed.

2. On the WMS tab, do the following:

Figure 20. Wyse Management Suite

a. Select the Enable Wyse Management Suite (WMS) check box to enable the Wyse Management Suite to discover your thin client. By default, this option is selected. Wyse Management Suite service automatically runs after the client boots.

NOTE: If the first discovery, for example, the Wyse Management Suite service is not successful, it continues until a

discovery is successful. If all discoveries fail, it is started again automatically.

b. Select the DNS SRV record check box if you want the thin client to obtain the Wyse Management Suite values through DNS server, and then try to register into the Wyse Management Suite server. By default, the check box is selected. If the check box selection is canceled, the thin client cannot obtain the Wyse Management Suite values through the DNS server.

c. In the Group Registration Key field, enter the group registration key as configured by your Wyse Management Suite administrator for your group. To verify the key, click Validate Key.

NOTE: A Group Registration Key is not required for the private Wyse Management Suite server. You can provide

the Wyse Management Suite server details to enable the device to check in to Wyse Management Suite. ThinOS

registers to a quarantine tenant in Wyse Management Suite.

d. Select the Enable WMS Advanced Settings check box to enter the Wyse Management Suite server details and to enable the CA validation. By default, the MQTT server option is disabled. The MQTT server value is populated after the ThinOS device is checked in to the Wyse Management Suite.

NOTE: If you enable the external secure MQTT option on the Wyse Management Suite server, the thin client

automatically fetches the MQTT server . If port 1883 is blocked in the Wyse Management

Suite server, the ThinOS client cannot switch to the External Secure MQTT server from the External MQTT server.

If you are blocking port 1883, select External Secure MQTT as Preferred MQTT in the Wyse Management Suite

server first.

e. Select the CA validation check box if you want to enable the CA validation feature.

76 Configuring connectivity

The CA validation is required when you import certificates into your Wyse Management Suite server. By default, the CA Validation check box is selected to improve the security when using the Wyse Management Suite cloud. This change affects connections to any of the following servers: *.dellmobilitymanager.com *.cloudclientmanager.com *.wysemanagementsuite.com

Table 25. CA validation

Wyse Management Suite deployment

CA Validation

Private cloud When you deploy Wyse Management Suite on a private cloud, the Enable CA Validation check box is available to configure after you specify the server details in the WMS Server field. By default, the check box is selected.

Public cloud When you deploy Wyse Management Suite on a public cloud, the Enable CA Validation check box is selected by default. You cannot disable the Enable CA Validation option.

3. Click OK to save your settings.

NOTE: When you modify the Wyse Management Suite information, a dialog box is displayed prompting you to restart

the thin client. To apply the settings immediately, click Reboot Now. If you do not want to restart your client, click

Cancel.

Configure the VPN Manager VPN Manager is included to manage Virtual Private Network connections. ThinOS uses the OpenConnect client that is based on the SSL protocol for connecting to a VPN.

About this task

This section describes how to configure the VPN Manager on your thin client.

Steps

1. From the desktop menu, click System Setup > VPN Manager. The VPN Manager dialog box is displayed.

2. To create a session, click the + icon and do the following:

Configuring connectivity 77

Figure 21. VPN Manager

a. Enter the name of the session in the Name field. This option is mandatory. The maximum character limit is 21 characters. b. Enter the IP address of the VPN server in the Server field. This option is mandatory and is defined as either an IP

address or a hostname. The maximum character limit is 63 characters. c. Enter the login username in the Username field. This option is mandatory. The maximum character limit is 31 characters. d. Enter the password in the Password field. This option is not mandatory. The maximum character limit is 31 characters. e. Click the Auto-connection on system startup button to automatically connect to the VPN when the device restarts. f. Click the Show progress in detail button to display the VPN connection progress. g. Click the Show debug information button to display the VPN debug details for better troubleshooting. h. Click OK.

When connections are created, the Auto column displays which connection is automatically connected when the device restarts. Only one session can be set to autoconnect.

NOTE: From ThinOS version 9.1.6108, you can connect to VPN with Cisco AnyConnect, Pulse Secure, or Global

Protect.

3. Select a session and click Connect.

4. Click OK to save your changes.

Configure VNC services

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. Click the Advanced tab.

3. Expand Services and click VNC Service.

4. To enable VNC shadowing, click the Enable VNC Daemon button.

a. Enter the password in the Password field. The password length is restricted to eight characters from ThinOS 9.1.2101.

78 Configuring connectivity

b. Click the Enable 8 bits button to use 8-bit color resolution. c. Click the Enable Zlib button to enable Zlib compression. d. Click the Enable VNC Prompt button to display a prompt to allow or reject a VNC shadowing request.

The shadowing request times out if there is no user interaction. The following options can be set for a timeout. Select Timeout TypeSelect the action to be performed after the VNC shadowing request times out. You can

select Accept or Reject. TimeoutSpecify a time between 0 to 600 seconds for the VNC shadowing request to timeout, if there is no user

interaction.

e. Click the Enable View Only button to activate the view only mode. f. Click the Active Visible button to notify the user that the device is being shadowed. g. Enter the IP addresses from which VNC connections can be initiated, in the VNCD Server field. You can only enter a

valid IP address in this field. h. Specify the VNC port used for TCP-based connections in the VNCD TCP Port field.

The default port is 5900. The current connection is not affected when you change the port. The port change takes effect during the next VNC connection.

5. Click Save & Publish.

Configuring connectivity 79

Configuring connection brokers In a Virtual Desktop Infrastructure (VDI) environment, a connection broker is a software entity that enables you to connect to an available desktop. The connection broker facilitates the VDI environment to securely and efficiently manage the centrally hosted desktop environments.

Configuring Citrix Citrix offers a complete virtualization solution, where all applications and resources are deployed on a centralized server, and published to remote devices. In ThinOS 9.x, Citrix Receiver is replaced by Citrix Workspace app. Citrix Workspace app, a client software released by Citrix, enables you to access all your virtual apps, desktops, and other Citrix products from a single workspace UI. For more information about Citrix Workspace App, see the Citrix documentation at docs.citrix.com.

NOTE: In ThinOS, USB device can only be redirected in to an ICA session when the mouse focus is inside the session.

For the Citrix VDI related settings in Wyse Management Suite and Admin Policy Tool, Dell Technologies recommends configuring the settings before signing in to Citrix broker. If you have already signed in to the broker, you must sign off or reboot the client.

To access Citrix sessions using Citrix Workspace app, do the following: 1. Deploy the Citrix Workspace app package using Wyse Management Suite or Admin Policy Tool. 2. Go to System Setup > Remote Connections > Broker setup, and configure the Citrix broker.

NOTE: The Enable Volume Control for Client Volume option added in Personalization > Shortcut Keys, under Admin

Policy Tool or Wyse Management Suite policy settings can be used to control the ThinOS local volume from the remote

session. This option is added to resolve the Citrix limitation.

From Citrix Workspace app 2112 and ThinOS 9.1.5067, the following updates are added:

The battery status indicator is displayed in the notification area for server VDAs. This feature is enabled by default. In the previous version of Citrix Workspace app, only Windows VDA such as Windows 10 is supported.

Adaptive audio works while using User Datagram Protocol (UDP) audio delivery. Adaptive audio is enabled by default. This feature requires VDA version 2112 or later versions. For more information, see the Citrix Virtual Apps and Desktops product documentation at www.docs.citrix.com.

NOTE: From ThinOS 9.1.5067 onwards. you can map a USB drive with NTFS format to Citrix and RDP sessions.

For information about the supported Citrix Workspace app features in ThinOS, see the Citrix Workspace app feature matrix table in the Release Notes of your ThinOS version at www.dell.com/support

Configure the Citrix broker setup

About this task

This section describes how to configure the Citrix broker setup on your thin client.

Steps

1. From the desktop menu, click System Setup > Remote Connections. The Remote Connections dialog box is displayed.

2. On the Broker Setup tab, select Citrix Virtual Apps and Desktops from the Select Broker Type drop-down list, and do the following:

9

80 Configuring connection brokers

Figure 22. Broker Setup

a. Select the Workspace Mode check box if you want to enable the Citrix Workspace based layout of published applications and desktops.

b. In the Broker Server field, enter the IP address or hostname or FQDN of the Citrix server. You can enter the Citrix NetScaler Gateway URL, StoreFront URL, or the web interface URL.

c. In the Auto Connect List field, enter the name of the connection that is displayed in Connection Manager to automatically connect after you log in the Citrix broker. You can enter more than one connection name. Each connection name is separated by semi-colon, and is case-sensitive.

NOTE: On the desktop taskbar, click to open Connection Manager.

d. Select the Enable automatic reconnection at logon check box if you want to automatically reconnect to the disconnected sessions or both active and disconnected sessions during login. You must click either of the following options:

Connect to disconnected session only Connect to active and disconnected sessions

e. Select the Enable automatic reconnection from button menu check box if you want to automatically reconnect to the disconnected sessions or both active and disconnected sessions by using the Reconnect button in the button menu. You must click either of the following options:

Connect to disconnected session only Connect to active and disconnected sessions

To use the reconnect option, left-click the button menu, and click Reconnect.

3. Click OK to save your settings.

Configuring connection brokers 81

Classic mode vs Workspace mode

This section summarizes the differences between classic mode and workspace mode.

Figure 23. Classic mode

Figure 24. Workspace mode

82 Configuring connection brokers

Table 26. Classic mode vs Workspace mode

Item Classic mode Workspace mode

How to enable By default, the ThinOS loads the classic mode if you do not select the Workspace mode check box during Citrix broker setup.

Select the Workspace mode check box during Citrix broker setup.

Desktop elements Displays the ThinOS full taskbar and the classic desktop.

Displays the ThinOS full taskbar and the workspace desktop.

Access all published desktops

Click the icon on the classic desktop to launch the published desktop.

Click the Desktops icon on the purple ribbon to access all the published desktops.

Access all published apps

Click the icon on the classic desktop to launch the published application.

Click the APPS icon on the purple ribbon to access all the published desktops.

Access favorites Not applicable Click the Favorites icon on the purple ribbon.

Access Connection Manager On the left corner of the taskbar, click .

Click the button menu in the upper-right corner of the screen, and then click Connection Manager.

Switch account when logged in with multi server

Displays all icons of desktop and applications. You cannot switch the account.

Click the button menu in the upper-right corner of the screen, and then click Accounts.

Refresh Citrix application

Click the PNAmenu button on the taskbar, and then click Refresh.

Click the button menu in the upper-right corner of the screen, and then click Refresh.

Reconnect a session Click the PNAmenu button on the taskbar, and then click Reconnect.

Click the button menu in the upper-right corner of the screen, and then click Connection Center > Reconnect.

Disconnect from the session

Click the PNAmenu button on the taskbar, and then click Disconnect.

Click the button menu in the upper-right corner of the screen, and then click Connection Center > Disconnect .

Log off all the connected ICA sessions

Click the PNAmenu button on the taskbar, and then click Logoff.

Click the button menu in the upper-right corner of the screen, and then click Connection Center > Logoff.

Sign out of broker agent

Click the Sign-off button in Connection Manager or from the Shutdown menu.

Click the button menu in the upper-right corner of the screen, and then click Sign out. You can also click Sign out from the Shutdown menu.

Use search bar Not applicable Use the search bar on the upper-right of the screen to search for your workspace item. You can open apps directly from the search results.

Access Desktop Viewer/Toolbar

Click the Desktop Viewer/Toolbar on the top center of the Citrix session screen to use the following toolbar options:

Home Switch Ctrl+Alt+Del Window/Full-screen Preferences Save Layout Disconnect Sign Out

You can switch a session between a windowed and a full-screen session window. Save layout is available only for the local AD user session and not for users who use SAML authentication to log in to the Citrix session.

Click the Desktop Viewer/Toolbar on the top center of the Citrix session screen to use the following toolbar options:

Home Switch Ctrl+Alt+Del Window/Full-screen Preferences Save Layout Disconnect Sign Out

You can switch a session between a windowed and a full-screen session window. Save layout is available only for the local AD user session and not for users who use SAML authentication to log in to the Citrix session.

Configuring connection brokers 83

Citrix ADC

ThinOS supports Citrix Application Delivery Controller (ADC), formerly known as Citrix NetScaler. The following authentication methods are supported on ThinOS: Lightweight Directory Access Protocol (LDAP) RSA DUO SMS PASSCODE Native OTP Federated Authentication Service with Azure active directory OKTA

Timeout is enabled for Citrix ADC login by default. To disable the timeout, go to Advanced > Broker Settings > Citrix Virtual Apps and Desktops Settings from the Wyse Management Suite policy settings or the Admin Policy Tool, and disable the Netscaler/ADC Login Timeout option.

By default, the NetScaler/ADC Authentication using web-based login option is enabled for the applicable Citrix ADC server. To disable the web-based login, go to Advanced > Broker Settings > Citrix Virtual Apps and Desktops Settings from the Wyse Management Suite policy settings or the Admin Policy Tool, and disable the Netscaler/ADC Authentication using web-based login option.

NOTE: Dell technologies recommends that you do not disable the Netscaler/ADC Authentication using web-based

login option.

Citrix two-factor authentication

ThinOS supports Citrix two-factor authentication that authenticates the identity of the user twice before granting access, adding an extra level of security.

For local authentication, there must be a user profile that is created in the Citrix ADC database. For external authentication, the username and password that is entered must be the same as registered in the authentication server. After a successful validation of the username and password, the user is requested for another level of authentication.

ThinOS supports LDAP, RSA+LDAP, SMS Passcode, DUO, OKTA, and Azure MFA authentications by default. The user must only provide the Citrix ADC gateway address.

To log in to NetScaler Gateway that uses LDAP with RSA authentication, you must select LDAP+RSA in the Wyse Management Suite policy. You can also go to Admin Policy Tool and configure the NetScaler/ADC Authentication Method option in the Citrix Virtual Apps and Desktops Settings window.

For specific users who want to use Citrix ADC authentication methods, such as RSA, Dell Technologies recommends that you configure the NetScaler/ADC Authentication Method with RSA either using the Wyse Management Suite policy or Admin Policy Tool.

For specific users who want to use Citrix ADC authentication methods, such as LDAP with MFA, Dell Technologies recommends that you configure the NetScaler/ADC Authentication Methodwith LDAP either using the Wyse Management Suite policy or the Admin Policy tool.

For specific users who want to use Citrix ADC authentication methods, such as RSA+LDAP with MFA, Dell Technologies recommends that you configure the NetScaler/ADC Authentication Method with RSA+LDAP either using the Wyse Management Suite policy or the Admin Policy tool. This setting is supported from Wyse Management Suite 3.5 and later versions.

Configure Citrix ADC using LDAP and RSA

About this task

This section describes how to configure the Citrix ADC (formerly NetScaler) using LDAP and RSA authentication.

Steps

1. Go to NetScaler > NetScaler Gateway > Virtual Servers, and click Edit.

2. Set the primary and secondary authentications based on the following scenarios:

84 Configuring connection brokers

If you use LDAP and RSA login, ensure that the primary authentication is LDAP and secondary authentication is RADIUS. You must also ensure that the NetScaler Gateway Authentication Method in the Wyse Management Suite policy or the Admin Policy Tool is configured as LDAP+RSA.

If you use RSA and LDAP login, ensure that the primary authentication is RADIUS and secondary authentication is LDAP. If you use only LDAP login, ensure that the primary authentication is LDAP and secondary authentication is none.

3. Go to System Setup > Remote Connections and select Citrix Virtual Apps and Desktops from the Broker type drop-down list.

4. Enter the Citrix ADC server address in the Broker Server field.

5. Log off from the client desktop, or restart the thin client. The login window for Citrix ADC is displayed.

For more information about configuring Citrix ADC with LDAP, RSA authentication, see the Citrix NetScaler Gateway Guide at www.citrix.com.

Configuring Citrix ADC using DUO

About this task

To configure the Citrix ADC (formerly NetScaler) using DUO authentication, do the following:

Steps

1. Go to NetScaler > NetScaler Gateway > Virtual Servers, and click Edit.

2. Ensure that the primary authentication is RADIUS that is configured with the DUO authentication RADIUS.

3. Ensure that the secondary authentication is none.

4. Enter the broker address in the ThinOS user interface.

Example

For more information about configuring Citrix ADC with DUO authentication, see the Citrix NetScaler Gateway Guide at www.duo.com.

Configure Citrix ADC using CensorNet MFA authentication

Prerequisites

SMS PASSCODE is re-branded as CensorNet MFA. You can configure the Citrix ADC (formerly NetScaler) to use a One Time Passcode/Password (OTP) in the form of a personal identification number (PIN) or passcode. To obtain this one-time password, you must install CensorNet app on your mobile. After you enter the passcode or PIN, the authentication server invalidates the one-time password. You cannot enter the same PIN or password again. For more information about configuring one-time passcode, see the Citrix documentation.

Prerequisites Citrix ADC (formerly NetScaler) v12.0 and later is installed on your client. SMS PASSCODE v9.0 SP1 or later is installed and configured in your network. You can download the SMS PASSCODE v9.0

file from download.smspasscode.com/public/6260/SmsPasscode-900sp1. Remote Authentication Dial-In User Service (RADIUS) authentication policy is configured and bind to the Citrix ADC server. CensorNet app is installed and configured on your mobile device.

About this task

To use the one-time passcode on ThinOS, do the following:

Steps

1. Log in to ThinOS and connect to the ADC URL.

2. Enter your credentials, and press Enter. The PASSCODE dialog box is displayed. You will receive a push notification from the CensorNet App on your phone with the code.

3. Click OK. If the authentication is successful, you are logged into the Citrix session.

Configuring connection brokers 85

Citrix ADC Native OTP

Citrix ADC (formerly NetScaler) Native OTP enables Citrix ADC Gateway to use one-time passwords (OTPs) for authentication without the need of an extra authenticating server. A one-time password that is generated by Google Authenticator is considered to be highly secure as passcodes are randomly generated.

In ThinOS 2205 and earlier versions, if you access the Broker agent using Citrix ADC native OTP authentication, lock terminal is not supported as it is a web-based authentication. When you try to use lock terminal, a message is displayed where you can click either Continue to log off or click Cancel to stay on the screen. You are automatically signed off from the account in sixty seconds for security purposes.

Figure 25. Unable to lock account

In ThinOS 2208 (9.3.2102), after logging into a VDI Broker agent with Web Authentication and locking the ThinOS session, you must set a temporary password to unlock the system.

From ThinOS 2211 (9.3.3096) onwards, a temporary password is not required. You can use the password that is used at the time of logging in to unlock the system directly.

For more information about Native OTP support for authentication, see the NetScaler Gateway12.0 documentation at docs.citrix.com.

Log in to Citrix ADC using the passcode

Prerequisites

Ensure that you are using Citrix ADC (formerly NetScaler) 12.0 build 51.24 and later versions. Ensure that you have registered your device with Citrix ADC. For a detailed procedure on how to register your device with

Citrix ADC, see the Native OTP support for authentication article at docs.citrix.com.

About this task

This section describes how to log in to Citrix ADC using the OTP.

Steps

1. From the desktop menu, click System setup > Remote Connections. The Remote Connections dialog box is displayed.

2. Click the Broker Setup tab and select Citrix Virtual Apps and Desktops from the Broker Type drop-down list.

3. Enter the IP address of the Citrix ADC FQDN server in the Broker Server field. You can configure other options if required.

4. Click OK. The NetScaler login window is displayed.

5. Launch the Google Authenticator application on your phone and get the passcode.

6. In the Citrix ADC login window, enter the passcode and click OK. If the authentication is successful, you are logged into Citrix ADC.

86 Configuring connection brokers

Citrix Federated Authentication Service SAML with Microsoft Azure Active Directory

ThinOS supports the Citrix Federated Authentication Service with Microsoft Azure Active Directory during single sign-on to Citrix ADC using the Security Assertion Markup Language (SAML) based authentication. The FAS server delegates the user authentication to the Microsoft ADFS server or Azure AD with Security Assertion Markup Language (SAML). Both, Azure AD Multiple Factors Authentication (MFA) and Self-service password reset (SSPR), are supported.

NOTE: To use this function, you must enable Federated Authentication Service. If Federated Authentication Service is

disabled, the Citrix ADC session fails to launch.

In ThinOS 2205 and earlier versions, if you access the Broker agent using SAML, lock terminal is not supported as it is a web-based authentication. When you try to use lock terminal, a message is displayed where you can click either Continue to log off or click Cancel to stay on the screen. You are automatically signed off from the account in sixty seconds for security purposes.

Figure 26. Unable to lock account

In ThinOS 2208 (9.3.2102), after logging into a VDI Broker agent with Web Authentication and locking the ThinOS session, you must set a temporary password to unlock the system.

From ThinOS 2211 (9.3.3096) onwards, a temporary password is not required. You can use the password that is used at the time of logging in to unlock the system directly.

Enable Azure Multiple Factor Authentication for Citrix ADC Single Sign-on with SAML Authentication

Prerequisites

Create an Azure AD user in Azure Active Directory. Enable the Multiple Factor Authentication (MFA) for the user. Add the user to Azure AD Citrix ADC (formerly NetScaler) Enterprise application users and groups. Ensure that the shadow account of the user exists in local domain users group. Ensure that the SAML authentication policy is enabled. For more information, see the NetScaler Gateway documentation at

docs.citrix.com.

About this task

This section describes how to log in to Citrix ADC using SAML with Azure Multiple Factor Authentication.

Steps

1. From the desktop menu, click System setup > Remote Connections. The Remote Connections dialog box is displayed.

2. On the Broker Setup tab, select Citrix Virtual Apps and Desktops from the Broker Type drop-down list.

3. Enter the Citrix ADC Gateway URL in the Broker Server field, and click OK. The login window is displayed.

4. Enter the username of the Azure AD user and click Next.

5. Enter the initial password for the Azure AD user, and click Sign in.

Configuring connection brokers 87

6. In the More information required window, click Next.

7. On the Additional Security Verification page, do the following:

a. From the How should we contact you? drop-down list, select any one of the following methods:

Authentication phone Mobile app

b. If you select Authentication phone, enter your phone number. If you select Mobile App, click Set up and follow the on-screen instructions to add an account to the Microsoft authenticator app.

c. Click Save.

8. Enter the Azure AD username with the initial password again.

9. If you are using mobile app, approve the notification. If you are using the authentication phone, verify your information through a phone call or a text code.

10. Log in to Citrix ADC and launch the session.

Enable Azure AD Self-Service Password Reset function for Citrix ADC Single Sign-on with SAML authentication

Prerequisites

1. Create an Azure AD user in Azure Active Directory. 2. Add the user to Azure AD Citrix ADC (formerly NetScaler) Enterprise application users and groups. 3. Ensure that the shadow account of the user exists in local domain users group. 4. Ensure that Self-Service Password Reset Enabled option is selected in Azure AD for the user.

About this task

This section describes how to enable Azure AD Self-Service Password Reset function for Citrix ADC Single Sign-on with SAML authentication.

Steps

1. On the Broker setup tab, select Citrix Virtual Apps and Desktops from the Broker type drop-down list.

2. In the Broker Server field, enter the Citrix ADC Gateway URL, and click OK. The login window is displayed.

3. Enter the user credentials of the Azure AD user and click Next.

4. On the Don't lose access to your account! page, configure the following options: Authentication Phone

a. Click Set it up now. b. From the drop-down list, select your country code. c. Enter your phone number. d. Click either text me or call me.

A verification code is received on your phone by call or text message.

e. Enter the verification code and click Verify. Authentication Email

a. Click Set it up now. b. Enter the valid email address. c. Click email me.

A verification code is sent to your email.

d. Enter the verification code and click Verify.

5. Click Finish.

6. Continue with the user login.

Configure Citrix NetScaler using Okta

Okta provides Single Sign-On (SSO) capability using Remote Authentication Dial-In User Service (RADIUS) for Citrix Virtual Apps and Desktops. ThinOS supports Okta through the Citrix NetScaler Gateway 11.0 or later. The Okta RADIUS Agent is

88 Configuring connection brokers

used for user authentication. The Okta RADIUS server agent assigns the user authentication to Okta using single-factor authentication (SFA) or multifactor authentication (MFA).

For more information about configuring Citrix NetScaler Gateway to use the Okta RADIUS Agent, see the Citrix NetScaler Gateway Radius Configuration Guide at help.okta.com.

NOTE:

On the ThinOS client, you need UPN at the login window.

Phone authentication by using Okta is supported only in US and Canada.

Limitation

In ThinOS 2208 and earlier versions, only OKTA with Citrix Gateway (RADIUS) is verified. However, the StoreFront with OKTA SAML authentication or OKTA with Citrix Gateway (SAML) is not verified. OKTA with Citrix Gateway (SAML) is supported from ThinOS 2211 and Citrix Workspace App 2209.

Log in to Citrix ADC using MFA with SAML, OKTA as IDP, and Citrix FAS for SSO to VDA

This section describes how to log in to Citrix Application Delivery Controller (ADC) through Multiple Factors Authentication (MFA) with Security Assertion and Markup Language (SAML). This section also describes how to log in to Citrix ADC using OKTA as the identity provider, and Citrix FAS for Single Sign-On (SSO) to VDA.

Steps

1. From the desktop menu, go to System setup > Remote Connections.

The Remote Connections dialog box is displayed.

2. Click the Broker Setup tab and select Citrix Virtual Apps and Desktops from the Broker Type drop-down list.

3. Enter the Citrix ADC gateway server URL in the Broker Server field. You can also configure other options.

4. Click OK. The NetScaler gateway Webview login window is displayed, and you are redirected to Okta IDP for authentication.

5. 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.

6. Select Enter a code or Get a push notification security method using Okta Verify application.

7. 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.

In ThinOS 2208 (9.3.2102), after logging into a VDI Broker agent with Web Authentication and locking the ThinOS session, you must set a temporary password to unlock the system.

From ThinOS 2211 (9.3.3096) onwards, a temporary password is not required. You can use the password that is used at the time of logging in to unlock the system directly

Citrix Cloud services

ThinOS supports Citrix Cloud services. It acts as a single management console to deploy applications or desktops on any virtual or cloud setup for a secure digital workspace. For more information about Citrix Cloud services, see the Citrix Cloud article at docs.citrix.com.

Getting started with Citrix Cloud

About this task

This section describes how to log in to the Citrix Cloud server on your thin client.

Configuring connection brokers 89

Steps

1. From the desktop menu, click System Setup > Remote Connections. The Remote Connections dialog box is displayed.

2. On the Broker Setup tab, select Citrix Virtual Apps and Desktops from the Broker Type drop-down list, and do the following:

a. Select the Workspace Mode check box if you want to enable the Citrix Workspace-based layout of published applications and desktops. If this option is not selected, you are logged in to the classic mode.

b. In the Broker Server field, enter the Citrix Cloud URL. c. In the Auto Connect List field, enter the name of the desktops that you want to launch automatically after logging

in to Citrix Cloud. You can enter more than one desktop. Each desktop name is separated by a semi-colon and is case sensitive.

d. Select the Enable automatic reconnection at logon check box if you want to automatically reconnect to the disconnected sessions or both active and disconnected sessions during login. You must click either of the following options:

Connect to disconnected session only Connect to active and disconnected sessions

e. Select the Enable automatic reconnection from button menu check box if you want to automatically reconnect to the disconnected sessions or both active and disconnected sessions by using the Reconnect button in the button menu. You must click either of the following options:

Connect to disconnected session only Connect to active and disconnected sessions

3. Click OK to save your settings.

4. In the login window, enter your domain username and password to log in to Citrix Cloud.

ICA icons are displayed in Connection Manager and on the client desktop.

Automatically configure using DNS for email discovery

You can connect to a Citrix session by using an email address. The email address is used to discover the StoreFront or NetScaler Gateway URL.

Prerequisites

Install a valid server certificate on the StoreFront/AppController server and Access Gateway appliance. The full chain or path to the root certificate must be correct.

About this task

This section describes how to connect to a Citrix session by using email-based discovery.

Steps

1. Add a service record (SRV) to your DNS server to enable email-based discovery. To add a service record to the DNS server, do the following:

a. Log in to the DNS server. b. Go to DNS > Forward Lookup Zone. c. Right-click Forward Lookup Zone, and click Other New Records. d. In the Resource Record Type dialog box, select Service Location (SRV). e. Click Create Record. f. In the Service field, enter _citrixreceiver.

g. In the Protocol field, enter _tcp.

h. In the Port number field, enter the port number. i. In the Host offering this service field, enter the FQDN and the port for the StoreFront/AppController server or Access

Gateway appliance.

NOTE: You cannot use the same FQDN for both StoreFront and the Access Gateway virtual servers.

2. On ThinOS, go to System Setup > Remote Connections. The Remote Connections dialog box is displayed.

90 Configuring connection brokers

3. On the Broker Setup dialog box, select Citrix Virtual Apps and Desktops from the Broker Type drop-down list.

4. Enter the email address in the Broker Server field, and click OK.

5. Restart the thin client.

6. In the login window, enter your email address and password to log in to the session.

Citrix HDX Adaptive transport (EDT)

ThinOS supports Citrix HDX Adaptive transport for Citrix Virtual Apps and Desktops. HDX Adaptive transport enables the ICA virtual channels to automatically adapt to varying LAN and WLAN connections and improves the data throughput.

For more information about Citrix HDX Adaptive transport, see the Citrix documentation at docs.citrix.com.

Enable HDX Adaptive Transport

About this task

This section describes how to enable the HDX Adaptive Transport policy setting on Citrix Studio.

Steps

1. Go to Citrix Studio > HDX Adaptive Transport policy.

2. Set the value for HDX Adaptive Transport to either Preferred or Diagnostic mode.

For more information about configuration on Citrix Studio, see the Adaptive Transport article at docs.citrix.com.

3. On the ThinOS client, start a session from the Citrix Workspace app.

The connection is established using adaptive transport.

NOTE: If the connection type is HDX and the protocol is UDP, EDT is active for the session. If the protocol is TCP, the

session is in fallback mode.

For information about how to verify if HDX Adaptive Transport is active, see the FAQs section in this guide.

HDX Adaptive Display V2

ThinOS supports the selective use of a video codec (H.264) to compress graphics during video playback in an ICA session. This feature combines the H.264 mode and Thinwire Compatible mode for a better user experience.

For more information about HDX Adaptive Display V2, see the Citrix documentation at docs.citrix.com.

Enable HDX Adaptive Display V2

About this task

This section describes how to enable HDX Adaptive Display V2 using Citrix Studio.

Steps

1. Go to Citrix Studio > Use video codec for compression policy.

2. Select the For actively changing regions option.

3. On the ThinOS client, launch an ICA desktop.

4. Open the web browser and play your preferred video.

HDX adaptive display V2 is used for video decoding on the ThinOS client. Thinwire uses JPEG (lossy) for complex or photographic imagery and RLE (lossless) for text imagery. The rest of the screen is decomposed by Thinwire.

For more information about the Use video codec for compression policy, see the Graphics Policy Settings article at docs.citrix.com.

Configuring connection brokers 91

Browser content redirection

Browser content redirection (BCR) enables any web browser content, including HTML 5 videos, to be redirected to the ThinOS client and not redirected on the VDA side.

Browser content redirection proxy setting If you use the browser content redirection proxy settings, enter a valid proxy address and port number in the browser content redirection proxy configuration policy. Citrix Workspace app follows the server fetch and client render mechanism to fetch URL from VDA and redirect browser content from the client.

NOTE: In ThinOS 9.1.4234, BCR with Chromium Embedded Framework (CEF) is enabled by default. ThinOS does not

provide the configuration to change BCR with WebKitGKT+.

Enable Browser Content Redirection

Prerequisites

If you are using a Chrome browser, import the BCR extension into the browser. If you are using an Edge browser, import the BCR extension into the browser. If you are using a IE browser, ensure the Citrix HDXJsInjector add-on exists in the browser. If you are using an RDS-hosted desktop, and if you are using a IE browser, install the BCR add-on manually from Citrix virtual

apps and desktops IOS installer. If you want to play a QUMU video, you must add the QUMU video URL to the Citrix policy.

About this task

This section describes how to enable Browser Content Redirection using Citrix Studio.

Steps

1. Go to Citrix Studio > Browser Content Redirection policy.

2. Select the Allowed option. This enables the Browser Content Redirection policy.

3. In the Browser Content Redirection Access Control List (ACL) policy settings, add URLs that can use the browser content redirection.

NOTE: Ensure that the URL is not listed in the Browser Content Redirection Blacklist Configuration policy.

4. On the ThinOS client, launch an ICA desktop.

5. Open either IE or Chrome and enter the URL that you have added in the Access Control List (ACL). The browser viewport is rendered on the ThinOS client side. Browser attributes such as Address Bar and Status Bar still run on the VDA side.

For more information about Browser Content Redirection, see the Browser Content Redirection article at docs.citrix.com.

HTML5 Video Redirection

HTML5 Video Redirection controls and optimizes the way Citrix Virtual Apps and Desktops servers deliver HTML5 multimedia web content to users. This feature is available for internal web pages only. It requires the addition of JavaScript to the web pages where the HTML5 multimedia content is available, for example, videos on an internal training site.

The following policies must be enabled on the server side:

Windows Media redirectionBy default this option is enabled. HTML5 video redirectionBy default this option is disabled.

For more information about the ICA Multimedia policy settings, see the Citrix documentation at docs.citrix.com.

For information about how to verify if HTML5 Video Redirection is working, see the FAQs section in this guide.

92 Configuring connection brokers

Windows Media Redirection

Windows Media Redirection enables the audio and video to be rendered on the user device instead of running on the server side. Using the Windows Media Redirection feature, you can optimize the performance of Windows Media player on virtual Windows desktops.

For more information about Windows Media Redirection, see the Citrix documentation at docs.citrix.com.

Enable Windows Media Redirection

Prerequisites

Ensure that the Windows Media redirection policy is set to Allowed in Citrix Studio. By default, the value is set to Allowed.

About this task

This section describes how to enable the Windows Media Redirection feature on your thin client.

Steps

1. On the ThinOS desktop, click Connection Manager.

2. Click Global Connection Settings.

3. Select the Enable HDX/MMR check box for the ICA connection.

4. Go to System Setup > Remote Connections.

5. On the Broker Setup tab, select Citrix Virtual Apps and Desktops from the Broker type drop-down list.

6. Enter the Citrix server in the Broker Server field, and click OK.

7. Launch an ICA desktop.

8. Open Windows Media Player and play a video or an audio file.

The following types are supported: H.264 video WMV-9 video WMV-8 video WMV-7 video WMC1 video MP4 video 4K video MOV/AVI video AAC/MP3/WMA file

For information about how to check if Windows Media Redirection is working, see the FAQs section in this guide.

For more information about the ICA Multimedia policy settings, see Citrix Product documentation at docs.citrix.com.

QUMU Video Optimization Pack for Citrix

QUMU's Video Optimization Pack (VOP) for Citrix enables you to stream quality videos to endpoints managed by Citrix Virtual Apps and Desktops servers by enabling client-side fetching. The QVOP video player runs on the client side, and the video stream uses the client's network to go directly to QUMU's Video Control Center instead of accessing through VDI desktops.

Prerequisites

Ensure that the Windows Media redirection policy is set to Allowed in Citrix Studio. By default, the value is set to Allowed.

About this task

This section describes how to use QUMU Video Optimization Pack for Citrix on your thin client.

Configuring connection brokers 93

Steps

1. On the ThinOS desktop, click Connection Manager.

2. Click Global Connection Settings.

3. Select the Enable HDX/MMR check box for the ICA connection.

4. Go to System Setup > Remote Connections, select Citrix Virtual Apps and Desktops from the Broker type drop-down list.

5. On the Broker Setup tab, enter the Citrix server in the Broker Server field, and click OK.

6. Launch an ICA desktop.

7. Use Citrix Browser Content Redirection to play QUMU videos.

For information about Browser Content Redirection, see Browser Content Redirection. For more information about the ICA Multimedia policy settings, see Citrix Product documentation at docs.citrix.com.

Citrix Self-Service Password Reset

You can reset the password or unlock the account after you complete the security questions enrollment.

Supported Environment

Citrix Virtual Apps and Desktops 7.11 and later versions Support StoreFront Server 3.7 and later versions Self-Service Password Reset Server 1.0 and later versions

Supported platformsAll platforms are supported.

Limitation Supports only StoreFront Server

Before resetting a password or unlocking an account

Before resetting your password or unlocking your account, you must register for the security questions enrollment. To register your answers for the security questions, do the following:

1. To access the Security Questions Enrollment window, do the following step that is applicable to the mode: a. In Classic mode, click the Manage Security Questions option from the PNAmenu. b. In Workspace mode, click the TASKS icon on the purple ribbon and click Start.

The Security Questions Enrollment window is displayed.

2. Enter the appropriate answers to the question set. 3. Click OK to register the security questions.

Use the Account Self-Service

After the security questions enrollment is complete, and when ThinOS is connected to a StoreFront server with Self-Service Password Reset enabled, the Account Self-Service icon is displayed in the sign-on window.

NOTE: If you enter the wrong password more than four times in the Sign-on window, the client automatically enters the

unlock account process.

1. Click the Account Self-Service icon to unlock your account or reset your password.

NOTE: You must register the security questions for users before using the unlock account or reset password feature.

2. Click Unlock account or Reset password based on your choice, and then click OK.

Unlock an account

After you register the security questions, do the following to unlock your account:

1. Choose a task (Unlock account) in the Account Self-Service window. 2. Enter the username.

94 Configuring connection brokers

The Unlock Account dialog box is displayed.

3. Enter the registered answers to the security questions.

If the provided answers match the registered answers, then the Unlock Account dialog box is displayed.

4. Click OK to successfully unlock your account.

NOTE:

If the provided answers are incorrect, an error message is displayed.

If you provide the wrong answers more than three times, you cannot unlock the account or reset the password, and

error messages are displayed.

Reset a password

After you register the security questions, do the following to reset your password:

1. Choose a task (Reset password) in the Account Self-Service window. 2. Enter the username.

The Reset Password dialog box is displayed.

3. Enter the registered answers to the security questions.

If the provided answers match the registered answers, then the Reset Password dialog box is displayed.

4. Enter and confirm the new password. 5. Click OK to successfully change the password.

If you provide the wrong answers, you cannot reset the password, and an error message is displayed.

Citrix SuperCodec

Citrix SuperCodec is a H.264 decoder integrated on the ThinOS client side. The server encodes the session image into the H.264 stream and sends it to the client side. The client decodes the H.264 stream by SuperCodec and display the image on the screen. This feature improves the user experience, especially for HDX 3D Pro desktops.

Citrix SuperCodec is supported in Citrix Virtual Apps and Desktops (XenApp and XenDesktop) version 7.5 or later versions.

In Citrix Virtual Apps and Desktops version 7.9 and later, the default setting for Use video codec for compression is Use when preferred. For best performance on ThinOS device, it is recommended that you set the Use video codec for compression policy to For the entire screen. You can set the policy to Do not use video codec. This policy setting allows ThinOS to use ThinWire Plus that saves bandwidth and reduces the CPU overhead. You can also set the policy to For actively changing regions. This policy setting allows ThinOS to use Selective H.264.

ThinWire PlusEquivalent to the Do not use video codec option Fullscreen H.264Equivalent to the For the entire screen option Selective H.264Equivalent to the For actively changing regions

Anonymous logon

The Anonymous logon feature enables the users to log into the StoreFront server configured with unauthenticated store without Active Directory (AD) user credentials. It allows unauthenticated users to access the applications instead of AD accounts.

NOTE: Anonymous logon is not supported with legacy mode of StoreFront server.

NOTE: After ThinOS 2208, Lock Terminal is supported for Anonymous logon.

Configuring connection brokers 95

Enable UDP audio in a Citrix session

Citrix recommends that you use audio over User Datagram Protocol (UDP) in low-bandwidth network connections for better audio quality. ThinOS does not support UDP audio over Citrix ADC (formerly NetScaler) due to Linux Citrix Workspace app limitation.

Steps

1. Start the Admin Policy Tool on your ThinOS 9.0-based device or open the ThinOS 9.x Policy settings in Wyse Management Suite.

If you are using the Admin Policy Tool on ThinOS, you must first select the audio quality as Medium and then enable UPD audio. UPD audio is automatically disabled when you select the audio quality as High on Admin Policy Tool. However, the UPD audio is not automatically disabled when you are configuring the setting using Wyse Management Suite. UPD audio may not work if you set the audio quality as High using Wyse Management Suite.

2. On the Advanced tab, expand Session Settings, and click Citrix Session Settings.

3. In the Basic Settings section, click the Enable UPD Audio toggle key to ON state.

NOTE: From Citrix Workspace app 2112 and ThinOS 9.1.5067, Adaptive audio works while using User Datagram Protocol

(UDP) audio delivery. Adaptive audio is enabled by default. This feature requires VDA version 2112 or later versions. For

more information, see the Citrix Virtual Apps and Desktops product documentation at www.docs.citrix.com.

4. From the Audio Quality drop-down list, select Medium.

If you are using the Admin Policy Tool on ThinOS, you must first select the audio quality as Medium and then enable UPD audio. UPD audio is automatically disabled when you select the audio quality as High on Admin Policy Tool. However, the UPD audio is not automatically disabled when you are configuring the setting using Wyse Management Suite. UPD audio may not work if you set the audio quality as High using Wyse Management Suite.

Keyboard layout synchronization in VDA

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. If a Linux client keyboard is synchronized to a Windows VDA, users may observe unpredictable keyboard output. 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. You can configure the keyboard layout mode using either Wyse Management Suite or Admin Policy Tool. The keyboard layout that you select on the thin client is not automatically synchronized in the VDA session. ThinOS supports the server default mode that enables VDA users to select or switch the keyboard layout inside the VDA session using the Windows Input Method Editor (IME) language bar. For other modes such as Specific keyboard, Client Setting, or Dynamic Sync, there can be unpredictable mismatch in the keyboard output if you switch the keyboard layout in VDA. This is because the Citrix Workspace app Linux keyboard sync mode does not support switching the layout in VDA.

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. The VDA user can 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.

96 Configuring connection brokers

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.

Table 27. Citrix Workspace app keyboard layout configuration for VDA users on ThinOS

VDA user scenario Wyse Management Suite settings

VDA settings Summary

The client keyboard is synchronized to VDA, and the keyboard layout is not switched in the VDA desktop or application.

Configure the required keyboard layout for local client users and remote VDA users.

Set the VDA policy for Dynamic synchronization.

Keyboard output follows the client Linux keyboard layout and not the Windows layout. As a result, there can be an unpredictable mismatch in the keyboard output. Citrix Workspace app Linux keyboard sync mode does not support switching the layout in VDA.

The client keyboard is synchronized to VDA, and the keyboard layout is switched in the VDA desktop using the IME language bar.

The client keyboard is synchronized to VDA, and the keyboard layout is switched in VDA published applications using the IME language bar.

The client keyboard is not synchronized to VDA, and the keyboard layout is not switched in the VDA desktop or application.

Configure the required keyboard layout for using the client locally. There is no impact to the keyboard usage on remote VDA.

No specific settings are required. For recommended settings, see the VDA settings for server default mode section.

Keyboard layout follows the VDA Windows layout with predictable output.

When opening a new application in a VDA session, locking the VDA session, or unlocking the VDA session, the keyboard layout falls back to the VDA default layout. For example, EN_US.

The following are the recommended settings for VDA administrators:

Enable multiple layouts in VDA IME. Enable IME on the Windows lock screen. Set the default keyboard layout to any non-

English keyboard layout. In the system registry of VDA, go to

HKEY_LOCAL_MACHINE\SYSTEM\Current ControlSet\Control\Keyboard Layout and create the following DWORD entry:

IgnoreRemoteKeyboardLayout=1.

For more information, see the Citrix article CTX223316 at www.support.citrix.com.

The client keyboard is not synchronized to VDA, and the keyboard layout is not switched in the VDA desktop using the IME language bar.

The client keyboard is not synchronized to VDA, and the keyboard layout is not switched in VDA published applications using the IME language bar.

Table 28. Language keyboard layout settings

ThinOS keyboard layout

Windows layout Wyse Management Suite settings

Citrix Workspace app Linux dynamic synchronization

Recommended settings

Polish Keyboard layout partially matches with the Windows layout.

Supported Enabled On the client side, select the keyboard layout that fully matches with the Windows layout for local usage.

On the VDA side, select the best layout from the Windows IME

Polish (Legacy)

Keyboard layout fully matches

Supported Enabled

Configuring connection brokers 97

Table 28. Language keyboard layout settings (continued)

ThinOS keyboard layout

Windows layout Wyse Management Suite settings

Citrix Workspace app Linux dynamic synchronization

Recommended settings

with the Windows layout.

language bar after the connection is established.

For VDA administrators, see the Citrix Workspace app keyboard layout configuration for VDA users on ThinOS table in this document.

French (France)

Keyboard layout partially matches with the Windows layout.

Supported Enabled

French (Microsoft)

Keyboard layout fully matches with the Windows layout.

Supported Enabled

Belgian Keyboard layout does not match with the Windows layout.

Supported Enabled

Belgian (Comma)

Keyboard layout fully matches with the Windows layout.

Supported Enabled

Spanish Keyboard layout does not match with the Windows layout.

Supported Enabled

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 and 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.

Table 29. Citrix Workspace app Linux keyboard layout settingsClient and VDA

Mode Client-side settings Server or VDA-side settings Additional information

Server default

~/.ICAClient/wfclient.ini [WFClient] keyboardlayout=(Server Default)

Setting is configured on the StoreFront server. For example,

C:\inetpub\wwwroot\Citrix\ [store name] \App_Data\default.ica [WFClient] keyboardlayout=(Server Default)

Set the mode on either the client side or the server side. This mode takes the highest priority.

Specific keyboard

~/.ICAClient/wfclient.ini [WFClient] keyboardlayout=French

XenApp server version 2006 and higherEnable the following policies on the server side: Set the Enable Unicode

keyboard layout mapping to Allowed.

XenApp server version before 2006 There are no policies available to enable specific keyboard sync mode. You must set the registry key in the Windows VDA desktop Keyboard sync

Set the mode on either the client side or the server side. You must set the value in /opt/Citrix/ ICAClient/module.ini [KeyboardLayout].

98 Configuring connection brokers

Table 29. Citrix Workspace app Linux keyboard layout settingsClient and VDA (continued)

Mode Client-side settings Server or VDA-side settings Additional information

configuration. The setting is enabled by default on Windows Server 2012 and Windows 10 operating system. The setting is disabled by default on Windows Server 2016 and Windows Server 2019.

To enable Unicode Keyboard Layout Mapping for Windows VDA, add the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWA RE\Citrix\CtxKlMap\Enable KlMap value= DWORD 1

HKEY_LOCAL_MACHINE\SOFTWA RE\Citrix\CtxKlMap\Disabl eWindowHookvalue=DWORD 1

Dynamic sync

/opt/Citrix/ICAClient/ config/module.ini [ICA 3.0] KeyboardSync=On ~/.ICAClient/wfclient.ini [WFClient] keyboardlayout=(User Profile)

XenApp server version 2006 and higherEnable the following policies on the server end: Set the Client Keyboard

Layout synchronization and IME improvement policy to Support dynamic client keyboard layout sychronization and IME improvement.

Set the Enable Unicode keyboard layout mapping to Allowed.

XenApp server version before 2006 There are no policies available to enable dynamic sync mode. You must set the registry key in the Windows VDA desktop Keyboard sync configuration. The setting is enabled by default on Windows Server 2012 and Windows 10 operating system. The setting is disabled by default on Windows Server 2016 and Windows Server 2019.

To enable the setting, add the following registry key: HKLM\Software\Citrix\ICA\Ic aIme\DisableKeyboardSync value=DWORD 0.

To enable Unicode Keyboard Layout Mapping for Windows VDA, add the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWA RE\Citrix\CtxKlMap\Enable KlMap value= DWORD 1

HKEY_LOCAL_MACHINE\SOFTWA RE\Citrix\CtxKlMap\Disabl eWindowHook value=DWORD 1

Set the mode on both the client side and the server side.

Sync once /opt/Citrix/ICAClient/ config/module.ini [ICA 3.0]

Not available Not available

Configuring connection brokers 99

Table 29. Citrix Workspace app Linux keyboard layout settingsClient and VDA (continued)

Mode Client-side settings Server or VDA-side settings Additional information

KeyboardSync=Off ~/.ICAClient/wfclient.ini [WFClient] keyboardlayout=(User Profile)

Table 30. ThinOS dynamic synchronization support

Keyboard Synchronization

Arabic (Algeria) Not supported

Arabic (Bahrain) Not supported

Arabic (Egypt) Not supported

Arabic (Iraq) Not supported

Arabic (Jordan) Not supported

Arabic (Kuwait) Not supported

Arabic (Lebanon) Not supported

Arabic (Libya) Not supported

Arabic (Morocco) Not supported

Arabic (Oman) Not supported

Arabic (Qatar) Not supported

Arabic (Saudi Arabia) Not supported

Arabic (Syria) Not supported

Arabic (Tunisia) Not supported

Arabic (U.A.E) Not supported

Arabic (Yemen) Not supported

Canadian Multilingual Supported.

Chinese (Simplified) Supported. When you switch to the language Keyboard layout in VDA, the keyboard layout is synchronized to the English layout.

Chinese (Traditional) Supported. When you switch to the language Keyboard layout in VDA, the keyboard layout is synchronized to the English layout.

Croatian Supported

Czech (Qwerty) Supported

Czech Supported

Danish Supported

Dutch Supported

English (3270 Australian) Supported

English (Australian) Supported

English (New Zealand) Supported

English (United Kingdom) Supported

English (United States) Supported

100 Configuring connection brokers

Table 30. ThinOS dynamic synchronization support (continued)

Keyboard Synchronization

Estonian (Estonia) Supported

Finnish Supported

French (Canadian Legacy) Supported

French (Canadian) Not supported

French (France) Supported

French (France Microsoft) Not supported

French (Switzerland) Supported

German (Switzerland) Supported

German Supported

Greek Supported

Hungarian Supported

Icelandic Supported

Italian (Switzerland) Not supported

Italian Supported

Japanese (OADG109A) Supported

Japanese (KWD) Supported. When you switch to the language Keyboard layout in VDA, the keyboard layout is synchronized to the English layout.

Korean (MS-IME2002) Supported. When you switch to the language Keyboard layout in VDA, the keyboard layout is synchronized to the English layout.

Korean Supported. When you switch to the language Keyboard layout in VDA, the keyboard layout is synchronized to the English layout.

Latvian (Latvia) Supported

Lithuanian (IBM) Supported

Lithuanian (Standard) Supported

Norwegian Supported

Polish Supported

Polish (Legacy) Not supported

Portuguese (Brazil) Supported

Portuguese Supported

Romanian Not supported

Russian Supported. When you switch to the language Keyboard layout in VDA, the keyboard layout is synchronized to the English layout.

Serbian Supported

Slovenian Supported

Spanish Supported

Swedish Supported

Turkish Supported

U.S.International Not supported

Configuring connection brokers 101

Enable keyboard layout mode

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. On the Advanced tab, expand Session Settings, and click Citrix Session Settings.

3. In the Basic Settings section, select one of the following options from the Keyboard Layout Mode drop-down list. Server DefaultThinOS allows VDA users to use the VDA-side default keyboard when logging in or reconnecting to

VDA. This is the default setting in ThinOS. Any keyboard layout change on the client side is not synchronized to the VDA session.

Specific KeyboardThinOS allows VDA users to use a specific keyboard when logging in or reconnecting to VDA. Any keyboard layout change on the client side is not synchronized to the VDA session. Ensure that you select a specific keyboard on the ThinOS client before configuring the Admin policy tool or the Wyse Management Suite policy. If not selected, you must reboot the thin client to synchronize the specific keyboard into VDA.

Client SettingThinOS allows VDA users to synchronize only the VDA-side keyboard with the client-side default keyboard when logging in or reconnecting to VDA. Any keyboard layout change on the client-side is not synchronized to the VDA session.

Dynamic SyncThinOS allows VDA users to synchronize the VDA-side keyboard with the client-side default keyboard dynamically in the VDA session. When the VDA user changes the client keyboard, the VDA keyboard is synchronized automatically in the session. You must configure both the client and VDA-side settings to enable this mode.

4. Click Save & Publish.

Keyboard layout server default mode enhancement

Keyboard Layout Server Default Mode enhancementFrom Citrix Workspace App 2109 and ThinOS 9.1.5067 onwards, only the Server Default mode uses the Scancode. Other Keyboard layout modes such as Specific Keyboard, Client Setting, and Dynamic Sync use the default Unicode. There are no changes to the other keyboard layout modes in Citrix Workspace App 2109.

To configure, do the following:

1. Set the Keyboard Layout Mode to Server Default using Admin Policy Tool or Wyse Management Suite. 2. On Admin Policy Tool or Wyse Management Suite policy settings, go to Advanced tab > VDI Configuration Editor >

Citrix Configuration Editor. 3. In the Citrix INI settings, click Add Row. 4. From the File drop-down list, select wfclient.ini. 5. From the Operation drop-down list, select Add or Update. 6. In the Section field, enter WFClient.

7. In the Key field, enter KeyboardEventMode.

8. In the Value field, enter Scancode.

9. Sign out or restart the device for settings to take effect. NOTE: If you want to change the Server Default mode to other keyboard layout modes, you must remove the

KeyboardEventMode with Scancode setting from Citrix Configuration Editor.

Keyboard layout Dynamic Sync mode enhancement

When setting the keyboard layout to Dynamic Sync, the switching keyboard progress bar is not displayed in desktop sessions after switching the keyboard language on the thin client. Hence, the keyboard layout in session is not automatically synced with the client. The issue also occurs in Linux Citrix Workspace app binary. To resolve the issue, do the following:

Steps

1. Set the Keyboard Layout Mode to Dynamic Sync using Admin Policy Tool or Wyse Management Suite.

2. On Admin Policy Tool or Wyse Management Suite policy settings, go to Advanced > VDI Configuration Editor > Citrix Configuration Editor.

3. In the Citrix INI Settings, click Add Row.

4. From the File drop-down list, select wfclient.ini.

5. From the Operation drop-down list, select Add or Update.

6. In the Section field, enter WFClient.

102 Configuring connection brokers

7. In the Key field, enter KeyboardSyncMode.

8. In the Value field, enter Dynamic.

9. Sign out or restart the device for the settings to take effect

Cursor pattern in ICA session

In ThinOS 9.1.2101, you can change the cursor pattern in the ICA session.

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. On the Advanced tab, expand Session Settings, and click Citrix Session Settings.

3. Enter one of the following values in the Cursor Pattern field to change the cursor pattern:

ffff,ffffEnter this value to set the cursor color as black. This value is set by default.

0,0Enter this value to set the cursor color as white.

aaaa,5555Enter this value to set the cursor color in a dotted pattern.

4. Click Save & Publish.

For the setting changes to take effect, you must either sign off from the Broker agent or restart the client.

Citrix multiple virtual channels

From ThinOS 9.1.3112 and later versions with Citrix Workspace app 2104 and later, ThinOS Citrix UC Virtual Channel Settings and Other Citrix Virtual Channels Settings are deprecated. The configuration changes that you make to the Admin Policy Tool or the Wyse Management Suite policy settings does not affect the Citrix multiple channel settings since multiple virtual channels are always enabled on the thin client. However, ensure that you uninstall the Unified Communications (UC) packages that are not required, to prevent the consumption of server and client resources. Dell Technologies recommends that you install the Citrix Workspace app package first, and then install the Citrix Unified Communications package.

Citrix UC Virtual Channel Settings and Other Virtual Channel Settings in the Admin Policy Tool or Wyse Management Suite server are only applicable for ThinOS 9.1.2101 or earlier versions. From ThinOS 9.1.3112 to 2208 (9.3.2102), Admin Policy Tool does not sync the Citrix Unified Communication Virtual Settings and Other Virtual Channel Settings from Wyse Management Suite policy settings.

The following combinations of UC optimizations and their virtual channel settings are tested on ThinOS 9.1.2101 and 131:

Table 31. Unified Communication optimizations and their default virtual channel settings

Virtual Channel categorie s

Settings Default status

Combinat ion 1

Combinat ion 2

Combinat ion 3

Combinat ion 4

Combinat ion 5

Combinat ion 6

Combinat ion 7

UC Virtual Channel Settings

Microsoft Teams Optimizati on

Enabled Enabled Disabled Disabled Enabled Disabled Enabled Disabled

RTME for Skype for Business

Enabled Enabled Disabled Disabled Disabled Disabled Disabled Enabled

Zoom Meetings Optimizati on

Disabled Disabled Disabled Enabled Enabled Disabled Disabled Disabled

JVDI for Cisco Jabber

Disabled Disabled Disabled Disabled Disabled Enabled Disabled Disabled

Cisco Webex Meetings

Disabled Disabled Enabled Disabled Disabled Disabled Disabled Disabled

Configuring connection brokers 103

Table 31. Unified Communication optimizations and their default virtual channel settings (continued)

Virtual Channel categorie s

Settings Default status

Combinat ion 1

Combinat ion 2

Combinat ion 3

Combinat ion 4

Combinat ion 5

Combinat ion 6

Combinat ion 7

for VDI Plugin

Cisco Webex Teams for VDI Plugin

Disabled Disabled Enabled Disabled Disabled Disabled Disabled Disabled

Other Citrix Virtual Channels Settings

USB redirection

Enabled Enabled Enabled Disabled Disabled Enabled Enabled Enabled

Imprivata Enabled Enabled Enabled Enabled Disabled Enabled Enabled Enabled

In ThinOS 9.1.2101 and earlier versions, Zoom Meetings Optimization plug-in uses four virtual channels. To use Zoom Optimizations along with Microsoft Teams or any other Cisco optimizations, you must disable other virtual channels. For example, if you are not using Imprivata SSO, you can choose to disable the Imprivata virtual channel. Similarly, if you do not use Skype for Business, you can choose to disable the RTME for Skype for Business virtual channel.

NOTE: The UC Virtual Channel settings do not apply to ThinOS versions later than 9.1.2101 but earlier than or equal to 2208

(9.3.2102). These settings are supported again from ThinOS 2211 and later. From ThinOS 2211, the default values of all UC

virtual channel settings have been changed to Enabled.

NOTE: When the UC virtual channels are disabled, the Unified Communication software on ThinOS uses the fallback mode,

which uses the HDX webcam and HDX audio. Using the fallback mode consumes more remote desktop resources such as

CPU, GPU, RAM, and Network.

NOTE: Enabling or disabling the UC plug-in settings in VDI Configuration Editor > Citrix Configuration Editor is

deprecated from ThinOS 2211.

For ThinOS 9.1.2101 or earlier versions, see ThinOS 9.1 Administrator's Guide at www.dell.com/support on the number of allowed virtual channels and tested combinations of Unified Communication optimizations.

Configure the Citrix virtual channels settings

About this task

This task is only applicable for ThinOS 9.1.2101 and earlier versions.

Steps

1. On the ThinOS client, open Admin Policy Tool, or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. On the Advanced tab, expand Session Settings, and click Citrix Session Settings.

3. In the UC Virtual Settings section, enable one or more Unified Communications (UC) virtual channels as per your preference. The available options are: Microsoft Teams Optimization RTME for Skype for Business Zoom Meetings Optimization JVDI for Cisco Jabber Cisco Webex Meetings for VDI Cisco Webex Teams for VDI

4. In the Other Citrix Virtual Channel settings, enable one or more virtual channels as per your preference. The available options are: USB redirection Imprivata

5. Click Save & Publish.

104 Configuring connection brokers

For the list of virtual channel combinations that are tested on ThinOS, see Citrix multiple virtual channels.

From ThinOS 2211, UC Virtual Channel settings in Citrix Session Settings in Admin Policy Tool or Wyse Management Suite policy is enabled again.

To configure UC Virtual Channel settings in Citrix Session Settings, do the following: a. On the ThinOS client, open Admin Policy Tool, or go to the ThinOS 9.x policy settings in Wyse Management Suite. b. In the Advanced tab, expand Session Settings, and click Citrix Session Settings. c. In the UC Virtual Channel Settings section, enable or disable one or more Unified Communications (UC) virtual

channels as per your preference. The available options are: Microsoft Teams Optimization HDX RealTime Media Engine for Microsoft Skype for Business Zoom Meetings Optimization Cisco Jabber Softphone for VDI (JVDI) Cisco WebEx Meetings for VDI Cisco WebEx VDI (formerly Cisco WebEx Teams)

d. Sign out or restart the device for the settings to take effect.

The following UC virtual channels labels are renamed in ThinOS 2211 Admin Policy Tool and Wyse Management Suite version 4.0 using the Configuration UI package vxxxxx:

RTME for Skype for Business is renamed to HDX RealTime Media Engine for Microsoft Skype for Business. JVDI for Cisco Jabber is renamed to Cisco Jabber Softphone for VDI (JVDI). Cisco Webex Meetings for VDI is renamed to Cisco WebEx Meetings for VDI. Cisco Webex Teams for VDI is renamed to Cisco WebEx VDI (formerly Cisco WebEx Teams).

NOTE: The UC Virtual Channel settings do not apply to ThinOS versions later than 9.1.2101 but earlier than or equal to

2208 (9.3.2102). These settings are supported again from ThinOS 2211 and later. From ThinOS 2211, the default values

of all UC virtual channel settings have been changed to Enabled.

NOTE: When the UC virtual channels are disabled, the Unified Communication software on ThinOS uses the fallback

mode, which uses the HDX webcam and HDX audio. Using the fallback mode consumes more remote desktop resources

such as CPU, GPU, RAM, and Network.

NOTE: Enabling or disabling the UC plug-in settings in VDI Configuration Editor > Citrix Configuration Editor is

deprecated from ThinOS 2211.

Configure the Citrix session properties

About this task

This section describes how to configure the Citrix HDX connections on your thin client.

Steps

1. On the taskbar, click Connection Manager. The Connection Manager dialog box is displayed.

2. Select a Citrix connection from the list, and click Properties.

3. Click the Connection tab and do the following:

You can view Server or Published Application, Connection Description, Browser Servers, Host Name or Application Name, and Encryption Level but cannot edit these options.

a. Display ResolutionSelect the display resolution for this connection.

If you select the Published Application option, the connection display enables you to select the Seamless Display Resolution option.

b. Window mode and Full screen modeSelect the initial view of the application and desktop in a windowed screen or full screen.

c. Autoconnect on start-upWhen this option is selected, the thin client automatically connects the session on start-up. d. Reconnect after disconnectWhen this option is selected, the thin client automatically reconnects to a session after

a non operator-initiated disconnect. The wait interval is the value that you set in the Delay before reconnecting box (enter the number of s 13600). The default is 20 s if you are a stand-alone user.

Configuring connection brokers 105

4. Click the logon tab to view Logging on area.

You can view Login Username, Password, Domain name, and Logon Mode.

5. Click the Options tab, and do the following:

a. Autoconnect to local devicesSelect any optionsPrinters, Serials, Smart Cards, Sound, and Disksto have the thin client automatically connect to the devices.

NOTE: USB devices that are connected are managed in Global Connection Settings.

b. Audio QualityFrom the drop-down list, select your preferred audio quality. c. Enable session reliabilityWhen enabled, session reliability allows you to momentarily lose connection to the server

without having to re-authenticate upon regaining a connection. Instead of the connection time-out, the session is kept alive on the server and is made available to the client upon regaining connectivity. Session reliability is most relevant for wireless devices. From version 21.12.0.18.2, the screen changes when session reliability begins. The session window is disabled and a countdown timer with the time until the next reconnection attempt is displayed.

6. Click OK to save your settings.

Using multiple displays in a Citrix session

ThinOS supports ICA desktop multiple displays in Citrix Virtual Apps and Desktops/Citrix Virtual Apps 7.6 and later versions.

Prerequisites

Increase the value of MaxVideoMemoryBytes REG_DWORD to support one or more 4K resolution-displays. For more information, see the Citrix documentation at support.citrix.com.

Increase the display memory limit to support more color depth and higher resolution. For more information, see the Citrix documentation at citrix.com.

Steps

1. Connect multiple displays to ThinOS device.

2. Go to System Setup > Display, disable Mirror Mode, and configure the display layout.

3. Launch an ICA desktop. By default, the ICA desktop is launched in the full-screen mode.

Table 32. Display details

Platforms Best Display resolution Maximum number of system displays

Standard or RDS desktop Windows 10, 2012 R2, and 2016

HDX 3D Pro desktop Windows 10 with NVIDIA TESLA P40 GPU

Wyse 5070 Extended Thin Client

1920 x 1080 6 4

2560 x 1440 6 4

3840 x 2160 4 4

5120 x 1440 2 2

Wyse 5070 Thin Client Pentium processor

1920 x 1080 3 3

2560 x 1440 3 3

3840 x 2160 3 3

5120 x 1440 2 2

Wyse 5070 Thin Client Celeron processor

1920 x 1080 2 2

2560 x 1440 2 2

3840 x 2160 2 2

5120 x 1440 2 2

4. Move the display blocks as per your requirement.

106 Configuring connection brokers

NOTE: For more information about the Citrix official multiple displays support, see the Citrix documentation at

support.citrix.com.

LimitationIf you set all monitors with either horizontal or vertical layout, the maximum supported resolution is 4x4 K. If you connect five or six monitors with 4x4 K + 1920x1080 or 4x4 K + 2x1920x1080 resolution combinations, you cannot launch ICA desktop by horizontal or vertical layout. Dell Technologies recommends using grid layout such as 2x3 or 3x2 or 2x2+1.

USB Printer Redirection

Prerequisites

Go to Citrix Studio, and enable the Client USB device redirection policy.

About this task

This section describes how to configure USB Printer Redirection in a Citrix session.

Steps

1. On the ThinOS desktop, open the Connection Manager window, and click Global Connection Settings. The Global Connection Settings dialog box is displayed.

2. Clear the Exclude printer devices check box, and click OK.

3. Log off from Citrix Broker agent, and then log in again.

4. Connect a USB printer to the thin client.

5. Log in to a Citrix session.

6. Go to Control Panel > Devices and Printer, and verify if the printer driver is automatically installed. After the printer drive installation is complete, the redirected printer is listed in the Printers section.

USB device redirection using Citrix Desktop Viewer

From ThinOS 2208 and Citrix Workspace App 2207, Devices section is able to show in Citrix Desktop Viewer.

Redirect USB devices from the Devices section

To redirect the USB devices from the Devices section to session, do the following:

Steps

1. In a desktop session, navigate to the Desktop Viewer under Devices. The USB devices are displayed.

2. To redirect a device to session, select the device from the menu item.

NOTE: To disconnect a device from the session, clear the required menu item or check boxes next to the devices when

the devices are mapping in session.

Redirect the USB devices from the Preferences section

To redirect the USB devices from the Preferences section to session, do the following:

Steps

1. Navigate to the Preferences > Devices section. The USB devices are displayed.

2. Select the Redirect check boxes next to the devices.

3. Click OK.

Configuring connection brokers 107

NOTE: To disconnect a device from the session, clear the required menu item or check boxes next to the devices when

the devices are mapping in session.

Configure the Citrix UPD printer

Use of Citrix Universal Print Driver (Citrix UPD) ensures that all printers that are connected to the thin client can also be used from a virtual desktop or application session without integrating a new printer driver in the data center. Citrix UPD is the base of Citrix Universal Printer. It is an autocreated printer object that uses the Citrix UPD and is not tied to any specific printer defined on the client.

About this task

This section describes how to configure the Citrix UPD usage on your thin client.

Steps

1. Connect a printer to the ThinOS client.

2. On the ThinOS desktop menu, do the following:

a. Open the Connection Manager window. b. Click Global Connection Settings. c. Go to the Session tab and select the Exclude printer devices check box. d. Click OK.

3. From the desktop menu, click System Setup > Printer Setup.

The Printer Setup dialog box is displayed.

4. Enter the name of the printer in the Printer Name box.

5. Enter any string of the Printer identification in the Printer Identification box.

6. Select the type of the printer class from the drop-down list, select the check box to enable the printer device, and click OK.

NOTE: In ThinOS, only PS class is supported.

7. Start a Citrix Virtual Apps and Desktops application connection.

8. Open the Devices and Printers in the desktop or application. The printer is mapped as the UPD printer by default.

Next steps

To enable the printer server policies for Citrix UPD printer, see the Citrix documentation at docs.citrix.com.

Configure the device-specific printer driver

Based on the Citrix Host Printer Policy settings, ThinOS supports device-specific printer drivers. This method allows Citrix hosts to automatically create client redirected printer queues based on the peripheral management printers settings of the ThinOS client. The host print manager uses the printer name and the printer ID to automatically create the printer queues.

About this task

This section describes how to configure the device-specific printer driver usage on your ThinOS client.

Steps

1. Connect a printer to the ThinOS client.

2. From the desktop menu, click System Setup > Printer.

The Printer Setup dialog box is displayed.

3. On the ThinOS desktop menu, do the following:

a. Open the Connection Manager window. b. Click Global Connection Settings. c. Go to the Session tab and select the Exclude printer devices check box. d. Click OK.

108 Configuring connection brokers

4. Enter the name of the printer in the Printer Name box.

5. Enter the specific printer driver identification in the Printer Identification box.

NOTE: The specific printer driver identification is installed on the remote Citrix desktop and you must note the specific

printer driver identification.

6. Select the check box to enable the printer device, and click OK.

NOTE: In ThinOS, only printer driver type 3 is supported.

7. Start a Citrix virtual connection.

8. Open the Devices and Printers in the desktop or application. The printer is mapped to the session.

Invert cursor color

From Citrix Workspace app 2112 and ThinOS 9.1.5067, the cursor color can be inverted based on the background color of a text. As a result, you can easily locate the position of the cursor in between texts. By default, this feature is disabled. To enable cursor color inverting feature, do the following:

Steps

1. On Admin Policy Tool or Wyse Management Suite policy settings, go to Advanced > VDI Configuration Editor > Citrix Configuration Editor.

2. In the Citrix INI Settings, click Add Row.

3. From the File drop-down list, select wfclient.ini.

4. From the Operation drop-down list, select Add or Update.

5. In the Section field, enter Thinwire3.0.

6. In the Key field, enter InvertCursorEnabled.

7. In the Value field, enter True.

8. Sign out or restart the device for the settings to take effect.

NOTE: If you have enabled the cursor color inverting feature, the Cursor Pattern setting from Advanced > Session

Settings > Citrix Session Settings in the Admin Policy Tool or Wyse Management Suite policy settings is deprecated.

Echo cancellation for Microsoft Teams

From Citrix Workspace app 2112 and ThinOS 9.1.5067, Microsoft Teams optimization supports echo cancellation. The echo cancellation option for Microsoft Teams is disabled by default.

Enable echo cancellation for Microsoft Teams

Steps

1. On Admin Policy Tool or Wyse Management Suite policy settings, go to Advanced > VDI Configuration Editor > Citrix Configuration Editor.

2. In the Citrix JSON Settings, click Add Row.

3. From the File drop-down list, select hdx_rtc_engine/config.json.

4. From the Operation drop-down list, select Add or Update.

5. In the Key field, enter EnableAEC.

6. In the Value field, enter 1.

7. Sign out or restart the device for the settings to take effect.

Limitation: If you set EnableAEC as 1, and 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.

If you encounter audio issues during Microsoft Teams calls or meetings, you can change the default settings to troubleshoot the audio issues (like robotic voice, increased system performance causing audio issues, and so on) by doing the following:

Configuring connection brokers 109

a. In the Citrix JSON Settings, click Add Rowto add the setting b. From the File drop-down list, select hdx_rtc_engine/config.json. c. From the Operation drop-down list, select Add or Update. d. In the Key field, enter EnableAGC.

e. In the Value field, enter 0.

f. In the Citrix JSON Settings, click Add Row to add the setting. g. From the File drop-down list, select hdx_rtc_engine/config.json. h. From the Operation drop-down list, select Add or Update. i. In the Key field, enter EnableNS.

j. n the Value field, enter 0.

k. Sign out or restart the device for the settings to take effect.

Multiwindow chat and meetings for Microsoft Teams

From ThinOS 2208 and Citrix Workspace App 2207, Microsoft Teams optimization supports the multiwindow chat and meetings feature. Using this feature, you can view chat and meetings in separate windows.

NOTE: For this feature to work, the Citrix Workspace app package version must be 22.7.0.20.2 or later, Citrix VDA version

must be 2112 or later, and Microsoft Teams version must be 1.5.00.11865 or later. You must sign out from Microsoft Teams

and restart the device for the feature to be enabled.

UDP audio through Citrix Gateway

From Citrix Workspace app 2112 and ThinOS 9.1.5067, Citrix Workspace app supports Datagram Transport Layer Security (DTLS) protocol for UDP audio. As a result, you can access the UDP audio through Citrix Gateway. By default, this feature is disabled.

Enable UDP audio through Citrix Gateway feature

Prerequisites

Ensure that UDP audio is enabled in ThinOS. To configure the settings, do the following: 1. On Admin Policy Tool or Wyse Management Suite policy settings, go to Advanced > Session Settings > Citrix Session

Settings. 2. Select the Enable UDP audio check box. 3. Select Audio quality as Medium. Ensure that Citrix Audio quality policy is High or Medium in Citrix Studio. 4. Sign off from the session and the broker for the changes to take effect.

Steps

1. On Admin Policy Tool or Wyse Management Suite policy settings, go to Advanced > VDI Configuration Editor > Citrix Configuration Editor.

2. In the Citrix INI Settings, click Add Row.

3. From the File drop-down list, select module.ini.

4. From the Operation drop-down list, select Add or Update.

5. In the Section field, enter WFClient.

6. In the Key field, enter EnableUDPThroughGateway.

7. In the Value field, enter True.

8. Sign out or restart the device for the settings to take effect.

110 Configuring connection brokers

Disable UDP audio through Citrix Gateway feature

Steps

1. On Admin Policy Tool or Wyse Management Suite policy settings, go to Advanced > Session Settings > Citrix Session Settings.

2. Clear the Enable UDP audio check box.

3. On Admin Policy Tool or Wyse Management Suite policy settings, go to Advanced > VDI Configuration Editor > Citrix Configuration Editor.

4. Remove the EnableUDPThroughGateway setting.

5. Sign out or restart the device for the settings to take effect.

Multiple audio redirection

From ThinOS 2205 and Citrix Workspace app 2203, Citrix Workspace app displays all available local audio devices in a session with their names. Plug-and-play support for Bluetooth and HDMI audio devices are also provided. This feature is disabled by default.

About this task

Follow this task to enable the feature.

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, go to Peripheral Management > VDI Configuration Editor > Citrix Configuration Editor.

3. In the Citrix INI Settings, click Add Row.

4. From the File drop-down list, select module.ini.

5. From the Operation drop-down list, select Add or Update.

6. In the Section field, enter ClientAudio.

7. In the Key field, enter AudioRedirectionV4.

8. In the Value field, enter True.

9. Click Save & Publish.

10. Sign out and restart the device for the settings to take effect.

For limitations and known issues, see the Release Notes of your ThinOS version at www.dell.com/support.

Citrix multiple audio redirection limitation

If JVDI package is installed in ThinOS, audio devices cannot be switched in the applications in session, and the session is disconnected when you open Windows > Sound, and go to the Recording devices list. If you want to use multiple ICA audio devices, it is recommended that you do not install the JVDI package.

Smart card reader plug and play

From Citrix Workspace app 2112 and ThinOS 9.1.5067, Citrix Workspace app supports plug and play functionality for smart card reader. When you insert a smart card, the smart card reader detects the smart card in the server and the client. You can plug and play multiple cards simultaneously, and all these cards are detected. This feature is enabled by default. From ThinOS 2205 and Citrix Workspace app 2203, you are allowed to disable smart card plug and play functionality.

Disable smart card plug and play

Steps

1. On Admin Policy Tool or Wyse Management Suite policy settings, go to Advanced > VDI Configuration Editor > Citrix Configuration Editor.

Configuring connection brokers 111

2. In the Citrix INI Settings, click Add Row.

3. From the File drop-down list, select module.ini.

4. From the Operation drop-down list, select Add or Update.

5. In the Section field, enter SmartCard.

6. In the Key field, enter DriverName.

7. In the Value field, enter VDSCARD.DLL.

8. Sign out or restart the device for the settings to take effect.

HDX RealTime Webcam Video Compression for 32-bit apps

Only 32-bit apps on the virtual desktop with HDX RealTime Webcam Video Compression are supported by ThinOS. Dell Technologies only qualified this feature using Citrix Workspace App 2109 package. With this feature, you can customize the camera resolution and frames per second from System Setup > Peripherals > Camera. You can also customize this feature using Admin Policy Tool or Wyse Management Suite policy settings. HDX RealTime Webcam Video Compression is compatible with most unified communications clients. The feature has been tested for compatibility with Cisco Webex Meetings, Cisco Webex Teams, Cisco Jabber, Microsoft Teams, Skype for Business 365, and Zoom. You can use a 32-bit browser such as Google Chrome or Mozilla Firefox to verify the webcam redirection online. External USB cameras or the integrated camera can be used with HDX RealTime Webcam Video Compression. Webcam bandwidth consumption can vary with webcam models. Different webcams offer different frame rates and resolution. Dell Technologies used the following webcams for initial feature validation: Microsoft LifeCam HD-3000Highest supported resolution with HDX RealTime Webcam Video Compression is 1920x800. Logitech C920, C922, C930eHighest supported resolution with HDX RealTime Webcam Video Compression is 1600x896. Wyse 5470 and 5470 All-in-One thin clients with built-in camera.

HDX RealTime Webcam Video Compression limitations

Camera with hardware encoding is not supported in ThinOS. Since x264 library is not integrated into ThinOS, 64-bit apps with HDX RealTime Webcam Video Compression are not

supported by Citrix Workspace App. Hence, only 32-bit apps with HDX RealTime Webcam Video Compression are supported in ThinOS.

Citrix Workspace App 2112 with HDX RealTime Webcam Video Compression works only with built-in camera. The issue is also reproduced in Linux Citrix Workspace app binary. Hence, from this ThinOS release, HDX RealTime Webcam Video Compression is only supported with Citrix Workspace app 2109.

Sometimes, the updated Camera Width, Camera Height and Camera FPS settings does not sync from Wyse Management Suite to the thin client. You must reboot the client for the changes to take effect.

HDX RealTime Webcam Video Compression in ThinOS supports only one webcam at a time. Citrix Workspace Linux binary can update the default webcam by modifying HDXWebCamDevice in $HOME/.ICAClient/wfclient.ini configuration file. For example, add HDXWebCamDevice=/dev/video2 to set the webcam mapped to /dev/video2 in a system. However, ThinOS does not allow to input the value /dev/video2 in VDI Configuration Editor due to security reasons.

If client camera is set to 2304x1296 or 2304x1536 video resolution, the HDX webcam redirection cannot be previewed in the session. This limitation is reproduced in CWA 2109 Linux binary as well.

If client camera is set to 1920x1080 video resolution, the HDX webcam redirection falls back to 325x288 video resolution in the session. This limitation is reproduced in CWA 2109 Linux binary as well.

HDX webcam camera sometimes does not work on WebEx Meeting call. This limitation is reproduced in CWA 2109 Linux binary as well.

Zoom application video preview sometimes fails when you use Citrix HDX Webcam. This limitation is reproduced in CWA 2109 Linux binary as well.

WebEx application video fails to preview when you use Citrix HDX Webcam. This limitation is reproduced in CWA 2109 Linux binary as well.

External USB camera does not work with Citrix HDX Webcam in Citrix Workspace app 2112. Only the built-in camera works. This limitation is reproduced in CWA 2109 Linux binary as well.

Prerequisites for HDX RealTime Webcam Video Compression

On the VDA, HDX RealTime Webcam Video Compression is enabled by default. Additional configurations are not required. Dell Technologies recommends using Citrix VDA version 1912CU3 or later.

112 Configuring connection brokers

HDX webcam video compression requires Multimedia conferencing and Windows Media Redirection policy settings to be enabled. The settings are enabled by default.

Ensure that Citrix_Workspace_App_21.9.0.25_6.pkg is installed. To use HDX RealTime Webcam Video Compression in the unified communication software in VDA, ensure that the following

conditions are met: For Skype for business application, ensure that the software is 32-bit and do not install the Citrix HDX RealTime

Connector in VDA. For ZoomVDI application, ensure that the software is 32-bit. Do not install Zoom_Citrix package in the thin client. Disable

Zoom VDI optimization using Admin Policy Tool or Wyse Management Suite policy settings, if you have installed Zoom package in thin client.

For Microsoft Teams application, ensure that the software is 32-bit. Disable Microsoft Teams VDI optimization in thin client using Admin Policy Tool or Wyse Management Suite policy settings.

For Webex meeting application, ensure that the software is 32-bit. Do not install Webex Meetings VDI package in thin client. Disable Webex Meetings VDI optimization using Admin Policy Tool or Wyse Management Suite policy settings, if you have installed Webex Meetings VDI package in thin client.

For Webex VDI application, ensure that the software is 32-bit. Do not install Webex VDI package in the thin client. Disable Webex VDI optimization using Admin Policy Tool or Wyse Management Suite policy settings, if you have installed Webex VDI package in thin client.

For Cisco Jabber application, ensure that the software is 32-bit. Do not install Cisco Jabber package in the thin client. Disable JVDI optimization using Admin Policy Tool or Wyse Management Suite policy settings, if you have installed Cisco Jabber package in thin client.

Configure camera for HDX RealTime Webcam Video Compression using Admin Policy Tool or Wyse Management Suite policy settings

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. On the Advanced tab, expand Peripheral Management, and click Camera.

3. Click Enable Camera to enable the camera.

By default, the option is enabled. If the option is disabled, the cameras on the thin clients are not shown.

4. Enable Optimize for CPU. By default the option is enabled. The default settings are format=RAW, resolution=320X240, and FPS=10. Disable the Optimize for CPU option to customize the camera format, resolution, and FPS settings. Ensure that the camera supports the custom values before continuing. Increasing the resolution and FPS impacts the performance.

5. Click Save & Publish.

HDX RealTime Webcam Video Compression for 64-bit apps

From ThinOS 2208 and Citrix Workspace App 2207, HDX RealTime Webcam Video Compression for 64-bit applications is supported. Webcam redirection works for 32-bit and 64-bit applications such as Skype or GoToMeeting. Use a 32-bit browser or 64-bit browser to verify the webcam redirection online. For example, use a 32-bit browser or 64-bit browser and go to www.webcamtests.com.

By default, ThinOS only supports webcam redirection feature for 32-bit apps. To enable webcam redirection feature for 64-bit apps, see Enable HDX RealTime Webcam Video Compression for 64-bit apps.

Enable HDX RealTime Webcam Video Compression for 64-bit apps

Steps

1. On Admin Policy Tool or the Wyse Management Suite policy settings, go to Advanced > VDI Configuration Editor > Citrix Configuration Editor.

2. Under Citrix INI Settings, click Add Row.

3. From the File drop-down list, select wfclient.ini.

4. From the Operation drop-down list, select Add or Update.

5. In the Section field, enter WFClient.

Configuring connection brokers 113

6. In the Key field, enter HDXH264InputEnabled.

7. In the Value field, enter True.

8. Sign out or restart the device for the settings to take effect.

Export Citrix Workspace App logs

From ThinOS 9.1.5xxx release onwards, Citrix Workspace App logs can only be exported from Troubleshooting > General > Export Logs.

Steps

1. From the desktop menu, click System Tools.

2. Click the Packages tab.

3. Select Citrix Workspace App, and click Advanced.

The Citrix Log Preferences window is displayed.

4. Right-click the classes that you require, and select Verbose.

5. Select the check boxes to select specific log items.

Click Set All Enabled to select all the check boxes.

6. Enter the file name and the output file pat in the Log Output Path field.

The default path is var/log/ICAClient.log. Dell Technologies recommends using the default log output path.

7. Click Apply Changes and close the Citrix Log Preferences window.

8. Connect the ICA session, reproduce the scenario that you require the log from, and disconnect the ICA session.

9. Connect a USB drive that is formatted with the FAT32 file allocation.

10. From the desktop menu, click Troubleshooting.

11. On the General tab, click Export Logs. Citrix Workspace app logs are exported to the USB drive.

Next steps

1. Reopen the Citrix Log Preferences window by performing the following steps: a. From the desktop menu, click System Tools. b. Click the Packages tab. c. Select Citrix Workspace App, and click Advanced.

The Citrix Log Preferences window is displayed.

2. Click both the Set All Default buttons. 3. Click the Load Default button. 4. Click Apply Changes.

The Citrix Workspace Log capture is disabled.

Configure multifarm

In ThinOS, multifarm works with only a Citrix Broker agent. You cannot use multifarm with other connection brokers.

Steps

1. Log in to the Wyse Management Suite server.

2. Go to the Groups & Configs page, and select your preferred group.

3. Click Edit Policies > ThinOS 9.x.

4. Click the Advanced tab.

5. Expand Broker Settings, and click Global Broker Settings.

6. Enable MultiFarm.

7. Click Save & Publish.

8. Check in the thin client to WMS group, and restart the thin client.

114 Configuring connection brokers

9. From the desktop menu, click System Setup, and then click Remote Connections.

10. Go to the Broker Setup tab, and enter the multi broker server in the Broker Server field.

For example, https://broker1,https://broker2 or https://broker1;https://broker2.

11. You can now log in to multi server with one user.

NOTE: If there is a server logon failure due to invalid credentials when you enable Multifarm and MultiDomain, the logon

continues. If there is no failure, logon exits immediately. You can switch between servers when you are logged in with

multiple servers using Citrix Workspace mode. To switch between servers, click the menu button at the upper-right

corner, and then click Accounts.

Configure multilogon

In ThinOS, multilogon works with only a Citrix Broker agent. You cannot use multilogon with other connection brokers.

Steps

1. Log in to the Wyse Management Suite server.

2. Go to the Groups & Configs page, and select your preferred group.

3. Click Edit Policies > ThinOS 9.x.

4. Click the Advanced tab.

5. Expand Broker Settings, and click Global Broker Settings.

6. Enable MultiLogon.

7. Click Save & Publish.

8. Check in the thin client to WMS group, and restart the thin client.

9. From the desktop menu, click System Setup, and then click Remote Connections.

10. Go to the Broker Setup tab, and enter the multi broker server in the Broker Server field.

For example, https://broker1,https://broker2 or https://broker1;https://broker2.

11. You can now log in to multi server with two different users.

NOTE: You can switch between servers when you are logged in with multiple servers using Citrix Workspace mode. To

switch between servers, click the menu button at the upper-right corner, and then click Accounts.

Virtual Display Layout

From ThinOS 2211 and Citrix Workspace App 2209, virtual display layout on VDA is supported. This section describes how to configure the virtual display layout on VDA.

Prerequisites

Single-session or multisession operating system VDA must be 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.

Steps

1. Right-click the graphics status indicator icon from the system tray and select Configure virtual displays. The virtual display configuration interface is launched.

2. Right-click a virtual display to mark it as the primary monitor.

3. 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.

4. 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.

Configuring connection brokers 115

Extended keyboard layouts

Japanese 106 keyboard, Portuguese ABNT/ABNT2 keyboards, and Multimedia keyboards are supported in Citrix VDI sessions from ThinOS 2211 and Citrix Workspace App 2209.

Prerequisites

To enable the extended keyboard layouts in Citrix VDI session, ensure that the Scancode keyboard input mode is configured. 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.

Steps

1. In Admin Policy Tool or Wyse Management Suite policy settings, go to Advanced > VDI Configuration Editor > Citrix Configuration Editor.

2. In Citrix INI Settings, click Add Row.

3. From the File drop-down list, select wfclient.ini.

4. From the Operation drop-down list, select Add or Update.

5. In the Section field, enter WFClient.

6. In the Key field, enter KeyboardEventMode.

7. In the Value field, enter Scancode.

8. Sign out or restart the device for the settings to take effect.

Configuring VMware VMware virtualization enables you to run multiple virtual machines on a single physical machine. VMware Horizon Client is a locally installed software application that communicates between View Connection Server and the thin client operating system. It provides access to centrally hosted virtual desktops from your thin clients.

In every ThinOS release, the VMware Horizon Client version may get updated to a newer version. You must upgrade the VMware Horizon package along with the ThinOS firmware. VMware Horizon package versions have a dependency on the ThinOS firmware versions. See the Release Notes of your ThinOS version at www.dell.com/support to know the corresponding VMware Horizon package version.

From ThinOS 2205, you can use touch screen gestures in both remote desktop and application sessions. Both full-screen mode and window mode support touch screen functionality. You can also use touch screen with the VMware Horizon Client user interface. Swiping down the screen, touch screen gestures, and multi-touch are not supported. If you enable relative mouse, the touch screen functionality may not work properly.

For information about the latest VMware Horizon Client version and the known issues, see the Release Notes of your ThinOS version at www.dell.com/support.

NOTE: If you are upgrading your thin client to the latest ThinOS version, you must ensure that the Horizon server or agent

version is updated to support the latest Horizon client version. For more information about the client and server/agent

version compatibility, see the VMware Product Interoperability Matrices page at www.vmware.com.

Configure the VMware broker connection

About this task

This section describes how to configure the VMware broker setup on your thin client.

Steps

1. From the desktop menu, click System Setup, and then click Remote Connections. The Remote Connections dialog box is displayed.

2. In the Broker Setup tab, select VMware Horizon from the Select Broker Type drop-down list, and do the following:

Broker ServerEnter the IP address/Hostname/FQDN of the broker server.

116 Configuring connection brokers

Auto Connect ListEnter the name of the desktops that you want to launch automatically after logging in to the respective broker. You can enter multiple desktop names. Each desktop name is separated by semicolon, and is case- sensitive.

Security modeSelect the preferred security mode from the following options: FullFull Security requires an FQDN address with a domain certificate. WarningWarn Security requires an FQDN address with a self-signed certificate, or without any certificate. But the

corresponding warning message is displayed for user to continue. LowSecurity allows an FQDN or IP address with or without a certificate.

Connection ProtocolFrom the drop-down list, select the type of protocol connection. By default, the option is set to Server Default.

NOTE: The PCoIP only connection protocol is applicable only to PCoIP clients. If you do not install the Teradici

PCoIP package, then the PCoIP protocol option is not available.

The available options are:

Server defaultSelect this protocol connection to display the desktop with default protocol as configured in the VMware View Admin console, for each pool in the broker. If a desktop pool is configured with default protocol as RDP in the View Admin console, then only the RDP connection of the desktop is displayed in ThinOS after users sign in to the device.

All SupportedSelect this protocol connection to display the desktop in all the available connections. This is applicable when a desktop pool is configured to allow users to select the protocol as yes. If the desktop is configured with default protocol as PCoIP and allow user to select protocol as no, then ThinOS only displays the desktop in the PCoIP connection.

RDP onlySelect this protocol connection to display the desktop in RDP connection only. If a desktop pool is configured with default protocol as PCoIP in the View Admin console, and allow users to select the protocol as no, then this desktop is not displayed in ThinOS after user signs in to the device.

PCoIP onlyThis option is available only for PCoIP enabled clients. Select this protocol connection to display only the desktop in the PCoIP connection, for each pool in the broker. If a desktop pool is configured with default protocol as RDP in the View Admin console, and allow user to select the protocol as no, then this desktop is not displayed in ThinOS after user signs in to the device.

Blast onlyVMware Blast display protocol can be used for remote applications and for remote desktops that use virtual machines or shared-session desktops on an RDS host. Select this protocol connection to display the desktop with the Blast protocol.

Log in anonymously using Unauthenticated AccessSelect this check box to anonymously log in to the VMware session with application remoting.

3. Click OK to save the settings.

VMware Real Time Audio-Video

About this task

Use the Real-Time Audio-Video feature to run Skype and other online conference applications on the remote desktop. Both audio and video devices that are connected to your thin client can be used for VoIP in a remote desktop. From ThinOS 2205, the Real-Time Audio-Video feature displays the actual names of redirected devices with (VDI) added to the name. For example, C670i FHD Webcam is displayed as C670i FHD Webcam (VDI). For audio playback, (VDI) is not added to the device name.

To know more about the VMware Real Time Audio-Video support, go to pubs.vmware.com.

NOTE: There is no additional configuration for ThinOS.

To validate the VMware Real Time Audio-Video, do the following:

Steps

1. Connect to the VMware PCoIP or Blast desktop with the audio and video devices.

NOTE: USB redirection must be disabled for the audio and video devices.

2. Verify the audio playback of the system using the VMware virtual audio.

3. Verify the system audio recording using the VMware virtual microphone.

4. Verify the audio settings in VoIP application.

5. Verify the video settings in VoIP application using the VMware virtual webcam.

Configuring connection brokers 117

6. Start the audio or video calls.

High Efficiency Video Coding

NOTE: OptiPlex 3000 Thin Client does not support HEVC.

In ThinOS 9.1.4234, VMware Blast Extreme supports High Efficiency Video Coding (HEVC). HEVC is also known as H.265 and it is the industry successor to H.264. Compared to H.264, H.265 provides 50% more compression by maintaining the same quality as H.264. This feature is disabled by default. HEVC in Blast Extreme requires both the ESXi hosts that support the virtual desktops, and RDSH servers to have NVIDIA Tesla or newer graphics cards to offload the encoding. HEVC does not work with only ESXi CPU encoding. If there are no supported graphics cards present, the H.264 or JPEG/PNG encoding is used.

NOTE: HEVC requires hardware support including the graphics card, on both the client and the agent side. If either the

client or the agent cannot support HEVC, the session falls back to H.264.

To enable this feature from the local user interface, select the Allow High Efficiency Video Decoding (HEVC) check box from Connection Manager > Global Connection Settings > Horizon. You can go to the VMware Horizon Performance tracker and see Encoder Name to verify whether HEVC is working. If you launch a session that has been launched from another device, the HEVC feature does not work. The server uses H.264 in this scenario. To use HEVC, sign off other sessions before connecting to the session from the ThinOS client.

NOTE: You must upgrade Wyse Management Suite to version 3.5 or later to support the HEVC feature.

For more information, see the VMware Blast Extreme Optimization Guide at techzone.vmware.com.

Enable or disable HEVC from Admin Policy Tool and Wyse Management Suite Policy settings

Steps

1. Go the Admin Policy Tool or Wyse Management Suite policy settings.

2. In the Advanced tab, expand Session Settings.

3. Click Blast Session Settings.

4. Click the Allow High Efficiency Video Decoding toggle to enable or disable HEVC.

5. Click Save & Publish.

Enable Scanner Redirection

Scanner Redirection feature enables you to scan information from VDI desktops using scanning and imaging devices that are connected to your thin client. Scanner Redirection supports standard scanning and imaging devices that are compatible with TWAIN, Windows Image Acquisition (WIA), and Scanner Access Now Easy (SANE) formats. The scanner redirection feature is applicable only for Blast sessions.

Prerequisites

Ensure that the Scanner Redirection feature is installed in the VMware Horizon session. You must select this feature in the VMware Horizon Agent wizard during the Horizon agent installation.

Steps

1. Log in to the ThinOS client.

2. From the system menu, click Admin Policy Tool.

3. In the Advanced tab, click Broker & Session, and expand VMware Horizon Settings.

4. Configure the following options based on your preference: If the Scanner Class ID starts with 06, click the Allow USB Imaging Family Device (Scanner) Redirection toggle

switch to enable the Scanner Redirection feature. If the Scanner Class ID does not start with 06, enter the Scanner VID and PID in the format vid-xxxx_pid-yyyy in

the Exclude Vid/Pid USB Device Redirection field.

5. Click Save & Publish.

118 Configuring connection brokers

6. Launch the Horizon View desktop on ThinOS.

7. Open the VMware Scanner Redirection menu from the Windows system tray. The available scanners are listed and can be selected based on your preference.

Enable Serial Port Redirection

Serial Port redirection feature enables you to redirect serial (COM) ports such as integrated RS232 ports or USB ports that are connected locally to serial-USB adapters. You can connect the serial devices to serial ports on your thin client and then use the serial devices in VDI desktops. The serial port redirection feature is applicable only for Blast sessions.

To use the Serial Port Redirection feature, you must install the feature in the VMware Horizon session. This feature is installed in the VMware Horizon Agent during the Horizon Agent installation. After the Serial Port Redirection feature is enabled in the VDI session, do the following:

1. Launch a Horizon View desktop on ThinOS. 2. Open the VMware Serial Port Redirection menu from the Windows system tray.

The available serial ports are listed and can be selected based on your preference. In Windows Device Manager, the serial port is displayed as Serial Port Redirection over VMware Horizon (COM1).

Enable Session Collaboration

Session Collaboration redirection feature enables you to invite other users to join your remote desktop session. The session collaboration feature is applicable only for Blast sessions.

NOTE: You cannot accept the invitation and join the remote desktop session of other users. This is a limitation on ThinOS.

By default, the session collaboration feature is enabled in the VMware session. To invite a user to join your desktop session, do the following:

1. Launch a Horizon View desktop on ThinOS. 2. Click the VMware Session Collaboration icon from the Windows system tray. 3. Enter the username or email address and click Send.

Enable Battery State Redirection

Battery State Redirection feature enables you to redirect the battery information of the ThinOS device to a remote desktop. To use the Battery State Redirection feature, you must ensure that the Enable Battery State Redirection Agent Policy Setting is enabled in Group Policy Management Editor. By default, this feature is enabled. The battery state redirection feature is applicable only for Blast sessions.

Relative mouse

When you enable the relative mouse feature, Horizon Client uses relative coordinates to transmit data about the mouse pointer movement and improve the mouse performance. The relative mouse feature is applicable for both PCoIP and Blast-enabled thin clients.

NOTE: The touch screen may not work when the relative mouse feature is enabled. This is a VMware limitation.

Enable relative mouse using Admin Policy Tool or Wyse Management Suite

Steps

1. On the ThinOS client, start Admin Policy Tool or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. On the Advanced tab, expand Session Settings, and click either Blast Session Settings or PCoIP Session Settings based on your preference.

3. Click the Enable Relative Mouse when launching session toggle key to enable the relative mouse feature.

4. Click Save & Publish.

Configuring connection brokers 119

NOTE: To disable the relative mouse feature, press Ctrl+ Alt key combination in a Blast session or press Ctrl +Alt+Down

key combination in a PCoIP session.

Enable relative mouse using session menu

Steps

1. On the ThinOS client, launch a PCoIP session or a Blast session.

2. In the system tray, click the PCoIP icon to view the active PCoIP sessions, or click the VMware icon to view the active Blast sessions.

3. Select a session from the menu.

4. Enable Relative Mouse.

NOTE: To disable the relative mouse feature, press Ctrl+ Alt key combination in a Blast session or press Ctrl +Alt+Down

key combination in a PCoIP session.

Configure Workspace ONE Mode

VMware Workspace ONE mode enables you to connect to remote desktops and applications through the Workspace ONE Web Portal. As a Horizon administrator, you can enable the Workspace ONE mode on a Connection Server instance. Horizon Client users are redirected to a Workspace ONE server to launch their remote desktops and applications.

Steps

1. Open the VMware Connection Server console.

2. Go to Settings > Servers > Connection Server and click the Authentication tab.

3. From the Delegation of authentication to VMware Horizon (SAML 2.0 Authentication) drop-down list, select Required.

4. Click Manage SAML Authenticators to add your Authenticator.

5. Select the Enable Workspace ONE mode check box.

6. Enter the Workspace ONE Server hostname and click OK.

7. Log in to the ThinOS client.

8. From the desktop menu, click System Setup, and then click Remote Connections. The Remote Connections dialog box is displayed.

9. In the Broker Setup tab, select VMware Horizon from the Select Broker Type drop-down list.

10. Enter the server URL in the Broker Server field.

11. Click OK and restart the thin client. The VMware Workspace ONE login window is displayed.

12. Enter the user credentials and click Sign In.

NOTE: The ThinOS lock terminal is not supported in Workspace ONE Mode. When you attempt to lock the terminal, a

warning message is displayed prompting for automatic sign-off. Click Continue if you want to sign out from the session.

NOTE: The Remember this setting option in Workspace ONE web portal is not supported due to the customized

browser limitation.

Unified Access Gateway

ThinOS supports Unified Access Gateway (UAG) that is used to securely access remote desktops and applications that are outside a corporate firewall. For information about the latest version of Unified Access Gateway, see Unified Access Gateway Documentation at docs.vmware.com.

VMware Horizon 7.11 with Unified Access Gateway 3.8 and later uses SAML-based multifactor authentication. It supports many modern cloud-based solutions including the Azure multifactor authentication.

120 Configuring connection brokers

Configure Unified Access Gateway on ThinOS

Prerequisites

Configure the Unified Access Gateway (UAG) setting on the server side. For more information about configuring the server-side settings for UAG, see the VMware Unified Access Gateway documentation at docs.vmware.com.

Open the connection server admin page, and specify the UAG information in the following sections: HTTP(s) Secure Tunnel PCoIP Secure Gateway Blast Secure Gateway

Steps

1. Start the ThinOS client.

2. From the desktop menu, click System Setup > Remote Connections. The Remote Connections dialog box is displayed.

3. On the Broker Setup tab, select VMware Horizon from the Select Broker Type drop-down list.

4. In the Broker Server field, enter the Unified Access Gateway URL.

5. Click OK.

Configure Microsoft Azure Multifactor authentication with VMware Unified Access Gateway

Prerequisites

Configure the Unified Access Gateway (UAG) settings and Azure Multifactor authentication settings on the server side. For more information about configuring the server-side settings, see the Microsoft Azure MFA with VMware UAG documentation at docs.vmware.com.

Steps

1. Start the ThinOS client.

2. From the desktop menu, click System Setup > Remote Connections. The Remote Connections dialog box is displayed.

3. On the Broker Setup tab, select VMware Horizon from the Select Broker Type drop-down list.

4. In the Broker Server field, enter the Unified Access Gateway FQDN.

5. Click OK.

6. On the Azure Sign In window, enter the Azure account.

7. Click Next.

8. Enter the password to log in to the session.

NOTE: ThinOS does not support Single Sign-On (SSO) to Azure MFA with VMware UAG.

Configure the VMware integrated printing settings

About this task

The VMware Integrated Printing feature allows you to print to a local or network printer without installing additional printer drivers in the remote desktop. The USB redirection feature enables you to print from a remote desktop using a USB printer that is connected to the local client device. For each printer configured locally on ThinOS, you must map the printer to the VMware Blast desktop. ThinOS Blast printer mapping is equivalent to VMware client printer redirection.

Currently ThinOS supports only PS printer in blast session since VMware has removed Thin print support from VMware Horizon 8.0 and VMware Horizon Client 2006. Ensure that the Agent version is later than 7.9, and that you select the component VMware Integrated Printing. Certain PS model printers may not work in Blast session as it depends on the VMware integration printing support.

To map your printer, do the following:

Configuring connection brokers 121

NOTE: LPT printer is considered as an example to explain the printer mapping scenario. Printer mapping in ThinOS works

similar to LPT for LPD and SMB printers.

Steps

1. Power on the ThinOS client with the VMware View broker configured in the Broker Setup tab.

2. Set the connection protocol as All Supported from the Connection Protocol drop-down list.

3. Go to Global Connection Settings > Session, and retain the Exclude printer devices check box selection. This option is selected by default.

4. Plug in a USB printer to the ThinOS client terminal.

5. Go to System Setup > Printer. The Printer Setup dialog box is displayed.

6. In the Printer Setup dialog box, do the following:

a. From the Select Port drop-down list, select LPT 1. b. Enter valid printer name and printer identification. c. Select the Enable the printer device check box. d. Click OK to save the configuration.

7. Click the Options tab, and do the following:

a. Set LPT1: as default printer. b. Click OK to save the configuration.

8. Connect to a VMware Blast session and go to Control Panel > Devices and Printers.

The printer that is configured locally in ThinOS is mapped to the session. The mapped printers driver is VMWARE POSTSCRIPT Driver and the port is VMWPORT.

The VMware Integrated Printing feature allows the ThinOS local printer to be mapped to the VMware Blast session without installing the printer driver in the session.

Configure the USB Printer Redirection in VMware Blast and PCoIP session

Steps

1. Connect a USB printer to the ThinOS client.

2. Go to Global Connection Settings > Session and clear the Exclude printer devices check box. This option is selected by default.

3. Log off from VMware Broker agent, and then log in again.

4. Log in to a Blast or a PCoIP session.

5. Go to Control Panel > Devices and Printer and verify if the printer driver is automatically installed. After the printer driver installation is complete, the redirected printer is listed in the Printers section.

NOTE: The drivers of certain printers may not get installed on the target Windows server automatically as the

installation depends on the Windows server. In such scenarios, the drivers must be installed manually.

USB Redirection in a VDI session

Upgrading to the ThinOS 9.1.3112 eliminates the local USB driver dependency on the USB redirection feature.

From ThinOS 9.1.3112 onwards, you can directly use the USB redirection feature in a VDI session without attaching the USB driver installed locally on your thin client. The local USB driver is automatically detached when using USB redirection in the VDI session. As a result, the USB redirection in the VDI session is fast and more reliable.

After upgrade, if you are configuring the USB settings on your local thin client, do either of the following: Using Global Connection Settings:

1. On the local ThinOS client, go to the Global Connection Settings > Session on local ThinOS UI. 2. Verify if the USB device redirection is selected, and click OK.

Using Admin Policy Tool: 1. On the Admin Policy Tool, go to Advanced > Session Settings > Global Session Settings > Local Resources and

USB redirection. 2. Ensure that the USB redirection option is enabled, and click Save and Publish.

122 Configuring connection brokers

Apply these setting changes when you are using the USB Redirection for the first time, after you upgrade from ThinOS 9.1.2X or older versions to 9.1.3112. The setting changes are not required after the first instance. If you are configuring the USB settings using Wyse Management Suite policy settings, you do not have to enable the USB redirection option again after upgrade.

There are no visible UI changes on the ThinOS client. However, the USB redirection speed is improved in the VDI session.

USB Redirection in a PCoIP session

For PCoIP session, ensure that the Group Policy is enabled to make the USB redirection work. Do the following to enable the GPO feature:

1. Open a PCoIP session and press WIN+R to open the Run window. 2. Enter gpedit.msc to open the Local Group Policy Editor. 3. Go to Computer Configuration > Administrative Templates > PCoIP Session Variables > Not Overridable

Administrator Settings, open Configure PCoIP USB allowed and unallowed device rules, select Enable, and click Apply.

NOTE: These steps are applicable to PCoIP session in VMware Horizon broker and Teradici Cloud Access broker. For

Teradici Remote Workstation Card and Amazon WorkSpace session, USB redirection is not supported by third party.

NOTE: Currently, the SDK integrated in ThinOS for PCoIP does not support the USB redirection feature for all USB drives.

This is a limitation from the third party SDK. For Headset and Camera, PCoIP does not support redirection in a session. Use

RTAV for audio and video devices.

Enable Multimedia Redirection in Blast session

Steps

1. Access the VMware Horizon connection server from the browser.

2. Go to Settings > Global Policy.

3. Change the Multimedia Redirection (MMR) drop-down value to Allow.

The default value is Deny.

4. Click OK.

NOTE: Multimedia Redirection (MMR) is enabled on ThinOS client side by default and there is no configuration item

to disable MMR from ThinOS client. To disable the MMR feature, select the value as Deny in the VMware Horizon

connection server. MMR feature uses Windows Media player as the default video player.

Smartphone sync

From ThinOS 9.1.4234, you can sync your iPhone or Android smartphone into a VMware Blast session.

NOTE: Among the Android smartphones, only Huawei and Samsung phones are tested.

Sync Huawei Android smartphone

Prerequisites

Download and install HiSuite in Blast session, from https://consumer.huawei.com/en/support/. Install HiSuite app on your Huawei smartphone.

Steps

1. Launch the Blast session.

2. Open HiSuite from the Blast session.

3. Connect your Huawei smartphone to the client.

4. Accept the access request on your phone.

A window that prompts you to enter a verification code from the phone, is displayed in the Blast session.

5. Open the HiSuite app on your phone and enter the verification code from the phone in the Blast session.

6. Click or tap Connect.

Configuring connection brokers 123

Sync Samsung Android smartphone and iPhone

Steps

1. Go the Admin Policy Tool or Wyse Management Suite policy settings.

2. In the Advanced tab, expand Session Settings.

3. Click Blast Session Settings.

4. Enable the Allow USB Imaging Family Device (Scanner) Redirection option.

5. Click Save & Publish.

6. Launch the Blast session and connect your Samsung smartphone or iPhone to the device.

7. Accept the access request on your Samsung smartphone or iPhone.

VMware Horizon Kiosk Mode

VMware Horizon VDI Broker agent can be connected to Kiosk Mode by entering the username as Client Mac.

Prerequisites

For information about Kiosk Mode authentication and configuration, go to docs.vmware.com.

Steps

1. From the desktop menu, click System Setup > Remote Connections.

The Remote Connections dialog box is displayed.

2. Click the General Options tab, and do the following:

a. Enter the username as Client Mac in the Default Sign-on Username field.

NOTE: Client Mac is hard code username, and it is case-sensitive.

b. Leave the Default Sign-on password field empty. c. Leave the Default Sign-on Domain field empty.

3. Click OK to save your settings.

NOTE: In earlier ThinOS versions, you must click the LOGIN button to log in to VMware Horizon Broker agent when

Kiosk Mode is configured in ThinOS. From ThinOS 2205, VMware Horizon logs in automatically if the Kiosk Mode

account Client Mac is configured as the ThinOS default user.

Special Peripheral Support

Bloomberg keyboard support

ThinOS 9.1.2101 supports Bloomberg Keyboard STB 100. The keyboard has two connection methods. One method uses a single USB cable to the USB port of the system. The second method is to connect dual USB cables to a KVM USB switch.

In a single USB cable connection, the keyboard device ID is vid-1188_pid-9545. All the six interfaces are under this device ID.

In the dual USB cable connection, the keyboard device IDs are vid-1188_pid-9525 for one device and vid-1188_pid-9535 for the other five devices.

Configure Bloomberg keyboard in Citrix sessions

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. On the Advanced tab, expand Peripheral Management, and click USB Redirection.

124 Configuring connection brokers

3. Click Add Row in the vUSB Force Redirect section: Redirect the entire keyboard into the sessionThe keyboard feature keys, fingerprint reader, and the KVM Keyboard are

redirected into the session. For Bloomberg keyboard that is connected with a single USB cable, add one row and enter the device ID. For

example, enter 0x11889545 to configure the device.

For Bloomberg keyboard that is connected with dual USB cables, add two rows and enter the device IDs. For example, enter 0x11889525 in one row and 0x11889535 in the other.

Split keyboard and partly redirect into the sessionYou can redirect the keyboard feature keys, fingerprint reader, or the KVM Keyboard individually. For Bloomberg keyboard that is connected with a single USB cable, add one row and enter the device ID. For

example, enter 0x11889545010100. This configuration means that the interface 010100 is redirected into session and other interfaces are not redirected.

For Bloomberg keyboard that is connected with dual USB cables, add one row and enter the device ID. For example, enter 0x11889545030001. This configuration means that the interface 030001 is redirected into session and other interfaces are not redirected.

4. Click Save & Publish.

Configure Bloomberg keyboard in PCoIP sessions

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. On the Advanced tab, expand Peripheral Management, and click USB Redirection.

3. Click Add Row in the vUSB Force Redirect section.

The Keyboard Feature keys, fingerprint reader, and the KVM Keyboard are redirected into the session.

For Bloomberg keyboard that is connected with a single USB cable, enter the device ID 0x11889545 to configure the device.

For Bloomberg keyboard that is connected with dual USB cables, add two rows in the vUSB Force Redirect section, enter 0x11889525 in one row and 0x11889535 in the other.

NOTE: PCoIP does not support USB device splitting.

4. Click Save & Publish.

Redirect Bloomberg keyboard in VMware Horizon Blast sessions

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. In the Advanced tab, click Broker Settings, and expand VMware Horizon Settings. Redirect the entire keyboard into the sessionThe keyboard feature keys, fingerprint reader, and the KVM Keyboard are

redirected into the session. For Bloomberg keyboard that is connected with a single USB cable, enter vid-1188_pid-9545 in the Include

Vid/Pid USB Device Redirection field. For Bloomberg keyboard that is connected with dual USB cables, enter

vid-1188_pid-9525;vid-1188_pid-9535 in the Include Vid/Pid USB Device Redirection field.

Split keyboard and partly redirect into the sessionYou can redirect the keyboard feature keys, fingerprint reader, or the KVM Keyboard individually. For Bloomberg keyboard that is connected with a single USB cable:

a. Enter vid-1188_pid-9545 in the Include Vid/Pid USB Device Redirection field.

b. Enable the Allow Auto USB Device Splitting Redirection button. c. Enter vid-1188_pid-9545(exintf:00;exintf:01;exintf:02) in the Split Vid/Pid Device field.

NOTE: This configuration means that the interfaces 03, 04, and 05 are redirected into session and the other

interfaces 00, 01, and 02 are not redirected. 03, 04, and 05 are audio related interfaces. The analog headset

from the audio port in Bloomberg keyboard can be redirected into the Blast session.

For Bloomberg keyboard that is connected with dual USB cables: a. Enter vid-1188_pid-9535 in the Include Vid/Pid USB Device Redirection field.

Configuring connection brokers 125

b. Enable the Allow Auto USB Device Splitting Redirection button. c. Enter vid-1188_pid-9535(exintf:00;exintf:01) in the Split Vid/Pid Device field.

NOTE: This configuration means that the interfaces 02, 03, and 04 are redirected into session and the other

interfaces 00 and 01 are not redirected. 02, 03, and 04 are audio related interfaces. The analog headset from

the audio port in Bloomberg keyboard can be redirected into the Blast session.

3. Click Save & Publish.

Mapping Bloomberg keyboard in VMware Blast sessions

You can connect the keyboard using either single or dual USB cables. No setting changes or redirection is required. All the function keys work without any redirection.

If you have set force redirection, see Remove Bloomberg keyboard force redirection settings for VMware Blast.

Remove Bloomberg keyboard force redirection settings for VMware Blast

Steps

1. Open the Admin Policy Tool on your thin client or go to the ThinOS 9.x policy settings on Wyse Management Suite.

2. Click the Advanced tab.

3. Expand Session Settings, and click Blast Session Settings.

4. Remove the following Bloomberg keyboard entries from the Include Vid/Pid USB Device Redirection field.

vid-1188_pid-9545 vid-1188_pid-9525 vid-1188_pid-9535

5. Click Save & Publish.

Bloomberg keyboard limitations

Hot plugging the Bloomberg keyboard is not supported for Bloomberg keyboard redirection. Configure the keyboard before logging in to the Broker agent and launching the session.

Disconnecting the Bloomberg keyboard cables when it is redirected into session may cause the session to close or the system to randomly reboot.

Confirm the USB interface redirection

This section contains the steps to confirm whether the USB audio device is redirected into the VDI session. You can confirm the USB redirection from the Device Manager, from the Audio Manager, or from the ThinOS Event Log.

Find the Vendor ID or Product ID of the connected device in ThinOS

This section contains the steps to find the Vendor ID (VID) or Product ID (PID) of your device in ThinOS.

Steps

1. Connect the USB device into the thin client.

2. Go to Settings > System Tools > Devices.

3. Expand USB Bus to find the name of your connected USB device.

4. Expand the name of the connected USB device to find the device Class, VID, PID, and the device interface. For example, if your connected USB device is Nuance PowerMic II-NS, the details are displayed as the following:

126 Configuring connection brokers

Figure 27. VID and PID

Device namePowerMicII-NS Device classclass_00 VIDVID_0554 PIDPID_1001 Device interfacefour interfaces belong to this device.

uaudio (Class_01 Subclass_01 Protocol_00) usb (Class_01 Subclass_02 Protocol_00) usb (Class_01 Subclass_02 Protocol_00) uhid (Class_03 Subclass_00 Protocol_00)

Confirm the USB interface redirection from Device Manager in ThinOS

Steps

1. Go to Settings > Peripherals.

The Peripherals dialog box is displayed.

2. Click the Audio tab.

Configuring connection brokers 127

3. Expand USB Bus to find the name of your connected USB device. If the USB redirection is successful, all the information under the USB device displays a usb prefix.

For example, if your connected USB device is Nuance PowerMic II-NS, the details are displayed as the following:

Figure 28. USB redirection

usb (Class_01 Subclass_01 Protocol_00) usb (Class_01 Subclass_02 Protocol_00) usb (Class_01 Subclass_02 Protocol_00) usb (Class_03 Subclass_00 Protocol_00)

Confirm the USB interface redirection from Audio Manager in ThinOS

Steps

1. Go to Settings > Peripherals.

The Peripherals dialog box is displayed.

2. Click the Audio tab. If the USB redirection is successful, the USB device is not displayed in drop-down lists under Playback Devices or Record Devices.

128 Configuring connection brokers

Confirm the USB interface redirection from ThinOS Event Log

Steps

1. Go to System Information > Event Log.

2. Verify the logs in the Event Log tab to confirm whether the USB redirection is successful.

For example, the thin client has only two audio devices HD audio-1 and PowerMicII-NS: If your logs display the following details, it means that the USB device is redirected into the VDI session and the ThinOS

playback and recording devices are changed to HD audio-1. Change playback to HD audio-1 Change record to HD audio-1

If your logs display the following details, it means that the USB device is released from the VDI session and the ThinOS playback and recording devices are reverted. Change playback to PowerMicII-NS Change record to PowerMicII-NS

Set playback or recording devices as default

To set the playback or recording devices as default, see Set default playback or recording devices.

Nuance PowerMic II-NS

The following are the device information of Nuance PowerMic II-NS.

Device IDClass 00, VID 0554, PID 1001 Device interface:

Audio or microphone interface010100 HID button interface030000 Mouse or track pad interfaces

Figure 29. Device interface

NuancePowerMic II-NS redirection in a Citrix session

Full USB redirection in a Citrix session

Except the mouse, all other interfaces are redirected to the VDI session.

Configuration in ThinOS

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, expand Peripheral Management, and click USB Redirection.

3. Click Add Row in the vUSB Force Redirect section, and enter the device ID 0x05541001.

4. Click Save & Publish.

Configuring connection brokers 129

Connecting Nuance PowerMic II-NS in a Citrix session

Launch Citrix session and connect Nuance PowerMic II-NS into the thin client.

Nuance PowerMic II-NS device is not displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Nuance PowerMic II-NS device is displayed in the Citrix session under Device Manager > Sound, video and game controllers.

Nuance PowerMic II-NS device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

In the Nuance Dragon Medical One desktop application, Nuance PowerMic II-NS is displayed in the Microphone drop-down list. All the HID buttons, voice recording, and audio playback features work in the Nuance Dragon Medical One desktop application.

HID buttons redirection in a Citrix session

Only the HID buttons are redirected into the VDI session. Other parts such as Audio or Microphone are kept in the ThinOS local device.

Configuration in ThinOS for HID buttons redirection only

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, go to Peripheral Management > VDI Configuration Editor > Citrix Configuration Editor.

3. In the Citrix INI Settings, click Add Row.

4. From the File drop-down list, select module.ini.

5. From the Operation drop-down list, select Add or Update.

6. In the Section field, enter ClientAudio.

7. In the Key field, enter AudioRedirectionV4.

8. In the Value field, enter True.

9. Go to Advanced tab, expand Peripheral Management, and click USB Redirection.

10. Click Add Row in the vUSB Force Redirect section, and enter the device ID 0x05541001030000.

11. Click Save & Publish.

Connecting Nuance PowerMic II-NS in a Citrix session with only HID buttons redirection

Launch Citrix session and connect Nuance PowerMic II-NS into the thin client.

Nuance PowerMic II-NS device is displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Nuance PowerMic II-NS device is displayed in the Citrix session under Device Manager > Sound, video and game controllers.

Nuance PowerMic II-NS device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

In the Nuance Dragon Medical One desktop application, Nuance PowerMic II-NS is displayed in the Microphone drop-down list. All the HID buttons, voice recording, and audio playback features work in the Nuance Dragon Medical One desktop application.

NOTE: The module.ini setting in Citrix is for the Citrix multi audio feature. If you do not add this setting, Nuance

PowerMic II-NS does not get displayed in Citrix sessions.

NuancePowerMic II-NS redirection in a VMware Blast session

Full USB redirection in a VMware Blast session

Except the mouse, all other interfaces are redirected to the VDI session.

130 Configuring connection brokers

Configuration in ThinOS

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, expand Session Settings, and click Blast Session Settings.

3. Enter vid-0554_pid-1001 in the Include Vid/Pid USB Device Redirection field.

4. Click Save & Publish.

Connecting Nuance PowerMic II-NS in a VMware Blast session

Launch the VMware Blast session and connect Nuance PowerMic II-NS into the thin client.

Nuance PowerMic II-NS device is not displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Nuance PowerMic II-NS device is displayed in the VMware Blast session under Device Manager > Sound, video and game controllers.

Nuance PowerMic II-NS device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

In the Nuance Dragon Medical One desktop application, Nuance PowerMic II-NS is displayed in the Microphone drop-down list. All the HID buttons, voice recording, and audio playback features work in the Nuance Dragon Medical One desktop application.

HID buttons redirection in a VMware Blast session

Only the HID buttons are redirected into the VDI session. Other parts such as Audio or Microphone are kept in the ThinOS local device.

Configuration in ThinOS for HID buttons redirection only

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, go to Session Settings > Blast Session Settings.

3. Enter vid-0554_pid-1001 in to the Include Vid/Pid USB Device Redirection field.

4. Enable Allow Auto USB Device Splitting Redirection.

5. Enter vid-0554_pid-1001(exintf:00;exintf:01;exintf:02) in to the Spit Vid/Pid Device field.

6. Click Save & Publish.

Connecting Nuance PowerMic II-NS in a VMware Blast session

Launch the VMware Blast session and connect Nuance PowerMic II-NS into the thin client.

Nuance PowerMic II-NS device is displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Nuance PowerMic II-NS device is not displayed in the VMware Blast session under Device Manager > Sound, video and game controllers. Only the VMware virtual microphone or audio is displayed.

Nuance PowerMic II-NS device cannot be set as the default device from the Playback or Recording tabs under Sound in Windows.

In the Nuance Dragon Medical One desktop application, Nuance PowerMic II-NS is not displayed in the Microphone drop-down list. However, all the HID buttons work in the Nuance Dragon Medical One desktop application. Voice recording works from both VMware Blast session and Peripherals > Audio > Recorder in the local ThinOS user interface. Audio works from both VMware blast session and ThinOS local user interface.

NOTE: The audio behaviors are different from Citrix sessions since VMware Blast session does not support multiple audio

devices.

Configuring connection brokers 131

Nuance PowerMic II-NS redirection in a PCoIP session

Full USB redirection in a PCoIP session

Except the mouse, all other interfaces are redirected to the VDI session.

Configuration in ThinOS

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, expand Peripheral Management, and click USB Redirection.

3. Click Add Row in vUSB Force Redirect section, and enter the device ID 0x05541001.

4. Click Save & Publish.

Connecting Nuance PowerMic II-NS in a PCoIP session

Launch the PCoIP session and connect Nuance PowerMic II-NS into the thin client.

Nuance PowerMic II-NS device is not displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Nuance PowerMic II-NS device is displayed in the PCoIP session under Device Manager > Sound, video and game controllers.

Nuance PowerMic II-NS device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

In the Nuance Dragon Medical One desktop application, Nuance PowerMic II-NS is displayed in the Microphone drop-down list. All the HID buttons, voice recording, and audio playback features work in the Nuance Dragon Medical One desktop application.

NOTE: PCoIP does not support USB interface splitting function. Hence, the feature to only redirect HID buttons is not

supported in a PCoIP session.

Olympus RecMic DR-2200

The following are the device information of Olympus RecMic DR-2200.

Model2200 Device IDClass 00,VID 07b4, PID 0254

Figure 30. Device information

132 Configuring connection brokers

Olympus RecMic DR-2200 redirection in a Citrix session

Full USB redirection in a Citrix session

Configuration in ThinOS

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, expand Peripheral Management, and click USB Redirection.

3. Click Add Row in the vUSB Force Redirect section, and enter the device ID 0x07b40254.

4. Click Save & Publish.

Connecting Olympus RecMic DR-2200 in a Citrix session

Launch Citrix session and connect Olympus RecMic DR-2200 into the thin client.

Olympus RecMic DR-2200 device is not displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Olympus RecMic DR-2200 device is displayed in the Citrix session under Device Manager > Sound, video and game controllers.

Olympus RecMic DR-2200 device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

All the control buttons work in the Olympus Device Configuration Manager application. Audio playback and audio recording works with Olympus RecMic DR-2200.

HID buttons redirection in a Citrix session

Only the HID buttons are redirected into the VDI session. Other parts such as Audio or Microphone are kept in the ThinOS local device.

Configuration in ThinOS for HID buttons redirection only

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, go to Peripheral Management > VDI Configuration Editor > Citrix Configuration Editor.

3. In the Citrix INI Settings, click Add Row.

4. From the File drop-down list, select module.ini.

5. From the Operation drop-down list, select Add or Update.

6. In the Section field, enter ClientAudio.

7. In the Key field, enter AudioRedirectionV4.

8. In the Value field, enter True.

9. Go to Advanced tab, expand Peripheral Management, and click USB Redirection.

10. Click Add Row in the vUSB Force Redirect section, and enter the device ID 0x07b40254030000.

11. Click Save & Publish.

Connecting Olympus RecMic DR-2200 in a Citrix session with only HID buttons redirection

Launch Citrix session and connect Olympus RecMic DR-2200 into the thin client.

Olympus RecMic DR-2200 device is displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Olympus RecMic DR-2200 device is displayed in the Citrix session under Device Manager > Sound, video and game controllers.

Olympus RecMic DR-2200 device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

Configuring connection brokers 133

All the control buttons work in the Olympus Device Configuration Manager application. Audio playback and audio recording works with Olympus RecMic DR-2200 in both ThinOS and Citrix sessions.

NOTE: The module.ini setting in Citrix is for the Citrix multi audio feature. If you do not add this setting, Olympus

RecMic DR-2200 does not get displayed in Citrix sessions. The recorder performance may not be clear on Windows Voice

Recorder application when the audio and recording is not redirected. Dell Technologies recommends using other third-party

voice recording applications.

Olympus RecMic DR-2200 redirection in a VMware Blast session

Full USB redirection in a VMware Blast session

Configuration in ThinOS

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, expand Session Settings, and click Blast Session Settings.

3. Enter vid-07b4_pid-0254 in the Include Vid/Pid USB Device Redirection field.

4. Click Save & Publish.

Connecting Olympus RecMic DR-2200 in a VMware Blast session

Launch the VMware Blast session and connect Olympus RecMic DR-2200 into the thin client.

Olympus RecMic DR-2200 device is not displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Olympus RecMic DR-2200 device is displayed in the VMware Blast session under Device Manager > Sound, video and game controllers.

Olympus RecMic DR-2200 device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

While using the Olympus Device Configuration Manager application, all the HID buttons work. Audio and voice recording features work using Olympus RecMic DR-2200.

HID buttons redirection in a VMware Blast session

Only the HID buttons are redirected into the VDI session. Other parts such as Audio or Microphone are kept in the ThinOS local device.

Configuration in ThinOS for HID buttons redirection only

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, go to Session Settings > Blast Session Settings.

3. Enter vid-07b4_pid-0254 in to the Include Vid/Pid USB Device Redirection field.

4. Enable Allow Auto USB Device Splitting Redirection.

5. Enter vid-07b4_pid-0254 (exintf:01;exintf:02;exintf:03;exintf:04 in to the Spit Vid/Pid Device field.

6. Click Save & Publish.

Connecting Olympus RecMic DR-2200 in a VMware Blast session

Launch the VMware Blast session and connect Olympus RecMic DR-2200 into the thin client.

Olympus RecMic DR-2200 device is displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Olympus RecMic DR-2200 device is not displayed in the VMware Blast session under Device Manager > Sound, video and game controllers. Only the VMware virtual microphone or audio is displayed.

134 Configuring connection brokers

Olympus RecMic DR-2200 device cannot be set as the default device from the Playback or Recording tabs under Sound in Windows.

While using the Olympus Device Configuration Manager application, all the HID buttons work. Audio can be recorded from a VMware Blast session and ThinOS local user interface. Audio playback works in both VMware Blast session and ThinOS local user interface.

NOTE: The audio behaviors are different from Citrix sessions since VMware Blast session does not support multiple audio

devices.

Olympus RecMic DR-2200 redirection in a PCoIP session

Full USB redirection in a PCoIP session

Configuration in ThinOS

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, expand Peripheral Management, and click USB Redirection.

3. Click Add Row in vUSB Force Redirect section, and enter the device ID 0x07b40254.

4. Click Save & Publish.

Connecting Olympus RecMic DR-2200 in a PCoIP session

Launch the PCoIP session and connect Olympus RecMic DR-2200 into the thin client.

Olympus RecMic DR-2200 device is not displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Olympus RecMic DR-2200 device is displayed in the PCoIP session under Device Manager > Sound, video and game controllers.

Olympus RecMic DR-2200 device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

While using the Olympus Device Configuration Manager application, all the HID buttons work. Audio and voice recording features work using Olympus RecMic DR-2200.

NOTE: PCoIP does not support USB interface splitting function. Hence, the feature to only redirect HID buttons is not

supported in a PCoIP session.

Philips SpeechMike III

The following are the device information of PHILIPS SpeechMike III.

ModelSpeechMike III Device IDClass 00, VID 0911, PID 0c1c

Figure 31. Device information

Configuring connection brokers 135

Philips SpeechMike III redirection in a Citrix session

Full USB redirection in a Citrix session

Configuration in ThinOS

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, expand Peripheral Management, and click USB Redirection.

3. Click Add Row in the vUSB Force Redirect section, and enter the device ID 0x09110c1c.

4. Click Save & Publish.

Connecting Philips SpeechMike III in a Citrix session

Launch Citrix session and connect Philips SpeechMike III into the thin client.

Philips SpeechMike III device is not displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Philips SpeechMike III device is displayed in the Citrix session under Device Manager > Sound, video and game controllers.

Philips SpeechMike III device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

All the control buttons work in the Philips Device Control Center application. Audio playback and audio recording works with Philips SpeechMike III.

HID buttons redirection in a Citrix session

Only the HID buttons are redirected into the VDI session. Other parts such as Audio or Microphone are kept in the ThinOS local device.

Configuration in ThinOS for HID buttons redirection only

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, go to Peripheral Management > VDI Configuration Editor > Citrix Configuration Editor.

3. In the Citrix INI Settings, click Add Row.

4. From the File drop-down list, select module.ini.

5. From the Operation drop-down list, select Add or Update.

6. In the Section field, enter ClientAudio.

7. In the Key field, enter AudioRedirectionV4.

8. In the Value field, enter True.

9. Go to Advanced tab, expand Peripheral Management, and click USB Redirection.

10. Click Add Row in the vUSB Force Redirect section, and enter the device ID 0x09110c1c030000.

11. Click Save & Publish.

Connecting Philips SpeechMike III in a Citrix session with only HID buttons redirection

Launch Citrix session and connect Philips SpeechMike III into the thin client.

Philips SpeechMike III device is displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Philips SpeechMike III device is displayed in the Citrix session under Device Manager > Sound, video and game controllers.

Philips SpeechMike III device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

136 Configuring connection brokers

All the control buttons work in the Philips Device Control Center application. Audio playback and audio recording works with Philips SpeechMike III in both ThinOS and Citrix sessions.

NOTE: The module.ini setting in Citrix is for the Citrix multi audio feature. If you do not add this setting, Philips

SpeechMike III does not get displayed in Citrix sessions. The recorder performance may not be clear on Windows Voice

Recorder application when the audio and recording is not redirected. Dell Technologies recommends using other third-party

voice recording applications.

Philips SpeechMike III redirection in a VMware Blast session

Full USB redirection in a VMware Blast session

Configuration in ThinOS

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, expand Session Settings, and click Blast Session Settings.

3. Enter vid-0911_pid-0c1c in the Include Vid/Pid USB Device Redirection field.

4. Click Save & Publish.

Connecting Philips SpeechMike III in a VMware Blast session

Launch the VMware Blast session and connect Philips SpeechMike III into the thin client.

Philips SpeechMike III device is not displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Philips SpeechMike III device is displayed in the VMware Blast session under Device Manager > Sound, video and game controllers.

Philips SpeechMike III device can be set as the default device from the Playback or Recording tabs under Sound in Windows.

While using the Philips Device Control Center application, all the HID buttons work. Audio and voice recording features work using Philips SpeechMike III.

HID buttons redirection in a VMware Blast session

Only the HID buttons are redirected into the VDI session. Other parts such as Audio or Microphone are kept in the ThinOS local device.

Configuration in ThinOS for HID buttons redirection only

Steps

1. On the ThinOS client, open Admin Policy Tool or go to the Wyse Management Suite policy settings.

2. On the Advanced tab, go to Session Settings > Blast Session Settings.

3. Enter vid-0911_pid-0c1c in to the Include Vid/Pid USB Device Redirection field.

4. Enable Allow Auto USB Device Splitting Redirection.

5. Enter vid-0911_pid-0c1c (exintf:00;exintf:01;exintf:02) in to the Spit Vid/Pid Device field.

6. Click Save & Publish.

Connecting Philips SpeechMike III in a VMware Blast session

Launch the VMware Blast session and connect Philips SpeechMike III into the thin client.

Philips SpeechMike III device is displayed in the ThinOS local audio device list under System Settings > Peripherals > Audio.

Philips SpeechMike III device is not displayed in the VMware Blast session under Device Manager > Sound, video and game controllers. Only the VMware virtual microphone or audio is displayed.

Configuring connection brokers 137