Administrator Guide
Table Of Contents
- Dell Wyse ThinOS Version 8.6 Administrator’s Guide
- Introduction
- Before working on ThinOS
- Getting started
- End User License Agreement
- Configuring ThinOS using the First Boot Wizard
- Connecting to a remote server
- Using your desktop
- Configuring thin client settings and connection settings
- Connecting to a printer
- Connecting to a monitor
- Locking the thin client
- Signing off and shutting down
- Battery information
- Sleep mode
- Additional getting started details
- Classic desktop features
- Login dialog box features
- Word wrap feature
- Accessing system information
- ENERGY STAR compliance
- IPv6 certification
- Global Connection settings
- Configuring connectivity
- Configuring the network settings
- Configuring the remote connections
- Configuring the central configurations
- Configuring the VPN Manager
- Configuring the connection brokers
- Configuring Citrix
- Configuring the Citrix broker connection
- Citrix Receiver feature matrix
- Citrix HDX RealTime Multimedia Engine or RealTime Optimization Pack
- Cisco Jabber Softphone for VDI
- Using Citrix ADC
- Citrix Cloud services
- Citrix icon refresh
- Using multiple audio in Citrix session
- Configuring ICA connections
- Support for multi-monitors in Citrix session
- ICA Self Service Password Reset
- QUMU or ICA Multimedia URL Redirection
- HTML5 Video Redirection
- ICA SuperCodec
- Anonymous logon
- Configuring the Citrix UPD printer
- Configuring VMware
- Configuring the VMware broker connection
- VMware Horizon Client feature matrix
- Using VMware Horizon View broker and desktop
- Enable username hint for smart card login
- Supporting VMware Real Time Audio-Video
- VMware Blast
- VMware Horizon Virtualization Pack for Skype for Business
- Using multi-monitors in PCoIP session
- Using Multi-monitors in VMware Blast session
- Blast Virtual Printing
- Enable hardware cursor in Blast session
- Enable relative mouse feature
- USB device splitting in Blast session
- Supporting Teradici SDK
- Configuring PCoIP connections using Teradici Remote Workstation card
- Customize PCoIP login window and icons
- Configuring Microsoft Remote Desktop
- Configuring Dell vWorkspace
- Configuring Amazon Web Services or WorkSpaces
- Configuring Teradici Cloud Access
- Configuring Citrix
- Configuring local settings
- Local Settings Menu
- Configuring the system preferences
- Configuring the display settings
- Configuring the peripherals settings
- Configuring the keyboard settings
- Configuring the mouse settings
- Configuring the audio settings
- Configuring the serial settings
- Configuring the camera settings
- Configuring the touch screen settings
- Configure the touch screen settings for VDI sessions
- Configuring the Bluetooth settings
- USB support
- Support for USB Type-C
- Configuring the printer settings
- Reset features
- Local Settings Menu
- TCX Suite
- Trusted Platform Module version 2.0
- Performing diagnostics
- BIOS management on ThinOS
- Security
- Troubleshooting
- Examples of common printing configurations
- Important notes
- Frequently asked questions
If the Optimized mode icon is not displayed, the Virtualization Pack is running in Fallback mode. This is because of the version
mismatch between the Horizon Client on the thin client and the Horizon Agent on virtual desktop.
For information about compatibility of Horizon Virtualization Pack for SFB components, see the Horizon Client 4.8 or later and
Agent 7.5 or later Virtualization Pack for Skype for Business is not compatible with older Client and Agent releases article at
kb.vmware.com.
Change Optimized mode to Fallback mode
To change the Optimized mode to Fallback mode, or to disable the Virtualization pack for Skype for Business on the Horizon
desktop, do the following:
1. On the VMware Horizon desktop, open the Windows Registry Editor.
2. Rename the registry keys based on the following deployment scenarios:
Table 22. Registry keys
Deployment scenario Registry key
View Desktops (64-bit) with Skype for Business (64-bit) Rename HKLM/Software/Microsoft/Office/Lync/
VdiMediaProvider to HKLM/Software/Microsoft/
Office/Lync/VdiMediaProviderDisabled.
View Desktops (64-bit) with Skype for Business (32-bit) Rename HKLM/Software/Wow6432Node/
Microsoft/Office/Lync/VdiMediaProvider
to HKLM/Software/Wow6432Node/Microsoft/
Office/Lync/VdiMediaProviderDisabled.
View Desktops (32-bit) with Skype for Business (32-bit) Rename HKLM/Software/Microsoft/Office/Lync/
VdiMediaProvider to HKLM/Software/Microsoft/
Office/Lync/VdiMediaProviderDisabled.
3. Close the Windows Registry Editor.
4. Restart Skype for Business.
Skype for Business is set to Fallback mode, and Real-Time Audio-Video (RTAV) is used for SFB calls.
Using multi-monitors in PCoIP session
This section is applicable to Wyse 5070 thin client. ThinOS supports multiple-monitor display to run virtual machines on each
monitor.
User scenario:
1. Connect multiple monitors to the ThinOS device.
2. In the Display Setup dialog box, disable Mirror Mode, and configure the display layout.
3. Launch a full screen PCoIP session.
● Display numbers—A virtual machine needs sufficient video memory to support three or four monitors. The default video
memory on VMware vSphere supports only two monitors.
○ Supports one session up to four monitors in span mode with resolution up to 2560 x 1600.
○ Supports one session up to two monitors in span mode with resolution up to 3840 x 2160.
The maximum number of monitors that can be stacked vertically is two. If you use more than two monitors, the monitors
must be in the same mode and have the same screen resolution. For instance, if you use three monitors, all three monitors
must be either in portrait mode or landscape mode, and must use the same screen resolution.
● Display layout—The display layout of the monitors must be aligned up and down, or left and right. Improper alignment
results in unusual display.
● 3D rendering—You can configure 3D graphics rendering for connected desktops. To use the 3D rendering feature, use up
to two monitors with resolution up to 1920 x 1200.
Table 23. Matrix for multi screen support
Configuring the connection brokers 133