Administrators Guide Wyse ThinOS TM Products: C10LE, S10, V10L, V10LE Issue: 020810 PN: 883682-08 Rev.
ii Copyright Notices © 2010, Wyse Technology Inc. All rights reserved. This manual and the software and firmware described in it are copyrighted. You may not reproduce, transmit, transcribe, store in a retrieval system, or translate into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, any part of this publication without express written permission.
iii Regulatory Compliance for Thin Clients Basic EMC and Safety Requirements Wyse thin clients are compliant with the regulatory requirements in the regions listed below. U.S.A. - FCC Part 15 (class B), cUL 60950 Canada - IC ICES-003, CAN/CSA-C22 No.
iv This page intentionally blank.
Contents Summary of Revisions vii 1 Introduction 1 About this Guide 1 Organization of this Guide 1 Wyse Technical Support 2 Related Documentation and Services Wyse Online Community 2 2 2 Establishing a Server Environment 3 Setting Up Access to Enterprise Servers 3 Understanding How to Configure Your Network Services 5 DHCP and FTP Servers Available 6 FTP Server Available (DHCP Server Unavailable) 7 DHCP and Virtual Desktop Servers Available 8 Virtual Desktop Server Available (DHCP Server Unavailable) 9
vi Contents Configuring {username}.
Summary of Revisions Wyse Technology Inc. 883682-08 Rev. T The following changes were made to this document since revision S Reference Description Model Cx0 Thin Client, Product C10LE Addition of Model Cx0 Thin Client, Product C10LE to the guide. Model VX0 Thin Client, Product V10LE Addition of Model VX0 Thin Client, Product V10LE to the guide. Wyse Technology Inc. 883682-08 Rev.
viii Summary of Revisions This page intentionally blank.
1 Introduction Wyse® thin clients running Wyse ThinOS™ are highly optimized thin clients that provide ultra-fast access to applications, files, and network resources made available on machines hosting Citrix™ ICA and Microsoft™ RDP session services. Locally installed software permits remote administration of the thin clients and provides local maintenance functions.
2 Chapter 1 Wyse Technical Support To access Wyse technical resources, visit http://www.wyse.com/support. If you still have questions, you can submit your questions using the Wyse Self-Service Center (on the Wyse.com home page, go to Support | Knowledge Base | Home tab) or call Customer Support at 1-800-800-WYSE (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. To access international support, visit http://www.wyse.com/global.
2 Establishing a Server Environment This chapter contains information on the network architecture and enterprise server environment needed to provide network and session services for Wyse thin clients running Wyse ThinOS. It also includes information to help you address important considerations when configuring access to the server environment and when configuring the services to be provided by the server environment.
4 Chapter 2 PPP connection over Ethernet to the DSL modem. The PPPoE Manager is not accessible for users with privileges set to None. However, access to the PPPoE Manager is not necessary if the connection is to be established at startup. And unless the unit is locked down, establishing the PPPoE connection would take place before reading an INI file. Therefore any thin client which is not locked down would have the default privilege (high) at this boot stage.
Establishing a Server Environment 5 Understanding How to Configure Your Network Services Network services used by the thin client can include DHCP, FTP file services, Virtual Desktop file services, DNS, and so on. How you configure your network services depends on what you have available in your Wyse ThinOS environment and how you want to design and manage it. To help you understand how a thin client can “fit” into an environment, Figure 1 shows the thin client boot flow process.
6 Chapter 2 The following topics in this section provide important overview information on the supported service situations you may have when configuring the network services for your Wyse ThinOS environment (after becoming familiar with your environment requirements, refer to "Configuring Network Services" for detailed instructions): • "DHCP and FTP Servers Available" • "FTP Server Available (DHCP Server Unavailable)" • "DHCP and Virtual Desktop Servers Available" • "Virtual Desktop Server Availabl
Establishing a Server Environment 7 Note If session connections or published applications are designated to open automatically on start-up, upon accessing the enterprise server environment you will see a session server log-in or server application window instead of the thin client desktop. Use CTRL+ALT+UPARROW to toggle between window display modes. Use CTRL+ALT+DOWNARROW to open a selection box for toggling between the desktop, the Connect Manager, and currently-active connections.
8 Chapter 2 Note A wnos.ini file contains the “global” parameters you want that will affect all thin clients accessing the file server. A {username}.ini file contains the user-specific or “user profile” parameters you want that will comprise the connection profile for an individual user. For information on constructing these INI files, refer to the Reference Guide: Wyse ThinOSTM INI Files. After the network settings are configured, reboot the thin client before using it.
Establishing a Server Environment 9 If the thin client accesses the enterprise server environment through a manually initiated Dial-up, PPPoE, and/or PPTP VPN, the automation provided by a DHCP server is not available. In such cases, refer to "Virtual Desktop Server Available (DHCP Server Unavailable)" for configuration information. Note If Dial-up, PPPoE, and/or PPTP VPN are automatically started, Virtual Desktop server services can be accessed through these connections.
10 Chapter 2 FTP and Virtual Desktop Servers Unavailable (Stand-alone User or PNAgent/ PNLite-only User) In an environment where FTP and Virtual Desktop Broker servers are not available (for example, Stand-alone User or PNAgent/PNLite-only User situations), configuration files are not available and network information must be entered locally at the thin client as follows: • Stand-alone User - This user does not access user profiles or PNAgent/ PNLite-published applications.
Establishing a Server Environment 11 server is not used, the thin client user must enter connection definitions locally (or for FTP servers, use what is published by PNAgent/PNLite servers residing on the network). You can also define connections in the INI files which are to be stored in local NV-RAM and used in cases where the file server fails. A wnos.ini file contains the “global” parameters you want that will affect all thin clients accessing the file server. A {username}.
12 Chapter 2 • • Linux FTP Server Guidelines - Be aware of the following: • The FTP server must be configured to offer FTP services (by adding the following line or equivalent to the /etc/inetd.conf file, if it is not already present): ftp stream tcp nowait root /usr/sbin/tcpd in.proftpd • The FTP server must be configured to support anonymous FTP.
Establishing a Server Environment 13 To configure an FTP server, complete the following procedures: 1.
14 Chapter 2 Configuring Virtual Desktop Infrastructure Servers When the thin client boots, it accesses the INI files from a Virtual Desktop Infrastructure (VDI) server. VDI servers are available through DHCP vendor option 188 (see "Configuring DHCP"). The thin client communicates with a Virtual Desktop Broker server by the sysinit, signon, signoff, and shutdown commands.
Establishing a Server Environment 15 registered with a DNS server before other thin clients will be able to locate this LPD server). The thin client does not dynamically register its name and the DNS registration must be manual. • Wyse Device ManagerTM (WDM) Guidelines - If you use WDM, the thin client uses port 80 as the default to access a WDM server (formerly known as Rapport server).
16 Chapter 2 Note Ensure that within the DHCP scope these new DHCP option tags you create are activated (this can be done using the Configure Options command), before you add them. Table 1 DHCP Options Option Description Notes 1 Subnet Mask Required. However, it is not is not required unless the thin client must interact with servers on a different subnet (MS DHCP requires a subnet mask and will always send one). 2 Time Offset Optional. 3 Router Optional, but recommended.
17 Establishing a Server Environment Table 1 DHCP Options, Continued Option Description Notes 162 Root path to the FTP files Optional string. If the option provided by the server is blank and the server provides no value for the field, a null string is used. \wyse\wnos is automatically appended to the search path. For example, if you enter pub\serversoftware, the path searched will be pub\serversoftware\wyse\wnos.
18 Chapter 2 Table 1 DHCP Options, Continued Option Description Notes 184 FTP Username Optional string. Wyse ThinOS version 4.3 and later only. 185 FTP Password Optional string. Wyse ThinOS version 4.3 and later only. 186 Wyse Device Manager (WDM) server list (formerly know as Rapport) Optional binary IP addresses of WDM. This option can specify up to two Wyse Device Manager servers. If two are specified, at boot time the thin client will attempt to check-in to the first server.
Establishing a Server Environment 19 Configuring DNS Thin clients accept valid DNS names registered on a DNS server available to the enterprise intranet. In most cases, DNS is not required but may be used to allow hosts to be accessed by their registered DNS names rather than their IP addresses. Every Windows DNS server in Windows 2000 and later includes Dynamic DNS (DDNS) and every server registers dynamically with the DNS server. There are also DDNS implementations available for *NIX environments.
20 Chapter 2 used for authentication and accounting for various types of network access). Cisco Secure Access Control Server (ACS) for Windows provides a centralized identity networking solution and simplified user management experience across all Cisco devices and security management applications. Configuring for Transport Layer Security (TLS) Connections Over a LAN The IEEE 802.
Establishing a Server Environment 21 8. (Wireless Networks Only) Click Wireless Setup to open the Wireless Setup dialog box and use the following guidelines: Note The on-board NIC is “favored” if a valid link is detected, and the USB wireless will not be activated; otherwise, USB wireless becomes the system’s LAN, all configured network settings apply to the wireless network, and the USB wireless controls the NIC and functions such as the local Ethernet.
22 Chapter 2 the server. ICA connects to NT TSE, Windows Server 2003, Windows Server 2008, or Windows 2000 Server hosts that have a Citrix MetaFrame server, Citrix Presentation server, or CDS installed. Load balancing is included. ICA browsing or DNS can be used to resolve the server name. For information on configuring ICA, refer to "Configuring ICA Session Services.
Establishing a Server Environment 23 Configuring ICA Session Services Before you use the information in this section to configure your ICA session services, be sure you have read "Configuring Session Services.
24 Chapter 2 Configuring RDP Session Services Before you use the information in this section to configure your RDP session services, be sure you have read "Configuring Session Services." RDP session services can be made available on the network using any of the following: • Windows 2000, 2003, or 2008 Server with Terminal Services installed • Windows NT 4.
3 Remote System Administration This chapter provides remote system administration information to help you perform the routine tasks needed to maintain your Wyse ThinOS environment.
26 Chapter 3 After obtaining software updates from Wyse, you must replace the existing software images in the wnos subdirectory on the FTP server to allow the thin clients to automatically detect and self-install the new software (upon thin client system start). The FTP server address and exact path to these files are specified in DHCP Options 161 and 162 (if DHCP is not used, the path is specified in the Network Setup dialog box on the thin client).
Remote System Administration 27 then (regardless of any circumstance in step 1) check for a file named express.rom and begin updates if appropriate. If an update is done, the thin client will again reboot. Managing Icons and Logos Icons and logos specified in the INI files must be placed in the file server /wnos/bitmap subdirectory. Icons are specified in the Icon clause of the connection statement and logos are specified in the FormURL statement. Supported image file types include .ico (icon), .
28 Chapter 3 Configuring Virtual Access Suite Support This section explains how to support the Wyse ThinOS with Provision Networks Virtual Access Suite (VAS). To support Wyse ThinOS with VAS, you must do the following: • Download Wyse ThinOS firmware version 5.3.0_14 or later and store it on all Connection Brokers under the WNOS directory (see “Updating the Wyse ThinOS Firmware (VAS Support)” ). • Download hotfix 5 for VAS 5.
Remote System Administration 29 Enabling HTTP and HTTPS Support on the Connection Brokers (VAS Support) The Connection Broker can be configured to accept http and https requests simultaneously. To support https requests, however, you must first obtain a Web server certificate for each Connection Broker. Installing Connection Broker Web Server Certificates (VAS Support) For https support, obtain a Web server certificate for each Connection Broker.
30 Chapter 3 To specify additional RDP connection parameters to the dynamically generated {username}.ini file, you must configure a custom RDP. ini file under the WNOS directory (for a list of optional RDP connection parameters that can be used, refer to the Reference Guide: Wyse ThinOSTM INI Files). If an RDP. ini file exists under the WNOS directory, the Connection Broker automatically merges its contents into the dynamically generated {username}.ini after authenticating the user. The final {username}.
4 Local System Administration This chapter provides local system administration information to help you perform the routine tasks needed to maintain your Wyse ThinOS environment.
32 Chapter 4 Resetting Display Settings Using V-Key Reset If the display settings are inappropriate for the particular monitor that is connected, it is possible that the display will not function properly when the thin client restarts. To correct this, power-on the thin client while continuously tapping the V key. This will restart the thin client with a display resolution of 640 x 480 pixels and a 60 Hz refresh rate.
Local System Administration 33 Configuring ThinPrint No ThinPrint-specific configuration is available on the thin clients. Thus to be able to use ThinPrint, users must first set up their printers according to the user documentation, and then configure ThinPrint on the thin client (by clicking on the desktop background, selecting System Setup from the menu to open the Network Setup dialog box, and then clicking Printer to open and use the printer configurations).
34 Chapter 4 This page intentionally blank.
Figures 1 Boot flow process 5
36
Tables 1 2 3 4 4 DHCP Options 14 System Variables 39 wnos.ini Only 40 wnos.ini and {username}.
Administrators Guide Wyse ThinOSTM Issue: 020810 Written and published by: Wyse Technology Inc.
