Dell Wyse ThinOS Version 8.5 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. © 2017 - 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.....
Chapter 7: Introduction to TCX Flash Redirection...................................................................... 130 Working status of TCX Flash Redirection................................................................................................................. 130 Chapter 8: Performing diagnostics............................................................................................. 131 System tools.........................................................................................
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.
● ThinOS UI-based updates: ○ Added a First Boot Wizard for a new or factory reset thin client. See, Configuring ThinOS using First Boot Wizard. ○ Added support for zero theme. See, Using zero theme. ○ Added a desktop wallpaper. Dell Wyse ThinOS v8.5 Release Notes. ○ Added the About tab in System Information. See, Accessing system information. ○ Added option to capture, and export screenshots. See, Using the troubleshooting options. ○ Added option to export the INI file.
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 NOTE: ThinOS is centrally managed and configured using INI files to automatically push u
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.
○ The option to define a wireless connection is not available on thin clients without a WLAN module. ○ 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.
● Citrix—The broker allows you to connect to full desktops using XenDesktop or individual applications using 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. ○ StoreFront style—Select this check box to enable the Citrix StoreFront based layout of published applications and desktops on the thin client.
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 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.
the URL that is centrally defined by file servers by using the Remote Connections dialog box as described in Remote Connections. ○ 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.
○ Microsoft Broker or RDP version ○ Teradici PCoIP version—This represents the PCoIP revisions between the ThinOS versions, and is applicable to the PCoIP devices only. ○ Imprivata version ○ Caradigm version ○ SECUREMATRIX version ○ HealthCast version NOTE: ○ Kernel mode—The components are implemented in Kernel according to the specification. The version is displayed as [max].[min], which is the base version of protocol or server or client of the component.
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.
a. Select the Enable H264 check box. This option allows H.264 decoding in Horizon Client. Enabling this option, improves the performance of high-end applications. To validate the H.264 decoding, navigate to the /tmp/vmware-user/ directory, open the vmware-mks-pid.log file, and check if the H264 support is enabled entry is registered in the log file. NOTE: ● Blast H.264 feature is not supported on Wyse 5010 thin clients, Wyse 5040 thin clients, and Wyse 7010 thin clients. 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 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 is added to the OneSignServer=AutoAccess=command. 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. Notes on Imprivata Bio-metric Single Sign-On ● Supported protocols are RDP, ICA, and PCoIP.
● Fingerprint authentication works on the ThinOS unlock window. 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. Click Manage Fingerprints, and enter the correct credentials in the displayed window to manage your Fingerprints. 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.
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, then 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.
6. Click OK to save the settings. The Wyse Device Manager option can be disabled using the following INI parameters: ● WMSService=no ● Service=wdm disable=yes ● RapportDisable=yes Configuring the VPN Manager VPN Manager is included to manage VPN connections. 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.
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 XenDesktop and XenApp environments to users on ThinOS devices. For more information about HDX RealTime Optimization Pack, see Citrix documentation.
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: ● The Upgrade option from 1.7 to 1.8 is discussed at docs.
● 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 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 then 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.
● 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. The resolution for the issue will be delivered in the next ThinOS release. 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 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 3. 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 appear 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 contains the master browsers list, or that could refer to another server that contains the list.
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 allows faster communication between the device and the ICA server because it requires less processing than the higher levels of encryption. NOTE: The encryption selection applies to the security of communications between the thin client and the ICA server only.
If the Login User name, Password, and Domain name boxes are not populated, you can enter the information manually in the ICA server login screen when the connection is made: ● 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.
● 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. ● The security question enrollment is not supported in Virtual Desktop Infrastructure (VDI) mode.
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.
2.
Click HDX Monitor > Graphics > Thinwire Advanced > Encoder > CompatibilityEncoder; CompatibilityEncoder. From XenDesktop/ XenApp 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 XenApp/XenDesktop 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 Citrix Connections with XenApp 6.5 and later versions and XenDesktop 7.0 and later versions.
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. In some scenario the video shows no content initially; when user resizes browser the video appears normally; it is likely to happen with x86 desktops and is a known issue for Citrix HDX FR Linux client. g. Playback with videos that can work with HDX FR on Linux or Windows client: There are a number of videos/websites known as not working with Citrix HDX FR solution such as msn.com, espn.com, movies.yahoo.com, and dell.com. Flash videos simply cannot load with these websites using HDX FR solution.
○ PCoIP only—This option is available only for PCoIP enabled clients. Select this protocol connection to display only the desktop in the PCoIP connection, for each pool in the broker. If a desktop pool is configured with default protocol as RDP in the View Admin console, and allow user to select protocol as no, then this desktop is not displayed in ThinOS after user signs in to the device.
USB redirection RDS desktop through PCoIP—This feature is supported. Using unauthenticated access—You can anonymously log in to the VMware session with application remoting. To use the unauthenticated option, do the following: 1. On your AD server, create two anonymous users, for example, anonymous1 and anonymous2. 2. Log in to your View Admin web portal. 3. Navigate to Users and Groups > Unauthenticated Access, and add the two new anonymous users to the View Connection Manager. 4.
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. Hide Domain List—The domain list can be hidden in the Horizon View Broker logon UI.
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.
Supporting 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.
Table 6. Blast feature matrix Blast features Support on ThinOS Comments/ Known issues VPN connect Yes N/A AES 128/256 Yes See, ThinOS AES design. Multi-display/ 4K/ 32-bit Yes See, VMware Blast support information. For example, the pre-requisite is VM video RAM. ClearType fonts support Yes ThinOS supports the TrueType fonts 3D display Yes See, VMware Blast support information Blast recovery from network interrupt Yes Requires Horizon View agent 7.0.
Figure 6. 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 7. 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 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.
2. Use the mouse to change the size of the session window. Resizing the session window causes the MS media player’s frame region to dispatch. This is a server side issue. Features of RDP 8.1 Remote Desktop Protocol (RDP) H.264 and VOR is enabled by default for all ThinOS v8.5-based devices. Remote desktops such as Window 8, Window 8.1, Window 10, Windows Server 2012 R2 and Windows Server 2016 are supported in this release. The following are the dependencies of RDP 8.1: ● Dependence 1—RDP GFX status, H.
● When the feature is disabled, the following screen is displayed in the Event Log tab for disablement: ● Also, when client resource used exceeds VOR limitation, there is no event log for VOR disablement. Work flow of dual display In dual display, the RDP feature only works within a limited resolution. The ‘maximum resolution possibly for the session’ for H.264 enablement is as follows: ● RDP without force span which is the same as single display.
Table 7. Support matrix for RDP 8.1 Platform Support GFX Support VOR Support RDP H.264 Default GFX Default VOR Default H.
2. Connection with TS gateway configured in unsupported OS (e.g. Windows Server 2008 R2), it uses TS gateway II and the logs are displayed as shown in the following screenshot: 3. When remote connection with TS gateway III closed: There are no additional logs displayed in the Event Log tab. Supporting RDP H.264 AVC444 RDP uses the ITU-T H.264 graphics compression (codec), also known as MPEG-4 AVC (Advanced Video Coding). In RDP 10, AVC/H.264 supports the full-screen AVC 444 mode.
set of software or hardware, instead of using a different codec. This results in more scalability on system work load and network bandwidth occupation. NOTE: In ThinOS v8.5, the RDP 8.1 session uses the original H.264 codec. For more information about Remote Desktop Protocol (RDP)10 AVC/H.264 improvements in Windows 10 and Windows Server 2016, see cloudblogs.microsoft.
● Select the check box to enable vWorkspace Gateway. ● vWorkspace Gateway—Enter the IP Address of the vWorkspace Gateway. 3. Click OK to save the settings. Configuring Amazon Web Services or WorkSpaces Amazon WorkSpace is a cloud-based virtual desktop that allows you to access remote applications with ease. Amazon WorkSpaces connection is applicable only for PCoIP clients running ThinOS 8.3, and later versions.
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, selection of 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. Click OK to acknowledge the message and remove it from the screen. b.
2560 x 1080 2560 x 1440 2560 x 1600 3840 x 2160 d. Rotation —Select a rotation option; either None, Left turn 90 degrees, or Right turn 90 degrees. e. Desktop Color— Only 32 bit is permitted from ThinOS 8.2. 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. Make note of the instructions in the area, regarding v-key reset usage in case of display failure. 3.
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. 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.
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 9. Keyboard settings Parameter Description Character Set Specifies the character set. Each character is represented by a number. The ASCII character set, for example, uses the numbers 0 through 127 to represent all English characters and special control characters. European ISO character sets 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.
2. Click the Audio tab to select the volume settings for connected devices. a. Click the Playback Devices tab to select the type of the audio from the drop-down menu. ● Use slider to control the volume settings for the playback devices. ● Select the check box to mute. b. Click the Recorded Devices tab to select the type of the record from the drop-down menu. ● Use slider to control the volume settings for the record devices. ● Select the check box to mute. c. Click Play to play the audio. d.
● ThinOS supports only the DisplayPort audio playback. Audio recording using DisplayPort is not supported. ● DisplayPort audio is supported only on Wyse 3030 LT thin client, Wyse 3040 thin client, and Wyse 5060 thin client. Disabling DisplayPort audio In Wyse 3040 thin client, the DP audio is enabled by default. However, in certain resolution, such as, 1920 x 1200, 2048 x 1152, 2048 x 1280, 2560 x 1080, 2560 x 1440, a black screen is displayed for 10 seconds after you restart the thin client.
Configuring the camera settings Use the Camera tab to interface with cameras that are locally connected to the thin client (USB) and supported by a UVC driver. When using the HDX RealTime webcam feature of XenDesktop/XenApp, you can control options such as maximum resolution and frames per second (10 FPS is recommended). By default, the format of USB camera is set to RAW.
NOTE: From ThinOS v8.4.1, the Bluetooth feature is supported on Wyse 3040 thin client with ThinOS and Wyse 3040 thin client with PCoIP. To configure the Bluetooth settings: 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.
Table 10. Bluetooth status connected to the ThinOS device. Paired Yes The Bluetooth device is paired with the ThinOS device. No The Bluetooth device is not paired with the ThinOS device. ● Address—Displays the address of the Bluetooth device connected to your thin client. The following are the user scenarios and corresponding Bluetooth statuses displayed on the Bluetooth page. Table 11.
USB support USB port—Wyse 7010 with ThinOS (Z10D) supports two USB 3.0 ports. USB 3.0 is compatible with USB 2.0. When USB 2.0 device is connected to 3.0 ports, the behavior of the device remains unaltered. For USB 3.0 device to connect to 3.0 ports, the device type should be of 5 Gbps. All types of USB devices work when connected to USB 3.0 port. USB hard disk—Do not plug in the USB hard disk with 10 or more drives, or do not plug in more than 10 USB keys into ThinOS client.
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.
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. Printer Name —(Required) Enter name you want 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.
Configuring the SMBs settings To configure the SMBs settings: 1. From the desktop menu, click System Setup, and then click Printer. The Printer Setup dialog box is displayed. 2. Click SMBs tab, and use the following guidelines when printing to a Windows network printer. 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.
1. From the desktop menu, click System Setup, and then click Printer. The Printer Setup dialog box is displayed. 2. Click the Options tab, and use the following guidelines: 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.
1. From the desktop menu, click Shutdown. The Shutdown dialog box is displayed. 2. After starting your thin client you will see a Dell logo for a short period of time. 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.
7 Introduction to TCX Flash Redirection The Dell Wyse TCX Suite is a single software solution that provides full benefits of cloud client-computing without the limitations of competing software suites. The TCX Flash Redirection is one of the components of TCX Suite that enables the cloud client users to experience improved Flash video content performance in a remote computing environment. TCX Flash Redirection uses the client CPU to decode and render flash.
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.
a. Click the Delete button to delete the selected package. b. Click the Delete all button to delete all the packages. The following packages are displayed in the Package tab: ● base.i386.pkg ● FR.i386.pkg—This package is introduced to support Flash Redirection. ● RTME.i386.pkg—This package is introduced to support Citrix RTME. ● Horizon.i386.pkg—This package is introduced to support VMware Blast protocol. The package version number is updated to match the latest Horizon client.
6. Click the User INI tab to view wnos.ini information. 7. Click the WDM INI to view the received WCM configurations.
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 WDM Package Manager and Profile Manager, refer to the WDM Admin Guide. 8. Click OK to save the settings.
Simplified Certificate Enrollment Protocol Simplified Certificate Enrollment Protocol (SCEP) was designed to be 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).
3. Click Ok to save the changes. NOTE: ● If the SCEP server is on Windows Server, the CA certificate HASH provided by MS Windows server is always an MD5 hash type. ● Request server URL must be an HTTP link. Do not add protocol prefix for HTTPS, and so on. Requesting certificate automatically Use INI parameters to automate the request and renew certificate process. Related INI parameters are of global scope and should be used with INI parameter ScepAutoEnroll.
Table 12. BTCTRoot.crt Certificate details Certificate field Default value/format Serial number 02 00 00 b9 Signature algorithm sha1RSA 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 13. Class3PCA_G2_v2.crt Certificate details Certificate field Default value/format OU=Class 3 Public Primary Certification Authority – G2 O=VeriSign, Inc 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 14. Class4PCA_G2_v2.
Table 15. Entrust_G2.crt Certificate details Certificate field Default value/format Issuer 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. 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.
Table 16. EquafaxCA1.crt Certificate details Certificate field Default value/format Key bits are displayed in the lower pane of the window.
Table 18. 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 20. 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 BIOS management consistent between Wyse and Dell BIOS, INI parameter Device=Cmos is introduced for Wyse BIOS, and Device=DellCmos for Dell Standard BIOS. For BIOS configuration, if the password is configured, to update any settings, the password is required to be supplied.
Table 21.
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 22. BIOS configuration options ○ Select Days 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. ● Device=DellCmos currentpassword=1234567 newpassword="" or currentpasswordenc=encrypted strings—Use this INI parameter to clear the existing password.
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 23.
● Wyse Management Suite, Microsoft RDS broker, Citrix broker, and SecureMatrix are always Full. File Server default protocol is retained as FTP without any setting from WDM/DHCP/INI and always displays the full address with protocol prefix. For example, ftp://. New firmware/client deploy information ● Dell recommends you to define the Security Policy before upgrading to version 8.3 and later. If not, you may get warning messages that require intervention to proceed. ● Before upgrading to version 8.
For warning security mode, the following warning messages are displayed: The server address does not convert to http, if WDM server is set as https. ● In the previous scenario, If WDM server is configured without HTTPS, and local WDM server address is specified in HTTPS, then the system converts it to HTTP address. ● In the current scenario, the system does not convert the WDM server address to HTTP. Manual discovery is removed from WDM. In the WDA tab, the Manual discovery method option is removed.
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. By default, the ThinOS client uses TLS 1.2 to secure any communication protocols, connections, or applications upon SSL/ TLS in general and falls back to the previous SSL/ TLS version when negotiating with the server.
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 24. DHCP options (continued) 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 24. DHCP options (continued) 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 24. DHCP options 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. 192 WDM server port Optional number, word or two-bytes array.
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 ● Wyse Management Suite version 1.1 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.
Installing the Windows IIS creates the directory C:\inetpub\ftproot, which is known as the FTP root. In the ftproot directory, create a folder wyse and a sub folder wnos. The directory structure must read as C: \inetpub\ftproot\WYSE\wnos. To upgrade the ThinOS firmware using FTP server: 1. Sign in to the Dell Digital Locker. 2. Download the latest ThinOS firmware and latest ThinOS packages that corresponds to your thin client model.
4. Add the two MIME types. Use .INI and . for the associated extension fields. 5. Apply the settings and close the IIS admin console. Installing IIS creates the default directory C:\inetpub\WWWroot, which is known as the WWW root. In the WWWroot directory, create a folder WYSE and a sub folder wnos. The directory structure must read as C: \inetpub\wwwroot\WYSE\wnos. To upgrade the ThinOS firmware using HTTP or HTTPS server: 1. Sign in to the Dell Digital Locker. 2.
8. Select the check box that corresponds to your ThinOS firmware file. 9. On the Groups & Configs page, select a custom group, and click Edit Policies > ThinOS. The Select ThinOS Configuration Mode screen is displayed. 10. Click Advanced Configuration. 11. In the Device Configuration pane, click Firmware Upgrade, and then click Configure this item. 12. From the Platform type drop-down list, select your thin client model. 13.
F Frequently asked questions 1. How to enable USB Redirection in RDP windows 10 session ? Change 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 disable Play device redirection. 2. How to enable ICA SuperCodec on XenDesktop 7.
If you select Use video codec when available, ICA SuperCodec is enabled for both HDX 3D Pro desktop and non-HDX 3D Pro desktop. NOTE: In XenDesktop 7.15, Citrix has introduced new names and options for this policy. With the default settings (the new Selective Adaptive Display version 2), ThinOS does not use the SuperCodec unless you enable the Video Compression Codec to be used for the entire screen.
