Administrators Guide Wyse Winterm™ 1 series, Based on Wyse Thin OS ® Issue: 121906 PN: 883682-08 Rev.
Copyright Notices © 2006, 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.
Thin Client Requirements Compliance FCC Compliance Model SX0, Product S10 thin clients meet Class B requirements. IEC/EN Compliance Model SX0, Product S10 thin clients meet Class B requirements. Canadian DOC Notices Refer to the previous section, “Thin Client Requirements Compliance,” to find out to which model thin client each of the statements below refers.
This page intentionally blank.
Contents 1 Introduction 1 About this Guide 1 Organization of this Guide 1 Wyse Technical Support 2 Related Online Resources Available at Wyse 2 2 Establishing a Server Environment 3 Setting Up Access to Enterprise Servers 3 About Configuring 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) 8 FTP and Virtual Desktop Servers Unavailable (Stand-alone Us
vi Contents Figures 51 Tables 53
1 Introduction Wyse® WintermTM 1 series Thin Clients use the Wyse Thin OS. These highly optimized thin clients 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 AskWyse.com. If you still have questions, you can submit your questions using the Wyse Support Request Form, or call Customer Support at 1-800-800-WYSE (toll free in U.S. and Canada). Hours of operation are from 5:00 am to 5:00 pm PST, 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® WintermTM 1 series Thin Clients. It also includes information to help you to 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 The No local LAN, invoke PPPoE only option must first be selected in the Network Setup dialog box. After being selected, the PPPoE Manager can be used and is available from the desktop to configure and invoke PPPoE connection to WAN. Once connected, all packets are through a PPP connection over Ethernet to the DSL modem. The PPPoE Manager dialog box is not accessible for users with sign-on privilege set to None.
Establishing a Server Environment 5 About Configuring Network Services Network services used by the thin client include DHCP, FTP file services, Virtual Desktop file services, and DNS. Note Thin clients accept valid DNS names registered on a DNS server available to the enterprise intranet. Figure 1 shows the thin client boot flow process.
6 Chapter 2 This section provides important overview information on the following service situations: • "DHCP and FTP Servers Available" • "FTP Server Available (DHCP Server Unavailable)" • "DHCP and Virtual Desktop Servers Available" • "Virtual Desktop Server Available (DHCP Server Unavailable)" • "FTP and Virtual Desktop Servers Unavailable (Stand-alone User or PNAgent/ PNLite-only User)" Caution If a thin client accesses the enterprise intranet through Dial-up, PPPoE, or PPTP VPN and the thin c
Establishing a Server Environment 7 Server Available (DHCP Server Unavailable)" and "FTP and Virtual Desktop Servers Unavailable (Stand-alone User or PNAgent/PNLite-only User)" for more information). Note This is true if these connections (Dial-up, PPPoE, and/or PPTP VPN) are manually initiated. If they are automatically started, FTP server services will be accessed through the Dial-up, PPPoE, or PPTP VPN connection.
8 Chapter 2 DHCP and Virtual Desktop Servers Available A thin client is initially (new-thin client or reset thin client to default configurations) configured to obtain its IP address and the location of the Virtual Desktop server from a DHCP server. DHCP can only be used for the Ethernet Direct access and Wireless Direct access configurations.
Establishing a Server Environment 9 After the network settings are configured, reboot the thin client before using it. As with the DHCP configuration, a sign-on name and password may be required. One or more connection or application may start automatically if selected in the Global or individual User profiles.
10 Chapter 2 Configuring Network Services Thin client network services reside on the enterprise intranet. When setting up thin client network services, remember that if thin clients are to access the enterprise intranet through Dial-up, PPPoE, or PPTP VPN, restrictions imposed by these access paths must be considered. Note Be sure you have read "About Configuring Network Services" before you begin configuring network services.
Establishing a Server Environment 11 About Configuring FTP Servers When the thin client boots, it accesses the software update images and user configuration profile files from the FTP server. The FTP server and path to the update files are available through DHCP vendor options 161 and 162 (see "Configuring DHCP").
12 Chapter 2 Configuring an FTP Server To configure an FTP server, complete the following procedures: 1. Create the following directory structure on your FTP server: /wyse/wnos/ /wyse/wnos/ini/ /wyse/wnos/bitmap/ /wyse/wnos/cacerts/ Note There is a difference between a path obtained from the DHCP server and a path entered in the UI.
Establishing a Server Environment 13 About Configuring Virtual Desktop Infrastructure Servers When the thin client boots, it accesses the Global and User configuration profile files from a Virtual Desktop Infrastructure server. Virtual Desktop Infrastructure servers are available through DHCP vendor option 188 (see "Configuring DHCP"). The thin client communicates with Virtual Desktop Broker server by the sysinit, signon, signoff, and shutdown commands.
14 Chapter 2 replace the information contained in the UI. However, if the thin client does not receive information from the DHCP server about a particular function, the information manually entered in the UI will remain and will be used. Guidelines for Windows Servers: • You can use the DHCP tools available on the Windows server. Guidelines for Linux Servers: • Enter DHCP options 161 and 162 (described in Table 1) in /etc/dhcpd.conf (refer to the manual page man dhcpd.
15 Establishing a Server Environment Table 1 DHCP Options, Continued Option Description Notes 61 Client identifier Always sent. 161 FTP server list Optional string. Can be either the name or the IP address of the FTP server. If a name is given, the name must be resolvable by the DNS server(s) specified in Option 6. If the option provided by the server is blank or the server provides no value for the field, the machine on which the DHCP server resides is assumed to also be the FTP server.
16 Chapter 2 Table 1 DHCP Options, Continued Option Description Notes 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). The selected domain is the one which must authenticate the user ID and password.
Establishing a Server Environment 17 Configuring DNS 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.
18 Chapter 2 About Configuring Session Services Thin-client session services are made available by servers hosting Citrix ICA and Microsoft RDP software products. Note A browser must be available through one of the session services to access any on-line help documentation for users. Be aware of the following connection information: • There can be more connections than desktop space to display them. • Connections can be defined in persistent memory (with a statement reading enablelocal=yes in the wnos.
Establishing a Server Environment 19 Configuring ICA Session Services ICA session services can be made available on the network using either of the following services: • Windows 2000 or 2003 Server with Terminal Services and one of the following installed: • Citrix MetaFrame XP • Citrix Presentation Server Use the instructions accompanying these products to install them and make sessions and applications available to the thin clients sharing the server environment.
20 Chapter 2 Configuring RDP Session Services RDP session services can be made available on the network using any of the following services: • Windows 2000 or 2003 Server with Terminal Services installed • Windows NT 4.0 Terminal Services (WTS) Edition • Windows XP Use the instructions accompanying these products to install them and make sessions and applications available to the thin clients sharing the server environment.
3 System Administration This chapter provides system administration information, remote management information, and detailed system command and parameter configurations, to help you design and manage a Wyse® WintermTM 1 series Thin Client environment. Note The password for the BIOS is Fireport. Updating Software The software version is embedded in both the RAM and flash memory images.
22 Chapter 3 client; the ICA client is fully contained in the thin client system and can only be updated by changing that entire system. The RDP client is also not replaceable. Caution Interrupting power during the update process can corrupt the FLASH on the thin client. Thin clients with corrupted FLASH must be shipped to Wyse for service.
System Administration 23 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. To reset the thin client to factory default settings, restart the thin client and continuously tap the G key during the restart process. G-key reset impacts all configuration items, including but not limited to both network configuration and connections defined in local NV-RAM.
24 Chapter 3 Desktop file server or add to the PNAgent/PNLite servers list. To access the Network Setup dialog box in such a case, disconnect the network cable and reboot the thin client to Stand-alone user mode. The Network Setup dialog box displays after the thin client initializes and you can then make the required entries (be sure to reconnect the network cable and reboot when finished).
System Administration 25 Using Wyse Device Manager Software For Remote Administration Wyse Device Manager (formerly known as Rapport) software is a full-featured remote administration tool set available from Wyse Technology. The software accesses your thin client through the factory-installed Wyse Device Agent and Preboot Execution Environment (PXE) client utilities. PXE upgrade services and a Virtual Network Computing (VNC) Viewer are built into Wyse Device Manager software.
26 Chapter 3 Using the User Profile ini File Command Set The following sections provide information about the user profile .ini file command set. • "About wnos.ini" • "About {username}.ini" • "Using the Sample .ini Files" • "Knowing the General Rules of the ini Files" • "Commands and Parameters - wnos.ini Only" • "Commands and Parameters - wnos.ini and {username}.
System Administration 27 Knowing the General Rules of the ini Files General rules of the .ini files include the following: • Commands and parameters can be entered for reference as necessary but are not mandatory unless changes from defaults are required. Certain parameters to the Connect= commands are mandatory and are noted in Tables 2 through 4. • Commands and parameters must always be separated by spaces, regardless of the command. • Blank lines can be used to enhance readability.
28 Chapter 3 Commands and Parameters - wnos.ini Only Table 2 lists the Command/Parameter and Description set for wnos.ini only. Table 2 wnos.ini Only Command/Parameter Description AddCertificate=filename Specifies a certificate file residing in the subfolder cacerts under the wnos folder to load on the nand flash device (on platforms with nand flash), or on the memory.
29 System Administration Table 2 wnos.ini Only, Continued Command/Parameter Description DefaultUser=username Default sign-on user. Note that this user name is displayed in the Sign-on dialog box and may be either used or replaced. DelCertificate={filename, all} Removes the named file from the nand flash or from the memory. If DelCertificate=ALL, then all certificates will be deleted from the flash.
30 Chapter 3 Table 2 wnos.ini Only, Continued Command/Parameter Description LongApplicationName={yes,no} Set to yes to display all 38 characters in a desktop icon name. Otherwise, icons display up to 19 characters (the last three characters will be … if over 19 characters). MaxVNCD={0 - 5} This command is for Wyse Thin OS version 4.3 and later only. Default = 1. Set to 0 to disable shadowing, or a non-zero absolute count of the number of concurrent VNC sessions. The maximum count value allowed is 5.
31 System Administration Table 2 wnos.ini Only, Continued Command/Parameter Description SignOn={yes,no, NTLM} [MaxConnect=max] [ConnectionManager={maximize, minimize, hide}] [EnableOK={yes,no}] [DisableGuest={yes,no}] [DisablePassword={yes,no}] Yes/no choice to enable the sign-on process. Default=yes (enabled). If set to NTLM, user can be authenticated with NTLM protocol. The optional keyword MaxConnect sets the maximum number of connects allowed to be specified in the wnos.ini and username.
32 Chapter 3 Table 2 wnos.ini Only, Continued Command/Parameter Description TimeZone=zone [ManualOverride={yes, no}] [daylight = {yes, no}] [start=mmwwdd end=mmwwdd] [TimeZoneName=timezonename] [DayLightName=daylightname] This statement is valid if the zone is Unspecified on the thin client or with the ManualOverride option parameter.
33 System Administration Commands and Parameters - wnos.ini and {username}.ini Table 3 lists the Command/Parameter and Description set for both wnos.ini and {username}.ini. Note Global parameters in Table 3 noted with * supersede the identically named user profile parameters. After user sign-off, user profile parameters in Table 3 noted with ** return to their original value set in wnos.ini. Table 3 wnos.ini and {username}.
34 Chapter 3 Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description **Desktop=bitmap file [Layout = {center, tile}] The Desktop command specifies a bitmap file to be used as wallpaper for the local desktop. This file could be a 4-bit, 8-bit, or 24-bit BMP file or a standard GIF file or a standard JPEG file. The file must be located in the FTP server wnos\bitmap directory. Default is no wallpaper. Layout is a parameter of the Desktop command.
35 System Administration Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description **DisableMouse={yes, no} Or MouseDisable={yes, no} Value and Disabled no — Mouse is enabled (default) yes — Mouse is disabled and no mouse pointer is shown on the screen. The pointer is enabled if any mouse activity occurs. **EnableLocal={yes, no) Set to yes to enable locally configured entries to show in the Connect Manager list (that is, activate local entries). Default = no.
36 Chapter 3 Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description **ICABrowsing={udp, http} Establishes the default browsing protocol. Default is udp. This setting can be overridden by the parameter HttpBrowsing={yes,no} in each connection property. The method of browsing selected must match the method provided by the server(s) being accessed. This setting in wmos.ini will be saved into nvram if EnableLocal is set to yes in wnos.ini.
37 System Administration Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description **Language=code Charset={ISO-8859-1, ISO-8859-7} Once specified in wnos.ini, it is saved in non-volatile memory. Set Charset={ISO-8859-7} to support Greek language on the desktop display. Default is ISO–8859-1.
38 Chapter 3 Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description **LowBand={no, yes} Establishes the default setting for all connections. yes or no choice to enable optimization for low speed connections, such as reducing audio quality and/or decreasing protocol-specific cache size. Default = no (disabled). This setting in wnos.ini will be saved into nvram if EnableLocal is set to yes in wnos.ini.
39 System Administration Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description PnliteServer=List of {IP address,DNS names} with optional port number for each entry ReconnectAtLogon={0, 1, 2} ReconnectFromButton={0, 1, 2} List of IP addresses or host names with optional TCP port number of PNAgent/PNLite servers. Default=Empty. Each entry with optional port is specified as Name-or-IP:port, where :port is optional; if not specified, port 80 is used as the default.
40 Chapter 3 Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description Printer={SMB1, SMB2, SMB3, SMB4} [Host=\[domain]\host] [Name=share_name] [PrinterID=window_driver] [Class=classname] [Enabled={yes, no}] [EnableLPD={yes, no}] [Username=username] [Password=password] [Domain=domain name] Specifies printers on the shared Microsoft network. Name is the shared printer name. Host is specified as \domain\host if the host is configured within a Microsoft domain.
41 System Administration Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description **PRIVILEGE=[None, Low, High] [LockDown= {yes, no}] [HideSysInfo = {yes, no}] [HidePPP = {yes, no}] [HidePN = {yes, no}] [HideConnectionManager = {yes, no}] [EnableNetworkTest = {yes, no}] Privilege controls access to thin client resources. Parameter and Operator Privileges None — This level of access is typical for kiosk or other restricted-use deployment.
42 Chapter 3 Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description **Reconnect={yes, no} Establish the default setting of Reconnect for all types of connections. This setting in wnos.ini will be saved into nvram if EnableLocal is set to yes in wnos.ini.
43 System Administration Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description **Seamless={yes, no} [HideTaskbar={0, 1, 2}] If set to yes, then the default resolution for ICA published applications is set to Seamless. Default = no. This is a command for Wyse Thin OS v4.2 and later only. The keyword HideTaskbar sets the status of taskbar when maximizing the seamless window.
44 Chapter 3 Table 3 wnos.ini and {username}.ini , Continued Command/Parameter Description VDIBroker=vdi_broker_url Specifies the VDI broker server (supports both http and https). If vdi_broker_url does not start with http nor https, the default protocol is http. For an https connection, only one URL is accepted. **VNCPrompt = {yes, no} [{Accept, Reject} = {10 to 600} (seconds)] [ViewOnly = {yes, no}] VNCPrompt set to yes means the user will always be prompted before shadowing starts.
45 System Administration ICA and RDP Connect Parameter List Table 4 lists the ICA and RDP Command/Parameter and Description set. Table 4 ICA and RDP Connect Parameter List Command/Parameter Description Alternate=[no, yes] ICA Only.Yes/no choice to use an alternate IP address returned from an ICA master browser to get through firewalls. Default = no. Autoconnect={0-99} Set to 1 to start a connection automatically (after sign-on, if sign-on is enabled). Default = 0.
46 Chapter 3 Table 4 ICA and RDP Connect Parameter List, Continued Command/Parameter Description Encryption={None, Basic, 40, 56, 128, Login-128} Connection security level. The highest level is 128-bit security (Login-128 option is 128 bit encryption for login only, and is only available for ICA). The lowest is None. Default=Basic. NOTE: The server must support the specified level of encryption or the connection will fail. Experience={0-15} RDP Only.
47 System Administration Table 4 ICA and RDP Connect Parameter List, Continued Command/Parameter Description Icon={default, bitmap file} Specifies an icon to appear on the thin client desktop for this connection. Use default to display a system default icon for this connection. For another icon, enter the name (with extension) of the bitmap file, and ensure that the file is located in the FTP server wnos\bitmap directory.
48 Chapter 3 Table 4 ICA and RDP Connect Parameter List, Continued Command/Parameter Description Reconnect={yes, no, 1 to 3600 (seconds)} Parameter Value and Action yes — Restart the connection after 20 seconds when disconnected. Default delay time for reconnect is 20 seconds. no — (default) No re-connection after a disconnect. seconds — (integer) Interval to wait (in seconds) before automatically restarting the connection after disconnection. Valid range is 1 to 3600.
49 System Administration Table 4 ICA and RDP Connect Parameter List, Continued Command/Parameter Description UnmapSerials={no, yes} ICA and RDP. Specifies to auto-connect to local serials when the connection starts. The default is yes. Username=[username, $SN, $MAC, $IP, $UN, $TN, $PW, $DN] Name to log-in to the application server. Either a conventional log-in name can be used or a variable can be used. Up to 31 characters are allowed for this entry.
50 Chapter 3 This page intentionally blank.
Figures 1 Boot flow process 5
52
Tables 1 2 3 4 DHCP Options 14 wnos.ini Only 28 wnos.ini and {username}.
Administrators Guide Wyse® WintermTM 1 series, Based on Wyse Thin OS Issue: 121906 Written and published by: Wyse Technology Inc.
