Dell Wyse ThinOS Version 8.6 Administrator’s Guide December 2020 Rev.
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. © 2018 — 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Introduction................................................................................................................. 7 About this guide................................................................................................................................................................7 Technical support...........................................................................................................................................................
Additional getting started details...........................................................................................................................34 Zero desktop features............................................................................................................................................34 Zero interactive desktop guidelines........................................................................................................................ 34 Zero toolbar.................
QUMU or ICA Multimedia URL Redirection.......................................................................................................... 111 HTML5 Video Redirection........................................................................................................................................ 112 ICA SuperCodec..........................................................................................................................................................112 Anonymous logon............
System tools......................................................................................................................................................................187 Simplified Certificate Enrollment Protocol.......................................................................................................... 190 About Default Certificates.......................................................................................................................................
1 Introduction Thin clients running Dell Wyse ThinOS firmware are designed solely for optimal thin client security and performance. These efficient purpose-built thin clients are virus and malware resistant and offer ultrafast access to applications, files and network resources within Citrix, Microsoft, VMware and Dell vWorkspace environments, and other leading infrastructures.
What is new in ThinOS 8.6_511 The following are the new features or updates to the existing features in this release: ● Added a security message for connection brokers and third party authentication applications. For more information, see Configuring the broker setup. ● Added security option for Microsoft broker connection with a security pop-up window for RDSH environments. For more information, see Configuring Microsoft Remote Desktop. ● Added new default certificates.
● Ability to limit core dumps by clearing Non-Volatile Random Access Memory (NVRAM). See, the Dell Wyse ThinOS 8.6 INI guide at www.dell.com.support. NOTE: Support for Wyse 3010 Thin Client has been depreciated since it is end of software support. There are no updates for Flash Redirection (FR) and TCX packages from this release onwards. What is new in ThinOS 8.
● ThinOS enhancements ○ Supports the Omnikey 5321v2 device. See, Smart cards and smart card readers. ○ Supports Rutoken smart cards. See, Rutoken smart card reader ○ Added the option to disable on-board serial ports using INI parameters. See, Configuring the serial settings. ○ Improved the security for CA validation on Wyse Management Suite. See, Configuring the Wyse Device Agent settings. ● INI parameter updates: Added new INI parameters. See, Dell Wyse ThinOS Version 8.6 INI Reference Guide at www.dell.
○ Added the sleep mode feature that enables the power-saving state and quickly resumes full power operations without loss of data. This feature is supported on Wyse 5040 All-in-One client and Wyse 5040 All-in-One client with PCoIP. See, Sleep mode. ○ Supports the VMware Blast Virtual channel on Imprivata Biometrics and Proximity devices. See, Imprivata Bio-metric Single Sign-On. ○ Supports User Datagram Protocol (UDP) through TS Gateway connections. See, Connect to RDP session using UDP with TS Gateway.
2 Before working on ThinOS This section contains information about firmware upgrade and system configuration that you need to know before using ThinOS version 8.6. Firmware upgrade and package deployment Consider the following before you upgrade the ThinOS firmware and deploy the ThinOS packages: ● On Wyse 5070 Extended thin client, the AMD firmware is upgraded to a newer version. If you want to downgrade ThinOS from 8.6 to 8.5.1, you must shut down and boot the thin client again.
Table 2. Package information (continued) Package name Details Pcoip.i386.pkg Automatically updated upon firmware upgrade of a PCoIP client. RTME.i386.pkg Upload the new package to central configuration, and system can update without INI configuration. Horizon.i386.pkg Upload the new package to central configuration, and configure the INI parameter to update this package. JVDI.i386.pkg Upload the new package to central configuration, and configure the INI parameter to update this package.
The option AddPkg is for adding packages. It depends on the value of LoadPkg. For more information about the INI parameter usage, see Dell Wyse ThinOS INI Reference Guide. 5. Save the wnos.ini file. 6. On the ThinOS client desktop, navigate to System Setup > Central Configuration > General. 7. In the General tab, enter the IP address of the file server or directory. For example: https://IPaddress/wyse.
BIOS upgrade BIOS upgrade is the process of updating your existing BIOS version to the latest version. Table 3. BIOS binary files Platform BIOS binary filename Wyse 3040 thin client A10Q_bios.bin Wyse 3040 thin client with PCoIP A10Q_bios.bin Wyse 5010 thin client D10G_bios.bin Wyse 5010 thin client with PCoIP PD10G_bios.bin Wyse 5040 AIO thin client AIO10G_bios.bin Wyse 5040 AIO thin client with PCoIP PAIO10G_bios.bin Wyse 5060 thin client D10Q_bios.
The Select ThinOS Configuration Mode window is displayed. 14. Click Advanced Configuration. 15. In the Device Configuration section, click Firmware Upgrade. 16. Select the Enable BIOS Upgrade check box. 17. Select one or more BIOS files. NOTE: ● When deploying a group policy, you can select multiple BIOS files. However, the policy must reject any duplicate platforms.
Upgrading BIOS on Wyse 5070 thin client This section describes the procedure to update BIOS on Wyse 5070 thin client with ThinOS, and Wyse 5070 thin client with PCoIP by using file server. The Dell Standard BIOS file is converted to BIN file format for signature and security purposes. The format of the BIN file is Wyse_5070_version.bin. To upgrade BIOS using the file server: 1. Download the Dell BIOS file from the Dell support site. For example, Wyse_5070_1.0.3.bin.
Upgrade BIOS on the Wyse 5470 All-in-One Thin Client This section describes the procedure to update BIOS on the Wyse 5470 All-in-One Thin Client by using file server. The Dell Standard BIOS file is converted to BIN file format for signature and security purposes. The format of the BIN file is 5470AIO_bios.bin for the Wyse 5470 All-in-One Thin Client. To upgrade BIOS using the file server: 1. Download the Dell BIOS file from the respective hardware pages on Dell support site. For example, 5470AIO_bios.bin.
How to set up fingerprint using Wyse Device Manager To set up your fingerprint using WDM, do the following: 1. Export the WDM server certificate from the WDM server that you want to access. 2. Extract the fingerprint value from the WDM certificate in the required format. You must use a system with OpenSSL installed. OpenSSL can be used to extract the fingerprint in required format from the WDM certificate itself.
Using DHCP options This table contains the DHCP options available for use. Table 4. DHCP options Option Description Notes 1 Subnet Mask Required. However, it is not required unless the thin client must interact with servers on a different subnet. MS DHCP requires a subnet mask and is always send one. 2 Time Offset Optional. 3 Router Optional, but recommended. It is not required unless the thin client must interact with servers on a different subnet.
Table 4. DHCP options (continued) Option Description Notes NOTE: You can have the \wyse automatic component of the search path omitted by appending a dollar sign ($) to the entered path. For example, if you enter pub \serversoftware$, the path searched will be pub \serversoftware\wnos. NOTE: The usage or omission of a leading slash (\) on the path is critical on some servers. Some servers limit access to the root path of the user specified at login.
Table 4. DHCP options (continued) Option Description Notes against a domain not in the list, the user has the option of not using any of the domains specified in option 182 and typing a different domain name at the time of login. 184 File server Username Optional string. Username to use when authenticating to the server specified in Option 161. 185 File server Password Optional string. Password to use when authenticating to the server specified in Option 161.
Table 4. DHCP options (continued) Option Description Notes 199 Wyse Management Suite Group Key Optional string. Can provide 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.
3 Getting started This chapter helps you quickly learn the basics and get started with your thin client. End User License Agreement End User License Agreement is added to ThinOS from this release. End User License Agreements must be read and accepted to continue using ThinOS. The End User License Agreement 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 version 8.5 or later, to factory settings.
Figure 1. Dell EULA Figure 2. Cisco EULA 3. Select Dell EULA and Cisco EULA from the right pane to read both the End User License Agreements. NOTE: Cisco End user Agreement is displayed only if you have the JVDI package installed. 4. Accept each End User License Agreement by clicking I Accept . The thin client validates the IP address from DHCP.
NOTE: To exit the First Boot Wizard during the network connection status check on the welcome screen, press the Ctrl + Esc key. 5. On the Would you like to load a ThinOS configuration file from USB? screen, do either of the following: ● To load a ThinOS configuration file from the USB drive, ensure that you create a wnos.ini file and add the file to the / wnos directory on the USB drive. Using this option, you can load packages, and wallpapers that are specified in the INI file.
● ● ● ● ● Locale—Select a language to start ThinOS in the regional specific language. Keyboard Layout—Select a keyboard layout to set the keyboard layout in the regional specific language. Time Zone—Select a time zone to set the time zone for your thin client. Time Server—Displays the IP addresses or host names with optional port number of time servers. Advanced—Click Advanced to configure settings, such as daylight saving, time format, date format, and time servers.
○ To exit the Attach the Ethernet cable screen, and load the ThinOS system desktop, click Exit. After the connection is established, the thin client validates the IP address from DHCP. If the DHCP contains the file server or the Wyse Device Manager or Wyse Management Suite configurations, then the ThinOS system desktop is loaded. If the DHCP validation fails, or the network connection fails, then the Management Configuration screen is displayed. Follow steps 6–9. 7.
● Citrix—The broker allows you to connect to full desktops using Citrix Virtual Apps and Desktops (formerly Citrix XenDesktop) or individual applications using Citrix Virtual Apps (formerly Citrix XenApp) from a centralized host through Citrix Receiver Client. ○ Server Address—Enter the host name or IP address of the broker connection. ○ Enable theme: ThinOS Lite—Select this check box to boot the thin client in ThinOS Lite mode.
If you must initially connect to central configuration through wireless, use the Wireless tab in the Network Setup dialog box to enter the SSID and encryption configurations required or set up by the network administrator. For more information, see Configuring the Network Settings.
NOTE: User Name is the user who is logged-on and is located at the lower-left pane of the taskbar ● Zero Desktop — Click the System Settings icon on the Zero Toolbar, and then select Remote Connections.
Battery information This section is applicable to the Wyse 5470 Thin Client. The battery indicator is displayed on the system tray in the classic mode. The battery indicator is displayed on the zero toolbar in the zero mode. The following table contains the battery indicators: Table 5.
● ● ● ● ● ● ● ● ● ● Performance Monitor Troubleshooting System Information System Tools VPN Manager Central Configuration System Preferences Display Printer Set Up Remote Connections NOTE: You are logged off from the ThinOS VDI broker and sessions in sleep mode. You must log in to broker sessions again after resuming from sleep mode. ● Network Set Up NOTE: Peripherals windows are closed in sleep mode to reinitialize any peripheral devices after resuming from sleep mode.
● Press any key on the USB keyboard. NOTE: By default, this feature is disabled. To enable the feature: ○ On the Wyse 5470 Thin Client, connect the AC adapter to the thin client, and use INI parameter wakeonusb=yes. ○ On the Wyse 5470 All-in-One Thin Client, use the INI parameter wakeonusb=yes. ● Press any key on the integrated keyboard. This option is applicable only to the Wyse 5470 Thin Client. ● Use the Wake on LAN feature to wake up from the sleep mode.
Table 6. Zero Desktop shortcuts (continued) Action Press Capture the full desktop to the clipboard Print Screen Capture the active window to the clipboard Alt+PrintScreen NOTE: ● You can copy and paste between application sessions and between sessions and the desktop, however, this function depends on session server configurations. ● In addition to the standard two-button mouse, the thin client supports a Microsoft Wheel Mouse used for scrolling.
Table 8. Connection options (continued) Option What It Does NOTE: It is useful when a connection is not functioning properly or you need to reboot the connection. Close icon Closes the connection. NOTE: The Close icon is grayed out for connections that are not open. Edit icon Opens the Connection Settings dialog box to change the connection options. NOTE: Depending on user privilege level, editing options may not be available for use. Add Connection Allows you to configure or add new connections.
● A network icon is added to the taskbar on the classic ThinOS desktop. The network icon is displayed irrespective of whether the Ethernet cable is connected to the thin client. Clicking the network icon displays the Network Setup window that can be used to configure your network settings. Figure 3. Taskbar NOTE: ● User Name is the user who is logged-on and is located at the lower-left pane of the task bar.
d. Troubleshooting options—Displays Performance Monitor graphs that display client CPU, Memory and Networking information, Trace and Event log settings, CMOS management extract and restore settings, and other options that are useful for ThinOS troubleshooting. e. Applications—Contains a submenu of all locally configured applications and is populated with published applications when a user is signed on using either PNLite or PNAgent. f.
○ Classic desktop—Use the Leave Administrator Mode option in the Shutdown dialog box. ○ Zero desktop—Use the Leave Administrator Mode option in the Shutdown dialog box, or use the Leave Administrator Mode icon (X) in the upper-right pane of the System Settings menu. NOTE: By default the Admin Mode button is not displayed on the log on dialog box. You can display it by selecting the Show local admin button check box in the Shutdown dialog box.
● ENET tab—Displays information about wired network connections. ● WLAN tab—Displays information about wireless network connections. ● About tab—Displays information about the ThinOS operating system. The following attributes are listed: ○ Platform name ○ Operating system type ○ ThinOS build name ○ ThinOS build version ○ BIOS name ○ BIOS version ○ Citrix Broker or Receiver version—This represents ICA revisions between the ThinOS versions.
4 Global Connection settings Use the Global Connection Settings dialog box to configure the connection settings such as ICA, RDP, Horizon, and PCoIP. ● Zero desktop—Click Global Connection Settings in the list of connections. ● Classic desktop—Click Global Connection Settings in Connect Manager. To configure the Global Connection settings: 1. On the desktop taskbar, click Connect Manager > Global Connection Settings. The Global Connection Settings dialog box is displayed. 2.
● Blast H.264 feature is not supported on Wyse 5010 thin clients, Wyse 5040 thin clients, and Wyse 7010 thin clients. Blast H.264 is automatically disabled on Wyse 5060 thin client for 1920 x 1200 resolution due to hardware limitation. ● A performance tracker is introduced by VMware for performance evaluation and data collection. b. From the Network Condition drop-down list, select whether to use a condition for your Blast connection.
5 Configuring connectivity This chapter helps you to understand various configuration settings for a secure connection. To configure the settings on Classic desktop, click System Setup from the desktop menu, and use the configuration tabs. To configure the settings on Zero desktop, click the System Settings icon on the zero toolbar, and then use the configuration tabs. Configuring the network settings Use the network options to configure the network based on your requirement.
○ ENET1—Enables you to set up the second Ethernet Wired Network connection using the Ethernet port on the docking station. Figure 5. General settings with ENET0 and ENET1 ● To set the default gateway on the Wyse 5470 Thin Client with the Dell Docking Station WD19, select the type of network interface from the following options: ○ ENET0— Enables you to set up the first Ethernet Wired Network connection using the onboard Ethernet port.
Figure 6. General settings with ENET0, ENET1, and WLAN ThinOS supports the following network combinations on the Wyse 5470 Thin Client: ● Onboard Ethernet port + Ethernet port on the docking station ● Onboard Ethernet port + Wireless ● Ethernet port on the docking station + Wireless NOTE: You do not need to reboot the system when you connect or disconnect the Dell WD 19 docking station for the network to work. You can connect your thin client to two wired network connections at the same time.
i. Enter the URL address of the DNS Domain in the DNS Domain box. ii. Enter the IP address of the DNS Server in the DNS Server box. Use of DNS is optional. DNS allows 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. Enter the DNS Domain and the network address of an available DNS Server.
a. DHCP Option IDs — Enter the supported DHCP options. Each value can only be used once and must be between 128 and 254. For information about DHCP options, see DHCP options. b. Interpret DHCP Vendor-Specific Info — Select this check box for automatic interpretation of the vendor information. c. DHCP Vendor ID — Shows the DHCP Vendor ID when the dynamically allocated over DHCP/BOOTP option is selected. d.
Figure 7.
Figure 8. ENET tab a. Ethernet Select—Allows you to select the wired network connection. For Wyse 5070 thin client without SFP or RJ-45 module, the ENET0 option is selected by default. For Wyse 5070 thin client with SFP or RJ-45 module, select either ENET0 or ENET1 based on your network preference. b. Ethernet Speed—The default value is Auto-Detect.
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. Select the IPv6 check box, and then click Advanced to select various IPv6 supported setting options from the available check boxes.
● PEAP—Select 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. ● FAST—Select 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.
2. Click the WLAN tab, and do the following: a. Add—Use 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. b. Remove—Use this option if you want to remove an SSID connection from the list. c. Properties—Use this option to view and configure the authentication properties of an SSID connection that is displayed in the list. d.
Configuring the proxy settings The network Proxy tab supports Wyse Management Suite, HDX Flash Redirection, and RealTime Multimedia Engine (RTME). Supported protocols—HDX FR, WMS and RTME ● For Wyse Management Suite: HTTP, HTTPS and Socks5 (recommended) protocols are supported. ● For RTME: HTTP, and HTTPS protocols are supported. 1. From the desktop menu, click System Setup, and then click Network Setup. The Network Setup dialog box is displayed. 2. Click the Proxy tab, and do the following: a.
d. Specify the supported applications as Wyse Management Suite, FR and RTME separated by a semicolon in the Apply proxy server on field. 3. Click OK to save the settings. User scenario 1. Configure correct proxy server host and port. 2. Configure the user credentials according to the proxy server settings. On system restart, the client checks in to the Wyse Management Suite server through SOCKS5 proxy server. MQTT connection is established through SOCKS5 proxy server.
Multiple logins with Citrix and VMware Horizon ThinOS supports PNA multiple login feature. You can log in to multiple Citrix StoreFront or PNAgent using different credentials. From this release onwards, you can simultaneously log in to Citrix StoreFront/PNAgent and the VDM server. To configure the multiple login feature, do the following: 1. Configure the Pnlite server and VDI broker in the INI file as follows: SelectServerList=vdm; \ description="description" host= SelectServerList=
NOTE: The Visual Experience tab is grayed out, if the StoreFront Style check box is selected for a Citrix Broker Server entered in the Broker Setup tab. a. Classic Desktop — Displays the full taskbar, desktop and Connect Manager familiar to ThinOS users. This option is recommended for terminal server environments and for backward compatibility with ThinOS 6.x versions. b. Zero Launchpad — Displays the new launch pad style GUI designed for VDI use.
2. Click the General Options tab, and use the following guidelines: a. Click the available options to select the action after you exit all open desktops. The available options are None, Sign-off automatically, Shut down the system automatically and Restart the system automatically. NOTE: By default, None is selected and the thin client automatically returns to the terminal desktop. b. c. d. e. Default Sign-on Username— Enter the Default user name. Default Sign-on password— Enter the Default password.
● ● ● ● Imprivata— Configuring Imprivata OneSign server. Caradigm—Configuring Caradigm server. SECUREMATRIX— Configuring SECUREMATRIX. HealthCast—Introduction to HealthCast. 3. After configuring your preferred authentication, click OK to save the settings. Configuring Imprivata OneSign server OneSign Virtual Desktop Access provides a seamless authentication experience and can be combined with single sign-on for No Click Access to desktops and applications in a virtual desktop environment.
● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Fast User Switching Non-OneSign user VDI access Hotkey Disconnect Proximity card reader redirection Guided Question and Answer login Authenticate w/Password Authenticate w/Password + Password Change Authenticate w/Password + Password Change | New Password is Invalid Authenticate w/Proximity Card + Password Authenticate w/Proximity Card + Pin Authenticate w/Proximity Card + Pin | Pin not enrolled Authenticate w/Proximity Card Alone | Retrieve Password Retrieve User Identity
○ If you enable this feature by selecting the check box, the shutdown and restart icon is shown in ThinOS login and locked windows. ○ If you clear the check box, the shutdown and restart icon is grayed out. ● FailedOneSignAuth Allow—Only yes or no options are supported. Non-OneSign user can log in to the Broker by clicking No radio button. ● Logging Allow ○ OneSign logs could output on ThinOS with this feature. An INI configuration is needed correspondingly. ○ Loglevel=0/1/2/3. The default value is 0.
The SSPR configuration object controls the Self-Service Password Reset behavior for a user. The enabled attribute specifies whether the user is allowed to reset their password as part of emergency access. The mandatory attribute specifies whether the user must reset their password as part of emergency access. 4. Configuring the RFIDeas configuration object The RFIDeas configuration object controls the behavior of the RFIDeas readers.
8. Password Self-Services force enrollment feature Selecting this check box allows you to reset the primary authentication password. INI configuration for Imprivata OneSign Server A new INI parameter AutoAccess=command is added. The new value is AutoAccess=Local. When AutoAccessis set to local, the ThinOS ignores the brokers that are set on the Imprivata OneSign Appliance and starts the broker/connections which are defined in wnos.ini or local defined on the client.
1. Tap the proximity card. The card enrollment page is displayed. 2. Enter the credentials and then click OK. Proximity card is enrolled successfully.
Imprivata Bio-metric Single Sign-On Fingerprint identification feature is highly reliable, and cannot be easily replicated, altered, or misappropriated. The prerequisites of OneSign server are: ● Imprivata v4.9 or later appliance version is needed that supports the WebAPI v5 and later versions. ● Fingerprint identification license is required. NOTE: ● Supported protocols are Microsoft RDP, Citrix ICA, PCoIP, and VMware Blast.
2. Unlocking the Virtual Desktop using Fingerprint Authentication. ● Enable the Imprivata Virtual Channel from the ThinOS Global Connection settings. ● When you lock the virtual desktop in the session, the Fingerprint window is displayed automatically. 3. Managing Fingerprints on virtual desktop. ● Legend Fingerprint Management is supported. ● Fingerprint management with Imprivata Confirm ID enabled is not supported.
Grace period to skip second authentication factor Grace period enables you to specify a time limit on OneSign server for logging in without the second authentication factor after the first login session. NOTE: After you specify the grace period, you must first use the proximity badge, and then enter password or OneSign PIN for the initial login.
Figure 9. Second authentication factor window with the message If you enter a wrong password or PIN, the second authentication factor window is displayed with the warning message OneSign could not authenticate you. Try again. Figure 10. Second authentication factor window with the warning Use smart card as proximity card You can use a smart card as a proximity card to authenticate the user.
Configuring the Caradigm server Caradigm Single Sign-on and Context Management (SSO & CM) is the product of the Caradigm Company which provides Single Sign-on and Context Management Services. Caradigm solution has been integrated since ThinOS 8.1. To configure the Caradigm integration on ThinOS, do the following: 1. From the desktop menu, click System Setup, and then click Remote Connections. The Remote Connections dialog box is displayed. 2. Click the Authentication tab, and then click Caradigm. a.
1. From the desktop menu, click System Setup, and then click Remote Connections. The Remote Connections dialog box is displayed. 2. Click the Authentication tab, click the Caradigm button, enter the IP address of the SSO & CM Server, and then click OK. 3. On the Caradigm Vault Server, use the following guidelines: ● Ensure that the Enroll unenrolled badges option is checked. ● Make sure that all Badge ID mapping entries are deleted. 4.
Use the Thin Client Certificates page to add certificates for the thin client devices. The certificate must be a text in PEM format, that is, a text-based Base64-encoded DER file. ● Open the DER cert file on Notepad. ● Log in to the Vault Server Admin Console, and then click Appliance > Thin Client Certificates.
Introduction to HealthCast HealthCast Single Sign-On (SSO) solution is designed to improve user convenience, streamline workflow, and strengthen security compliance in demanding environments. The same proximity cards used for physical access are used to tap-in and tapout of unique user sessions and to tap-over any sessions unintentionally left open on the ThinOS devices.
2. Click the Authentication tab, and then click HealthCast. 3. Enter the HealthCast server details in the box provided.
4. To import the client certificate, click Browse, and select the appropriate certificate you want to use. 5. Click OK to save the settings. INI configuration To configure using INI parameters, add the following INI parameters to your wnos.ini file: HealthCastServer— The server address and options needed for the client to connect to the HealthCast Web API Server.
wherever HealthCast is installed. ● Manual login and lock/unlock terminal—If you do not have a card, or choose not to use your card, then you can manually log in using your user name and password. Administrators can disable manual login, if they wish, so that users can sign on with their proximity cards. You can also lock or unlock the terminal, if you have signed on with a manual login.
You can lock the session to secure it, but leave the remote session connected for fast access when you return. To do this, tap the proximity card and the session is locked. To resume the session, tap the card again. ● Walk away—Terminals can be configured to lock or log off sessions that have been left open. The time that will elapse before automatic lock or log off can be set by an administrator using the convenient web administration application.
● Lost or stolen card—If you report a card as lost or stolen, an administrator can immediately disable the card using the convenient web administration application. This prevents anyone else from using it. ● Self-Service Password Reset (SSPR)—If SSPR enabled by an administrator, you can register for SSPR and reset your passwords without calling the help desk.
File Servers/Path, Username, and Password—Enter the IP address or hostname of the file server that provides the system software and update images. The address can be supplied through DHCP, if DHCP is used. If you configure DHCP_Scope option with ftp://server address, http://server address, or https://server address, the File Servers/Path field is filled with ftp://server address/Wyse, http://server address/Wyse, or https://server address/Wyse respectively.
Configuring the Wyse Device Agent settings Use this tab to configure the Wyse Device Manager and Wyse Management Suite settings. ThinOS supports all the Wyse Management Suite Group Policy settings. Dell Wyse Device Agent (WDA) has been enhanced to support the following three types of customer security environments: ● Highly secured environment—Administrators must log in to each device, and use the USB device or File Server to import the server certificate.
By default, the WMS option is selected. Wyse Management Suite service automatically runs after the client boot up. If the first discovery, for example, the Wyse Management Suite service is not successful, it seeks for the next priority, for example, WDM service. This continues until a discovery is successful. If all discoveries fail, it is started again automatically after a fixed time—24 hours. a.
Value Returned: WDMNG Server URL Example: _WMS_MGMT._TCP.WDADEV.com # MQTT Server URL DNS Record Type: DNS SRV Record Name: _WMS_MQTT._TCP. Value Returned: WMS Server URL Example: _WMS_MQTT._TCP.WDADEV.com # Group Token DNS Record Type: DNS Text Record Name: _WMS_GROUPTOKEN. Value Returned: Group Token (as String) Example: _WMS_GROUPTOKEN .WDADEV.com # CA Validation DNS Record Type: DNS Text Record Name: _WMS_CAVALIDATION.
For more information about using Wyse Management Suite to manage the ThinOS devices, see the Wyse Management Suite Administrator's Guide at www.dell.com/manuals. 3. Click OK to save the settings. When you modify the ThinOS policy of the registered thin client using Wyse Management Suite, a dialog box is displayed prompting you to postpone or restart the thin client. To apply the settings immediately, click Restart Now. If you want to delay this task, click Postpone. Figure 11.
● Service=wdm disable=yes ● RapportDisable=yes Configuring the VPN Manager VPN Manager is included to manage Virtual Private Network connections. ThinOS uses the OpenConnect client that is based on SSL protocol for connecting to VPN. A virtual private network (VPN) extends a private network across a public network such as the Internet.
When the connections are created, the description column lists the session name and the Auto column shows which connection is automatically connected when the unit restarts. Only one session can be set to auto-connect. 4. Click Connect. The connection status is displayed.
6 Configuring the connection brokers In a Virtual Desktop Infrastructure (VDI) environment, a connection broker is a software entity that allows you to connect to an available desktop. The connection broker facilitates the VDI environment to securely and efficiently manage the centrally hosted desktop environments. NOTE: ● Linux hosted desktop in Citrix, VMware, and Dell vWorkspace brokers are supported.
Citrix Receiver feature matrix Table 10.
Table 10.
Introduction Citrix HDX RealTime Optimization pack offers high-definition audio and video calls. In every ThinOS release, the RTME version may be updated to newer version. For more information about the Citrix RTME 1.8 feature, see the HDX RealTime Optimization Pack article at docs.citrix.com. For more information about the Citrix RTME 2.x feature, see the latest RealTime Optimization Pack article at docs.citrix.com. Supported environments ● Citrix environment: Citrix Virtual Apps and Desktops 5.6/6.5/7.x.
3. (This step is for RTME 1.8 only) Configure the Domain Name Server (DNS) settings on ThinOS for Lync Server. NOTE: You must ensure that the thin client does not have USB redirection for video/audio devices in order to have RTME working correctly. 4. Log in to your Citrix Desktop, and sign in to Lync client or Skype for Business (SFB) client. ● For RTME 1.8, the RTME icon is displayed in the lower-left corner of the Lync client window. ● For RTME 2.x, the RTME icon is displayed on taskbar.
2. Click the About tab in the Citrix HDX RealTime Connector for Microsoft Lync 2013 dialog box. The RTME status is displayed in the upper-right pane of the dialog box. If the RealTime Multimedia Engine is successfully initiated between the ThinOS client and Citrix desktop, the RTME status is displayed as follows: Table 11.
Known issues ● RTME operation system on ThinOS is displayed as Linux. ● The RTME 1.8 feature on ThinOS does not work with other versions of HDX RealTime connector due to known Citrix limitation. ● If you change the audio device during an RTME call, the audio input or output might stop responding. ● In a video conference call, when different user is speaking, the on-screen video switches to the active user, but takes a few seconds to switch over. Verifying the RTME 2.
● In Citrix RTME version 2.3, the video performance of applications is designed for a lower CPU consumption. Therefore, the video resolution may be downgraded compared to version 2.2. ● ThinOS RTME package update does not support hardware acceleration. For more information, see the Citrix documentation at docs.citrix.com. Citrix RTME call statistics Table 12.
● RTME, TCX, FR, and Horizon This issue is not observed on thin clients with more disk space. Supported environment Table 13.
NOTE: If ThinOS running Cisco Jabber (JVDI) fails to register with Cisco Unified Communications Manager, add the DNS servers and DNS domains that are used by the Citrix host and the Cisco Unified Communications Manager servers to ThinOS. You can either specify the domain name and server IP on the General tab in Network Setup, or add the DNS server and domain value to the DHCP server by providing the IP address information to the ThinOS client.
Figure 13. Use my computer for calls Using Device Selector Cisco Jabber Softphone for VDI consists of a component called Device Selector. Use the Device Selector menu to manage your audio devices and cameras. If you have multiple devices connected to the thin client, you can view your active device, or select a different device. To enable a device, do the following: 1. In the Windows notification area, click the Device Selector icon. The available devices are listed. Figure 14. Device Selector 2.
● ● ● ● ● ● ● ● ● ● ● Merge the calls Audio conferencing Transfer the call Play voice mail Forward the call to voicemail Forward the call to another number Forward voice messages directly Use the Device Selector menu to switch between headsets Use the Device Selector menu to switch between cameras Set up secure phone capabilities Answer the call on multiple phone devices (Shared Line feature) NOTE: Dell recommends that you reduce the video resolution to 640 x 360p with 30fps on Wyse 3040 thin client.
Table 14. Known issues (continued) Description Workaround restart when you hotplug or turn off/on the monitor when using the DP audio in JVDI. you first set the DP audio in the ThinOS client and then launch the ICA session. Audio output is poor when you enable the JVDI audio during the full screen video call on Wyse 5060 and 3040 thin clients. This is due to the hardware performance limitation. Use the JVDI video call with window mode on Wyse 5060 and 3040 thin clients.
3. Ensure that the secondary authentication is none. 4. Add the following INI parameter in the wnos.ini file, and configure your file server: pnliteserver= Storefront={yes,no} For more information about configuring Citrix NetScaler Gateway with DUO authentication, see the Citrix NetScaler Gateway Guide at www.duo.com. Using Citrix NetScaler with CensorNet MFA authentication SMS PASSCODE is re-branded as CensorNet MFA.
If the authentication is successful, then you are logged into the Citrix session. Configuring 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 used for user authentication.
Citrix icon refresh Citrix applications can be refreshed by clicking Refresh from PNMenu. There are two methods to refresh the Citrix applications: ● Manual refresh ● Auto refresh using the INI parameter Refreshing Citrix applications manually To refresh the Citrix application manually, do the following: 1. For single StoreFront or PNAgent server, change the application in broker, and click Refresh from PNMenu. The following message is displayed in the lower right pane during application refresh. 2.
4. Refresh scope covers the aspects such as, application removed, added, duplicated, disabled, enabled, icon/title change, and on/off desktop. Active sessions that are started are not affected by application refresh. 5. The disconnect session can be reconnected after application refresh, if Automatic reconnection at logon is enabled in remote connection.
Configuring ICA connections To configure the ICA connections: 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, from the drop-down list, select the Broker type as None. 3. Click ICA connection protocol, and click Configure. The Default ICA dialog box is displayed. NOTE: Default ICA is always used for direct connection to a published application and not for StoreFront or PNAgent. 4.
entry is needed if the list is on an ICA server in the same network segment as the thin client. No entry is necessary if the connection is to a server, or if the server name or IP contains the IP address of the server. d.
Figure 16. Default ICA—Logon a. Logging on area—Enter username, password, domain name, and logon mode. If the login username, password, and domain name boxes are not displayed, enter the information manually in the ICA server login screen. ● Login Username—Maximum of 31 characters is allowed. ● Password—Maximum of 19 characters is allowed. ● Domain Name—Maximum of 31 characters is allowed. ● Logon Mode—Select User-specified credentials, Smart Card, or Local User. b.
Figure 17. Default ICA—Options a. Autoconnect to local devices—Select any options (Printers, Serials, USB, Smart Cards, and Disks) to have the thin client automatically connect to the devices. b. Allow font smoothing—When selected, enables font smoothing (smooth type). c. Optimize for low speed link—When selected, allows optimization for low-speed connections, such as reducing audio quality and/or decreasing protocol-specific cache size. Intended for a connection spanning a WAN link or using dial-up. d.
● Increase the value of MaxVideoMemoryBytes REG_DWORD to support one or more 4K resolution monitors. For more information, see Citrix documentation at support.citrix.com. ● Increase the display memory limit to support more color depth and higher resolution. For more information, see Citrix documentation citrix.com. User scenario: 1. Connect multiple monitors to ThinOS device. 2. In the Display Setup dialog box, disable Mirror Mode, and configure the display layout. 3. Launch an ICA desktop with full screen.
Before resetting password or Unlocking 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. From the PNMenu, click the Manage Security Questions option (Classic and StoreFront only). The Security Questions Enrollment window is displayed. 2. Enter the appropriate answers to the question set.
3. Click OK to register the security questions. Using Account Self-Service After the security questions enrollment is complete, 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 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.
2. Click Unlock account or Reset password based on your choice, and then click OK. Unlocking account After you register the security questions, do the following to unlock your account: 1. Choose a task (Unlock account) in Account Self-Service window. 2. Enter the user name. 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, the following error message is displayed. ● If you provide the wrong answers more than three times, you cannot unlock the account or reset the password, and the following error messages are displayed.
Resetting password After you register the security questions, do the following to reset your password: 1. Choose a task (Reset password) in Account Self-Service window. 2. Enter the user name. 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. QUMU or ICA Multimedia URL Redirection QUMU utilizes ICA Multimedia URL Redirection. You are required to install a browser plug-in for this feature to work.
HTML5 Video Redirection HTML5 Video Redirection controls and optimizes the way XenApp and XenDesktop servers deliver HTML5 multimedia web content to users. From XenApp and XenDesktop 7.12, 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 server policies must be enabled: ● Windows Media redirection—By default this option is enabled.
Figure 19. Use video codec for compression setting ● ThinWire Plus—Equivalent to Do not use video codec option ● Fullscreen H.264—Equivalent to For the entire screen option ● Selective H.264—Equivalent to For actively changing regions Verifying the working status of the ICA connections ● For Dell Wyse 3040 thin client—By default, ICA SuperCodec is enabled when the ThinOS display resolution is lesser than or equal to 1920 x 1080.
NOTE: For ICA connections, there is no INI parameter. If you set the Use video codec for compression policy to Do not use video codec, ICA SuperCodec is disabled, and ThinOS does not print any log. Anonymous logon 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.
7. Open the Devices and Printers in the desktop or application, notice the printer is mapped as UPD printer by default. You can use the HP-LaserJet-P2035 [UPD:PCL5c] to perform the print job. Citrix UPD configuration on server a. To enable the printer policy, use the following guidelines: i. To enable the printer policy in Citrix Virtual Apps 6.5– Go to the DDC Server, click Start > Citrix AppCenter . ii.
iv. To enable the printer policy in Citrix Virtual Apps and Desktops 7.5 and later versions, do the following: i. Go to the Citrix DDC server, Ordered Click List Citrix Number studio5 > policies and add a policy. Enable the Auto-create generic universal printer option. Ordered Set the ListUniversal Number 5print driver usage to Use universal printing only from the drop-down menu. b. Check registry and make sure the same driver has been installed.
i. Check the drivers in registry of the server or desktop which you want to connect. The server or desktop must have ps, pcl5, pcl4 drivers in the registry and the same driver must be installed on the server or desktop. ii. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\UniversalPrintDrivers\. ThinOS does not support EMF and XPS. NOTE: The supported drivers in the following table are one of the supported drivers for Citrix UPD used in ThinOS. One of the recommended driver is provided here as an example.
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 thin client operating system. It provides access to centrally hosted virtual desktops from your thin clients. In every ThinOS release, the Horizon Client version may be updated to newer version.
NOTE: The PCoIP only connection protocol is applicable only to PCoIP clients. If you do not install Horizon package, then the Blast only protocol option is not available for selection. PCoIP protocol is required for PCoIP session. Horizon package is required for Blast session. The available options are: ○ Server default—Select this protocol connection to display the desktop with default protocol as configured in the VMware View Admin console, for each pool in the broker.
Table 19.
Table 19.
Table 19.
Table 19.
Table 19. VMware Horizon Client feature matrix (continued) Client type ThinOS Access to Linux Desktop - Blast Protocol Supported Audio Playback Supported Seamless Window Not supported Launching multiple client instances using URI Not supported One-click Install of Client Not supported Parameter pass-through to RDSH apps Not supported Performance Tracker Supported Shortcuts from server Not supported Workspace ONE mode Not supported Supported—Both PCoIP and Blast protocols are supported.
USB redirection RDS desktop through PCoIP/Blast—This feature is supported. USB audio redirection—USB audio redirection enables you to use USB audio devices in the remote session. However, Dell does not recommend that you enable the USB audio redirection because of sound quality. Using unauthenticated access—You can anonymously log in to the VMware session with application remoting. To use the unauthenticated option, do the following: 1.
● Using View Connection Server web portal 1. Log into your View Connection Server web portal. 2. Navigate to View Configuration > Global Settings > Edit, select the Hide server information in client user interface check box, and clear the Hide domain list in client user interface check box. 3. Click OK. 4. Log in to the VMware Horizon broker. The server URL is hidden, and the domain list is displayed. ● Using INI parameter Use the INI parameter, ConnectionBroker=vmware DisableShowServer=yes.
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. 6. Start the audio or video calls. Dependencies and known issues ● Dependency: RTME.i386.pkg needs to be installed for RTAV video. ● The answer call button of the local audio device, supported by HDX RTME, is not supported by RTAV. ● RTAV does not support RDS desktop, for example, 2008 R2/ 2012 R2 according to VMware. ● Support for PCoIP and Blast protocol only. RDP protocol is not supported according to VMware.
VMware Blast VMware 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. NOTE: When you pause the pointer over the connection icons, the corresponding connection protocols are displayed in tooltip. This is designed for RDSH applications. From ThinOS 8.4 release, RDSH application is supported for both PCoIP and Blast protocol.
Table 20. Blast feature matrix (continued) Blast features Support on ThinOS Comments/ Known issues AES 128/256 Yes See, ThinOS AES design. Multi-display/ 4K/ 32-bit Yes See, VMware Blast support information. For example, the prerequisite is VM video RAM. ClearType fonts support No ThinOS supports TrueType fonts. 3D display Yes See, VMware Blast support information. Blast recovery from network interrupt Yes Requires Horizon View agent 7.0.1.
To verify if the VMware Horizon Virtualization Pack for Skype for Business is installed on the deployed virtual machines, check if the following registry keys exist: ● HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Lync\VdiMediaProvider - GUID (REG_SZ) ● HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Lync\VdiMediaProvider - GUID (REG_SZ) For information about pairing modes for a session, see the Configuring Skype for Business document at docs.vmware.com.
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.
Table 23. Matrix for multi screen support PCoIP Multi-monitor support Wyse 5070 Extended thin client Resolutio n No.
● 4K display—ThinOS supports four displays with 4K resolution in a Horizon blast session. Due to low performance, Dell recommends that you do not use four displays with 4K resolution. Table 25. 4K display support Hardware version Windows version Number of 4K displays supported 10 (ESXi 5.5.x compatible) 7, 8, 8.x, and 10 1 11 (ESXi 6.0 compatible) 7—3D rendering feature and Windows Aero are disabled. 3 11 7—3D rendering feature is enabled. 1 11 8, 8.
Figure 21. Printer Setup d. Click Ok to save the configuration. 6. Click the Options tab, and do the following: a. Set LPT1: as default printer. NOTE: Do not select the Enable .print Client check box. b. Click Ok to save the configuration.
Figure 22. Options 7. Connect to a VMware Blast session. Go to Control Panel > Devices and Printers. The printer that is configured locally in ThinOS is mapped to the session. The mapped printer’s driver is TP PS Driver and the port is TPVM port. The virtual printer allows the ThinOS local printer to be mapped to the VMware Blast session without installing the printer driver in the session. Enable hardware cursor in Blast session The hardware cursor enables GPU to control the display of your mouse cursor.
To enable the relative mouse feature in the Classic mode, do the following: 1. Connect to a remote desktop using the PCoIP display protocol. 2. Right-click the remote desktop icon on the ThinOS taskbar. 3. Click Enable Relative Mouse. NOTE: To disable the relative mouse feature, right-click the remote desktop icon on the ThinOS taskbar, and click Disable Relative Mouse. To enable the relative mouse feature in the Zero mode, do the following: 1. Connect to a remote desktop using the PCoIP display protocol.
● Ensure that the Teradici Remote Workstation card version matches the Teradici PCoIP SDK version 2.9. ● Ensure that host cards are connected to a remote workstation. ● Ensure that host cards are installed correctly, that is, connected to a remote workstation with GPU. NOTE: The SDK in ThinOS does not function similar to Teradici zero client firmware. For example, the SDK in ThinOS does not support USB redirection with the host card connection.
Figure 24. Connection Settings - PCoIP a. Enter the description for the PCoIP connection. b. Enter the IP address of the remote host card. c. From the Display Resolution drop-down list, select a display resolution for the PCoIP connection. TERA2220 supports a single display with 2560 x 1600 resolution or two displays with 1920 x 1200 resolution. TERA2240 supports two displays with 2560 x 1600 resolution or four displays with 1920 x 1200 resolution. d.
● Wyse 5070 Thin Client with PCoIP ● Wyse 5470 Thin Client with PCoIP ● Wyse 5470 AIO Thin Client with PCoIP To customize the broker agent window and icons, do the following: 1. To enable this feature, use the INI parameter SignOn=yes BitmapsMap={yes,no} You must set BitmapsMap as yes for changing integrated bitmap images into customized bitmap images. 2. Place the text file bitmaps.map in the same folder as ThinOS builds.
3. Click RDP connection protocol, and click Configure. The Default RDP dialog box is displayed. 4. Click the Connection tab, and use the following guidelines: a. Connection Description—Enter the descriptive name that is to appear in the connection list (38 characters maximum). b. Host Names—Use the list to select the valid DNS server name or the IP address of the server to which the thin client connection is to be made. You can also use Browse next to the box to make the selection you want.
● Mirror mode is enabled on multi-display or single display—The Default on screen x option is not displayed. The display resolution of the RDP connection is set as Default irrespective of the value configured in the onscreen=x INI parameter. ● Span mode is enabled on multi-display—The Default on screen x option is displayed. You can select your preferred display on which you want to start the RDP session. You can also set your preferred display using the onscreen INI parameter.
b. Application (127 characters maximum) and Working Directory (63 characters maximum)—Enter an initialization string and arguments, including an associated working directory, that you want to start automatically on the server when the connection is made. c. Use TS Gateway—Enables the use of Terminal Services Gateway (TS Gateway) server when connecting. If required, then enter the IP address or URL of the TS Gateway server in the Server name box.
NOTE: USB—Redirects locally attached USB devices on the thin client to a Microsoft Windows terminal server. When the user connects to the terminal server, locally attached USB devices on the thin client are accessible. g. RDP Audio Playback—Select the audio playback options such as Play Locally, Do not play, and Play on remote computer. h. RDP Audio Recording—Select the audio recording options such as Do not record, and Record from local. i.
Table 27. RDP display capability matrix Destination endpoint Maximum resolution per monitor [Enable Force Span] Maximum display support [Span Monitors] Windows 7 SP1 4096 (w) x 2048 (h) 4096 (w) x 2048 (h) Windows 8.1 8192 x 8192 6 x 4K Windows Server 2012 R2 8192 x 8192 6 x 4K Windows 10 8192 x 8192 6 x 4K Windows Server 2016 8192 x 8192 6 x 4K RDP H.264 From ThinOS version 8.5.1, logs of H.264 and H.264-AVC444 are hidden and not displayed in the Event Log tab. In ThinOS version 8.
Table 29. RDP H.264 decoding matrix (continued) Unit type GPU Wyse 5070 thin client— Pentium processor Session Windows 10/Windows Server 2016 Windows 8.1/Windows Server 2012 R2 Display resolution H.264AVC444 Decoding H.264 Decoding 2560 x 1440 Enabled Software Disabled 2048 x 1280 Enabled Software Enabled Hardware 1920 x 1200 Enabled Software Enabled Hardware All data described in the table is based on virtual machine without RemoteFX/vGPU enabled configuration.
Figure 25. Event log tab NOTE: ● Dependence 1—RDP GFX status, H.264, and VOR work only when GFX is enabled. ● Dependence 2—VOR is dynamic. So the enablement/disablement of VOR dynamically changes during the change in the video resolution (enlarge/shrink). ● Dependence 3—H.264 enablement is decided at the beginning of connection, depending on the maximum resolution available for the session. If H.
● TS Gateway II and TS Gateway III are downward compatible with Windows Server 2016, that means, if the WebSocket connection fails or the TS Gateway server or thin client version does not support WebSocket, then TS Gateway II or TS Gateway III is used. The following screenshot displays the TS Gateway II connection setup logs: Figure 26. Event log tab The following screenshot displays the TS Gateway III connection setup logs: Figure 27.
Connect to RDP session using UDP with TS Gateway To connect to a Remote Desktop Session using User Datagram Protocol (UDP) with TS Gateway, do the following: 1. Deploy the following INI parameter to the thin client: SessionConfig=RDP TSGWUDP=yes. 2. Enable Terminal Services Gateway (TSGW) for the applications and desktops from the Microsoft RDS broker server. 3. On the ThinOS client, start a Remote Desktop Session using the RDS connection broker. 4. Connect to the published desktop.
Amazon WorkSpaces connection is applicable only for PCoIP clients running ThinOS 8.3, and later versions. This section provides information about how to configure the Amazon WorkSpaces (AWS) connection on your ThinOS device, and other Amazon WorkSpace features that you can configure on ThinOS. Configuring the Amazon WorkSpaces broker connection Amazon WorkSpaces connection is applicable only for PCoIP clients. To configure the Amazon WorkSpaces (AWS) broker setup: 1.
Figure 30. Amazon WorkSpaces with the Registration Code field NOTE: You cannot configure the direct connection mode using the INI parameter or Wyse Management Suite. ThinOS enables you to modify the registration code anytime from the Amazon WorkSpaces (AWS) login window. This feature is applicable if you are connecting to AWS using the registration code. Deploy the INI parameter EnableAWSREGCode={yes, no} to use this feature.
Figure 31. Amazon WorkSpaces login window for servers that support MFA If your server does not support MFA, use the following INI parameter: ConnectionBroker=AWS Host=wsnrt+KQRQWM UseRegistrationCode=yes EnableMFA=no Figure 32. Amazon WorkSpaces login window for servers that do not support MFA ● If you want to connect to AWS using the default PCoIP Gateway mode, enter the IP address/Hostname/FQDN of the broker server in the Broker Server field.
● Full—This security mode requires FQDN address with domain certificate that is installed in PCM, and certificate installed on the client. ● Low—This security mode enables FQDN/IP address with/without certificate. ● Default—Follows global security mode settings. NOTE: The Connection Protocol drop-down list is disabled for the AWS broker. By default, the option is set to PCoIP Only. 6. Click OK For information about deploying AWS WorkSpaces and AWS EC2 PCM for AWS WorkSpaces, go to www.teradici.
Figure 33. Broker setup - Teradici Cloud Access 2. On the Broker Setup tab, from the Select Broker Type drop-down list, select Teradici Cloud Access, and configure the following options: ● Broker Server—Enter the IP address or FQDN of the broker server. ● Auto Connect List—Enter the name of desktops that you want to start automatically after logging in to the respective broker. Use a semicolon to separate each desktop name. NOTE: Field values are case-sensitive.
7 Configuring local settings You can configure available thin client settings on the thin client using the following. Depending on user privilege level, some dialog boxes and options may not be available for use. NOTE: While it is not recommended to use dialog boxes for configuring thin client settings, they are available in case you want to temporarily override central default configurations or you do not have the option to set up central configuration (smaller environments).
● ● ● ● ● ● ● ● ● ● ● ● ● ● Username/Password/Domain System Information Shut down the system, restart the system, reset the system setting to factory default OK, Cancel Initiating devices Looking up IP address from DHCP, Note: Pressing CTRL-ESC keys cancel out of network check Retry DHCP for an IP address Waiting for network link.
b. Enable Daylight Saving— Allows you to enable the daylight saving settings. When selected, the Start Date and End Date boxes must be properly configured to define the daylight saving starting (month/week/day) and ending (month/ week/day) periods. Use the following guidelines to enter the Start date and End date: ● Month— Specifies the month in the year from January through December. ● Week— Select 1 through 4 for the week in the month. Week last denotes the last week in the month.
3. Click OK to save the settings. Configuring the display settings Use the Display dialog box to select the resolution and refresh rate for the monitor used with the thin client. Configuring the display setup This section is applicable to Wyse 5070, Wyse 5470, and Wyse 5470 All-in-One thin client. Use the Display Setup dialog box to configure the display settings for the connected monitors. To configure the display setup: NOTE: On Wyse 5470 Thin Client, the built-in display stays on by default. 1.
Figure 34. Display settings If you clear the Mirror mode check box, the Span Mode is enabled. The following screen represents the span mode configuration.
Figure 35. Display settings Blocks displayed on the screen represent the number of monitor screens connected to the thin client. Each block represents a single monitor screen. Every monitor contains a unique display order number and display configuration. You can move the blocks horizontally or vertically and construct the multi-display layout in mixed directions. To construct a new display layout, move the blocks to your preferred position, and click Apply. A new display layout is created.
NOTE: The default screen resolution on the Wyse 5470 Thin Client is 1366 x 768 or 1920 x 1080 depending on the configuration. The default screen resolution on the Wyse 5470 All-in-One Thin Client is 1920 x 1080. In Mirror Mode, the resolution list is derived from the intersection of resolutions in all connected monitors. In Span Mode, select a monitor block and change its resolution from the Resolution drop-down list.
This section describes the hardware capability for display. Table 31. Port preferences Model Summary Wyse 5070 thin client with Celeron processor ● On Wyse 5070 thin client without wireless module, the optional port can be used as second RJ-45, SFP, VGA, or second serial port. ● On Wyse 5070 thin client with wireless module, the optional port cannot be used as second RJ-45 or SFP. ● When monitor is connected on USB Type-C port, DisplayPort 2 becomes inactive.
Wyse 5070 thin client with Pentium processor Table 34. Display matrix Number of displays Supported display resolution 4K resolution Non-4K resolution 3840 x 2160 @ 60 Hz Up to 2560 x 1600 @ 60 Hz One display Yes Yes Two displays Yes Yes Three displays¹ Yes Yes ¹Dell recommends that you configure a maximum of two displays with 4K resolution and the third display with non-4K resolution on DisplayPort 3 for optimized stability and performance.
Table 37. Ports Ports DP1 DP2 DP3 VGA USB Type-C mDP4 mDP5 DP6 Monitor priority 1 2B¹ 3B² 3A² 2A¹ 4 5 6 4K display Yes Yes Yes No³ Yes Yes Yes Yes Non-4K display Yes Yes Yes Yes³ Yes Yes Yes Yes ¹DP2 and USB Type-C port are mutually exclusive with USB Type-C port taking higher priority. ²DP3 and VGA port are mutually exclusive with VGA port taking higher priority. ³VGA port supports only 1080p resolution.
● Hot plugging a monitor may result in a black screen in the VDI connected session. To recover the session screen, you must power off the monitor, and then power on the monitor. This issue will be resolved in the next release. ● Hot plugging a monitor during VDI connection or display setup configuration may result in unexpected issues, such as terminal freeze or display layout change. This issue will be resolved in the next release.
If your monitor is not DDC compatible, then Monitor does not support Plug and Play message is displayed. Click OK to acknowledge the message and remove it from the screen. b. DDC table—If the monitor is VESA DDC2B (Display Data Channel) compatible, selection of this option allows you to select the resolution and refresh rate you want from the list. c. User defined display setting—Select this option and select the resolution and refresh rate supported by your monitor. All combinations are allowed.
This feature is applicable for supported Dual Monitor capable thin clients Only. a. Dual Head—Select Mirror Mode to have the two monitors work in a matching state, or Span Mode to have the two monitors work separately second is extended from first. b. Main Screen—Select which of the two monitors you want to be the main screen (Screen1 or Screen2). The other screen is extended from the main screen. The other screen is extended from the main screen.
For Swap dual screens, when you set Main Screen to Screen2, an additional check box is displayed at the bottom of the tab that allows you to swap dual screens. If you clear the check box, the Screen1 is usually the left one or the top one in dual display. When you set Main Screen to Screen2, the main screen is changed to the right screen or bottom screen.
Go to System Setup > Display > General, and do the following: 1. Change resolution from DDC table or User defined display settings. 2. Change rotation setting from User defined display settings. When the display settings are changed during active sessions, the active sessions do not resize dynamically in the following situations: ● Seamless sessions ● For dual head mode, including: ○ Change from single mode to dual head. ○ Change from dual head to single mode. ○ Change display setting in dual head mode.
Configuring the peripherals settings The Peripherals dialog box enables you to configure the settings for the Keyboard, Mouse, Audio, Serial, Camera, Touch Screen, and Bluetooth. Configuring the keyboard settings To configure the keyboard settings: 1. From the desktop menu, click System Setup, and then click Peripherals. The Peripherals dialog box is displayed. 2. Click the Keyboard tab and set the Character Set, Keyboard Layout, Delay Before Repeat and Repeat Rate parameters.
Function key combinations The Wyse 5470 Thin Client supports the following Function (Fn) key combinations: NOTE: Blast protocol does not support Fn keys. Table 39.
5. Select the Enable big mouse pointer check box to increase the size of the local mouse pointer by two times. NOTE: This option affects ThinOS local mouse pointer. 6. Select the Disable trackpad check box if you want to disable the touchpad on the device. This option is applicable only to the Wyse 5470 Thin Client. 7. Select the Disable trackpad while typing check box if you want to disable the touchpad while typing using the integrated keyboard. This option is applicable only to the Wyse 5470 Thin Client.
g. Select the Enable DP audio check box to enable the DisplayPort audio function on your thin client. You must click either Port 1 or Port 2 to select your desired DisplayPort. On the Wyse 5470 Thin Client, ThinOS supports DP audio only over one port. You must select either Port 1 or Port 2 based on your port preferences. On the Wyse 5470 All-in-One Thin Client, only Port 1 is available. h.
Limitations on the Wyse 5470 All-in-One Thin Client ● You must enable the DP audio as it is disabled by default. ● Hot plugging is not supported. You must plug in the DP cable, and reboot the thin client for the DP audio to work. ● Converter is not supported. ● Turning off or turning on the display is not supported. Restart the thin client for the DP audio to work in the following scenarios: ○ If the power button is pressed, to power off, and then power on the display.
● Wyse 5070 Thin Client with Celeron processor ● Wyse 5070 Thin Client with Pentium processor ● Wyse 5070 Extended Thin Client with Pentium processor To disable or enable the onboard serial port, use the INI parameter Device=SerialDisable={yes, no}. The default value is no. This option does not affect the USB serial devices. The value that you specify is saved into NVRAM and a system reboot is required for changes to take effect.
● On a JVDI-enabled client, the CPU usage of the integrated camera is 10% higher than the CPU usage of Logitech C930e camera. The difference in the CPU usage is observed while video calling on Cisco Jabber in a ICA session. Configuring the touch screen settings Use the Touch Screen tab to configure touch screens that are connected to the thin client.
1. From the desktop menu, click System Setup, and then click Peripherals. The Peripherals dialog box is displayed. 2. Click the Bluetooth tab, and use the following guidelines: Bluetooth enabled devices, such as headsets and mouses that are available in the thin client environment are listed in the Bluetooth page. The following attributes are displayed in the list: ● Name—Specifies the name of the Bluetooth enabled device.
Table 42. User scenario User scenario Status Device turned off Disconnected | Paired Device turned on Connected | Paired Device disconnected from ThinOS Disconnected | Not Paired ● Scan—All Bluetooth devices enter into Page Scan mode. Different Bluetooth devices enter into the Page Scan mode at different instances such as when a specific button is pressed three times or a specific button is pressed and held until the LED turns blue.
Configuring the printer settings Use the Printer Setup dialog box to configure network printers and local printers that are connected to the thin client. Through its USB ports, a thin client can support multiple printers. If more than one printer is to be used and another port is not available on your thin client and the port that is to be used must be shared with a USB modem converter, connect a USB hub to the port. Configuring the ports settings To configure the ports settings: 1.
file and type the content, such as "HP Color" = "HP Color LaserJet CM1312 MFP PCL6 Class Driver". Add the command line printermap=printer.txt to your wnos.ini file. Now, you can type “HP Color” in the Printer Identification field instead of the full driver string. d. Printer Class— This is optional. Select the printer class from the list PCL5, PS, or TXT or PCL4. e. Enable the printer device — Select this option to enable the directly-connected printer. It enables the device to display on the remote host.
driver name mapping takes place either through a printer-mapping file read by the system as part of the global profile (wnos.ini) or by MetaFrame servers through the MetaFrame printer configuration file (\winnt\system32\wtsprnt.inf). d. LPD Hosts—The DNS or WINS name of the server for the network printer. An IP address of the printer on the network can also be entered.
a. Select SMB—Select the SMB you want from the list. b. Printer Name—(Required) Enter the name to be displayed in your list of printers. c. Printer Identification—Enter the type or model of the printer in the exact text of the Windows printer driver name— including capitalizations and spaces. This name must be either the device driver name for the printer under the Microsoft Windows system, or a key to map to the device driver.
a. Default Printer —Select the printer you want to be the default printer from your list of available printers. b. Enable .print Client and Port —If you want to enable .print Client, select Enable .print Client , and then enter the port. 3. Click OK to save the settings. Using the Help When you click the Help tab, the following message is displayed in the text box. Printer Identification is supplied by printer device. Change it to a Window’s printer driver name or setup a driver mapping file.
3. Click Restart the system to restart your thin client. 4. Select the Reset the system setting to factory default check box to restore your system settings to default factory settings. 5. Click OK to save the settings. Shutdown reset impacts all configuration items, including, but not limited to network configuration and connections defined in local NV-RAM. However, the terminal name will not be changed.
8 TCX Suite NOTE: TCX is not supported anymore as it is deprecated from the ThinOS 8.6_303 release onwards. Dell Wyse TCX Suite is a single software solution that provides the benefits of cloud client computing. The supported environments for Dell Wyse TCX Suite are Microsoft Remote Desktop Services, Citrix Virtual Apps and Desktops, Citrix Virtual Apps, Teradici, and VMware Horizon View.
9 Trusted Platform Module version 2.0 Wyse 5070 thin client supports disk encryption and decryption through Trusted Platform Module (TPM) version 2.0. ● Measured boot—SHA1 (Secure Hash Algorithm 1) is used to produce a hash value for ThinOS image, and extend the integrity measurement into Platform Configuration Registers (PCR) inside TPM—TPM_PCR16. This is used to generate disk encryption or decryption key.
10 Performing diagnostics This chapter helps you identify and troubleshoot your thin client using the troubleshooting options. System tools Use the System Tools dialog box to view device details, package details and Global INI/User INI information. You can also import certificates using the Certificates tab. 1. From the desktop menu, click System Tools. The System Tools dialog box is displayed. 2.
a. Import the certificates by selecting either USB Storage or File Server from the drop-down list, and then click Import to import the required certificate. b. Click Delete to delete the imported certificate. c. Click View Certificate to view the imported certificate information such as Version, Validity, and Serial number. You can also view the certificate path and certificate status. For more information about the default certificates, see About default certificates. d.
● pcoip.i386.pkg—This package is available only on Wyse 3040 with PCoIP, Wyse 5010 with PCoIP (D10DP), Wyse 5040 AIO with PCoIP (5213), and Wyse 5060 with PCoIP. ● TCX.i386.pkg—This package is introduced to support TCX. You cannot delete the base package separately. If you click Delete All, all packages are deleted including the base package. When you click Delete All, a message is displayed prompting you to restart the device. The base.i386.pkg is mandatory for all ThinOS clients.
WCM function is supported from WDM for comprehensive client configuration. Without configuration from server, the client loads the cached settings (wdm.ini), if available. Limitation To upgrade or downgrade firmware/image through WCM, you are required to enable WDM file server function by selecting the WTOS INI path upon checkin (HTTPS/CIFS) check box in the WTOS preferences in the WDM configuration manager. 8. Click OK to save the settings.
Requesting certificate manually To request the certificate manually, do the following: 1. Go to System Tools > Certificates > Request Certificate. The Request Certificate dialog box is displayed. 2. Enter the appropriate values in the Request Certificate dialog box, and then click the Request Certificate button. The certificate request is sent to the server, and the client receives the response from server and installs both CA certificate and client certificate. 3. Click Ok to save the changes.
About Default Certificates Default certificates embedded in the ThinOS are displayed in the Certificate dialog box. To view the default certificate, set ThinOS to factory default, and on the desktop click System Settings > System Tools > Certificates. The following default certificates are displayed in the cacerts folder, in an expandable tree structure format: ● BTCTRoot.crt ● Class3PCA_G2_v2.crt ● Class4PCA_G2_v2.crt ● DigiCertGlobalRootCA.cer ● Entrust_G2.crt ● gd-class2–root.crt ● GeoTrust_Universal_CA.
Table 43. BTCTRoot.crt Certificate details (continued) Certificate field Default value/format OU=CyberTrust O=Baltimore C=IE Public key RSA (2048 bits). Key bits are displayed in the lower pane of the window.
Table 45. Class4PCA_G2_v2.crt Certificate details Certificate field Default value/format Version V1 Serial number 32 88 8e 9a d2 f5 eb 13 47 f8 7f c4 20 37 25 f8 Signature algorithm sha1RSA Issuer VeriSign Trust Network OU=VeriSign Trust Network OU=(c) 1998 VeriSign, Inc.
Table 46. DigiCertGlobalRootCA.cer Certificate details (continued) Certificate field Default value/format C=US Public key RSA (2048 bits). Key bits are displayed in the lower pane of the window.
Table 48. gd-class2–root.crt Certificate details Certificate field Default value/format Version V3 Serial number 00 Signature algorithm sha1RSA Issuer Go Daddy Class 2 Certification Authority OU=Go Daddy Class 2 Certification Authority O=The Go Daddy Group, Inc. C=US Valid from 2004–06–29 17:06:20 Valid to 2034–06–29 17:06:20 Subject Go Daddy Class 2 Certification Authority OU=Go Daddy Class 2 Certification Authority O=The Go Daddy Group, Inc. C=US Public key RSA (2048 bits).
Table 49. GeoTrust_Universal_CA.cer Certificate details (continued) Certificate field Default value/format C=US Public key RSA (4096 bits). Key bits are displayed in the lower pane of the window.
Table 51. gsdomainvalsha2g2r3.cer Certificate details (continued) Certificate field Default value/format Issuer CN=GlobalSign O=GlobalSign OU=GlobalSign Root CA - R3 Valid from 2011-08-02 10:00:00 Valid to 2022-08-02 10:00:00 Subject CN=GlobalSign Domain Validation CA - SHA256 - G2 O=GlobalSign nv-sa C=BE Public key RSA (2048 bits). Key bits are displayed in the lower pane of the window.
Table 52. Pc32ss_v4.crt Certificate details (continued) Certificate field Default value/format OU=Class 3 Public Primary Certification Authority O=VeriSign, Inc. C=US Valid from 1996–01–29 00:00:00 Valid to 2028–08–01 23:59:59 Subject Class 3 Public Primary Certification Authority OU=Class 3 Public Primary Certification Authority O=VeriSign, Inc. C=US Public key RSA (1024 bits). Key bits are displayed in the lower pane of the window.
Table 53. PCA-3G5.
● Click either USB or File Server to select your target device you want to use for CMOS management. ● Extract CMOS—Click this option to extract the CMOS settings and certain BIOS settings to the USB drive or file server based on your target device selection. ThinOS reads the CMOS settings from the SMBIOS Interface for Dell BIOS, and the CMOS interface for legacy Wyse BIOS. For information about the support matrix, see the Dell Wyse ThinOS Version 8.6 Release Notes at www.dell.com/support.
Figure 40. Trace 4. Click the Capture tab, and configure the export event log, network capture, wireless capture, and capture USB packets as per your requirements.
Figure 41. Capture a. Export Event log—Click either the One-time or Persistent option to enable logging any unexpected error messages. You can turn off logging and check the log file under the folder https:/wnos/trouble_shoot. Ensure to enable the Enable Trace option of the Privilege parameter in a wnos.ini file. For more information, see the Dell Wyse ThinOS INI Guide. b. Enable SmartCard log—To enable the client to log error messages of the smart card, select the Enable SmartCard log check box. c.
NOTE: Ensure that you have inserted the USB drive into the thin client before selecting the network capture option. If the USB drive is not inserted and you exit the dialog box, the network capture is automatically cleared. e. Wireless capture to USB—Click either the One-time or Persistent option to enable the capture of wireless network information.
Ping sends an echo request to a network host. The host parameter is either a valid hostname or an IP address. If the host is operational and on the network, it responds to the echo request. Ping sends one echo request per second and calculates round trip times and packet loss statistics. It displays a brief summary upon completion of the calculation. The ping utility can be used to: ● Determine the status of the network and various foreign hosts. ● Track and isolate hardware and software problems.
● Start—Executes the tracert command. ● Stop—Terminates the tracert command and leaves the Trace Route dialog box open, so that you can read the information posted in the data area. The tracert utility traces the path from your thin client to a network host. The host parameter is either a valid hostname or an IP address.
Figure 45. Telnet window 8. Click OK to save your settings.
11 BIOS management on ThinOS This appendix describes the BIOS management on the ThinOS devices with Wyse BIOS (CMOS), or Dell Standard BIOS. To make the BIOS management consistent between Wyse BIOS and Dell BIOS, an INI parameter Device=Cmos is introduced for Wyse BIOS, and Device=DellCmos for Dell Standard BIOS. If the password is configured for the BIOS configuration, then you must enter an appropriate password to update any settings.
Table 54.
a. In the file server, create a cmos.ini file and place it in the wnos directory/folder under the file server ini directory. Make sure that wnos directory on the file server has upload privilege. b. Type the following name in the cmos.ini file: Device=cmos Action=extract. 3. To reboot the reference device to the file server containing the CMOS INI file: a. On the thin client you want to use as a reference device, start the thin client. b.
a. On all of the target thin clients that you want to distribute the reference device CMOS settings, start the thin client. b. Use the Restore CMOS from USB GUI feature of ThinOS to write the CMOS settings from the USB Key to the target thin client: For Classic Desktop, Right-click the desktop and select Restore CMOS from USB. For Wyse Zero Desktop, in the General tab of the System Tools dialog box ( System Settings icon > System Tools > General tab), click Restore CMOS from USB. c.
12 Security A new global security policy has been defined for ThinOS and this policy is applied to all secure connections (https/SSL connections) with a few exceptions. Purpose—To improve the security level by default and add the global configuration. This security policy integrates security setting for each application. Table 56.
The following scenarios are allowed without need of using INI parameters: ○ Upgrade from 8.3.x firmware to 8.4 firmware. ○ Upgrade or Downgrade between 8.3.x and/or earlier firmware. ○ Upgrade or Downgrade between 8.4 and later firmware. Transport Layer Security Transport Layer Security (TLS) is a protocol that provides communication security between the client and server applications. Upgrade to Transport Layer Security (TLS)— In the ThinOS 8.2 release, the TLS is upgraded from version 1.0 to version 1.2.
13 Troubleshooting This section describes some basic troubleshooting that you can implement when you experience any problem. ● ThinOS devices allow secure SSL connections—SecurityMode=Full—only after verifying the certificates. In the present scenario, the devices enforce the warning policy after you define a server using a valid IP address.
A Examples of common printing configurations This appendix provides examples on using the Printer Setup dialog box and ThinOS INI parameters for common printing situations. Use these general guidelines in addition to the information provided in Configuring the Printer Setup. NOTE: Host-based printers are not supported.
3. Click OK to save the settings. Using INI parameters for local USB or parallel printers Configuring local printing using ThinOS INI parameters is simple and an easy way to configure a printer for all clients in your environment assuming every printer is the same. Your INI parameters will look something like the following: Printer=LPT1 \ Name="HP LaserJet 4000" \ PrinterID="HP LaserJet 4000 Series PCL" \ Enabled=yes NOTE: The PrinterID is the exact text of the Windows printer driver name, so if a printer
Using INI parameters for non-Windows network printers Configuring network printing using ThinOS INI parameters is simple and an easy way to configure a printer for all clients in your environment assuming every printer is the same. Your INI parameters will look something like the following: Printer=LPD1 \ LocalName="HP LaserJet 4200n" \ Host=10.10.10.1 \ Queue=auto \ PrinterID="HP LaserJet 4200 PCL6" \ Enabled=yes NOTE: The PrinterID is the exact text of the Windows printer driver name, so if a printer driv
Using INI parameters for Windows network printers Configuring SMB printing using ThinOS INI parameters is simple and an easy way to configure printers shared by a Windows server for all clients in your environment. The primary advantage of configuring SMB printing using ThinOS INI parameters is that you can pre-define the domain account to use to authenticate the printer. The following examples discuss how the credentials can be supplied. 1.
Using the Printer Setup dialog box for configuring LPD services From the Classic desktop mode only, a thin client can be configured to provide LPD (Line Printer Daemon) services making the thin client a printer server on the network. Set up the thin client that is to provide LPD print services as follows: To configure LPD services using the Printer Setup dialog box. 1. From the desktop menu, click System Setup > Network Setup to open the Network Setup dialog box. 2.
To configure the ThinPrint, use the following guidelines: ● Use the Printer Identification field to enter a printer class (you can change the printer name as needed).
B Important notes ● VNC RFB version upgrade—Since ThinOS 8.0_214, the VNC RFB version has been upgraded to 3.8. This version upgrade provides support for applications like DameWare. Thus, an administrator can now remote into a ThinOS device using either DameWare or VNC Viewer. Prior to 8.0_214, you could only use VNC Viewer. ● Headless boot—ThinOS supports the headless mode that enables you to boot the operating system without a monitor.
C Frequently asked questions This section contains information about the frequently asked questions (FAQs). How to enable USB Redirection in RDP windows 10 session To enable USB Redirection in RDP windows 10 session, you must change the policy. Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Service > Remote Desktop Session Host > Device and Resource Redirection > Do not allow supported Plug and Play device redirection and disable this policy.
