Dell Wyse ThinOS Version 8.5 Hotfix Administrator’s Guide February 2021 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 2021 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...........................................................................................................................................................
Configuring the general central configurations .................................................................................................. 56 Configuring the Wyse Device Agent settings.......................................................................................................57 Configuring the VPN Manager.......................................................................................................................................60 Chapter 5: Configuring the connection brokers.....
Resetting to factory defaults using shutdown reset.............................................................................. 129 Resetting display settings using V-Key reset............................................................................................ 129 Chapter 7: TCX Suite................................................................................................................. 130 Working status of TCX Flash Redirection.............................................................
Firmware upgrade using HTTP or HTTPS................................................................................................................. 173 Firmware upgrade using Wyse Management Suite version 1.1............................................................................. 174 Appendix F: Frequently asked questions.....................................................................................
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.
● Added new INI parameters. See, Dell Wyse ThinOS 8.5 Hotfix INI Reference Guide at www.dell.com/manuals.
2 Getting started Use the following information to quickly learn the basics and get started using your thin client: ● 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 ● Additional getting started details ThinOS supports the headless mode that enables you to boot the operating system without
Figure 1.
Figure 2. First Boot Wizard—network failure To configure the First Boot Wizard: 1. Connect a new thin client or existing thin client to the Ethernet using a wired connection. The existing thin client must be reset to factory default settings to enter the First Boot Wizard.
2. Turn on your thin client. The thin client checks for a wired network connection. If the network connection is successful, a welcome screen with the model name of your thin client is displayed. 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 without entering the First Boot Wizard.
● ● ● ● ● 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. 5.
● 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.
NOTE: You can also configure automatic behavior after all desktop sessions are closed by using the Remote Connections dialog box, see Central configuration: Automating updates and configurations.
Zero toolbar The Zero toolbar usually appears at the left corner of the Zero Desktop. However, depending on administrator configurations, the toolbar can be removed or hidden. It is shown only when a user moves the mouse pointer over the left edge of the desktop screen. Administrators can configure the toolbar settings using either a dialog box, see Configuring the remote configurations or the SysMode parameter in the wnos.ini file, see Dell Wyse ThinOS INI Guide. Table 2.
Table 3. Connection options (continued) Option What It Does and use the Global Connection Settings dialog box to configure settings that affect all the connection in the list. Using Zero theme Use the zero theme option to customize the look and feel of your ThinOS for Citrix, VMware, Classic or VDI mode. To enable a zero theme, deploy the INI parameters based on your zero theme preference, and restart your thin client.
The Shortcut menu is displayed. 3. On the Shortcut menu, you are able to view and use the following options: a. Administrator Mode—Allows administrators to configure various settings locally on thin client. b. Hide all windows—Brings the full desktop to the foreground. c. Copy to clipboard—Copies an image of the full screen, current window or event log to the clipboard. The clipboard contents can then be pasted to an ICA or an RDP session.
● Non-privileged users cannot view the Connect Manager. The Connection Manager dialog box is displayed. 2. In the Connection Manager dialog box, use the following buttons to configure the Connection Manager settings: a. Click Connect to select a connection from the list and make a connection. b. Click New to open the Connection Settings dialog box either directly or through the Connection Protocol menu selection for creating a new connection definition.
This process assumes that the security questions and answers have been pre-registered by the user inside their Windows environment. Users must use HTTPS (not HTTP) for an account self-service server address such as Https://IPAddress, in the Broker Setup tab. For more information, see Configuring the remote connections. After the security questions are answered, your new password will be set or your account will be unlocked.
VMware Horizon version is 4.6.45422, and so on. The components are matched to the installed packages. If the packages are removed, the field remains empty in the About tab.
3 Global Connection settings If you do not use INI files to provide central configuration (global connection settings) to users, you can use the Global Connection Settings dialog box to configure settings that affect all of the connections in your list of connections: ● Zero desktop—Click Global Connection Settings in the list of connections. ● Classic desktop—Click Global Connection Settings in the Connect Manager. To configure the Global Connection settings: 1.
Table 4. Blast H.264 decoding Screen resolution within VMware Horizon Blast session Blast H.264 decoding in VMware Horizon Blast session Summary Session display width is less than or equal to 1920 pixels. Blast H.264 decoding is always enabled. Horizon client uses Blast H.264 decoding even if the H.264 decoder setting is disabled using GUI or INI options. Session display width is greater than 1920 pixels. Blast H.264 decoding is disabled by default. You can enable Blast H.
4 Configuring the connectivity This chapter helps you to understand various configuration settings for a secure connection. Connectivity menu includes: ● ● ● ● Configuring the network settings. Configuring the remote connections. Configuring the central configurations. Configuring the VPN manager. NOTE: To configure the settings on Classic desktop, click System Setup from the desktop menu, and use the configuration tabs.
a. To set the default gateway, select the type of network interface from the available options. i. Single Network support—Either wireless or wired network is connected. ● ENET — Click this option, if you want set up the Ethernet Wired Network Connection. ● WLAN — Click this option, if you want set up the Wireless Network Connection. ● If the user use wireless network after selecting ENET connection or wired network after selecting WLAN connection, then the system log "WLAN: set default gateway xx.xx.xx.
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.
a. Ethernet Speed —Normally the default (Auto-Detect) should be selected, but another selection can be made if automatic negotiation is not supported by your network equipment. Selections include Auto-Detect, 10 MB HalfDuplex, 10 MB Full-Duplex, 100 MB Half-Duplex, 100 MB Full-Duplex, and 1 GB Full-Duplex. The 10 MB Full-Duplex option can be selected locally at the device, however, this mode may need to be negotiated through AutoDetect. b. The IPV4 check box is selected by default.
The following check boxes are displayed in the IPv6 Advanced Settings dialog box: ● Allow IPv4 to be disabled when IPv6 is enabled ● Prefer IPv4 over IPv6 when both are available ● Disable Stateless Address Auto configuration (SLAAC) ● Disable Duplicate Address Detection (DAD) ● Disable ICMPv6 Echo Reply ● Disable ICMPv6 Redirect Support ● Use Standard DHCPv6 Timers Click Properties and use the following guidelines: ● Wait DHCP—Selecting this option enables your thin client to wait for IPV6 DHCP before the
● FAST—If you select the FAST option, click Properties to open and 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. From ThinOS 8.3, EAP-FAST authentication is supported. During the initial connection, when there is a request for a Tunnel PAC from the authenticator, the PAC is used to complete the authentication.
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 page of the WLAN tab. b. Remove—Use this option if you want to remove a SSID connection by selecting the SSID connection from the list.
c. Properties—Use this option to view and configure the authentication properties of a SSID connection that is displayed in the list. d. Select the Disable Wireless Device check box, if you want to disable a wireless device. ● Always—Click this radio button if you want to disable the wireless device at all times. ● EnetUp—Click this radio button if you want to disable the wireless device whenever the wired network is connected. 3. Click OK to save the settings. NOTE: From ThinOS version 8.
a. Enter the HTTP proxy port number or HTTPS proxy port number, User name and Password in the respective fields. However, credential pass through ($UN/$PW) is not recommended because it starts before user sign on. Wyse Management Suite uses both HTTP/HTTPS and MQTT protocols to communicate with the WMS/MQTT server. However, the HTTP proxy cannot redirect TCP packages to the MQTT server which requires a SOCKS5 proxy server.
Configuring the remote connections Use the Remote Connections dialog box to configure thin client remote connections including ICA, RDP, Citrix Virtual Apps and Desktops (formerly Citrix XenDesktop), Microsoft, VMware View, Dell vWorkspace, and other broker server connections. This dialog box also enables you to configure visual options, and general connection settings.
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.
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.
● ● ● ● ● ● ● ● ● ● ● ● ● 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 Password Reset User Identity Password Update User Identity Password Enroll Proximity Card Lock/Unlock Termi
○ 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 RDP, ICA, and PCoIP.
2. Unlocking the Virtual Desktop using Fingerprint Authentication. ● Enable the Imprivata Virtual Channel from 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. This requires both supervisor and user to finish the enrollment and it is recommended to use Windows platform to perform this action. To manage fingerprints, do the following: a. Right-click the OneSign agent icon in System tray. b.
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. SSO & CM Server—Enter the IP addresses of the Single Sign-On (SSO) and Context Management (CM) Servers. b. Default Group Name—Type the name of the default group in the Default Group Name box. c. Enable logoff remote desktop ● Select the check box to log off the current user from the session before system sign-off. ● Clear the selection to disconnect from the session. 3. Click OK to save the settings. Configuring the Caradigm Vault server To configure the Caradigm Vault server on ThinOS: 1.
4. Click SSO&CM > Advanced Configurations , and use the following guidelines: a. Ensure that the Enable Proximity Support check box is selected. b. Ensure that the Enable way2care check box is selected. 5. To prepare a certificate to the Caradigm Vault Server, use the following guidelines: The Caradigm Vault Server uses the certificate to validate the connection between the Tap Server and the thin client. a.
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.
ThinOS UI configuration ● To use the HealthCast Web API, configure the HealthCast settings on the thin client side. To configure, 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 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.
registration process. This is a one-time event after which you can use the card 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 host name of the file server that provides the system software and update images. The address can be supplied through DHCP, if DHCP is used. a. File Servers/Path — Allows maximum of 127 characters for file server, and maximum of 127 characters for root path. The data specifies part of the path to be used when the server is accessed. Multiple file servers/paths may be named, as long as all data fits in the length limitation. b.
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, then it is started again automatically after a fixed time—24 hours. a.
# CA Validation DNS Record Type: DNS Text Record Name: _WMS_CAVALIDATION. Value Returned: TRUE or FALSE (as String) Example: _WMS_CAVALIDATION.WDADEV.com c. Group Registration Key—Enter the Group Registration Key as configured by your Wyse Management Suite administrator for the desired group. To verify the key, click Validate Key. A Group Registration Key is not required for the private Wyse Management Suite server.
1. Click WDM, and use the following guidelines: a. WDM Servers—Enter the IP addresses or host names, if WDM is used. Locations can also be supplied through user profiles, if user INI profiles are used. b. DNS Name Record—(Dynamic Discovery) Allows devices to use the DNS hostname lookup method to discover a WDM server. c. DHCP Inform—(Dynamic Discovery) Allows devices to use DHCP Inform to discover a WDM server. d.
3. Click New to create a new session. a. Session Name (up to 21 characters)—Enter the name of the Session Name. This is not a mandatory option. If the field is left blank, the VPN server name will be used as the session name. b. VPN server (up to 63 characters)—Enter the IP address of the VPN Server. This is defined as either an IP address or a host name. This is a mandatory option. c. Login Username (up to 31 characters)—Enter the Login Username. This is a mandatory option. d.
4. Click Connect. The connection status is displayed.
5 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. ● Windows 10 desktop in multiple brokers is supported.
Citrix HDX RealTime Multimedia Engine or RealTime Optimization Pack HDX RealTime Optimization Pack (RTOP) provides a scalable solution to deliver audio-video conferencing and Voice over Internet Protocol (VoIP) enterprise telecommunication by using Microsoft Skype for Business. The Optimization Pack supports Citrix Virtual Apps and Desktops (formerly XenDesktop) and Citrix Virtual Apps (formerly Citrix XenApp) environments to users on ThinOS devices.
Setting up the RealTime Multimedia Engine connector This section describes how to install and use Lync or Skype for Business (SFB) on a Citrix desktop. 1. Install Citrix HDX RealTime Connector on Citrix desktop VDA/Server. HDX RealTime Multimedia Engine (RTME) is the package installed on ThinOS. It is HDX RealTime Connector that needs to be installed or upgraded on the remote server and VDA. NOTE: The following are applicable to RTME 1.8 only: ● You can upgrade from RTME version 1.7 to 1.8.
● Click the Lync menu icon in the upper-right corner of the Lync application window, and click Tools > Audio Video Settings. The Citrix HDX RealTime Connector for Microsoft Lync 2013 dialog box is displayed. 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.
Known Issues with RTME 1.8 feature ● 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.
Citrix Cloud services ThinOS supports Citrix Cloud services. It acts as a single management console to deploy applications or desktops on any virtual or cloud setup for a secure digital workspace. For more information about Citrix Cloud services, see the Citrix Cloud article at docs.citrix.com. Citrix icon refresh Citrix applications can be refreshed by clicking Refresh from PNMenu.
NOTE: Warning message is displayed when you open, edit, or remove applications when you refresh the applications. 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.
● During a call, the audio device settings can be switched without plugging in or plugging out the device. ● Multiple audio can be shared across sessions. Limitations ● Wyse 3010 thin client with ThinOS and Wyse 3020 thin client with ThinOS are not supported. ● In Wyse 3030 LT thin client with ThinOS, set the DP audio as the default audio device to use DP audio in a session. Else, the DP audio will not available in the session. ● Citrix multiple audio feature does not work with HDX generic audio.
3. Click OK. If the authentication is successful, then you are logged into the Citrix session. 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.
Figure 4. Default ICA a. Server or Published Application—Select the type of connection to which the settings apply. b. Connection Description—Enter the descriptive name that is to be displayed in the connection list (38 characters maximum). c. Browser Servers—Enter a delimited (comma or semicolon) list of IP addresses or DNS-registered names of ICA servers that contain the master browsers list, or that can direct to another server that contains the list.
the application. DNS uses the default domain name in the network control panel to attempt to construct an FQDN. However, it tries to resolve the name without using the default value. e. Encryption Level—Allows you to select the security level of communications between the thin client and the ICA server. Basic (the default option) is the lowest level of security. Basic enables faster communication between the device and the ICA server because it requires less processing than the higher levels of encryption.
Figure 5. 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 6. 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.
● Support Storefront server 3.7 and later versions ● Self-Service Password Reset server 1.0 and later versions Supported platforms—All platforms are supported Limitations ● Supports only storefront server. ● The Legacy Account Self-Service (which needs Account Self-Service Server configured in ThinOS Remote Connections) is independent with this storefront version. Storefront version will cover Legacy Account Self-Service.
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 Citrix Hypervisors (formerly Citrix XenServer) deliver HTML5 multimedia web content to users. From Citrix Virtual Apps and Desktops 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.
2.
Click HDX Monitor > Graphics > Thinwire Advanced > Encoder > CompatibilityEncoder; CompatibilityEncoder. From Citrix Virtual Apps and Desktops 7.11, the Encoder is changed to Deprecated. ● For Wyse 3010 with ThinOS (T10) and Wyse 3020 with ThinOS (T10D): ○ ICA SuperCodec is always enabled without any limitation. ○ ThinOS event log displays ICA: SuperCodec enabled. NOTE: For ICA connections, there is no INI parameter.
Configuring the Citrix UPD printer Use of Citrix Universal Printer Driver (Citrix UPD) ensures that all printers connected to a client can also be used from a virtual desktop or application session without integrating a new printer driver in the data center. Citrix UPD is the base of Citrix Universal Printer. It is an auto-created printer object that uses the Citrix UPD and is not tied to any specific printer defined on the client. To configure the Citrix UPD usage on ThinOS: 1.
ii. Click Citrix Resources > XenApp > Policies > User > Settings > Printing > Client Printers and enable the Auto-create generic universal printer. iii. Click Printing > Drivers and set the Universal print driver usage to Use universal printing only from the drop-down menu available.
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.
Introduction to Flash Redirection The Flash Redirection solution is to off-load flash content to the ThinOS client, and locally render and decode the flash playback. The off-loading is conducted by Citrix HDX Flash Redirection. The local rendering and decoding process are conducted by customized flash player and other multimedia process that runs locally on ThinOS. Supported Environment— Supports only connections with Citrix Virtual Apps 6.5 and later versions and Citrix Virtual Apps and Desktops 7.
1. Upload packages to directory \wnos\pkg\. 2. Ensure that the INI autoload is not set to 0. Set INI AutoLoad=1 AddPkg=FR in wnos.ini. 3. Restart the client to read the file server and wait till the auto installation of packages is complete. You can view the installed packages in the Packages tab in the System Tools dialog box. 4. Server configuration for Flash redirection a.
f. Playback YouTube.com videos may run into some issues. For example, cannot show video unless you copy the URL and paste it to the browser. Limitation—Non-Latin URLs are not supported. Configuring VMware VMware virtualization allows 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.
Using VMware Horizon View broker and desktop VMware Horizon View Broker timeout—The VMware Horizon View Broker timeout does not force the user to sign out from the broker anymore when the secure tunnel is enabled. In earlier version of ThinOS, when the broker times out, the user session is disconnected and the user is logged out from the broker. From ThinOS 8.2 release, ThinOS disconnects the user session from the broker, but does not force user logout.
5. Click Edit > Authentication tab, and select the Enabled for unauthenticated access check box. Do not select any users for the default unauthenticated user. 6. Go to Application Pools, add a few applications that you have installed on the Virtual Machine, and entitle the applications to anonymous1 and anonymous2 user. 7. On the ThinOS broker setup dialog box for VMware View, select the Log in anonymously using Unauthenticated Access check box. 8. Restart your thin client.
To know more about the VMware Real Time Audio-Video support, go to pubs.vmware.com/horizon-62-view/topic/ com.vmware.horizon-view.desktops.doc/GUID-D6FD6AD1-D326-4387-A6F0-152C7D844AA0.html. NOTE: There is no additional configuration for ThinOS. RTAV video requires RTME package to be installed on your device. To validate the VMware Real Time Audio-Video, do the following: 1. Connect to the VMware PCoIP or Blast desktop with the audio and video devices.
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. ● Webcam preferences are not supported.
Table 7. Blast feature matrix (continued) Blast features Support on ThinOS Comments/ Known issues RDSH applications Yes Application window does not support Seamless mode. For example, all applications open in single window because of the VMware limitation. RDSH application supports the PCoIP protocol from ThinOS 8.4, with same limitation. Unified communication No Third party plug-ins are not available.
To map your printer, do the following: NOTE: LPT printer is considered as an example to explain the printer mapping scenario. Printer mapping in ThinOS works similar to LPT for LPD and SMB printers. 1. Power on the ThinOS client with the VMware View broker configured in the Broker Setup tab. Set the connection protocol as All Supported from the Connection Protocol drop-down list. 2. Go to Global Connection Settings > Session, and retain the Exclude printer devices check box selection.
Figure 9. 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.
Configuring the Microsoft Remote Desktop broker connection To configure the Microsoft Remote Desktop broker setup: 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 Microsoft, and do the following: ● Broker Server—Enter the IP address/Hostname/FQDN of the Broker Server.
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. For example, a list of WTS servers on the local network from which you can select. NOTE: The server name may be resolved using one of two mechanisms: DNS, and WINS.
5. Click the Logon tab, and use the following guidelines: a. Logging on area—Enter login username, password, and domain name. If these boxes are not populated, you can enter the information manually in the RDP server login screen when the connection is made. Use the following guidelines: ● Login Username —Maximum of 31 characters is allowed. ● Password—Maximum of 19 characters is allowed. ● Domain Name—Maximum of 31 characters is allowed. b.
a. b. c. d. Wallpaper—When selected, disables the desktop wallpaper. Menu / Window animation—When selected, disables the menu or window animation. Theme—When selected, disables the desktop themes. Show content when dragging—By default, when you grab a Window by the title bar and move it around, the contents of the window will move with it. Select this to disable this content view so that only the outline of the window moves when dragging it, until you drop the window.
Resizing the session window causes the MS media player’s frame region to dispatch. This is a server side issue. VOR codec in RDP session When you are playing video in an RDP session—Windows 8.1, Windows 2012 R2, Windows 10 and Windows 2016—VOR codec is used. The following logs are displayed in the Event Log tab. Figure 10. Event log tab NOTE: ● Dependence 1—RDP GFX status, H.264 and VOR work only when GFX is enabled. ● Dependence 2—VOR is dynamic.
Support matrix for RDP 8.1 The following table displays the support matrix for RDP 8.1: Table 8. Support matrix for RDP 8.1 Platform Support GFX Support VOR Support RDP H.264 Default GFX Default VOR Default H.264 HW/ SW decoder H.
Table 9. Supported TS Gateway versions Server operating system TS Gateway II TS Gateway III WebSocket Windows 2008 R2 Support Not support Not Support Windows 2012 R2 Support Support Not Support Windows 2016 Support Support Support NOTE: ● TS Gateway - WebSocket is a new feature introduced from ThinOS version 8.5. ● In TS Gateway II or III connection, the setup uses a two half-duplex communication between Terminal Server (TS) Gateway server and thin client.
NOTE: WebSocket connection log is hidden and not displayed in the Event Log tab. If you want to view the WebSocket connection log, go to Troubleshooting > Capture and enable Persistent for the export event log. Configuring H.264 AVC444 in RDP 10 session Prerequisites: ● Thin client must run on ThinOS version 8.5 or later. ● Windows 10 or Windows Server 2016 must be created in Microsoft RDS 2016 broker or in the latest VMware View broker. NOTE: H.264-AVC444 is also used in Windows 8.
Configuring the Amazon WorkSpaces broker connection Amazon WorkSpaces connection is applicable only for PCoIP clients. To configure the Amazon WorkSpaces (AWS) broker setup: 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 Amazon WorksSpaces, and do the following: ● Broker Server—Enter the IP address/Hostname/FQDN of the Broker Server.
6 Configuring thin client 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.
a. Screen Saver — Allows you to select the type of screen saver you want. The default is to Turn Off Screen. Other available screen savers are Flying Bubbles, Moving Image, Showing Pictures, and Playing Video. b. Timer — Select a time after which the screen saver is to be activated; either disable, 1 minute, 3 minutes, 5 minutes, 10 minutes (default), 15 minutes, or 30 minutes. When the thin client is left idle for the specified idle time, the screen saver is initiated. c.
1. From the desktop menu, click the System Setup, and then click System Preferences. The System Preference dialog box is displayed. 2. Click the Time/Date tab, and use the following guidelines: a. Time Zone— Select a time zone where the thin client operates from the drop-down list. Default value is Unspecified. b. Enable Daylight Saving— Allows you to enable the daylight saving settings.
2. Click the Custom Info tab to enter configuration strings used by WDM software. The configuration strings can contain information about the location, user, administrator, and so on. Clicking OK transfers the custom field information you enter in the dialog box to the Windows registry. The information is then available to the WDM Client Manager. For more information on using Custom Fields and using WDM for remote administration and upgrading thin client software, see WDM documentation. 3.
a. Select best display setting on DDC monitor—If the monitor is VESA DDC2B (Display Data Channel) compatible, selecting this option allows the thin client to automatically select the best resolution and refresh rate. If your monitor is not DDC compatible, then Monitor does not support Plug and Play message is displayed. remove it from the screen. b.
1920 x 1200 1920 x 1440 2560 x 1080 2560 x 1440 2560 x 1600 3440 x 1440 (Display resolution supported on Wyse 3030 LT thin client) 3840 x 2160 d. Rotation—Select a rotation option. The available options are None, Left turn 90 degrees, or Right turn 90 degrees. e. Desktop Color—Only 32-bit is permitted. This value is selected by default. f. Usage Help—This section contains brief instructions for using the Display dialog box and running the test. No operator entry can be made in this box.
For information about the tested monitors, see the latest Dell Wyse ThinOS Release Notes. Configuring the Dual Head display settings To configure the Dual Head display settings: 1. From the desktop menu, click System Setup, and then click Display. The Display dialog box is displayed. 2. Click Dual Head tab, and use the following guidelines: This feature is applicable for supported Dual Monitor capable thin clients Only. a.
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.
Table 11. Keyboard settings (continued) Parameter Description are similar to ASCII, but they contain additional characters for European languages. Keyboard Layout Presently the keyboard languages listed in the Keyboard layout drop-down list are supported. The default value is English (United States). Delay Before Repeat Specifies the repeat parameters for held-down key.
Figure 13. Audio tab a. Click the Playback Devices tab to select the type of the audio from the . ● If the HD audio and DP audio options are available in playback devices, the thin client determines the priority between HD audio and DP audio when the DP cable is connected. In this scenario, select the playback device type based on your preference, and click OK. The playback device which you select takes the priority. ● Use slider to control the volume settings for the playback devices.
Using DisplayPort audio Use the DisplayPort (DP) interface to connect your thin clients to the display devices. The interface can include audio signals in the same cable as the video signals. To enable the DisplayPort audio, ensure that you set up the following components: ● A thin client that supports DisplayPort audio and/or dual mode with audio. ● A display device, such as monitor, that supports audio playback in ICA, RDP, Blast, or the PCoIP sessions.
c. d. e. f. Parity—Click the button to select the Parity. Stop—Click the button to select the stop bits 1, 1.5, 2. Default value is 1. Size—Click the button to select the Character size 5, 6, 7, or 8 bits. Default is 8. Flow Control—Click the button to select Flow Control: Either None, XON/XOFF, CTS/RTS, or Both can be selected. Default is None. g. Serial Touch Screen selections—Select the required touch screen from the drop-down list. Available options are ELO, MicroTouch and FastPoint. h.
NOTE: From ThinOS version 8.5, the ELO touch screen does not work in certain scenarios. For more information, see the latest Dell Wyse ThinOS Release Notes. Configuring the Bluetooth settings The Bluetooth feature helps you to connect your thin client with Bluetooth enabled devices such as headsets and mouses. ThinOS supports both Intel wireless chipset 7260 and 7265. For mouse, keyboard, and headset, ThinOS supports both Bluetooth 3.0 and 4.0. Bluetooth 4.0 supports Classic and Bluetooth Low Energy (BLE).
Table 12. Bluetooth status Attribute Value Summary Status Connected The Bluetooth device is connected to the ThinOS device. It is ready to be used. Connecting The Bluetooth device is connecting to the ThinOS device. Disconnected The Bluetooth device is not connected to the ThinOS device. Yes The Bluetooth device is paired with the ThinOS device. No The Bluetooth device is not paired with the ThinOS device.
Known issues of the Bluetooth feature 1. If more than two Bluetooth mouse devices are connected to ThinOS along with more than two other Bluetooth devices, it may cause low performance of Bluetooth connectivity. Workaround: Dell recommends using one mouse and one keyboard in ThinOS with Bluetooth connection. 2. The Bluetooth device name displays N/A sometimes. Workaround: Remove this device from the list and re-scan. 3.
a. Select Port— Select the port you want from the list. LPT1 or LPT2 selects the connection to a direct-connected USB printer. b. Printer Name — (Required) Enter name you want displayed in your list of printers. most USB direct-connected printers report/fill in their printer name automatically. NOTE: If Enable LPD service for the printer is selected, the printer name becomes the queue name for other clients using LPR to print to this printer. c.
3. Click OK to save the settings. Configuring the LPDs settings To configure the LPDs settings: 1. From the desktop menu, click System Setup, and then click Printer. The Printer Setup dialog box is displayed. 2. Click the LPDs tab, and use the following guidelines when printing to a non-Windows network printer: NOTE: Be sure to check with your vendor that the printer can accept Line Printer Request print requests. a. Select LPD —Select the port you want from the list. b.
NOTE: If the printer is attached to another thin client on your network, the LPD Queue Name must match the content of the Printer Name box on the thin client with the printer attached. f. Printer Class— (Optional) Select the printer class from the list. g. Enable the printer device—Must be selected to enable the printer. It enables the device so it displays on the remote host. 3. Click OK to save the settings.
e. Printer Class —(Optional) Select the printer class from the list. f. Enable the printer device—Must be selected to enable the printer. It enables the device so it displays on the remote host. g. Enable LPD service for the printer—Select this to make the thin client an LPD (Line Printer Daemon) network print server for LPR printing requests from the network, see Using Your Thin Client as a Print Server (LPD).
Resetting to factory defaults using G-Key reset High-privileged or stand-alone users can reset the thin client to factory default settings using the G-key reset feature. To reset the thin client to factory default settings, restart the thin client and continuously tap the G key during the restart process. G-key reset impacts all configuration items, including, but not limited to, both network configuration and connections defined in local NV-RAM.
7 TCX Suite 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. The Collaborative Processing Architecture (CPA) used in Dell Wyse TCX divides the workload between the server and Plug-n-Play USB devices.
● ● ● ● ● ● ● Wyse Wyse Wyse Wyse Wyse Wyse Wyse 5010 with ThinOS (D10D) 5010 with PCoIP (D10DP) 5040 AIO thin client (5212) 5040 AIO with PCoIP (5213) 5060 with ThinOS 5060 with PCoIP 7010 with ThinOS (Z10D) Working status of TCX Flash Redirection Prerequisites ● ● ● ● TCX.i386.pkg must be installed on client for the feature to work. TFRSServerBHO Class must be enabled in browser add-on. Enable Protected Mode is turned off in the Security options of Internet Explorer.
8 Performing diagnostics Diagnostics include: ● System tools ● 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. Click the Devices tab to display all the locally attached devices, including USB, Serial, and Parallel on applicable platforms.
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.
● 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. At present, PCoIP package is mandatory for the PCoIP enabled thin clients. Other packages are optional. Base package and PCoIP package are integrated into the ThinOS firmware image.
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 (FTP/HTTPS/HTTP/CIFS) check box in the WTOS preferences in the WDM configuration manager. User Scenario a. Create or edit client configurations from WCM (JSON).
b. Select the target devices, and publish configuration settings through the Package Distribution Wizard.
For more information about Wyse Device Manager (WDM) Package Manager and Profile Manager, see the WDM Administrator's Guide. 8. Click OK to save the settings.
Simplified Certificate Enrollment Protocol Simplified Certificate Enrollment Protocol (SCEP) was used in a closed network where all end-points are trusted. The goal of SCEP is to support the secure issuance of certificates to network devices in a scalable manner. Within an enterprise domain, it enables network devices that do not run with domain credentials to enroll for certificates from a Certification Authority (CA).
NOTE: ● The CA Certificate Hash type currently supports MD5, SHA1, and SHA256. ● The request server URL can be an HTTP or HTTPs link. You can add the protocol prefix before the URL. Requesting certificate automatically Use INI parameters to automate the request, and renew the certificate process. Related INI parameters are of global scope and should be used with INI parameter ScepAutoEnroll. For more information about using the INI parameters, refer to the latest Dell Wyse ThinOS INI Reference guide.
Table 14. BTCTRoot.crt Certificate details (continued) Certificate field Default value/format Issuer Baltimore CyberTrust Root CN=Baltimore CyberTrust Root OU=CyberTrust O=Baltimore C=IE Valid from 2000–05–12 18:46:00 Valid to 2025–05–12 23:59:00 Subject Baltimore CyberTrust Root CN=Baltimore CyberTrust Root OU=CyberTrust O=Baltimore C=IE Public key RSA (2048 bits). Key bits are displayed in the lower pane of the window.
Table 15. Class3PCA_G2_v2.crt Certificate details (continued) Certificate field Default value/format C=US Public key RSA (1024 bits). Key bits are displayed in the lower pane of the window. Thumbprint algorithm sha1 Thumbprint 85 37 1c a6 e5 50 14 3d ce 28 03 47 1b de 3a 09 e8 f8 77 0f Certificate name—Class4PCA_G2_v2.crt Table 16. Class4PCA_G2_v2.
Table 17. Entrust_G2.crt Certificate details (continued) Certificate field Default value/format CN=Entrust Root Certification Authority—G2 OU=(c) 2009 Entrust, Inc. – For authorized use only OU=See www.entrust.net/legal-terms. O=Entrust, Inc. C=US Valid from 2009–07–07 17:25:54 Valid to 2030–12–07 17:55:54 Subject Entrust Root Certification Authority CN=Entrust Root Certification Authority—G2 OU=(c) 2009 Entrust, Inc. – For authorized use only OU=See www.entrust.net/legal-terms. O=Entrust, Inc.
Table 18. EquafaxCA1.crt Certificate details (continued) Certificate field Default value/format Key bits are displayed in the lower pane of the window.
Table 20. GTECTGlobalRoot.crt Certificate details Certificate field Default value/format Version V1 Serial number 01 a5 Signature algorithm md5RSA Issuer GTE CyberTrust Global Root CN=GTE CyberTrust Global Root OU=GTE CyberTrust Solutions, Inc. O=GTE Corporation C=US Valid from 1998–08–13 00:29:00 Valid to 2018–08–13 23:59:00 Subject GTE CyberTrust Global Root CN=GTE CyberTrust Global Root OU=GTE CyberTrust Solutions, Inc.
Certificate name—PCA-3G5.crt Table 22. PCA-3G5.crt Certificate details Certificate field Default value/format Version V3 Serial number 18 da d1 9e 26 7d e8 bb 4a 21 58 cd cc 6b 3b 4a Signature algorithm sha1RSA Issuer VeriSign Class 3 Public Primary Certification Authority — G5 CN=VeriSign Class 3 Public Primary Certification Authority — G5 OU=(c) 2006 VeriSign, Inc.
2. Click the General tab, and use the following guidelines: ● 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 to the USB Key or file server based on your target device selection. ● Restore CMOS—Click this option to write the CMOS settings from the USB Key to the target thin client. ● Performance Monitor—Click this option to display your thin client CPU, Memory, and Networking information.
4. Click the Capture tab to configure the Export Event Log, Network Capture to USB, Wireless Capture to USB, and capture USB packets.
If you want to enable the error messages, use the following guidelines: ● Click either One-time or Persistent option to enable logging the unexpected error message. ● Turn off logging and then check the log file under the folder ftp:/wnos/trouble_shoot. ● Be sure to enable the Enable Trace option of the Privilege parameter in a wnos.ini file. For more information, see Dell Wyse ThinOS INI Guide.
For example, for Ethernet, the file name is yx008064b2bfd7_ENET.20150415_064455.pcap. For wireless, the file name is yx008064b2bfd7_WS.20150415_064455.pcap. NOTE: Ensure that you have inserted the USB drive into the thin client before selecting the Network capture to USB option. The Network capture to USB option is automatically cleared, if there is no USB drive inserted and you exit the dialog box, or after restarting the thin client; if needed, you must select the option again. 5.
NOTE: Not all network equipment will respond to ping packets, as this is a common mechanism used in denial-of-service attacks. Lack of response does not necessarily indicate that the target of the ping is unusable for other purposes. 6. Click the Trace Route tab to execute the tracert diagnostic utility and display response messages. Use the following guidelines: ● Enter Hostname or IP — Enter the IP address, DNS-registered host name, or WINS-registered host name of the target to be traced.
9 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 23.
CMOS central management and extracting CMOS settings to the file server for distribution CMOS central management allows ThinOS administrators to easily manage CMOS settings for large deployments of thin client devices using central configuration methodologies. Wyse 5010 thin client with ThinOS (D10D) is considered here as an example. The following instructions are for Wyse 5010 thin client with ThinOS (D10D) BIOS version 3.0D.
1. To prepare a reference drive containing BIOS version 3.0D or later: a. The reference device is a golden image you use to distribute to other thin client devices. To use reference drive, enter the BIOS setup utility. Press the Delete key, enter the password — Fireport (case sensitive) and press Enter. Configure the CMOS settings, includes Auto Power, Boot Order, P-key setting, and BIOS Password. b. Save your CMOS settings. c. Restart your thin client device. 2. To extract the CMOS settings to a USB key.
Table 24. BIOS configuration options (continued) Parameters Settings ○ Select Days ● Wake-On-USB Device boot ● USB boot ● PXE boot For information about INI parameters and their usage, see the latest Dell Wyse ThinOS INI Reference Guide. The following are examples of INI parameters: ● Device=DellCmos newpassword=1234567 or newpasswordenc=encrypted strings—Use this INI parameter to create the admin password when password is not set.
10 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 25.
● Improved user-friendly messages are displayed for errors and warnings. NOTE: If the WDM server is set as https, the server address does not convert to http. Firmware signature Firmware signature feature was introduced in ThinOS 8.3.1 for better firmware security. From ThinOS 8.4 release, firmware signature verification is added to enhance firmware security. Salient features ● By default, signature verification is required on firmware downgrade/upgrade process. ● Provision to downgrade from 8.
A Automating updates and settings using central configuration This appendix describes how to set up your environment to provide your thin clients running ThinOS with automatic updates and configurations in three simple steps. NOTE: Dell Wyse thin clients do not require device management software. They are configured to obtain their IP address, as well as the location of firmware and configuration instructions, from a DHCP server.
Table 26. DHCP options (continued) Option Description Notes 53 DHCP Message Type Recommended. 54 DHCP Server IP Address Recommended. 55 Parameter Request List Sent by thin client. 57 Maximum DHCP Optional (always sent by thin client). Message Size 58 T1 (renew) Time Optional, but recommended. 59 T2 (rebind) Time Optional, but recommended. 61 Client identifier Always sent. 161 File server (ftp/http/https) Optional string. Can be either the name or the IP address of the file server.
Table 26. DHCP options (continued) Option Description Notes requires the slash to be specified in order to complete proper access. 165 WMS Server Optional string. Specifies the IP address of the Wyse Management Suite Server. 166 WMS MQTT Server Optional string. Specifies the IP address of the MQTT Server. 167 WMS CA Validation Optional string. 181 PNAgent/ PNLite server list Optional string.
Table 26. DHCP options (continued) Option Description Notes interpreted in reverse order when it is sent as 2-bytes example, the value of 0x0050 was interpreted as 0x5000. This option tag was used by old ThinOS releases. New ThinOS releases still accept this option tag for backward compatibility. 188 Virtual Desktop Broker server Optional string. 190 WDM secure port Optional number, word or two-bytes array. Specifies to use HTTPS to communicate with WDM instead of HTTP.
B 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).
C 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.
D 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. The resolution for the issue will be delivered in the next ThinOS release.
monitor is attached or powered on after 20 seconds, the monitor displays the black screen. Turn on the monitor first, and then turn on the thin client. ○ Wyse 3040 thin client and Wyse 5060 thin client: The client waits until the monitor is attached or turned on.
E Firmware upgrade Firmware upgrade is the process of updating your existing ThinOS firmware version to the latest version. To upgrade the ThinOS firmware, use any of the following: ● File Transfer Protocol (FTP) Windows server ● HTTP/HTTPS Windows server ● Dell Wyse Management Suite NOTE: Ensure that you are enrolled in our Software Maintenance Program and are eligible to receive new versions of ThinOS software and subsequent releases of corresponding documentation uploaded on Dell Digital Locker.
Table 30. Package information Package name Details Base.i386.pkg Automatically updated upon firmware upgrade. 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. FR.i386.
NOTE: ● If there is no default password or if the password is changed, then you must set your password. For example, abe@abc.com. You can also reset the thin client to factory default settings. When you reset the thin client to factory default settings, the anonymous user is configured with the default password. However, you need to reconfigure the thin client. ● You can also use DHCP option tags 161 and 162 to configure the ThinOS client, file server and path information.
7. In the General tab, enter the IP address of the file server or directory. For example: https://IPaddress/wyse. NOTE: You can also use DHCP option tags 161 and 162 to configure the ThinOS client, file server and path information. You must create these options on your DHCP server, configure them with the correct server information, and enable the DHCP server scope in your environment. 8. Click OK. 9. Restart the thin client and wait until the auto-installation of packages is complete.
F Frequently asked questions Question: How to enable USB Redirection in RDP windows 10 session? Solution—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.
