Dell Wyse ThinOS Release 8.3.
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. © 2016 - 2018 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction....................................................................................................................................................6 About this Guide.................................................................................................................................................................6 Technical Support...............................................................................................................................................
Configuring the WDA Settings.................................................................................................................................59 Configuring the VPN Manager.......................................................................................................................................62 5 Configuring Thin Client Settings..................................................................................................................66 Local Settings Menu.................
B CMOS Management.................................................................................................................................. 153 CMOS Central Management: Extracting CMOS Settings to the File Server for Distribution..............................153 CMOS Local Management: Extracting CMOS Settings to a USB Key for Distribution........................................ 154 C Examples of Common Printing Configurations...........................................................................
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.
Technical Support To access Dell Wyse Cloud Client Management technical resources (self-service portal, knowledge base, software downloads, registration, warranty extensions/RMAs, reference manuals, and so on), see http://www.dell.com/wyse/support. For more information, you can call Customer Support at 1.800.800.9973 (toll free in U.S. and Canada). Hours of operation are from 6:00 A.M. to 5:00 P.M. Pacific Time, Monday through Friday.
2 Getting Started: Quickly Learning the Basics Use the following information to quickly learn the basics and get started using your thin client: • 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 update
Central Configuration — If you are configured for automatic detection using INI files — see Dell Wyse ThinOS INI Guide , your thin client will automatically detect and connect to the configured remote services during the boot-up process. Press the power button to turn on your thin client to see the Login dialog box. Enter your User name, Password, and Domain, and then click Login. After authentication is successful, your available connections are presented.
In any desktop case, you can select the desktop option you want (Classic Desktop or Zero Desktop) and create the connections you need using the Visual Experience tab on the Remote Connections dialog box. To open the Remote Connections dialog box, perform one of the following tasks: • Classic Desktop — Click User Name , and then select System Setup > Remote Connections.
• Classic Desktop — Click Shutdown in the Connect Manager or Desktop Menu. • Zero Desktop — Click the Shutdown icon on the Zero Toolbar. 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.
NOTE: • You can copy and paste between application sessions and between sessions and the desktop, however, this function depends on session server configurations. • In addition to the standard two-button mouse, the thin client supports a Microsoft Wheel Mouse used for scrolling. Other similar types of a wheel mouse may or may not work. To switch the left and right buttons, use the Peripherals dialog box, see Configuring the Peripherals Settings.
Table 2. Connection Options Option What It Does Name of the connection Opens the connection you want to use. NOTE: All open connections display a blue icon to the left of the connection name in the list. Reset icon Resets the connection. NOTE: It is useful when a connection is not functioning properly or you need to reboot the connection. Close icon Closes the connection. NOTE: The Close icon is grayed out for connections that are not open.
• Clicking the User Name or clicking on the desktop, opens the Desktop Menu, see Using the Desktop Menu. NOTE: User Name is the user who is logged-on and is located at the lower-left pane of the task bar.
• Peripherals — Allows you to select the peripherals settings such as keyboard, mouse, volume and touch screen settings. For more information, see Configuring the Peripherals Settings. • b c d e f Printer — Allows configuration of network printers and local printers that are connected to the thin client. For more information, see Configuring the Printer Settings. System Information — Provides thin client system information. See Accessing System Information .
For more information on the Connection Settings dialog box, refer to Advanced Details on Configuring ICA and RDP Connections. Be aware of the following information: d e f g • High-privileged user — Can view and edit the definitions for the currently selected connection. Edits are not permanently retained when the user signs-off. • Low-privileged user — Cannot create or edit connections, but can view connection definitions.
Accessing System Information Use the System Information dialog box to view system information. • Classic Desktop — Click System Information from the desktop menu. • Zero Desktop — Click the System Information icon on the zero toolbar.
Following is the screenshot displaying the Event Log tab for Monitors details: • Status Tab — Displays status information about TCP performance related parameters, UDP performance related parameters, CPU Busy, System Up Time, CCM status, Free Memory, Active sessions, and WDM status. • IPv6 Tab — Displays IPv6 information such as Link-local Address, IPv6 Address and IPv6 Default Gateway.
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.
NOTE: ICA sessions always have automatic connection to attached smart card readers. When using the Disks check box for automatic connection to connected USB sticks, use the following guidelines: • More than one disk can be used at the same time, however, the maximum number of USB sticks including different subareas is 12. • Be sure to save all data and sign off from the session mapping the USB stick before removing the USB stick.
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. IMPORTANT: To configure the settings on Classic desktop, click System Setup from the desktop menu, and use the configuration tabs.
2 Click the General tab, and use the following guidelines: a To set the default gateway, select the type of network interface from the available options. 1 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.
is used to make the connection. These entries can be supplied through DHCP, if DHCP is used. DNS and WINS provide essentially the same function, name resolution. If both DNS and WINS are available, the thin client attempts to resolve the name using DNS first and then WINS. f 3 You can enter two WINS Server addresses (primary and secondary), separated by a semicolon, comma, or space. Enter the digit multiplier of 30 seconds in the TCP Timeout box to set the time-out value of a TCP connection.
d 3 DHCP UserClass ID — Shows the DHCP UserClass ID when the dynamically allocated over DHCP/BOOTP option is selected. Click OK to save the settings. Configuring the ENET Settings To configure the ENET settings: 1 From the desktop menu, click System Setup, and then click Network Setup. The Network Setup dialog box is displayed.
• Statically specified IP Address — Select this option to manual enter the IP Address, Subnet Mask and Default Gateway: • IP Address — Must be a valid network address in the server environment. The network administrator must provide this information. • Subnet Mask — Enter the value of the subnet mask. A subnet mask is used to gain access to machines on other subnets. The subnet mask is used to differentiate the location of other IP addresses with two choices: same subnet or other subnet.
NOTE: Using only the FQDN, that is company.wyse.com does not work. You must use one of the options (note that *.wyse.com is the most common option as multiple authentication servers may exist): servername.wyse.com *.wyse.com *wyse.com *.com f g LEAP — If you select the LEAP option, click Properties to open and configure the Authentication Properties dialog box. Be sure to use the correct Username and Password for authentication. The maximum length for the username or the password is 64 characters.
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. b c After you configure the SSID connection, the added SSID connection is listed on the page of the WLAN tab. Remove — Use this option, if you want to remove a SSID connection by selecting the SSID connection from the list.
d e Properties — Use this option to view and configure the authentication properties of a SSID connection that is displayed in the list. Select the Disable Wireless Device check box, if you want to disable a wireless device. 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.
• User credential pass through is possible with $UN/$PW. • For CCM, HTTP, HTTPS and Socks5 (recommended) protocols are supported. 1 From the desktop menu, click System Setup, and then click Network Setup. The Network Setup dialog box is displayed. 2 Click the Proxy tab, and use the following guidelines: a Enter the HTTP proxy port number or HTTPS proxy port number, Username and Password in the respective fields.
Configuring the Broker Setup To configure the Broker setup: 1 From the desktop menu, click System Setup, and then click Remote Connections. The Remote Connections dialog box is displayed. 2 Select Broker type from the drop-down list. a If you select None from the list, click either of the following connection protocols: • b 30 ICA — For more information, see Configuring ICA Connections. • RDP — For more information, see Configuring RDP Connections.
• Select the check box to enable automatic reconnection at logon. NOTE: If you enable the automatic reconnection, you are able to select from the reconnection options. Click either of the options where you can connect to the disconnected sessions only or connect to both active and disconnected sessions. • Select the check box to enable automatic reconnection from the button menu. NOTE: If you enable the automatic reconnection, you are able to select from the reconnection options.
f g • Auto Connect List—Enter the name of the desktops that you want to launch automatically after logging in to the respective broker. More than one desktop can be listed. Each desktop name is separated by a semi-colon, and is case-sensitive. • Select the check box to enable vWorkspace Gateway. • vWorkspace Gateway— Enter the IP Address of the vWorkspace Gateway. If you select Other, you must enter the IP address of the Broker server in the Broker Server box.
For information about deploying AWS WorkSpaces and AWS EC2 PCM for AWS WorkSpaces, go to www.teradici.com/webhelp/Connecting_ZC_AWS_HTML5/TER1408002_Connecting_ZC_AWS.htm#03_DeployPCM.htm%3FTocPath%3D3. For information about configuring the Broker Server address = “URI (https://) of the PCM”, go to www.teradici.com/web-help/Connecting_ZC_AWS_HTML5/TER1408002_Connecting_ZC_AWS.htm#05_Connect.htm %3FTocPath%3D5.
The following are the screenshots of PCoIP enabled on Wyse 3030 LT thin client with PCoIP, Wyse 5010 thin client with PCoIP (D10DP), Wyse 5040 AIO thin client with PCoIP (5213), and Wyse 5060 thin client with PCoIP.
• 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.
In the Disclaimer window, if you click Accept, you are directed to the user login window. If you click Cancel, the user login window displays the message broker initialization failed. • Changes applicable to Wyse 3030 LT thin client with PCoIP, Wyse 5010 thin client with PCoIP (D10DP), Wyse 5040 AIO thin client with PCoIP (5213), and Wyse 5060 thin client with PCoIP. • PCoIP session NUM/CAP keyboard status synchronizes with session instead of thin client This is applicable for session startup only.
• USB redirection RDS desktop through PCoIP This feature is not supported in this version. The same limitation applies to the VMware Horizon View Linux client as well. Supporting the VMware Real Time Audio-Video Use the Real-Time Audio-Video feature to run Skype and other online conference applications on the remote desktop. Using this feature, both audio and video devices that are connected to your thin client are available to use for VoIP in remote desktop.
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/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, 2008R2/ 2012R2 according to VMware. • Support for PCoIP protocol only. RDP protocol is not supported according to VMware. • Webcam preferences are not supported.
The following message is displayed in the lower right pane during application refresh. 2 Applications are refreshed in Session bar list, Connect Manager list and App menu list. The following log is displayed in the Event Log window: ICA: refresh store “xxx”…” or “ICA: refresh PNAgent”xxx”… 3 For MultiFarm (StoreFront or PNAgent servers) or Multilogon (StoreFront or PNAgent servers), select a single server to refresh or click Refresh All to refresh all servers.
5 The disconnect session can be reconnected after application refresh, if Automatic reconnection at logon is enabled in remote connection. Refreshing the Citrix Applications Automatically Using INI Parameter To automatically refresh the Citrix application, set the following INI parameter: SessionConfig=ICA RefreshTimeOut=dd:hh:mm For example, 01:01:22, means the application will start refresh automatically, every 1 day: 1 hour: 22 minutes.
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 b 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. Zero Launchpad — Displays the new launch pad style GUI designed for VDI use.
Configuring the General Options To configure the general options: 1 From the desktop menu, click System Setup, and then click Remote Connections. The Remote Connections dialog box is displayed. 2 Click the General Options tab, and use the following guidelines: a b c d e 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.
The Remote Connections dialog box is displayed. 2 Click the Authentication tab, and select the authentication type. Three types of authentication are displayed. 3 • Imprivata— Configuring the Imprivata OneSign Server. • Caradigm—Configuring the Caradigm Server. • SECUREMATRIX— Configuring SECUREMATRIX. After configuring your preferred authentication, click OK to save the settings.
• Citrix Xen Desktop • VMware View • Kiosk Mode • Fast User Switching • Non-OneSign user VDI access • Hotkey Disconnect • Proximity card reader redirection • Guided Question and Answer login • Authenticate w/Password • Authenticate w/Password + Password Change • Authenticate w/Password + Password Change | New Password is Invalid • Authenticate w/Proximity Card + Password • Authenticate w/Proximity Card + Pin • Authenticate w/Proximity Card + Pin | Pin not enrolled • Authenticate
• • 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 • 2 • 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. If set to 0, logs are not displayed.
• Lock Screen type —Only obscure type is supported. • Hot key to lock workstation or log off user— ThinOS can support following keys: “F1 ~ F12”, "BKSP", “DEL”, “DOWN”, “END”, “ENTER”, “ESC”, “HOME”, “INS”, “LALT”, “LEFT”, “LCONTROL”, “NUMLOCK”, “PGDN”, “PGUP”, “RCONTROL”, “RIGHT”, RTALT”, “SPACE”, “TAB”, “UP”, “a~z”, “A~Z”, “0~9” and modifier “+”, “%”, “^” (Shift, Alt and Control) • 3 Suspend action — The server configuration controls this feature on ThinOS.
• The largest size supported by ThinOS is 17 characters. ThinOS UI: 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.
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 • ARM platforms (T/TD) are not supported. • Supported protocols are RDP, ICA, and PCoIP.
• 2 Fingerprint authentication works on the ThinOS unlock window. Unlocking the Virtual Desktop using Fingerprint Authentication. • Enable the Imprivata Virtual Channel from ThinOS Global Connection Settings.
• 52 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.
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 54 Click the Authentication tab, and then click Caradigm.
a b c 3 SSO & CM Server—Enter the IP addresses of the Single Sign-On (SSO) and Context Management (CM) Servers. Default Group Name—Type the name of the default group in the Default Group Name box. 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. Click OK to save the settings.
3 56 On the Caradigm Vault Server, use the following guidelines: • Ensure that the Enroll unenrolled badges option is checked. • Make sure that all Badge ID mapping entries are deleted.
4 Click SSO&CM > Advanced Configurations , and use the following guidelines: a b 5 Ensure that the Enable Proximity Support check box is selected. Ensure that the Enable way2care check box is selected. 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.
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.
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 b c 3 File Servers/Path — Allows maximum of 128 characters. 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. Username — Enter the username to log in to the file server.
If the first discovery, for example, the WDM service is not successful, then it seeks for the next priority, for example, CCM service. This continues till a discovery is successful. If all discoveries fail, then it is started again automatically after a fixed time (24 hours). a b c d 3 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.
The following is the INI parameter for this feature: WDAService={yes(default),no}Priority ={WDM(default),CCM,“WDM;CCM”,“CCM;WDM”} To configure the CCM settings, do the following: 1 Click CCM, and use the following guidelines. a Enable Cloud Client Manager (CCM) — Select the check box to enable the Cloud Client Manager(CCM).
b Group Registration Key — Enter the Group Registration Key as configured by your cloud Client Manager administrator for the desired group. NOTE: If you enable the Cloud Client Manager (CCM ), make sure that you have entered the Group Registration Key and enabled the CCM Advanced Settings. 2 Click OK to save the settings. Configuring the VPN Manager VPN Manager is included in ThinOS 8.1 to manage VPN connections.
In Zero Mode, user can view the VPN Manager tab in System Settings panel. 2 Click VPN Manager. The VPN Manager dialog box is displayed.
3 Click New to create a new session. a b c d e f g 64 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. 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. Login Username (up to 31 characters) – Enter the Login Username. This is a mandatory option.
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 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.
Setting the General System Preference To configure the general settings for system preference: 1 From the desktop menu, click System Setup, and then click System Preferences. The System Preference dialog box is displayed. 2 Click the General tab, and use the following guidelines: a b c Screen Saver — Allows you to select the type of screen saver you want. The default is to Turn Off Screen.
d • Check Cable, No Ethernet link • Leave administrator mode • Connecting • Sign off from account • Lock Terminal, Unlock Password • Terminal is locked, Invalid unlock password Terminal Name — Allows entry of a name for the thin client. The default is a 14-character string composed of the letters WT followed by the thin client Ethernet MAC address. Some DHCP servers use this value to identify the IP address lease in the DHCP Manager display. 3 Click OK to save the settings.
e f 3 Time Servers — List of IP addresses or host names with optional TCP port number of Time Servers. Each entry with optional port number is specified as Name-or-IP: port, where: port is optional. If not specified, port 80 is used. Locations can be supplied through user profiles if user profiles are used. The Time Servers provide the thin client time based on the settings of time zone and daylight saving information. If DHCP is used, locations can be supplied through DHCP.
• Configuring the Dual Head Settings Configuring the General Display Settings To configure the general display settings: 1 From the desktop menu, click System Setup, and then click Display. The Display dialog box is displayed.
1280 x 720 1280 x 768 (not on T10) 1280 x 1024 1360 x 768 (not on T class) 1366 x 768 1368 x 768 (not on T class) 1400 x 1050 1440 x 900 1600 x 900 1600 x 1200 1680 x 1050 1920 x 1080 1920 x 1200 1920 x 1440 (R class only) 2560 x 1080 (Single monitor only; R class and D/Z class only) 2560 x 1440 (Single monitor only; R class and D/Z class only) 2560 x 1600 (Single monitor only; R class and D/Z class only) 3840 x 2160 (Single monitor only; D/Z class only) Refresh rate list selections include: 60 Hz (default)
1152 x 864 1280 x 720 1280 x 768 1280 x 1024 1360 x 768 1366 x 768 1368 x 768 1400 x 1050 1440 x 900 1600 x 900 1600 x 1200 1680 x 1050 1920 x 1080 1920 x 1200 2560 x 1080 2560 x 1440 2560 x 1600 3440 x 1440 3840 x 2160 Dual 3840 x 2160 is supported with Dual Display ports for 30 Hz display refresh rate.
This feature is applicable for supported Dual Monitor Capable Thin Clients Only. a b c 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. Main Screen—Select which of the two monitors you want to be the main screen (Screen1 or Screen2). The other screen is extended from the main screen. The other screen is extended from the main screen.
For Swap dual screens, when you set Main Screen to Screen2, an additional check box is displayed at the bottom of the tab that allows you to swap dual screens. If you clear the check box, the Screen1 is usually the left one or the top one in dual display. When you set Main Screen to Screen2, the main screen is changed to the right screen or bottom screen.
• Configuring the Touch Screen Settings • Configuring the Bluetooth Settings Configuring the Keyboard Settings To configure the Keyboard settings: 1 From the desktop menu, click System Setup, and then click Peripherals. The Peripherals dialog box is displayed. 2 Click the Keyboard tab and set the Character Set, Keyboard Layout, Delay Before Repeat and Repeat Rate parameters. The following table explains the parameters present on the Peripherals dialog box.
Configuring the Mouse Settings To configure the Mouse settings: 1 From the desktop menu, click System Setup, and then click Peripherals. The Peripherals dialog box is displayed. 2 Click the Mouse tab to select the mouse speed and mouse orientation. 3 Select the Swap left and right mouse buttons check box to swap mouse buttons for left-handed operations. 4 Click OK to save the settings.
a Click the Playback Devices tab to select the type of the audio from the drop-down menu. • b • c d e Use slider to control the volume settings for the playback devices. • Select the check box to mute. 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.
a b c d e f g h 3 Select Port—Click the button to select the Port. Default is COM 1 Baud Rate — Select the Baud Rate from the drop-down list. Default is 9600. 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 .
NOTE: You can optimize performance and modify the frame rate per second, if the Optimize for CPU check box is selected—supported values include 1/1, 1/2, 1/3, 1/4, 1/5, and 1/6– directly from the thin client (if the webcam supports Universal Video Driver). This feature is experimental and does not currently support central configuration (INI parameters).
Bluetooth enabled devices, such as headsets and mouses that are available in the Thin Client environment are listed in the Bluetooth page. The following attributes are displayed in the list. • Name — Specifies the name of the Bluetooth enabled device. • Type — Specifies the type of the Bluetooth enabled devices, such as headsets, mouses, and keyboards. Both Human Interface Devices (HID) and Headset Bluetooth devices are supported in ThinOS 8.2. • • HID Type • HID includes mouse and keyboard.
User Scenario Status Device turned off Disconnected | Paired Device turned on Connected | Paired Device diconnected from ThinOS Disconnected | Not Paired • Connect— Select a particular Bluetooth enabled device, and click Connect to connect the selected device to the thin client. If the Bluetooth device is connected successfully, the status is displayed as Connected in the Bluetooth window.
• Jabra Speak 510 MS, Bluetooth speakerphone • Jabra EVOLVE 65 MS Stereo Headset 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.
a b Select Port— Select the port you want from the list. LPT1 or LPT2 selects the connection to a direct-connected USB printer. 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. c d e f 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.
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 b c d e 84 Select LPD —Select the port you want from the list.
This name can be different for each vendor. This field is required and must be correct so that the network printer accepts incoming print jobs properly. For example, auto can be used for HP LaserJet 4200n PCL6 as per documentation found on the HP Web site. 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.
d e f g \\Host\Printer—Enter the Host\Printer or use the browse folder icon next to the box to browse your Microsoft Networks and make the printer selection you want from the network printers available (the DNS name or IP address of the Windows print server on the network). Printer Class —(Optional) Select the printer class from the list. Enable the printer device—Must be selected to enable the printer. It enables the device so it displays on the remote host.
To configure the Citrix UPD usage on ThinOS: 1 Connect a printer to ThinOS client. 2 From the desktop menu, click System Setup, and then click Printer. The Printer Setup dialog box is displayed. 3 Enter the name of the printer in the Printer Name box. 4 Enter any string of the Printer identification in the Printer Identification box. 5 Select the type of the printer class from the drop-down list, select the check box to enable the printer device and then click OK.
2 Click Citrix Resources > XenApp > Policies > User > Settings > Printing > Client Printers and enable the Auto-create generic universal printer. 3 Click Printing > Drivers and set the Universal print driver usage to Use universal printing only from the drop-down menu available.
4 To enable the printer policy in XenApp/XenDesktop 7.5 and XenApp/XenDesktop 7.6: a Go to the Citrix DDC Server, 1 Click Citrix studio > policies and add a policy. Enable the Auto-create generic universal printer option. 2 Set the Universal print driver usage to Use universal printing only from the drop-down menu.
b Check registry and make sure the same driver has been installed. 1 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. 2 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.
2 Under HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\UniversalPrintDrivers\PCL5c\, change DriverAlias and DriverName HP LaserJet 2200 Series PCL 5.
• Resetting Display Settings Using V-Key Reset • Accessing Thin Client BIOS Settings 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.
6 Citrix HDX RealTime Multimedia Engine (RTME) RTME 1.8 was a new feature introduced in ThinOS 8.2. This is the Citrix HDX RealTime Optimization Pack 1.8 for Lync. From ThinOS 8.3 release, the Citrix HDX RealTime Optimization Pack 2.0 (RTME 2.0) is supported. Citrix RTME 2.0 is introduced to support Microsoft Skype for Business 2015 client/UI (only), in addition to RTME 1.8 supporting the Microsoft Lync 2010/2013 clients.
For more information about Citrix RTME 1.8 feature, go to docs.citrix.com/en-us/hdx-optimization/1-8/hdx-realtime-optimization-packabout.html. For more information about Citrix RTME 2.0 feature, go to docs.citrix.com/en-us/hdx-optimization/2-0/about.html. For information on how to use Citrix RTME 1.8 feature, go to docs.citrix.com/en-us/hdx-optimization/1-8/hdx-realtime-optimization-packtroubleshooting.html. For information on how to use Citrix RTME 2.0 feature, go to docs.citrix.
NOTE: RTME version 2.0.100.6 is included in the release package. If the connector version is the previous version 2.0.0.417, then the RTME feature works and a warning sign is displayed to indicate the version difference that is displayed next to the taskbar icon. Installing the RTME package on ThinOS You are required to install the RTME.i386 package for the RTME 1.8 and 2.0 feature to work on ThinOS. To install the RTME.i386 package: 1 Upload the RTME.i386.pkg to directory \wnos\pkg\.
Setting Up the RealTime Multimedia Engine (RTME) for Lync This section describes how to install and use Lync on a Citrix desktop. 1 Install Citrix HDX RealTime Connector version 1.8 or 2.0 on Citrix desktop VDA/Server. For more information about installing Citrix HDX RealTime Connector version 1.8 on Citrix Desktop VDA/Server, see docs.citrix.com/en-us/hdx-optimization/1-8/hdx-realtimeinstall.html. For more information about installing Citrix HDX RealTime Connector version 2.
IMPORTANT: From ThinOS 8.3, the RTME 1.8 and 2.0 co-exist in the release package, supporting both versions of RTME connectors. 3 (This step is for RTME 1.8 only) Configure the Domain Name Server (DNS) settings on ThinOS for Lync Server. NOTE: You must ensure that the thin client does not have USB redirection for video/audio devices in order to have RTME working correctly. 4 Log in to your Citrix Desktop, and sign in to Lync client. • For RTME 1.
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 RTMS 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. • RTME audio device on ThinOS will display only one device from ThinOS local playback device. It can actually work the way they are configured at ThinOS local playback device and record device. The RTME audio device for ringtone is limited to use ThinOS local playback device. • The RTME 1.8 feature on ThinOS does not work with other versions of HDX RealTime connector due to known Citrix limitation.
5 Verify the RTME connector 2.0 icon on taskbar. The status is displayed as Connected. 6 Verify the About, and Settings options from the RTME connector 2.0 menu. 7 Verify the audio/video devices from SFB client menus. 8 Establish the video/audio calls. 9 Pick up the calls by either clicking the mouse or using the headset button. 10 Verify the Call Statistics from the RTME connector 2.0 menu. NOTE: RTME 2.0 supports various call scenarios. For more information, refer to Citrix technical overview.
7 Advanced Details on Configuring ICA and RDP Connections Use the following information when configuring ICA and RDP connections. This information assumes that the thin client does not have a locked down privilege level. • High-privileged user — The additional functionality provided by the Connection Settings dialog box allows testing of connection definitions before they are entered by a network administrator into the user profile files.
a b c d Server or Published Application — Select the type of connection to which the settings apply. Connection Description — Enter the descriptive name that is to appear in the connection list (38 characters maximum). 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.
NOTE: The Host Name may be resolved using one of three mechanisms: ICA master browser, DNS or WINS. Master browser is the only mechanism that can resolve a published application unless manual entry is made in DNS for the application. DNS uses the default domain name in the network control panel to attempt to construct an FQDN but will also try to resolve the name without using the default.
a Logging on area — Enter Login Username, Password, Domain name, and Logon Mode. If the Login Username, 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: b • 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.
a b c d Autoconnect to local devices — Select any options (Printers, Serials, USB, Smart Cards, and Disks) to have the thin client automatically connect to the devices. Allow font smoothing — When selected, enables font smoothing (smooth type). 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 dialup.
a b c d Connection Description— Enter the descriptive name that is to appear in the connection list (38 characters maximum). 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.
You can reset the options on the Connection tab of the Connection Settings (RDP) dialog box. To do so, click the Reset VM command button. This command button is located in the upper-right of the dialog box. It appears only with a VDM broker connection. 3 Click Logon tab, and use the following guidelines: a b c Logging on area —Enter login username, password, and domain name.
4 Click Options tab, and use the following guidelines: a b c d e f g h i j k l 5 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.
1 Launch an RDP session (Windows 8.1/2012 r2) by using Window mode and non-default resolution. 2 Use the mouse to change the size of the session window. Known Issues Resizing the session window causes the MS media player’s frame region to dispatch. This is a server side issue.
8 ICA SuperCodec ICA SuperCodec is a H.264 decoder integrated on ThinOS ICA client side. Server encodes the session image into H.264 stream and sends it to client side. Client decodes the H.264 stream by SuperCodec and show the image on screen. It should improve user experience especially for HDX3DPro desktops. Supported Environment XenDesktop/XenApp 7.5 or later versions Supported Platforms All the platforms support ICA SuperCodec except on C10LE and R10L.
b When the feature is disabled, you can view the following results: ThinOS event log: System resolution exceeds hardware limitation (1920 x 1080), disable SuperCodec ICA SuperCodec 111
Click HDX Monitor > Graphics > Thinwire Advanced > Encoder > CompatibilityEncoder; CompatibilityEncoder. • For other platforms except C10LE, R10L Wyse 3010 Thin Client with ThinOS (T10) and Wyse 3020 thin client 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. ICA 14.0.0.91 • Supported Environment This release supports ICA connections with XenApp 7.
• New Features — This version of ICA has new features such as: • Multicast support in Virtual Driver Multi-Media (VDMM) 1 Launch an ICA Desktop in XenDesktop 7.x or XenApp 7.x 2 Start multimedia and from the file menu, click Open URL. Event logs are displayed. NOTE: ICA multicast does not support C10 due to VIA platform limits. 3 • Supported protocols: HTTP, MSB, MMS; RTSP/RTCP are not supported.
9 Features of RDP 8.1 Remote Desktop Protocol (RDP) H.264 and VOR is enabled by default for all ThinOS platforms, except C10LE and R10L. Remote desktops such as Window 8, Window 8.1, Window 10, and Windows 2012R2 are supported in this release. The following are the dependencies of RDP 8.1: • Dependence 1: RDP GFX status, H.264 and VOR work only when GFX is enabled. • Dependence 2: VOR is dynamic.
• When the feature is disabled, the following screen is displayed in the Event Log tab for disablement: • Also, when video resolution 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.
Support Matrix for RDP 8.1 The following table displays the support matrix for RDP 8.1: Table 3. 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.
10 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 offloading 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.
You can view the installed packages in the Packages tab in the System Tools dialog box. NOTE: For ThinOS package versions, see Dell Wyse ThinOS 8.3.1 Release Notes. 4 Server configuration for Flash redirection a To ignore the differences in flash player versions, user must add the FlashPlayerVersionComparisonMask and ClientFlashPlayerVersionMinimum registry key on the desktop. If it is XenApp 6.5, IEBrowserMaximumMajorVersion registry key is required to ignore the differences in IE Browser versions.
b During the flash playback, it will display ThinOS event logs for HDX FR in the System Information dialog box. 1 FR: Media type video/x-264 2 FR: Media type audio/mpeg Known Issues a Playback flash videos in Internet Explorer browser with normal security settings. b Playback with videos ≤ 720p; the 1080p video may show graphic issue.
a ThinOS client built-in Flash player version is 11.1. If the version installed on VDA/XenApp machines is higher than 11.1, then user needs to disable flash version compatibility check for the HDX Flash redirection feature to work. b User can disable the version check by modifying Windows Registry Key on VDA/XenApp named “FlashPlayerVersionComparisonMask” which is a DWORD that must be set to zero. c This needs to be set on each and every VDA/XenApp where the user needs the checking disabled.
a HDX Flash client side rendering feature does not work with Internet Explorer 11 with HDX Flash redirection enabled on XenApp 6.5 and XenDesktop 5.6 VDA. b The registry key value IEBrowserMaximumMajorVersion is queried by the HDX Flash service to check for maximum Internet Explorer version that HDX Flash supports. For Flash Redirection to work with Internet Explorer 11, set the registry key value IEBrowserMaximumMajorVersion to 11 on the machine where HDX flash service is running.
4 a Launch the XenApp/XenDesktop manage console, and then go to Polices node pane. b User can edit ‘Unfiltered’ User Policy directly that applies to all connections. User can also view a personal policy, such as ‘FlashTest’ policy, and assign this policy to user’s own computer OU and domain user. To view the list of Flash policies: Go to Settings tab, and then select Flash Redirection. All the Flash Redirection policies are listed as shown in the following screenshot.
5 To activate a policy: After modifying any Citrix policy, run the CMD command ‘gpupdate /force’ in the XenApp/VDA machine, and then reconnect the session. The policy will be updated immediately. 6 To verify if Flash is getting client rendered OR HDX Flash redirection is working: a Right-click on the Flash Region to view the Flash context menu. If the Flash context menu is same as native Linux menu, the ThinOS built-in Adobe Flash Player version is 11.1.
7 To delete the dynamic blacklist manually: In Registry Editor, right-click HKEY_CURRENT_USER to find entries with Keywords ‘DynamicBlacklist’, and then delete all the Backlist keys/records.
Citrix HDX Flash Redirection Policies Configurations Policy - Flash default behavior 1 Remove all other active flash related policies in XenApp/XenDesktop server side. 2 Set Enable Flash acceleration for policy 'Flash default behavior' in XenApp/XenDesktop server side. Then run a web Flash video in ICA session for the client to render the flash video.
3 Set Block Flashacceleration for the policy Flash default behavior in the XenApp/XenDesktop server side, and then run a web Flash video in ICA session, the flash video will be server rendered and event 55 generates in event viewer > ApplicationsAndServicesLogs > Citrix > Multimedia > Flash > Admin.
Policy - Flash URL compatibility list 1 Edit XenApp/XenDesktop policy 'Flash URL compatibility list', such as new item {Render On Client, *youku.com*, Any}, and then access the website (For example, www.youku.com). All flash instances on the website are client rendered.
Introduction to Flash Redirection
2 Edit XenApp/XenDesktop policy 'Flash URL compatibility list', such as new item {Render On Server,*youku.com*, Any}. And then access the website (For example, www.youku.com). All flash instances on the website are server rendered, and Event 59 generates in event viewer. 3 Edit XenApp/XenDesktop policy 'Flash URL compatibility list', such as new item {Block, *youku.com*, Any}. And then access the website (For example, www.youku.com).
2 130 Disable the policy Flash intelligent fallback in XenApp/XenDesktop server side. Run some flash websites in ICA session. there will be no new event 61 in event viewer > Applications And ServicesLogs > Citrix > Multimedia > Flash > Admin.
Policy - Flash server-side content fetching URL list 1 Edit the Flash server-side content fetching URL list in XenApp/XenDesktop policy, such as new item {*} Introduction to Flash Redirection 131
2 Set the ThinOS Lite INI using the {SessionConfig=ICA HDXFlashEnableServerSideContentFetching=Enabled} 3 Make sure that the client cannot access your testing Flash website, set an unreal DNS server to break client internet connection. You can try to ping your website domain name for example www.youku.com that request will be timed out. 4 Access any website for example www.youku.com to play a flash video through HDX FR.
11 Introduction to TCX 7.0 Flash Redirection The Dell Wyse TCX Suite 7.0 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 component of TCX Suite 7.0 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.
Known Issues with TCX 7.0 Flash Redirection TCX FR on ThinOS is not working for certain flash video pages. However, the result is the same between FR over RDP, and FR over PCoIP. Dell recommends you to validate, and block the URL that does not work, before deploying TCX FR on all the systems. 134 Introduction to TCX 7.
12 Performing Diagnostics Diagnostics include: • System Tools • Using the Trouble Shooting Options Topics: • System Tools • Using the Trouble Shooting 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.
NOTE: The Mirror File Server tab has been removed from the System Tools dialog box, as it can now be viewed in the Devices tab.
a b c 4 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. Click Delete to delete the imported certificate. 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.
a b Click the Delete button to delete the selected package. 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 • RTME.i386.pkg • pcoip.i386.pkg—This package is available only on Wyse 3030 LT thin client with PCoIP, Wyse 5010 thin client with PCoIP (D10DP), Wyse 5040 AIO thin client with PCoIP (5213), and Wyse 5060 thin client with PCoIP. • TCX.i386.
NOTE: From ThinOS 8.2 release, base.i386.pkg is mandatory for all ThinOS clients. PCoIP package is mandatory for Wyse 5010 thin client with PCoIP (D10DP) and Wyse 5040 AIO thin client with PCoIP (5213). In ThinOS 8.3, PCoIP package is mandatory for Wyse 3030 LT thin client with PCoIP. From ThinOS 8.3.1, PCoIP package is mandatory for Wyse 5060 thin client with PCoIP. 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 140 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 142 Click OK to save the settings.
Using the Trouble Shooting Options Use the Trouble Shooting dialog box to configure Trace and Event log settings, performance monitor graphs that display client CPU, Memory, and Networking information, and CMOS management extract and restore cmos settings as described in CMOS Local Management: Extracting CMOS Settings to a USB Key for Distribution. It also allows you to view wnos.ini cached information for troubleshooting purposes.
4 144 Click the Capture tab to configure the Export Event Log, Network Capture to USB, Wireless Capture to USB, and USB DEV Trace.
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.
• Use the Network capture to USB option to enable the capture of network information, that is, a network trace of all traffic coming in and out of the thin client to a USB drive that is inserted into the thin client. After login and use of the XenDesktop server or network, you will see a ThinOS_WS.pcap file in the USB drive which you can analyze using software such as a packet analyzer used for network troubleshooting, and analysis.
NOTE: Ping sends an echo request to a network host. The host parameter is either a valid host name or an IP address. If the host is operational and on the network, it responds to the echo request. Ping sends one echo request per second and calculates round trip times and packet loss statistics. It displays a brief summary upon completion of the calculation. The ping utility can be used to: • Determine the status of the network and various foreign hosts. • Track and isolate hardware and software problems.
The tracert utility traces the path from your thin client to a network host. The host parameter is either a valid host name or an IP address. The tracert utility sends out a packet of information three times to each device (routers and computers) in the path and displays the round trip response times and identifying information in the message box. 7 148 Click OK to save the settings.
A Central Configuration: Automating Updates and Configurations 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. However, you can use WDM for a more hands-on management of your thin clients.
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.
credentials of the user and to obtain a list of ICA published applications valid for the validated credentials. The user supplies those credentials when logging in to the thin client. 182 NT domain list for PNAgent/ PNLite Optional string. The thin client creates a pull-down list of domains from the information supplied in option 182. This list is presented at thin client login in the order specified in the DHCP option (for example, the first domain specified becomes the default).
NOTE: The value of this option tag represents the same information as option tag 187. The difference is that ThinOS interprets the value of this option tag in correct order (for example, the value of 0x0050 is interpreted as0x0050). If the DHCP server provides both option tag 192 and 187, option tag 192 takes precedence. 194 WDM FQDN Optional Fully Qualified Domain Name for the WDM. 199 Cloud Client Manager Group Key Optional string.
B CMOS Management This appendix includes general CMOS management information for use with the following supported versions: • C10 BIOS version 1.0B_SPC001-0407 or later • D10D BIOS version 3.0D or later • R10 BIOS version 1.0H_SPC-0T51 or later Depending on the method of distribution you want to use, complete one of the following: • CMOS Central Management: Extracting CMOS Settings to the File Server for Distribution. • CMOS Local Management: Extracting CMOS Settings to a USB Key for Distribution.
5 Log in to all Target Device to the File Server containing the CMOS INI File: a b c Start the thin client devices for which you want to distribute the Reference Device CMOS Settings. To access the cmos.ini. file, enter your credentials in the Login dialog box. To open Event Log, click System Information icon. In the System Information dialog box, select Event Log tab. You can view the CMOS: restore from C10_cmos.1.0B_SPC001 event.
C 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. IMPORTANT: Host-based printers are not supported.
Using the Printer Setup Dialog Box for Local USB or Parallel Printers In this example you have an HP LaserJet 4000 attached to a thin client USB port. When connecting USB printers, some printers fill out the Printer Name and Printer Identification fields for you. To Configure the Printer to print locally attached printers through USB or Parallel ports. 1 From the desktop menu, click System Setup > Printer. The Printer Setup dialog box is displayed.
Using the Printer Setup Dialog Box for Non-Windows Network Printers (LPD) To configure the Printer Setup dialog box for Non-Windows Network Printers (LPD). 1 From the desktop menu, click System Setup, and then click Printer. The Printer Setup dialog box is displayed. In this example we have an HP LaserJet 4200n attached to a thin client through LPR. 2 Click the LPDs tab and use the following guidelines when printing to a non-Windows network printer: a Select LPD — Select LPD1 or LPD2 port.
Since connecting to a Microsoft Windows Print Server requires domain credentials, you must provide the credentials to ThinOS either on demand as the printer is used or by administrator setup providing credentials cached from the Dell Wyse login screen, see Example 3: Defining an SMB Printer to Use User Credentials Cached by ThinOS (Advanced) in Using INI Parameters for Windows Network Printers (SMB). This section will discuss both methods.
Name="TechSupportPrinter" \ PrinterID="HP LaserJet 4100 Series PCL" \ Enabled=yes \ Username-enc=PACGOGDBPKDOPGDGKC \ Password-enc=PFDBOHDBODCJPODP \ Domain=contoso NOTE: In order to create the encrypted passwords for use in an INI file you will want to use a program such as ConfGen. This application has built in support for creating the encrypted strings. ConfGen can be downloaded from technicalhelp.de/ IMPORTANT: This is a non-supported tool that is linked solely for the purpose of this example. 3.
Setting Up Windows 2003/2008 Servers To Configure Setting the Windows 2003/2008 Servers 1 Navigate to Control Panel > Administrative Tools > Services and ensure the Microsoft TCP/IP Printing service is installed. If it is not, install it using the Microsoft installation instructions. 2 Add the thin client as the LPD printer by completing the following: a Navigate to Control Panel > Printers > Add Printers > Local Printer > Create a new port and select LPR PORT.
• LPD3 = 8 — The LPD Queue name is transmitted as the printer name; the Printer Identification as class • SMB1 = 9 — In the form \\host\printershare • SMB2 = 10 • SMB3 = 11 • SMB4 = 12 To install the relevant ThinPrint product on the server use the following guidelines: • Printer Objects Created Manually by the Administrator — After you install.print Engine, create a printer object on the server to use the native driver and ThinPort as a printer port.
D Security Changes 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.
• CCM, 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 SecurityPolicy 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 (Highlighted in red color in the following screenshot).
E Transport Layer Security (TLS) 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.
F Important Notes • USB 3.0 on Wyse 7010 thin client with ThinOS (Z10D)—The Wyse 7010 thin client with ThinOS (Z10D) devices support two USB 3.0 ports. The USB 3.0 is supported on ThinOS 8.1 and 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. Known issue • • Camera preview has some known issue.
• Wyse 5010 thin client with ThinOS (D10D) • Wyse 5040 AIO thin client (5212) • Wyse 5060 thin client with ThinOS • Wyse 7010 thin client with ThinOS (Z10D) This feature is supported on the following PCoIP enabled clients: • • Wyse 3030 LT thin client with PCoIP • Wyse 5010 thin client with PCoIP (D10DP) • Wyse 5040 thin client with PCoIP (5213) • Wyse 5060 thin client with PCoIP Anonymous logon—This feature enables the users to log into the Storefront server configured with unauthenticate
c • When remote connection with TS gateway III closed: There are no additional logs displayed in the Event Log tab. Linux/Windows 10 desktop support • Linux hosted desktop in Citrix, and vWorkspace brokers is supported. • Windows 10 desktop in multiple brokers is supported. • Windows 10 desktop is supported in Citrix, VMware, RDS brokers. • Windows 10 does not support MMR/TSMM over RDP protocol, but Windows 10 MMR works with the Citrix connections. • Server Name option—In ThinOS 8.
G 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.
Although ICA SuperCodec is disabled on non-HDX 3D Pro Desktop, if you set Use video codec when preferred or Do not use video codec, OR disabled on HDX 3D Pro Desktop if you set Do not use video codec, ThinOS may still print log ICA: SuperCodec enabled, and this is a known issue. If you select Use video codec when available, ICA SuperCodec is enabled for both HDX 3D Pro desktop and non-HDX 3D Pro desktop.
