Wyse S10 User Manual

Users Guide

Wyse ThinOSTM

Products: C10LE, S10, V10L, V10LE

Issue: 020810
PN: 883681-08 Rev. R

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.

End User License Agreement (“License”)

A copy of the Wyse Technology End User License Agreement is included in the software and provided for your
reference only. The License at http://www.wyse.com/license
agreement. By copying, using, or installing the software or the product, you agree to be bound by those terms.

Trademarks

The Wyse logo and Wyse are trademarks of Wyse Technology Inc. Other product names mentioned herein are for
identification purposes only and may be trademarks and/or registered trademarks of their respective companies.
Specifications subject to change without notice.

Patents

This product and/or associated software are protected by copyright, international treaties, and various patents,
including the following U.S. patents: 6,836,885 and 5,918,039.

Restricted Rights Legend

You acknowledge that the Software is of U.S. origin. You agree to comply with all applicable international and
national laws that apply to the Software, including the U.S. Export Administration Regulations, as well as end-user,
end-use and country destination restrictions issued by U.S. and other governments. For additional information on
exporting the Software, see http://www.microsoft.com/exporting

as of the purchase date is the controlling licensing

.

Ordering Information

For availability, pricing, and ordering information in the United States and Canada, call 1-800-GET-WYSE
(1-800-438-9973) or visit us at http://www.wyse.com

FCC Statement

This equipment has been tested and found to comply with the limits for either Class A or Class B digital devices,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy
and, if not installed and used in accordance with the instructions, may cause harmful interference to radio
communications. However, there is no guarantee that interference will not occur in a particular installation. If this
equipment does cause harmful interference to radio or television reception, which can be determined by turning
the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following
measures:

• Reorient or relocate the receiving antenna.

• Increase the separation between the equipment and the receiver.

• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

• Consult the dealer or an experienced radio/TV technician for help.

Shielded interconnect cables and shielded AC power cable must be employed with this equipment to insure
compliance with the pertinent RF emission limits governing this device. Changes or modifications not expressly
approved by the system’s manufacturer could void the user’s authority to operate the equipment.

Caution

Modifications made to the product, unless expressly approved by Wyse Technology, could void
the user’s authority to operate the equipment.

. In all other countries, contact your sales representative.

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. 60950
Europe - EN 55022 (class B), EN 55024

Canadian DOC Notices

Class A - This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus

set out in the Radio Interference Regulations of the Canadian Department of Communications.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux
appareils numériques de la classe A prescrites dans le Réglement sur le brouillage radioélectrique édicté par le
Ministère des Communications du Canada.

Class B - This digital apparatus does not exceed the Class B limits for radio noise emissions from digital apparatus
set out in the Radio Interference Regulations of the Canadian Department of Communications.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux
appareils numériques de la classe B prescrites dans le Réglement sur le brouillage radioélectrique édicté par le
Ministère des Communications du Canada.

Device Power Supply

For use with external power supply included in the shipping carton.

Caution

Replace power adapter with the same or a certified equivalent model supplied by the
manufacturer.

Model Cx0 Thin Client, Product C10LE

For use with External Power Supply Model PA-1031-0, or DA-30E12 or certified equivalent model supplied by the
manufacturer, output rated 12Vdc, 2.5A.

Model SX0 Thin Client, Product S10

For use with External Power Supply Model DSA-0421S-12 3 30, or certified equivalent model supplied by the
manufacturer, output rated 12Vdc, 2.5A.

Model VX0 Thin Client, Products V10L and V10LE

For Use with External Power Supply Model PA-1051-01, or certified equivalent model supplied by the
manufacturer, output rated 12Vdc, 4.16A or minimum 4.0A.

Battery Information

Models Cx0 and VX0 contain an internal button cell battery replaceable by Wyse or one of our Authorized Service
Centers. For service, visit http://www.wyse.com/serviceandsupport/service/service.asp

.

Warning

There is a risk of explosion if the battery is replaced by an incorrect type. Always dispose of used
batteries according to the instructions accompanying the battery.

Warning

Perchlorate Materials – Special Handling May Be Required under California Code of Regulations,
title 22. (Only required within the U.S.A.)

This page intentionally blank.

Content s

Summary of Revisions vii

1 Introduction 1

About this Guide 1

Organization of this Guide 1

Wyse Technical Support 1

Related Documentation and Services 2
Wyse Online Community 2

2 Getting Started 3

What Happens When You Turn on Your Thin Client 3

Accessing the Enterprise Servers Available 3

Signing-on 5

Changing Your Password 6
Roaming Smart Card Log-In Support 6
Understanding Your User Profile 6
Knowing Your Assigned Privileges and User Mode 7

Assigned Privileges 7

User Modes 8
Understanding System Lock-down 9
About the Session Services You Will Use 9

Locking the Thin Client 10
Logging Off and Shutting Down 10
Using the Desktop 11

Viewing System Information 12
Understanding the Window Display Modes 13
Using the Shortcut Menu and Desktop Menu 14

Using the System Setup Submenu 14

Accessing System Information 15

Accessing Available Applications 15

Accessing the PPPoE Manager 15

Accessing the Dialup Manager 16

Accessing the PPTP Manager 16

Accessing the Network Test Tools 16

Accessing the Shutdown Options 16

Using the Connect Manager 17
About Configuring ICA and RDP Connections 18

About Wyse TCX Software 19
About Wyse Virtual Desktop Accelerator Software 19
Configuring ICA Connections 20
Configuring RDP Connections 24

vi Contents

3 Setting Up the Thin Client 27

Setting System Preferences 28
Configuring Network Settings 31
Selecting Display Settings 39
Configuring Dual Monitor Settings 40
Configuring Serial Communications 41
Setting Up Printers 42

Configuring LPD Services 46

Adding and Deleting TCX Licenses Manually 48
Configuring Touch Screens 48

4 Using and Configuring Access Connections 49

Using Ethernet Direct Access 49
Using Wireless Direct Access 49
Configuring PPPoE Access 50
Configuring Dialup Modem Access 51
Configuring PPTP VPN Access 54

5 Using the Network Test Tools 57

Using Ping 57
Using Trace Route 58

Setting Up Windows NT4 Servers 47

Setting Up Windows 2000/2003/2008 Servers 47

Figures 59
Tables 61

Summary of Revisions

Wyse Technology Inc. 88368-08 Rev. R

The following changes were made to this document since revision P

Reference Description

Model Cx0 Thin
Client, Product
C10LE

Model VX0 Thin
Client, Product
V10LE

Wyse Technology Inc. 88368-08 Rev. P

The following changes were made to this document since revision N

Reference Description

New
documentation
references

Windows Server
2008

802.11n wireless
support

Updated figures
and workflow

Addition of Model Cx0 Thin Client, Product C10LE to the guide.

Addition of Model VX0 Thin Client, Product V10LE to the guide.

General rewrite of the guide to include references to the new titles
of the Wyse ThinOS documentation (1 Series is no longer used).

Addition of Windows Server 2008 support and information to the
guide.

Addition of 802.11n wireless support and information to the guide.

All figures and workflow instructions have been updated to include
and describe the new user interface.

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 reso urces 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.

Session and network services available on enterprise networks may be accessed through
a direct intranet connection, a dial-up server, or an ISP which provides access to the
Internet and thus permits the thin client to connect to an enterprise virtual private network
(VPN) server.

About this Guide

This guide is intended for users of Wyse thin clients running Wyse ThinOS. It provides
detailed instructions on using the thin client to manage the connections and applications
available to users from a network server.

Organization of this Guide

This guide is organized as follows:
Chapter 2, "Getting Started," provides information to help you quickly get started using

your thin client. It describes basic thin client functions and provides instructions on using
the desktop and Connect Manger to manage the connections and applications available
for you to use.

Chapter 3, "Setting Up the Thin Client," contains information to help you set up your thin
client using the System Setup submenu.

Chapter 4, "Using and Configuring Access Connections," provides information and
detailed instructions on using and configuring connections to access th e enterp rise server
environment available to the thin client.

Chapter 5, "Using the Network Test Tools," contains information on using the network test
tools available on the thin client.

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
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

(on the

.

2 Chapter 1

Related Documentation and Services

Wyse thin client features can be found in the datasheet for your specific thin client model.
Datasheets are available on the Wyse Web site. Go to http://www.wyse.com/products
click the Wyse Thin Clients link, click the link for your thin client, and then click the
Download Datasheet link.

Sample User INI files are intended for administrators of Wyse thin clients running Wyse
ThinOS. These files are available from the Wyse Web site (go to

http://www.wyse.com/manuals

then click the sample ini link to open and use the file download dialo g bo x to save the
compressed file to a folder you want). These sample files are annotated to allow you to
use them as a “starter set” (that you can modify for your users needs) to quickly get your
file server up and running. For information on using the sample files, refer to the

Reference Guide: Wyse ThinOS
Reference Guide: Wyse ThinOS

clients running Wyse ThinOS. It provides the detailed information you need to help you
understand and use the Wyse ThinOS INI files. It contains information on the different
Wyse ThinOS INI files you can use and the rules for constructing the files. It also provides
the parameter details you need (with working examples) to get the most out of your Wyse
ThinOS INI files. In addition, this guide also includes an appendix that contains all of the
supported connect parameters you can use for ICA and RDP connections. It is available
at: http://www.wyse.com/manuals

Getting Started Guide: Wyse ThinOS

system. It provides a setup and configuration overview of the entire Wyse ThinOS system
to help you get your Wyse ThinOS environment up and running quickly and easily. It is
available at: http://www.wyse.com/manuals

Administrators Guide: Wyse ThinOS

running Wyse ThinOS. It provides information and detailed system configurations to help
you design and manage a Wyse ThinOS environment. It is available at:

http://www.wyse.com/manuals

,

, search for sample.ini, click the reference guide link, and

TM

INI Files.

TM

INI Files is intended for administrators of Wyse thin

.

TM

is intended for administrato rs of the Wyse ThinOS

.

TM

is intended for administrators of Wyse thin clients

.

Wyse Thin Computing Software is available on the Wyse Web site at:

http://www.wyse.com/products/software

Wyse Online Community

Wyse maintains an online community where users of our products can see k and exchange
information on user forums. Visit the Wyse Online Community forums at:

http://community.wyse.com/forums/

.

.

2 Getting St arted

This chapter provides information to help you quickly get started using your thin client. It
describes basic thin client functions and provides instructions on using the desktop and
Connect Manger to manage the connections and applications available for you to use.

What Happens When You Turn on Your Thin Client

What you see, initially, when you turn on or reboot your thin client, depends on your
method of access to the enterprise intranet and how your network administrator has set up
your account. With Wyse ThinOS software, your thin client can also be turned on by the
Wake-On-LAN feature. Using this feature, an administrator can turn on the thin client
connection by using a LAN message that the thin client recognizes on a single Ethernet
subnet.

Accessing the Enterprise Servers Available

There are five basic methods of access to the enterprise server environment available to
the thin client. Except for Ethernet Direct, all of the access methods require that some
local settings be made on the thin client. These settings cannot be automated because the
thin client has not yet accessed global and user profiles. For certain privileges, these local
settings are retained and are available for the next thin client system start. Activating these
local settings and the defined connections can also be automated at thin client system
start.

Methods of access include:

• Ethernet Direct - This
enterprise intranet. No additional hardware is required. An account Sign-on dialog box
displays if required, then either the desktop or an application window opens (the
application window opens, with or without a session server logon requirement, if se t by
the administrator to open automatically ). User pr o files nor mally ar e used in this mode
and are accessed automatically. However, if the Dynamic Host Configu ration Protocol
(DHCP) - a protocol for assigning dynamic IP addresses to devices on a network - is
not available on the enterprise intranet, the location of the file server where user
profiles are located must be entered in the Network Setup dialog box. For information
on the Network Setup dialog box, refer to "Configuring Network Settings."

ireless Direct - If a wireless network device is connected to the thin client, you can

• W
use the Wireless Setup dialog box to configure the wireless connection. When a
connection is established, the behavior is the same as for an Ethernet Direct
connection, including automatic access to user profiles through DHCP. For information
on the Wireless Setup dialog box, refer to "Configuring Network Settings."

is a connection from the thin client Ethernet port directly to the

4 Chapter 2

• PPPoE - The
invoke PPPoE connection to WAN. Once connected, all WAN packets go though a
PPP connection over Ethernet to the DSL modem. The PPPoE Manager is not
accessible for users with sign-on privilege set to None. Open the PPPoE Manager by
selecting it from the Desktop menu. The PPPoE Manager can also be set to open
automatically on system start-up. For information on the PPPoE Manager, refer to
"Configuring PPPoE Access."

• Dialup Mode
automatically when the thin client is turned on or restarted, the thin client is configured
to access the network through a dial-up modem. A Sign-on dialog box may appear
when the network connection is accomplished. DHCP cannot automatically connect
your thin client to user profiles when using dial-up access; the location of the FTP
server where the profiles reside must be entered in the Network Setup dialog box. For
information on the Dialup Manager, refer to "Configuring Dialup Modem Access." For
information on the Connec
information on the Ne

• PPTP VP
thin client is turned on or restarted. This facilitates connection to an enterprise network
through an ISP, the Internet, and a virtual private network (VPN) PPTP server. If dial- up
is used to contact the ISP providing access to the Internet, the Dialup Manager and
Connect Manager also open. DHCP cannot automatically connect your thin client to
user profiles when using PPTP VPN access; the location of the FTP server where the
profiles reside must be entered in the Network Setup dialog box. For information on
the PPTP Manager, refer to "Configuring PPTP VPN Access." For information on the
Dialup Manager, refer to "Configuring Dialup Modem Access." For information on the
Connect Manager, refer to "Using the Connect Manager." For information on the
Network Setup dialo

PPPoE Manager is available from the Desktop menu to configure and

m - If both the Dialup Manager and the Connect Manager open

t Manager, refer to "Using the Connect Manager." For

twork Setup dialog box, refer to "Configuring Network Settings."

N - The PPTP Manager can be configured to open automatically when the

g box, refer to "Configuring Network Settings."

Note

If the Network Setup dialog box initially appears, or the Connect Manager is
active when the thin client is started (or when the enterprise intranet is
accessed), network services are not fully configured. In this case sign-on is
not required and thin client network settings (and possibly connection
definitions) must be entered locally on the thin client (for example, a
Stand-alone user). For more information, refer to “Using the Connect
Manager” and "Configuring Network Settings."
If the network to which the thin client is con
services, a user profile will not be available and network addresses and
connection definitions must be entered locally on the thin client. If user
profiles (and update services) are available from an FTP server but DHCP
does not supply the location of the FTP server, you can access the profiles
by entering the location of the FTP server locally on the thin client (refer to
“Configuring Network Settings” for more details).

nected does not provide FTP

Signing-on

Getting Started 5

After a connection to the enterprise intranet is established, sign-on to the network and/or
session services may or may not be required (depending on a global profile option set by
the network administrator, the session servers, or any requirements of PNAgent/PNLite
services). If sign-on to the enterprise intranet is required, a Sign-on dialog box opens
when you turn on the thin client, when you restart the thin client, or af ter signing off from a
user profile account.

Note

In a Virtual Desktop environment, user authentication is made against the
Virtual Desktop Broker. Therefore, you will only authenticate against the
Broker. You will sign-on as described in this section only when a Virtual
Desktop environment is not used or is unavailable.

Sign-on name and password are assigned initially by the administrator when the account
is established, but the password can be change d by the user at a thin client in some cases
(see "Changing Your Password"). To sign on to a standard account, enter the user name
for the account and password allocated to you by the network administrator. Account user
names are not case sensitive, however, passwords are case sensitive.

Note

If you cannot successfully sign-on, ask your network administrator for help.

If a user account is not established but PNAgent/PNLite-published applications are to be
accessed on the PNAgent/PNLite server, you must enter the user name for the account
and password (in this case, account user names are not case sensitive, but passwords
are case sensitive) and also select a Domain in which the applications appears (if the
correct domain does not appear in the list, type it into the Domain box).

Note

Applications can be published to the network by PNAgent/PNLite services.
These applications are available to the thin clients on the network as long as
accounts are established on the PNAgent/PNLite server. If user profiles are
used, the thin client will send the enterprise server sign-on and domain
information to the PNAgent/PNLite server for log-on. If user profiles are not
used (a sign-on is not required to access user profiles) but a PNAgent/PNLite
server address is entered into the Network Setup dialog box, the Sign-on
dialog box with the PNAgent/PNLite Domain box will still be presented to you
for access to the published applications. PNAgent/PNLite-published
applications will be merged with connections defined through user profiles
and local settings for a combined total number of connections. The maximum
number of connections has a default limit of 216, but can be set from 100 to
1000 through wnos.ini.

6 Chapter 2

Changing Your Password

If you are required to sign on and you are not using PNAgent/PNLite services or a Virtual
Desktop environment, you can change your assigned password by selecting Check here
to change password in the Sign-on dialog box and using the Change Password dialog
box (type the new password in both the New Password and Confirm boxes, and then
click OK).

Note

If you are using both PNAgent/PNLite and a user profile, the user name must
be defined in the Windows domain to be used and the pa ssword must be the
same for both the domain and the user profile.
In a Virtual Desktop environment, user au
Virtual Desktop Broker (the user name and password are stored on the
Broker or a third-party authentication server). Therefore, the password must
be changed on the Broker or the authentication server.

If you are required to sign on and are using PNAgent/PNLite services (so that the user

rofile password is forwarded to the PNAgent/ PNLite server), you can ha ve an application

p
change your domain password but you cannot change your INI file password while using
PNAgent/PNLite. Therefore, if you change the domain password, you will lose the effect of
any directives in the user.ini file, including any potential upgrade of privilege (for example,
the privileges in the wnos.ini file may be set to None, but the privileges in the user.ini file
are set to High).

thentication is made against the

Roaming Smart Card Log-In Support

If your thin client supports smart card log-ins, the Sign-on dialog box changes when you
insert a smart card. Instead of being asked to enter your username and password, you are
asked to enter a PIN to gain access to your applications and connections. If you want to
exit the Smart Card Sign-on dialog box, you can press the Esc key; you will then be
presented with the usual Sign-on dialog box.

Note

If the smart card you are using is not supported, there will be no change to
the Sign-on dialog box.

Understanding Your User Profile

Profiles for users contain the settings and connection definitions for the thin client. They
are created and maintained by the network administrator and reside on the enterprise
intranet FTP server or Virtual Desktop server. The thin client accesses these user profiles
when you sign on. The location of these files may be automatically supplied to the thin
client by the DHCP server (if set up by the network administrator), or if DHCP is not
available, their location must be entered in the Network Setup dialog box.

Note

The “global” (wnos.ini) and user (user.ini) INI files on an FTP server can take
effect only when a Virtual Desktop environment is not used.

Types of profiles for users include:

obal - All clients of the same FTP server have these “global” profile settings.

• Gl

• User -

Only the individual user has these “user” profile settings. Settings in user

profiles can override corresponding global profile settings.

Getting Started 7

Note

If you want to change your user profile, contact your network administrator.
In a Virtual Desktop environment, the use
Thus, different users with the same policy can have the same user profile.

You have the same user profile, regardless of wh ich thin clie nt you us e. If allowe d by the
network administrator, a limited number of settings are available locally. For instructions
on selecting local operator preferences such as display, keyboard, mouse, and printer
selections, refer to "Setting Up the Thin Client."

Note

If the network to which the thin client is connected does not provide FTP or
Virtual Desktop services, a user profile will not be available and network
addresses and connection definitions must be entered locally on the thin
client. If user profiles are available from an FTP or Vi rtual Desktop server b ut
DHCP does not supply the location of the server, you can access the user
profiles by entering the location of the FTP or Virtual Desktop server locally at
the thin client (refer to "Configuring Network Settings" for more details).

r profile is set in the user policy.

Knowing Your Assigned Privileges and User Mode

As a thin client operator, you have a thin client account with certain privileges. Your thin
client account is a set of application connection definitions and thin client configuration
settings that are grouped under a privilege level and assigned to you by your
administrator. Administrators create thin client accounts that possess specific connection
capabilities, security, and various thin client functions. Assigned privileges and user
modes allow you certain levels of access to thin client resources.

Note

Access to system-reset-to-factory defaults and the Network Setup dialog
box can be denied by the user privilege (not the lock-down state). Thus, if the
thin client is locked down in High privilege, access to all facilities is allowed,
regardless of other items (unless there is an intervening privilege statement
in an INI file). It is only when the thin client is locked down in the privilege
None that you cannot recover control of the thin client. For more information
about system lock-down, refer to "Understanding System Lock-down."

Assigned Privileges

The profiles for users (global and user) can assign three privilege levels of access to thin
client resources: High-privileged, Low-privileged, and Non-privileged.

• High-

privileged - With High privilege, all thin client resources (including resetting to
factory defaults) are available with no restrictions. This is an administrative level
log-on. Connection definitions can be entered locally on the thin client (typically these
may be lost upon log-off/shutdown). However, if configured by an administrator
(enablelocal=yes), locally-defined connection definitions can be saved.

Note

High privilege is the default privilege (unless locked down in another
privilege) and is in effect if a user profile is read that does not contain a
privilege statement. If no wnos.ini file is read (same conditions), the
connection definitions entered locally on the thin client are persistent and
may even be visible if a wnos.ini file is found on a subsequent reboot (if an
enablelocal=yes statement is read from one of the INI files).

8 Chapter 2

w-privileged - This is the level assigned to a typical user of the thin client. The

• Lo

Network selection on the System Setup submenu is disabled (the Network Setup
dialog box cannot be opened). A Low-privileged user cannot reset th e device to factory
defaults.

• Non-
deployment. The System Setup selection on the Desktop menu is disabled (the various
dialog boxes available from the System Setup cannot be displayed). The Connect
Manager is not available. The user cannot reset the device to factory default s. Both the
Dialup Manager and PPTP Manager are disabled.

Note

If you are accessing the enterprise intranet through Dial-up or PPTP VPN,
the Network Setup dialog box is available during the dial-up process to
establish the initial connection to the FTP server. If you then log on as a
Low-privileged or Non-privileged user, however, access to the Network
Setup dialog box is then disabled. The Dialup Manager and PPTP Manager
are also disabled for a Non-privileged user.

User Modes

User Modes define your login state and include the following types of user:

• Guest use
available) and does not need a password. The Guest user will be disabled if no
connection is defined in the global profile. The Guest user cannot access the Network
Setup dialog box and cannot reset the device to factory defa u lts. Otherwis e, all
remaining local resources are available. Although an enterprise file services account
password is not required, individual application servers may require a password.

tand-alone user - This mode makes operation of the thin client possible when user

• S
profiles or PNAgent/PNLite-published applications are not available. No user log-on is
required and network information and connection definitions must be defined locally on
the thin client. Locally entered connection definitions are preser ved when the thin client
is turned off or restarted, but individual user accounts are not available and automatic
software updates are not available when the thin client is restarted.

privileged - This level of access is typical for kiosk or other restricted-use

r - This mode logs on using the global profile only (no user profile is

Note

It is possible to have an FTP server which supplies software updates but no
INI files. In this case, software updates would take place but the user would
still be Stand-alone.

• PNAgent/PNLite-only user - This mode is similar to a Stand-alone user, except
applications published by Citrix PNAgent/PNLite services are available (the IP address
of a PNAgent/PNLite server is entered into the Network Setup dialog box). The user
logs on to the PNAgent/PNLite server but does not log on to the file server or use
configuration user profiles. If the PNAgent/PNLite server publishes fewer than the limit
of applications set by the administrator, the user can locally define additional
applications. As long as the domain password for the PNAgent/PNLite server matches
the password in an INI file for the same user on the FTP server, both the PNAgent/
PNLite published applications and the directives in the user.ini file will be processed
(with the PNAgent/PNLite published applications being processed first). However,
other directives from the user.ini file could alter the privilege, the default display
resolution, and so on. With the enable local clause for the connect statement,
connections defined in the user.ini file may be persistent.

Getting Started 9

Understanding System Lock-down

Your administrator can configure whether or not to allow access to the Network Setup
dialog box to locally re-configured the thin client to operate in a different mode or to access
a different file server.

Note

High-privileged users always have access to the Network Setup dialog box.

During normal thin client operation, Low-privileged and Non-privileged users may access
the Network Setup dialog box by temporarily disconnecting the Ethernet cable from the
rear of the thin client and rebooting to S t and-alone user mode . The Network Setup dialog
box can also be accessed by a hot-key reset to factory default, in addition to the system
reset available to a Stand-alone user through the Sign-off/Shutdown/Restart the
System dialog box.

In most cases, access to normal operation resources is desirable. However, network
environments requiring maximum security typically do not permit uncontrolled changes to
thin client network operation. To achieve this security, the network administrator can place
a lock-down argument in any privilege statement (either in the user.ini file or in wnos.ini
file). This prevents Low-privileged and Non-privileged users from accessing the Network
Setup dialog box by resetting the thin client or through system restart to Stand-alone user
mode.

Caution

If a thin client accesses the enterprise intranet through Dial-up or PPTP and
the thin client is locked-down, a user attempting to reboot to Stand-alone
user mode will disable the Network Setup dialog box. The user will not be
able to re-access the enterprise intranet through this path. If this happens,
the thin client must be moved to a location where it can access the intranet
directly so that an administrator can set the profile to unlock the thin client.
If the thin client is configured for Dial­server answering the configured telephone number. Otherwise, the thin client
will require factory attention for recovery.

About the Session Services You Will Use

The desktop connection icons and Connect Manager list entries allow you to initiate
connections to servers providing ICA and RDP services. These se rvices are configured by
the administrator for you to use. Depending on your privileges you can modify some of the
settings on these services. You can start connections by using the various Desktop or the
Connect Manager options made available by the administrator.

The Multiple Sessions feature allows the thin client to have multiple active connections.
The number of active connections you can have depends on the following:

• amount of RAM

• types of connections open

• number of connections configured

up access, there must be an RAS

For more information on ICA connections, refer to "Configuring ICA Connections."

r more information on RDP connections, refer to "Configuring RDP Connections."

Fo

10 Chapter 2

Locking the Thin Client

To help ensure that no one else can access your private information without permission,
Wyse ThinOS allows you to lock your thin client so that credentials are required to unlock
and use the thin client after you do one of the following:

• Unplug a signed
for the Signing parameter in the INI files and you unplug the smart card that you used
to sign on to the thin client, then the thin client will lock. To unlock the think client for
use, you must use the same smart card and your correct PIN. Note that removing a
signed-on smart card can also cause the thin client to log-off, if the administrator has
set the INI files to do so (in this case you must sign-on as usual to use the thin client).

• Use

• Use

LockTerminal from the Shortcut menu - Right-click on the desktop and select

Lock Terminal. To open the thin client for use, you must use your correct password.

For more information on the Shortcut menu, refer to "Using the Shortcut Menu and
Desktop Menu."

the screen saver - If the administrator has set LockTerminal=2 for the
ScreenSaver parameter in the INI files and you use the screen saver, then the thin
client will lock. To open the thin client for use, you must use your correct password.

-on smart card - If the administrator has set SCRemovalBehavior=1

Logging Off and Shutting Down

After using your thin client, you can sign off from your account (if you signed in initially) or
you can shut down the thin client (if your privilege or user mode allows you).

Note

High-privileged and Low-privileged users can also sign off from the Connect
Manager.

Click the User Name on the
the Sign-off/Shutdown/Restart the System dialog box. Use this dialog box to do one of
the following:

• Sign-

• Shut

• Re

• Res

off from the account User Name - Allows you to sign off from the current open

account (the Sign-on dialog box appears and is ready for another user).

down the system - Turns off the thin client.

start the system - Signs off the user account and also allows posted software

updates to be loaded into the thin client memory (the Sign-on dialog box appears after
the thin client restarts).

et the system setting to factory default - Appears for High-privileged and
Stand-alone users only. This option allows you to reset the thin client to factory
defaults.

Note

Depending on how the servers and applications are configured, signing off
from or shutting down the thin client may not necessarily close any open
server sessions. Generally, you should close sessions before signing-off
from or shutting down the thin client.

taskbar and select Shutdown from the Desktop menu to open

Getting Started 11

Using the Desktop

The desktop has a plain background with a horizontal taskbar at the bottom of the screen.
The number of icons that can be displayed on the desktop depends on the desktop
resolution and administrator configuration.

Note

Custom icons can be assigned to any or all connections defined in the INI
files or a default icon can be used. If no icon is assigned to a connection, the
connection will only appear in the Connect Manager and not on the desktop.
Connections supplied by PNLite and PNAgent have icons assigned by the
server. If you ha ve a High privilege level, you can righ t-click an icon to open a
Connections Settings dialog box.

If configured by your administrator (Longapp
wnos.ini), the number of icons displayed for a resolution is as follows:

• 640 x 480: Up to 8 icons are displayed.

• 800 x 600: Up to 10 icons are displayed.

• 1024 x 768: Up to 21 icons are displayed.

• 1280 x 1024: Up to 40 icons are displayed.

• 1360 x 768: Up to 28 icons are displayed.

• 1400 x 1050: Up to 40 icons are displayed.

• 1440 x 900: Up to 32 icons are displayed.

• 1600 x 1200: Up to 60 icons are displayed.

• 1680 x 1050: Up to 50 icons are displayed.

• 1920 x 1080: Up to 60 icons are displayed.

• 1920 x 1200: Up to 72 icons are displayed.
PNAgent - The thin client features PNAgent (a Program Neighborhood folder support).

With PNAgent, icons are populated to folders based on the Program Neighborhood setup
on the server. Depending on the Citrix server configuration, these icons can display on the
desktop, in the Desktop menu, in the Connect Manager, and in the system tray.

Note

If any network connection is designated to open automatically on sta rtup, you
will see the server log-in or server application window instead of the desktop.

licationname=yes as defined in

Figure 1 Desktop example

12 Chapter 2

Use the following guidelines:

• Icons representing available server connectio
displayed on the background. Hovering the mouse pointer over an icon pops-up
information about the connection. Right-clicking (or left-clicking if the mouse buttons
are reversed) on an icon opens a Connection Settings dialog box which displays
additional information about the connection.

• You can open a server connection/published a
icon or you can navigate to the desktop icon you want by using tab key and pressing
Enter to initiate the connection.

• The Desktop menu may be opened by clicking the mouse button on the desktop

ckground or by clicking on the User Name on the taskbar.

ba

• If configured to display (by an administrator)
right corner of the taskbar and the current time and date are shown when the cu rsor is
placed on the time.

Note

The thin client is capable of synchronizing its clock to time provided by a
Simple Network Time Protocol (SNTP) server.

• Press CTRL+ALT+UPARROW to toggle between window display modes.

• Press CTRL+AL T+DOWNARROW to open a se
desktop, Connect Manager, and currently-active connections.

• Keyboard shortcuts are supporte d. Use the
keyboard for keyboard shortcuts (the RIGHT ALT+UDERLINED LETTER combination
is not currently supported).

•Use the Syst
information on the System Preference dialog box, refer to "Setting System
Preferences."

• In addition to the standard two-button mouse, the thin client supports a Microsoft
Wheel Mous
not work.

• You can copy and paste between applicatio
desktop, however, this function depends on session server configurations.

ns and published applications are

pplication by double-clicking a desktop

, the volume control is displayed in the

lection box for toggling between the

LEFT ALT+UDERLINED LETTER on the

em Preference dialog box to switch the left and right buttons. For

e (used for scrolling). Other similar types of a wheel mouse may or may

n sessions and between sessions and the

Viewing System Information

System information is available from the t askbar and from the Sy stem Information dialog
box. If configured by the administrator, CPU usage and free memory are displayed in the
box on the right side of the taskbar. If you click on this area, it will toggle between percent
of CPU usage currently in use and available free memory in megabytes. If you put the
mouse cursor on the taskbar without clicking, a popup appears showing the number (for
example, percent of CPU currently in use and available free memory in megabytes). This
information is also available in the System Information dialog box.

Note

Starting an ICA or RDP connection requires at least 3 MB of free memory.

Clicking the ? icon on the t
menu) opens the System Information dialog box where you can view thin client system
information (see "Accessing System Information").

askbar (or selecting System Information from the Desktop

Getting Started 13

Understanding the Window Display Modes

The thin clients allow three different display modes, including:

• S

tandard window - Window frame, title bar, content area, including icons, and so on.

This mode is available for use with any connection.

• Sea

• Fu

The display modes that are available depend on what window mode was in use when the
con
screen and connection. The screen resolution is the actual hardware resolution used by
the thin client video chip (local resolution set either by DDC or selected manually and is
referred to as the default resolution). This resolution can be different than the connection
resolution (set with the Connection Settings dialog box or in the user profile by the
administrator), which is the dimensions of the connection screen display in pixels.

mless window - Seamless display. This mode is available for use with published

applications only.

ll-screen - Occupies the entire monitor screen with no th in client taskb ar , title bar, or

window borders. This mode is available for use with any connection.

Note

In all display modes, use CTRL+ALT+DOWNARROW to open a selection
box for toggling between the desktop, Connect Manager , and currently-active
connections.

nection was started. That in turn depends on the relative resolution settings of the

Use the following guidelines:

• If the connection is started in full-screen mode, a user can toggle between Full-screen

de and Standard window mode by using CTRL+ALT+UPARROW.

mo

• If the connection is started with either the d
matching the current display resolution, and then the Seamless window mode is
selected, the connection starts in the Seamless window mode (the Seamless mode
has a few less rows of pixels than the Full-screen mode to make room for the thin client
taskbar at the bottom of the screen). The taskbar displays on startup, but can be
modified to be shown or hidden by using CTRL+ALT+UPARROW. In this Seamless
window mode the connection display cannot be moved to a different location on the
screen, regardless of whether or not the taskbar is displayed. When the taskbar is
hidden, the area at the bottom of the screen is blank (black). When the taskbar is
shown, it can be used to switch between sessions simply by clicking an icon for
another session in the taskbar.

• If the connection is started with an explicit resolution (that is, something other than the

efault resolution set in the user profile or Connection Settings dialog box) less than

d
the current default resolution and the Standard window mode is selected (in the
Connection Settings dialog box or in the user profile setting), the connection is
displayed in a Standard window. Using CTRL+ALT+UPARROW changes the current
screen resolution to match the connection resolution and the conne ction is displayed in
Full-screen mode. Using CTRL+ALT+UPARROW again restores the original screen
resolution and will again display the connection in the Standard window mode. In
Full-screen mode the hardware resolution changes only for the duration of the
connection, then changes back to the default resolution when the connection is no
longer in the foreground.

• Making a Seamless window a Full-screen display
the screen. Instead, the application remains the same size and any portion of the
screen previously not occupied is filled with a black mask (including the screen space
previously occupied by the thin client taskbar).

efault resolution or a connection resolution

does not cause the application to fill

14 Chapter 2

Note

The thin client features PNAgent (a Program Neighborhood folder supp ort).
With PNAgent, icons are populated to folders based on the Program
Neighborhood setup on the server. These icons display on the desktop and
in various places (for example, Systray and the user Desktop submenu
application selections) depending on the Citrix server configuration.

For more information on configuring the resolution and re fresh rate for the monitor used
wit

h the thin client, refer to "Selecting Display Settings."

Using the Shortcut Menu and Desktop Menu

Right-clicking on the desktop provides a Shortcut menu with the following options:

• Hide all

windows – To bring the full desktop to the foreground.

• Copy

to clipboard – To copy the image of the full screen, current window, or event log
to the clipboard. The clipboard contents can then be pasted to an ICA or an RDP
session.

• Purg

e clipboard – To discard the contents of the clipboard in order to free up memory.

• Lo

ck Terminal – To put the terminal in a locked state if the user has signed on to the

system with a password. The terminal can only be unlocked using the same password.

Clicking the User Name on the taskbar (or clicking on the desktop) opens the Desktop
menu (the User Name shows the user log-on name).

Note

Users may lock the terminal at any time by pressing
CTRL+ALT+LEFTARROW or CTRL+ALT+RIGHTARROW.

Figure 2 Desktop menu

Using the System Setup Submenu

Selecting System Setup in the Desktop menu opens the System Setup submenu (for
High-privileged and Low-privileged users only). The System Setup submenu provides
access to the following local system setup dialog boxes:

• Pref

erence - Allows user selection of thin client parameters that are a matter of
personal preference. For more information on the System Preference dialog box,
refer to "Setting System Preferences."

• Network - Allows

selection of DHCP or manual entry of network settings, operation in
modem dialup and PPPoE modes, as well as entry of locations of servers essential to
thin client operation. This menu selection is disabled for Low-privileged users. For
more information on the Network Setup dialog box, refer to "Configuring Network
Settings."

Getting Started 15

• Display - Allows you to configure the monitor resolution and refresh rate. For more
information on the Display Setup dialog box, refer to "Selecting Display Settings."

• Dual Head
expand the monitor display to two screens. For more information on using the

DualHead Setup dialog box, refer to "Configuring Dual Monitor Settings."

ial - Allows configuration of the ports for modem dialup mode and serial

• Ser
communications. For more information on the Serial Setup dialog box, refer to
"Configuring Serial Communications."

• Printer - Allows
to the thin client. For more information on the Printer Setup dialog box, refer to
"Setting Up Printers."

• TCX Licen
above ICA and RDP connections that enable multiple monitor awareness, rich
multimedia playback, high quality bidirectional audio capabilities, and seamless USB
device access for Wyse thin clients. For more information on using the TCX License
dialog box, refer to "Adding and Deleting TCX Licenses Manually."

ouch Screen - Allows configuration of Serial and USB touch screens from ELO,

• T
MicroTouch (Model M150 only), or FastPoint. For more information on Touch Screen
setup, refer to "Configuring Touch Screens."

- (Supported Dual Monitor Capable Thin Clients Only) Allows you to

configuration of network printers and local printers that are connected

se - Allows use of Wyse® TCX Software™ to provide an enrichment layer

Accessing System Information

Selecting System Information in the Desktop menu opens the System Information
dialog box.

The following information is available:

• General T
Boot From, Memory Size (Total and Free), Terminal Name, IP Address, Net Mask,
Gateway, and DHCP Lease.

vices Tab - Displays information about devices such as the CPU Speed, ROM Size,

• De
Monitor, Parallel Ports, Ethernet Speed, Memory Speed, NAND Size, Resolution,
Serial Ports, and the thin client MAC Address.

• Copy

• Eve
System Version to Checking Firmware) or error Messages that are helpful for
debugging problems.

tatus Tab - Displays status information about TCP performance-related parameters,

• S
CPU Busy , System Up T ime , Wireless performance-related parameters, Fre e Memory,
and DHCP lease time remaining.

ab - Displays general information such as System V ersion, Serial Number,

right/Patents Tab - Displays the software copyright and patent notices.

nt Log Tab - Displays the thin client start-up steps (normally beginning from

Accessing Available Applications

Applications is an additional Desktop menu option that is available. Applications contains

a submenu of all locally configured applications and is populated with published
applications when a user is signed on using either PNLite or PNAgent.

Accessing the PPPoE Manager

Selecting PPPoE Manager in the Desktop menu opens the PPPoE Manager and allows
you to configure or start PPP connection over Ethernet to a DSL modem. The terminal can
be configured to run PPPoE to connect to WANs through DSL modems to eliminate the
need of installing a DSL router between the terminal and the DSL modem. You can also
use the PPPoE Manager to automatically open a connection on system start-up. For more
information on the PPPoE Manager, refer to "Configuring PPPoE Access."

16 Chapter 2

Accessing the Dialup Manager

Selecting Dialup Manager in the Desktop menu opens the Dialup Manager and allows
you to initiate a connection through a modem. The Dialup Manager also opens
automatically on log-on when a thin client is configured to access a network through a
modem and a dial-up server.

For more information on the Dialup Manager, refer to "Configuring Dialup Modem Access."

Note

The Dialup Manager is not available to Non-privileged users.

Accessing the PPTP Manager

Selecting PPTP Manager in the Desktop menu opens the PPTP Manager and allows you
to initiate a connection through an enterprise V irtual Private Network (VPN) via an Internet
Service Provider (ISP), the Internet, or a PPTP VPN server. The PPTP Manager can also
be set to open automatically on system start-up.

For more information on the PPTP Manager, refer to "Configuring PPTP VPN Access."

Note

The PPTP Manager is not available to Non-privileged users.

Accessing the Network Test Tools

Selecting Network Test in the Desktop me nu ope ns a subme nu from which the Ping an d
Trace Route dialog boxes can be opened. Use these dialog boxes to ch eck the integrity of

the network connection.
For more information on the Ping dialog box, refer to "Using Ping."
For more information on the Trace Route dialog box, refer to "Using T race Route."

Accessing the Shutdown Options

Selecting Shutdown in the Desktop menu opens the Sign-off/Shutdown/Shutdown/
Restart the System dialog box. Use this dialog box as described in "Logging Off and

Shutting Down."

Getting Started 17

Using the Connect Manager

Clicking Connect Manager on the taskbar opens the Connect Manager. The Connect
Manager has a list of connection entries and a set of command buttons available for use
with the connections.

Note

Non-privileged users cannot view the Connect Manager.

Figure 3 Connect Manager (High-privileged user example)

The command buttons available depend on the p
configuration; the following default examples are typical:

• High-

• Lo

• S

The use associated with these command buttons also depends on user privilege. For
example, Settings allows a High-privileged user to view and edit connection definitions,
while it allows a Low-privileged user to only view connection definitions.

The Connect Manager command buttons include:

• Conn

• New -

privileged user - Includes Connect, New, Settings, and Sign-off.

w-privileged user - Includes Connect, Settings, and Sign-off.

tand-alone user - Includes Connect, New, Settings, and Delete.

Note

If set by the administrator (enablelocal=yes in the user.ini/wnos.ini file),
High-privileged and Low-privileged users will have the Delete command
button available instead of the Sign-off command button).

Note

Guest user privileges are determined by the administrator.

ect - To make a connection, select a connection from the list and click Connect.

Clicking New opens the Connection Settings dialog box either directly or
through the Connection Protocol menu selection for creating a new connection
definition (for more information on the Connection Settings dialog bo x, refer to "About
Configuring ICA and RDP Connections"). The new locally-defined connections are
added to the connection list. Be aware of the following information:

rivileges of the user and administrator

18 Chapter 2

• High-

• S

• Settings - Clic
selected connection (for more information on the Connection Settings dialog box,
refer to "About Configuring ICA and RDP Connections"). Be aware of the following
information:

• High-

• Low

• S

• Sign-

• Delete - T

privileged user - Typically, all locally-defined connectio n definitions are
temporary and are lost when the user logs off and when th e thin client restarts or is
shut down. However, if configured by the administrator (enablelocal=yes),
locally-defined connection definitions can be saved in these cases.

tand-alone user - Locally-defined connections are retained when the thin client
restarts or is shut down (there is no individual log-on). Network configuration
settings must be made locally.

king Settings opens the Connection Settings dialog box for the

privileged user - Can view and edit the definitions for the currently-selected

connection. Edits are not permanently retained when the user signs-off.

-privileged user - Cannot create or edit connections, but can view connection

definitions.

tand-alone user - Can permanently modify the persistent connections (except
when PNAgent/PNLite services are used).

off - To sign-off from the thin client, click Sign-off.

o delete a connection, select a connection from the list and click Delete.

About Configuring ICA and RDP Connections

To open the Connection Settings dialog box for a connection, select the connection you
want from the list of available connections in the Connect Manger and click Settings (to
add new connections, click New in the Connect Manager).

Note

There is no need to configure the encryption of RDP connections on the
client side because Wyse ThinOS will defer to the encryption settings of your
terminal server (that is, low, client-compatible, high, or FIPS).

For information on configuring ICA connections
For information on configuring RDP connections, refer to "Configuring RDP Connections."
Use the following information when configuring connections (this information assumes

that the thin client does not have a locked down privilege level):

• High-pr
Settings dialog box allows testing of connection definitions before they are ente red (by
the network administrator) into the user profile files.

• Lo
cannot be edited, and new connections cannot be defined. Connection definitions are
controlled by the network administrator and are accessed by the thin client from the
user profiles located on a remote server.

• S
connection definitions cannot be accessed from remote user profiles. If user profiles
are available on an FTP server but are not accessed because DHCP is not available or
is not configured to provide the file server IP address, the file server IP location can be
entered manually using the Network Setup dialog box.

ivileged user - The additional functionality provided by the Connection

w-privileged user - The settings for the selected connection can be viewed but

tand-alone user - The Connect Manager is available to Stand-alon e users because

, refer to "Configuring ICA Connections."

Getting Started 19

About Wyse TCX Software

Wyse® TCX Software™ provides an enrichment layer above ICA and RDP connections
that enable multiple monitor awareness, rich multimedia playback, high quality
bidirectional audio capabilities, and seamless USB device access for Wyse thin clients.
Wyse ThinOS has built-in support for the following Wyse TCX solutions (a license may be
required to activate a feature):

®

• Wyse

• Wyse

• Wyse

• Wyse

• Wyse

TCX Multi-Display™

®

TCX Multimedia™

®

TCX Rich Sound™

®

TCX USB Virtualizer™

®

TCX Flash Redirection™

For more information about Wyse TCX software and support platforms, visit

www.wyse.com/tcx

.

About Wyse Virtual Desktop Accelerator Software

Wyse® Virtual Desktop Accelerator (VDA) is a software product that, when used with
Wyse thin clients, provides an “accelerated” user experie nce on remote d esktop sessio ns
with high round-trip delay between the server and client. By accelerating the remote
desktop protocols by a factor of up to 3 times on certain network s, a Wy se VDA ses sio n
with a server located thousands of miles from your thin clients “feels” similar to a
non-accelerated session with a server located just a few hundred miles from your thin
clients.

Built for use on high-bandwidth high-latency networks that are prone to packet loss
situations, primary use cases for Wyse VDA include:

• Datacenter Consolidation

• Desktop Cloud Computing

• Remote Off-Shore Desktop Computing

20 Chapter 2

Configuring ICA Connections

If you open the Connection Settings dialog box for an ICA connection (select the ICA
connection in the Connect Manger and click Settings), you can view and configure the
connection (to add new ICA connections, use New in the Connect Manager).

Figure 4 Connection Settings (ICA) - Server option

Note

If you select the Published Application option, the Application Name box
replaces the Host Names box.

Figure 5 Connection Settings (ICA) - Published Application option

Getting Started 21

Use the following guidelines:

• Ser

• Conn

• Browser

• Host N

ver or Published Application - Select the type of connection to which the settings

apply.

ection Description - Enter the descriptive name that is to appear in the

connection list (38 characters maximum) .

Servers IP - 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. The master browsers list is
generated automatically by a browsing progra m on one of the ICA servers (selected by
negotiation between servers). It is used to provide the information displayed in the
Server Name or IP box. No entry is needed if the list is on an ICA server in the same
network segment as the thin client. No entry is necessary if the connection is to a
server, or if the server name or IP contains the IP address of the server.

ame or Application Name (title depends on the Server or Published

Application option selected) - You can enter a delimited (semicolon or comma

separated) list of server hostnames or IP addresses, or you can select from the list of
ICA servers or published applications (depending on Server or Published

Application option selected) obtained from the ICA master browser (you can also use
Browse next to the box to make the selection you want). If you enter a delimited list of

servers, the thin client attempts to connect to the next server on the list if the previous
server attempt failed. If you use the list and the selected connection fails, the thin client
attempts to connect to the next one on 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.

• Encryption Level - Allows you to select th e securi ty level of communications betwe en
the thin client and the ICA server. Basic (the default option) is the lowest level of
security. Basic allows faster communication between the device and the ICA server
because it requires less processing than do the higher levels of encryption.

Caution

The encryption selection applies to the security of communications between
the thin client and the ICA server only. It is independent of the security
settings of individual applications on the ICA server . For exampl e, most W eb
financial transactions require the thin client to use 128-bit encryption.
However, transaction information could be exposed to a lower level of
security if the thin client encryption is not also set to 128 bits.

• Use HTTP for browsing - When selected, the thin client, by default, uses http when
browsing.

• Alter

nate address via firewall - When selected, the thin client will use an alternate IP
address returned from the ICA master browser to get through firewalls. Used for the
Windows log-on when the connection is activated.

22 Chapter 2

se VDA - When selected, the thin client will use Wyse® Virtual Desktop Accelerator

• Wy
software to provide an “accelerated” user experience on remote deskto p sessions with
high round-trip delay between the server and client.

gging on area - Enter Login Username, Password, Domain name, and Logon

• Lo
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. Use the following guidelines:

• Lo

• Password - 19

• Domain Name -

• Lo

Figure 6 Connection Settings (ICA) - Options tab

gin Username - 31 characters maximum.

characters maximum.

31 characters maximum.

gon Mode - Select User-specified credentials, Smart Card, or Local User.

Use the following guidelines:

• Application (1
maximum) - Enter an initialization string and arguments, including an associated
working directory, that you want to start automatically on the server when the
connection is made.

Note

This area is disabled (grayed) for a published application option.

27 characters maximum) and Working Directory (63 characters

Getting Started 23

• Display Resolution - Select the display resolution for this connection (if you select the

Published Application option, the Connection Display will allow you to select the
Seamless Display Resolution option):

• Default

40 x 480

• 6

• 8

00 x 600

• 10

24 x 768

• 12

80 x 1024

• 13

60 x 768

• 14

00 x 1050

• 14

40 x 900

• 16

00 x 1200

• 16

80 x 1050

• 19

20 x 1080

• 19

20 x 1200

• Colors
Colors is selected and the ICA server does not support this color depth, the thin client

renegotiates the color depth to the lower value (for example, 256 Colors [8 bits]).

• W
windowed screen or full screen. You can toggle between viewing modes by using
CTRL+ALT+UPARROW.

• Aut
start-up.

• Re-
reconnect to a session after a non-operator-initiated disconnect. If selected, the wait
interval is that set in the Delay before re-connecting box or the user profile for yes
(20 seconds) or seconds. The default is 20 seconds if there is no INI file description of
this connection, or is a Stand-alone user, or simply omitted.

• T
high-speed connections).

• Optimiz
connections, such as reducing audio quality and /or decr easing pr otocol-specific cache
size. Intended for a connection spanning a WAN link or using dialu p.

• Ma

• Ena
momentarily lose connection to the server without having to re-authenticate upon
regaining a connection. Instead of a user’s connection timing out after X seconds, the
session is kept alive on the server and is made available to the client upon regaining
connectivity. Session reliability is most relevant for wireless devices.

• Aut
Cards, Sound, and Disks) to have the thin client automatically connect to the devices
(an ICA session will not automatically connect to a device through a serial port).

• Delay before
selected. Enter the number of seconds (1 to 3600) be fore trying to reconnect after a
disconnect.

• M
RDP session (in 1/100 of a second). It can be used to adjust the bandwidth of a
network.

- Select the color depth of the ICA session. If High Colors (16bits) or True

indow mode and Full screen mode - Select the initial view of the application in a

o-connect on start-up - When selected, automatically connects the session on

connect after disconnect - When selected, causes the th in client to automatically

urn compression off - When selected, turns compression off (intended for

e for low speed link - When selected, allows optimization for low-speed

p all disks under (z:) - When selected, maps all disks under the Z drive.

ble session reliability - When enabled, session reliability allows a user to

o-connect to local devices - Select any options (Printers, Serials, USB, Smart

re-connecting - Becomes active if Re-connect after disconnect is

ouse queue timer - Specifies the default queue timer of a mouse event in an ICA or

24 Chapter 2

Configuring RDP Connections

If you open the Connection Settings dialog box for an RDP connection (select the RDP
connection in the Connect Manger and click Settings), you can view and configure the
connection (to add new RDP connections, use New in the Connect Manager).

Note

In a Virtual Desktop environment, an RDP connection will be assigned by the
Virtual Desktop Broker; you do not need to create an RDP connection
manually. The Virtual Desktop Broker virtual machine can be reset from the
thin client by opening the Connection Settings dialog box of the virtual
machine, and then clicking the reset button (appears in the top-right of the
dialog box).

Figure 7 Connection Settings (RDP) - Connection tab

Use the following guidelines:

• Conn

• Host Names - Use the list to select the va

• Wyse VDA - When selected, the thin client will use Wyse® Virtual Desktop Accelerator

ection Description - Enter the descriptive name that is to appear in the

connection list (38 characters maximum) .

lid 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. 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.

software to provide an “accelerated” user experience on remote deskto p sessions with
high round-trip delay between the server and client.

Getting Started 25

• Console - Select to set the RDP connection with Console mode.

• Lo

gging on area - Enter login username, password , and domain name. If th ese boxes
are not populated, you can enter the information manually in the RDP server login
screen when the connection is made. Use the following guidelines:

gin Username - 31 characters maximum.

• Lo

• Password - 19

• Domain Name -

• Application (1
maximum) - Enter an initialization string and arguments, including an associated
working directory, that you want to start automatically on the server when the
connection is made.

Note

Y ou can re set the options on the Con nection 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.

Figure 8 Connection Settings (RDP) - Options tab

characters maximum.

31 characters maximum.

27 characters maximum) and Working Directory (63 characters

Use the following guidelines:

• Display Resolution -

• Default

• 6

40 x 480

• 8

00 x 600

• 10

24 x 768

• 12

80 x 1024

• 13

60 x 768

• 14

00 x 1050

• 14

40 x 900

Select the display resolution for this connection:

26 Chapter 2

• 16

• 16

• 19

• 19

• Colors
Colors (32 bits) is selected and the RDP server does not support this color depth, the
thin client renegotiates the color depth to the lower value (for example, 256 Colors (8
bits). The highest is 32 bits, if hardware supports it.

Note

For some thin clients versions, only the 256 Colors (8 bits) selection is
available for RDP connections. Also, for older versions of the server sof tware
(for example, RDP 4.0) the server only supports 8 bit color. This is not
detectable in advance but results in use of 8-bit color when the conn ection is
established.

• Window mode and Full screen mode - Select the initial view of the application in a
windowed screen or full screen. You can toggle between viewing modes by using
CTRL+ALT+UPARROW.

allpaper - When selected, disables the desktop wallpaper.

• W

• Me

nu / Window animation - When selected, disables the menu or window animation.

• Th

eme - When selected, disables the desktop themes.

• Show cont
and move it around, the contents of the window will move with it. Select this to disable
this content view so that only the outline of the window moves when dragging it, until
you drop the window. This option can be beneficial, as it uses less processing power.

nt smoothing - Converts vector text to bitmap for better display. This option is

• Fo
enabled by default.

• Aut

• USB -

• Re-

• T

• Optimiz

• Aut

• Delay before

• M

o-connect on start-up - When selected, automatically connects the session on

start-up.

terminal server. When the user connects to the terminal server, locally attached USB
devices on the thin client are accessible.

connect after disconnect - When selected, causes the th in client to automatically
reconnect to a session after a non-operator-initiated disconnect. If selected, the wait
interval is that set in the Delay before re-connecting box or the user profile for yes
(20 seconds) or seconds. The default is 20 seconds if there is no INI file description of
this connection, or is a Stand-alone user, or is simply omitted.

urn compression off - When selected, turns compression off (intended for

high-speed connections).

connections, such as reducing audio quality and /or decr easing pr otocol-specific cache
size. Intended for a connection spanning a WAN link or using dialu p.

o-connect to local devices - Select any of the options (either Printers, Serials,
Smart Cards, Sound, and Disks) to have the thin client automatically connect to the

devices.

selected. Enter the number of seconds (1 to 3600) be fore trying to reconnect after a
disconnect.

ouse queue timer - Specifies the default queue timer of a mouse event in an ICA or
RDP session (in 1/100 of a second). It can be used to adjust the bandwidth of a
network.

00 x 1200
80 x 1050
20 x 1080
20 x 1200

- Select the color depth of the RDP session. If High Colors (16 bits) or True

ent when dragging - By default, when you grab a Window by the title bar

Redirects locally attached USB devices on the thin client to a Microsoft Windows

e for low speed link - When selected, allows optimization for low-speed

re-connecting - Becomes active if Re-connect after disconnect is

3 Setting Up the Thin Client

This chapter contains information to help you set up your thin client using the System
Setup submenu.

Since the setup information for individual users (user profile) is stored in a remote
database, very little setup is required of a thin client operator. Your user profile is loaded
into the thin client when you log-on. For this reason, you can log-on to another thin client
(under the same account name) and see the same user profile settings.

A few setup items are reserved for local selection (not available to Non-privileged users).
They are available locally because they are user preference items or pertain to the thin
client hardware, rather than the person using the thin client. Additional local settings may
be required if some of the network services are no t av aila ble . Ge ne ra lly, the defaults and
initial setup configurations are adequate and any changes should be made under the
guidance of your network administrator.

To access the local setup menus (System Settings submenu), click User Name (User
Name is the user who is logged-on and is located at the bottom-left side of the taskbar),
and select System Setup.

The System Setup submenu provides access to local system setup dialog boxes for:

• “Setting System Preferences”

• “Configuring Network Settings”

• “Selecting Display Settings”

• “Configuring Dual Monitor Settings”

• “Configuring Serial Communications”

• “Setting Up Printers”

• “Adding and Deleting TCX Licenses Manually”

• “Configuring Touch Screens”

28 Chapter 3

Setting System Preferences

The System Preference dialog box allows you to select personal preferences such as
time zone, screen saver, mouse speed and left/right buttons, keyboard language, and so
on.

Figure 9 System Preference - General tab

Use the following guidelines:

ime Zone - Allows you to select a time zone where the terminal operates (default is

• T

Unspecified).

Note

Time zone is supported by MetaFrame XP FR2 release or later.

• Enable Daylight Saving - Allows you to enable the daylight saving settings. When
selected, the six boxes must be properly configured to define the daylight saving
starting (month/week/day) and ending (month/week/day) periods. Use the following
guidelines:

nth - Specifies the month in the year from January through December.

• Mo

• We

ek - Select 1 through 4 for the week in the month. Week Last denotes the last

week in the month.

• Day

• Scr
to Turn Off Screen. Other selections available include Flying Bubbles and Moving
Image (which are screen savers with the monitor remaining on).

• Ti
minutes, 10 minutes or default is 20 minutes). When the thin client is left idle for the
specified idle time, the screen saver is initiated.

• Des

• T

erminal Name - Allows entry of a name for the thin client. The default is a
14-character string composed of the let ters 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.

- Specifies the day of the week from Monday through Sunday.

een Saver - Allows you to select the type of screen saver you want. The default is

mer - Select a time after which the screen saver is to be activated (either 1 minute, 5

ktop Color - Select the Desktop Color (either 16 bit or 32 bit).

Setting Up the Thin Client 29

Figure 10 System Preference - Advanced tab

• Char

acter Set - Select the character set (Each character is represented by a number.

The ASCII character set, for example, uses the numbers 0 through 127 to repr esent all
English characters as well as special control characters. European ISO character sets
are similar to ASCII, but they contain additional characters for European languages).

• M

ouse Speed and Swap left and right mouse buttons - Select the mouse speed.
You can also swap mouse buttons for left-handed operation by selecting Swap left
and right mouse buttons. If the mouse is changed for use by a left-handed person,
the mouse arrow points right for a local session only. It reverts back to a left-pointing
arrow when an ICA or RDP session opens.

• Key

board Language - Currently the following keyboard languages are supported

(default is English (United States)).

Table 1 Supported Keyboard Languages

Supported Keyboard Languages

Arabic (Saudi Arabia)
Arabic (Iraq)
Arabic (Egypt)
Arabic (Libya)
Arabic (Algeria)
Arabic (Morocco)
Arabic (Tunisia)
Arabic (Oman)
Arabic (Yemen)
Arabic (Syria)
Arabic (Jordan)
Arabic (Lebanon)
Arabic (Kuwait)
Arabic (U.A.E.)
Arabic (Bahrain)
Arabic (Qatar)
Brazilian
Canadian (Multilingual)
Chinese (Simplified)
Chinese (Traditional)

Croatian
Czech
Danish
Dutch
Dutch (Belgian)
English (Australian)
English (3270 Australian)
English (New Zealand)
English (United Kingdom)

English (United States)

Finnish
French (Belgian)
French (Canadian)
French (France)
French (Swiss)
German
German (IBM)
German (Swiss)
Greek
Hungarian

Italian
Italian (Swiss)
Japanese
Korean
Norwegian
Polish (214)
Polish Programmers
Portuguese
Portuguese (Brazil)
Romanian
Slovakian
Slovakian (Qwerty)
Sloven

ian
Spanish
Spanish (Mexican)
Swedish
Turkish
Turkish (QWERTY)
U.S. International

30 Chapter 3

• Delay before
repeat (either 1/5 second, 1/4 second, 1/3 second, 1/2 second, 1 second, 2
seconds, or No Repeat). The default is 1/3 second.

• Repeat Rate -

Figure 11 System Preference - Session tab

repeat - Repeat parameters for held-down key. Select the Delay before

Select Slow, Medium, or Fast. The default is Medium.

Note

Default settings are not active to connections saved in NV-RAM, but do effect
new connections immediately and other connections upon system restart
and log-on.

• Settings common to all sessions - Select the check boxes you want for the options
that are available to all sessions. (The Smart Card check box specifies the default
setting for connecting to a smart card reader at startup.)

Note

ICA sessions always have automatic connection to attached smart card
readers, while RDP connections require use of the Smart Cards check box.

When using the Disks check box for automatic connection to connected
USB sticks, use the following guidelines:

- Support is for VF AT File System only, be sure that the USB stick you use is
formatted to FAT16 or FAT32.

- More than one disk can be used at the same time, however, the maximum
number of USB sticks (including different subareas) is 12.

- It recommended that you use Windows XP, Windows Server 2003, or
Windows Server 2008 for the ICA or RDP server.

- Be sure to save all data and log off from the ICA or RDP session mapping
the USB stick before removing the USB stick.

• Settings common to all ICA sessions - Select the check boxes you want for the
options that are available to all ICA sessions.

Setting Up the Thin Client 31

Configuring Network Settings

The Network Setup dialog box allows you to configure thin client network settings
(including operation in modem dialup and PPPoE modes, as well as locations of servers
essential to thin client operation).

Note

If required by the operating environment, the network administrator may
disable access to this dialog box. Specifically, it cannot be accessed by
Low-privileged and Non-privileged users (and not until after log-on if using
dial-up or PPPoE access). In addition, if the network administrator has set
the lockdown mode by means of an entry in the user profile, both system
reset and access to this dialog box are disabled for Stand-alone users as
well. For more information about system lock do wn , re fer to "Understanding
System Lock-down."

Figure 12 Network Setup - General tab

Use the following guidelines:

hernet Speed - Normally the default (Auto-Detect) should be selected, but another

• Et
selection can be made if automatic negotiation is not supported by your network
equipment. Selections include Auto-Detect, 10 Mb Half-Duplex, 10 Mb Full-Duplex,

100 Mb Half-Duplex, 100 Mb Full-Duplex.

Note

The 10 Mb Full-Duplex option can be selected locally at the device,
however, this mode may need to be negotiated through Auto-Detect.

• No loc
a network through a dial-up modem (for more information, refer to "Configuring Dialup
Modem Access"and "Configuring Serial Communications."

• No local LAN, invoke PPPoE
network through a PPPoE connection. For more information, refer to "Configuring
PPPoE Access."

al Ethernet, Modem dialup only - Select this option if the thin client will access

only - Select this option if the thin client will access a

32 Chapter 3

• Dyna

• Statically specified IP Address - Select this option to manual enter the IP Address,

• DHC

• DHCP User

mically allocated over DHCP/BOOTP - Selecting this option enables the thin
client to automatically receive (from the DHCP server) the following (the network
administrator must configure the DHCP server to provide this information. Any value
provided by the DHCP server will replace any value entered locally, however, locally
entered values will be used if the DHCP server fails to provide replacement values):

• All network settings, including its IP address and the location of the file server.

• A list of PNAgent/PNLite servers that may be

applications.

• A list of Windows domains that can be sele

for PNAgent/PNLite.

• An FTP user name and password to be authenticate d when using non-anonymous

server access.

FTP

• A list of Wyse Device Manager (formerly known as Rapport) servers and the TCP

ort to be used when contacting those servers.

p

• A VDI Broker to be authenticated, when a VDI broker server is specified.

Note

If the thin client is to be used as an LPD server, DHCP cannot be used and a
static IP address must be assigned (see “Configuring LPD Services” ).

Subnet Mask, and Default Gateway.

• IP Addre

The network administrator must provide this information.

• Subn

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. If the
location is other subnet, messages sent to that address must be sent through the
Default Gateway, whether specified through local configuration or through DHCP.
Ask the network administrator for this value.

• De

multiple networks (routing or delivering IP packets between them). The default
gateway is used for accessing the Internet or an intranet with multiple subn ets. If no
gateway is specified, the thin client can only address other systems on the same
subnet. Enter the address of the router that connects the thin client to the Internet.
The address must exist on the same subnet as the thin client as defined by the IP
address and the subnet mask. If DHCP is used, the address can be supplied
through DHCP.

P Vendor ID - Shows the DHCP Vendor ID when the Dynamically allocated

over DHCP / BOOTP option is selected.

allocated over DHCP / BOOTP option is selected.

ss - Must be a valid network address in the thin client server environment.

et Mask - Enter the value of the subnet mask. A subnet mask is used to gain

fault Gateway - Use of gateways is optional. Gateways are used to interconnect

Class ID - Shows the DHCP UserClass ID when the Dynamically

used to obtain a list of published

cted for use when authenticating a user

Setting Up the Thin Client 33

Figure 13 Network Setup - Name Servers tab

Use the following guidelines:

• DNS

Domain and DNS Servers - Use of DNS is optional. DNS allows you to specify
remote systems by their host names rather than IP addresses. If a specific IP address
(instead of a name) is entered for a connection, it rather than DNS will be used to make
the connection. Enter the DNS Domain and the network address of an available DNS
Server. The function of the DNS Domain entry is to provide a default suffix to be used
in name resolution. The values for these two boxes may be supplied by a DHCP
server. If the DHCP server supplies these values, they will replace any locally
configured values. If the DHCP server does not supply these values, the locally
configured values will be used.

Note

You may enter two DNS Server addresses, separated by a sem ico lo n,
comma, or space. The first address is for the primary DNS server and the
second is for a backup DNS server.

• WINS Servers - Use of WINS is optional. Enter the network address of an available
WINS name server. WINS allows you to specify remote systems by their host names
rather than IP addresses. If a specific IP address (instead of a name) is entered for a
connection, it rather than WINS will be 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 will
attempt to resolve the name using DNS first and then WINS.

Note

You may enter two WINS Server addresses (primary and secondary),
separated by a semicolon, comma, or space.

34 Chapter 3

Figure 14 Network Setup - Servers tab

Use the following guidelines:

• File Servers/
server that provides the system software and update images. The address can be
supplied through DHCP if DHCP is used. Use the following guidelines:

• File Servers/Path -

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

• Password - T

Path, Username, and Password - IP address or host name of the FTP

Allows 128 characters maximum. The data specifies part of the

- To log in to the FTP server. Use 15 characters maximum.
o log in to the FTP server. Use 15 characters maximum.

Note

The FTP server also provides global and user profiles (if they exist), optional
custom bitmaps to modify the appearance of the login window (if used), and
bitmaps for custom icons to be used when displaying conne ctions on the
desktop.

• PN Agent/Lite Servers, Rapport Serve rs, Time Servers, VDI Broker T ype, an d VDI
Brokers - 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 server(s) provide thin client time based
on the settings of time zone and daylight saving information. If DHCP is used, locations
can be supplied through DHCP.

Use the VDI Broke
VDM (VMware Virtual Desktop Manager). Choose VDM to enable VDM 2.1 XML

port.

sup

Note

The Virtual Desktop Broker supports both http and http s, and depends on the
Virtual Desktop Broker server support. If http or https is not specified on the
Virtual Desktop Broker server, then http is used by default. If https is
specified, the client side must install a corresponding root certificate.

r Type to set the type of VDI broker. The options are Default and

Setting Up the Thin Client 35

After making a VDI Brokers entry, be sure to reboot the thin client to have the changes
take effect.

You can also click the PNA com

mand button to open the Reconnect Options dialog

box, and further configure the connection for automatic reconnection.

Figure 15 Network Setup - Reconnect options

Figure 16 Network Setup - Options tab

Use the following guidelines:

• DHC

P Option IDs - Enter the supported DHCP options (each value can only be used
once and must be between 128 and 254). For information on DHCP options, refer to
the Administrators Guide: Wyse ThinOS

TM

.

• In

terpret DHCP Vendor-Specific Info - Allows you to enable interpretation of DHCP

Vendor-Specific information.

• T

cp Timeout - Enter the number of 30 seconds for the timeout value of a TCP
connection. The value must be between 1 and 255 which means the connection
timeout value is from 1x30 seconds to 255x30 seconds.

36 Chapter 3

Figure 17 Network Setup - Securi ty tab

Use the following guidelines:

• Net

• Acc

• Enable IEEEE 802.1x authentication -

• EAP T

work Mode - Select either the Wired LAN or Wireless option.

ess T ype - (For Wire less Option Only) Se lect the access type o ption (either None,

WPA_Personal, WPA2_Personal, WPA_Enterprise, or WPA2_Enterprise) to be

used for this wireless communication link.
WPA_Personal a
Key (PSK) encryption can be enabled by selecting one of these options (WPA was
designed to improve upon the security features of WEP; WPA2 provides government
grade security).
WPA_Enterprise an
encryption can be enabled by selecting one of these options (WPA2-Enterprise verifies
network users through a server. WPA2 is backward compatible with WPA).

authentication and activate the EAP Type list of options.

select the EAP Type option you want (TLS, LEAP, or PEAP).

• TL
Authentication Properties dialog box (you can use Browse to find and select the
Client Certificate file and Private Key file you want). Note that the CA certificate
must be installed in the device.

• LEAP - I
Authentication Properties dialog box (be sure to use the correct Username and
Password for authentication). Note that the maximum length for the username or
the password is 64 characters.

• PEAP - If

Authentication Properties dialog box (be sure to select either EAP_GTC or
EAP_MSCHAPv2, and then use the correct Username, Password, and Domain, if

necessary, for authentication). To configure EAP-GTC, enter the username only,
and the password or PIN will be asked when authenticating. To configure
EAP-MSCHAPv2, enter the username, password, and domain (domain\username
in the username box is supported, but you must leave the domain box blank). Note
that the CA certificate must be installed in the device (the server certificate is forced
to be validated).

nd WPA2_Personal - Wi-Fi Protected Access (WPA)_Pre-Shared

d WPA2_Enterprise - Wi-Fi Protected Access (WPA)_Enterprise

Select this check box to enable this

ype - If you have enabled the Enable IEEEE 802.1x authentication check box,

S - If you select the TLS option, click Properties to open and configure the

f you select the LEAP option, click Properties to open and configure the

you select the PEAP option, click Properties to ope n and configure the

Setting Up the Thin Client 37

• Certificate Management - Opens the Certificates Browser where you can select the

Import From option you want to import a certificate (either USB Storage or File
Server).

• USB

Figure 18 Import - USB

Storage - If you select the USB Storage option, click Import to open and use

the Import dialog box to find and select the certificate you want to use. The
maximum importing path is limited to 128 characters and the maximum certificate
name is limited to 64 characters.

• File Server ­Import dialog box to enter the detailed path to th e cer tificate you want to use in the
File Servers box (if necessary, be sure to use the correct Username and
Password). Note that you must enter the absolute path of the certificate. For
example: 10.151.121.100/wnos/cacerts/mycertificate.cer. The maximum importing
path is limited to 128 characters and the maximum certificate na me is limited to 64
characters.

Figure 19 Import - File Server

ireless Setup - (For Wireless Option Only) Clicking Wireless Setup opens the

• W
Wireless Setup dialog box and allows you to configure the parameters required for

wireless wide-band modem access to the enterprise intranet.

If you select the File Server option, click Import to open and use the

Note

Service Set Identification (SSID), Channel, and encryption configurations
must be entered in the Wireless Setup dialog box on the thin client.
Corresponding entries must also be made in the enterprise access point.

38 Chapter 3

Figure 20 Wireless Setup

•Network Mod

Infrastructure (default) - This mode of operation

specification 802.11b/g/n-compliant access point. All communication is done
through the access point which relays packets to other wireless clients as well as to
nodes on a wired Ethernet network.
Ad Hoc - This is
mode, only one wireless cell is supported for each different Service Set
Identification (SSID). All communication is done client-to-client without the u se of an
access point.

• SSID - E

the network administrator for this wireless communication link (maximum is 32
characters).

• Channel - Sele

communication link (the channel can only be selected in Ad Hoc mode; the chan nel
is automatically selected in Infrastructure mode based on the relative strength of
signals from the available access points).

• Algorith

WPA/2 is selected as access type, it will be disabled and selected to be ‘Open’
automatically

• Encryption - Sele

#2, WEP Key #3, WEP Key #4, WPA_PSK, WPA2_PSK , WPA_Enterprise, or
WPA2_Enterprise) to be used for this wireless communication link (If WPA is

selected, TKIP and CCMP will be supported; if WPA2 is selected, CCMP will be
supported).

None - S
WEP Key #1 through #4 - Wire

enabled by selecting one of these options.
WPA_PSK an
(PSK) encryption can be enabled by selecting one of these options (WPA was
designed to improve upon the security features of WEP; WPA2 provides
government grade security).
WPA_Enterprise an
(WPA)_Enterprise encryption can be enabled by selecting one of these optio ns
(WPA2-Enterprise verifies network users through a server. WPA2 is backward
compatible with WPA).

e options:

requires the presence of an IEEE

the IEEE 802.11b/g/n peer-to-peer mode of operation. In this

nter the Service Set Identification (name of the wireless network) set up by

ct the frequency channel (1 through 14) to be used for this wireless

ms - Select either Open or Shared Key for the authentication type. When

ct the encryption option (either None, WEP Key #1, WEP Key

elect None if encryption is not required.

d Equivalent Privacy (WEP) encryption can be

d WPA2_PSK - Wi-Fi Protected Access (WPA)_Pre-Shared Key

d WPA2_Enterprise - Wi-Fi Protected Access

Setting Up the Thin Client 39

Key - If active (depending on Encryption option), enter the key according to the
dialog box Note area. The selected key is used to encrypt/decrypt each frame
transmitted from or received by the wireless adapter. The access point must
recognize frames encrypted by the same key. Keys can be 5 or 13 characters for
the 64 or 128 bit encryption key, or specified as 10 or 26 hex-decimal digits.

Selecting Display Settings

The Display Setup dialog box allows you to select the resolution and refresh rate for the
monitor used with the thin client. The number of icons that can be displayed on the
desktop depends on the desktop resolution and administrator configuration.

Note

On thin clients that only support 8 bit color, the 1280 x 1024 resolution will be
used to display full screen connections. The 1280 x 1024 resolution will not
be used to display the desktop, windowed connections, or seamless
connections.

If configured by your administrator (Longapp
wnos.ini), the number of icons displayed for a resolution is as follows:

• 640 x 480: Up to 8 icons are displayed.

• 800 x 600: Up to 10 icons are displayed.

• 1024 x 768: Up to 21 icons are displayed.

• 1280 x 1024: Up to 40 icons are displayed.

• 1360 x 768: Up to 28 icons are displayed.

• 1400 x 1050: Up to 40 icons are displayed.

• 1440 x 900: Up to 32 icons are displayed.

• 1600 x 1200: Up to 60 icons are displayed.

• 1680 x 1050: Up to 50 icons are displayed.

• 1920 x 1080: Up to 60 icons are displayed.

• 1920 x 1200: Up to 72 icons are displayed.

Figure 21 Display Setup

licationname=yes as defined in

40 Chapter 3

Use the following guidelines:

• Selec

t best display setting on DDC monitor - If the monitor is VESA DDC2B
(Display Data Channel) compatible, selection of this option allows the thin client to
automatically select the best resolution and refresh rate. If your monitor is not DDC
compatible, a Monitor does not support Plug and Play message is displayed (click OK
to acknowledge the message and remove it from the screen).

• DDC

table - If the monitor is VESA DDC2B (Display Data Channel) compatible,
selection of this option allows you to select the resolution and refresh rate you want
from the list.

• Use

r defined display setting - Select this option and sele ct the resolution and re fresh

rate supported by your monitor (all combinations are allowed):

• Resolution

list selections include:

640 x 480
800 x 600 (default)
1024 x 768
1280 x 1024
1360 x 768
1400 x 1050
1440 x 900
1600 x 1200
1680 x 1050
1920 x 1080
1920 x 1200

• Refresh

rate list selections include:

60 Hz (default)
75 Hz
85 Hz

• Usage Help ar

ea - Contains brief instructions for using the Display Setup dialog box
and running the test. No operator entry can be made in this box. Make note of the
instructions in the area regarding v-key reset usage in case of display failure.

Configuring Dual Monitor Settings

(Supported Dual Monitor Capable Thin Clients Only) The DualHead Setup dialog box
allows you to configure the way two monitors display.

Figure 22 DualHead Setup

Use the following guidelines:

• Dual Head - Select Disab

le to have the two monitors work in a matching state, or

Enable to have the two monitors work separately (second is extended from first).

Setting Up the Thin Client 41

• 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.

entation - Select how you want the two monitors to display (Horizontal or

• Ori

Vertical).

askbar - Select under which screen you want the Taskbar to appear (Whole

• T
Screen or Main Screen).

Configuring Serial Communications

The Serial Setup dialog box allows configuration of the ports used for modem dialup
mode and serial communications. A serial port can be used for modem access to a
network (intranet or Internet) through a dial-up server (for example, a Microsoft Remote
Access Server, or an ISP supporting industry-standard protocols) as an alternative or
supplement to using the thin client network port (see “Using and Configuring Access
Connections” ). For this use, a USB modem or a converter and a serial modem must be
connected to the thin client USB port. A USB hub may be employed to support up to two
USB ports if another USB connector is not available on your thin client (see "Configuring
Dialup Modem Access"). For supported converters, refer to the Wyse Web site.

Note

With Wyse software version 4.2 and later, ICA virtual COM driver supports
synchronizing with Palm devices over a serial port.

Figure 23 Serial Setup

Use the following guidelines:

• Select Port -

2, COM 3, or COM 4 can be selected (default is Port COM 1). For Models SX0 and
VX0, COM 1 or COM 2 selects from either the USB or serial device.

• Baud Rate ­can be selected (default is 9600).

ity - Either None, Even, or Odd can be selected (default is None).

• Par

Select the port to which this setup definition applies. Either COM 1, COM

Either 1200, 2400, 4800, 9600, 19200, 38400, 57600, or 115200 baud

42 Chapter 3

op - Either 1, 1.5, or 2 stop bits can be selected (default is 1).

• St

• Size

• Flow Con
is None).

• Serial Touch Screen selections - Select the proper touch screen ELO, MicroT

FastPoint from the list.

ouch Screen on - Select the proper serial port (COM port) or None from the list.

• T

Setting Up Printers

The Printer Setup dialog box allows configuration of network printers and local printers
that are connected to the thin client (USB and Serial). Through its USB port s, a thin client
can support multiple printers. If more than on e printer is to b e used and an other port is no t
available on your thin client and the port that is to be used must be shared with a USB
modem converter, connect a USB hub to the port.

Note

If required, USB-to-Parallel and USB-to-Serial converter cables are available
from Wyse Technology. Port LPT1 or LPT2 selects the connection to a USB
printer or parallel printer through a USB-to-Parallel cable. Port COM1 or
COM2 selects the connection to a serial device through a USB-to-Serial
cable. For ordering information, refer to the Wyse Web site at:

http://www.wyse.com/products/accessories/accessories.asp.

- Character size 5, 6, 7, or 8 bits can be selected (default is 8).

trol - Either None, XON/XOFF, CTS/RTS, or Both can be selected (default

ouch or

Typically, printers are also available through the ap
network printers and printers locally connected to the application servers. When
connecting to a Citrix server, the locally connected printer shows as the default printer.

Figure 24 Printer Setup - Ports tab

plication sessions. This can include

Setting Up the Thin Client 43

Use the following guidelines:

• Select Port - Select th

• Printer Name ­selected, the printer name becomes the queue name for other clients using LPR to
print to this printer.

• Printer Identification ­either the device driver name for the printer under the Microsoft Windows system, or a
key to map to the device driver. If not specified, the name will be defaulted to the
printer-supplied identification for standard direct-connected USB printers or Generic /
Text Only for non-USB or serial-connected printers upon connection to Windows
hosts. The driver name mapping takes place either through a printer -m app ing file re ad
by the system as part of the Global system profile (wnos.ini) or by MetaFrame servers
through the MetaFrame printer configuration file (\winnt\system32\wtsprnt.inf).

Note

Most USB direct-connected printers or parallel printers connected through
USB-to-parallel cable converters do report their printer identifications. Port
LPT1 or LPT2 selects the connection to a USB printer or parallel printer
through a USB-to-Parallel cable. Port COM1 or COM2 selects the connection
to a serial device through a USB-to-Serial cable.

This is a required entry. If Enable LPD service for the printer is

e port you want from the list.

Enter the type or model of the printer. This name should be

In an ICA environment, it is recommended that administrators use the wtsprnt.inf file to
define printer driver mapping to maintain the consistency of usage from various ICA
client devices. In an RDP environment, administrators should use the wnos.ini file to
define printer driver mapping. If there is no mapping file, or if the mapping entry for the
printer is not found, the identification must be a supported driver name on the
connected hosts for the printer to be automatically created on the hosts.

• Printer Class - Select the printer class from the list.

• En

able the printer device - Must be selected to enable the directly-connected printer.

• Enable LPD
Printer Daemon) server for LPD printing requests from the network (see “Configuring
LPD Services” ).

Note

If the thin client is to be used as an LPD printer server, DHCP must not be
used and a static IP address must be assigned to the thin client (see
“Configuring Network Settings” for more details).

service for the printer - Select this to make the thin client an LPD (Line

44 Chapter 3

Figure 25 Printer Setup - LPDs tab

Use the following guidelines:

• Select LPD - Select th

• Printer Name -

• Printer Identification ­either the device driver name for the printer under the Microsoft Windows system, or a
key to map to the device driver. If not specified, the name will be defaulted to the
printer-supplied identification for standard direct-connected USB printers or Generic /
Text for non-USB or serial-connected printers upon connection to Windows hosts. The
driver name mapping takes place either through a printer-mapping file read by the
system as part of the Global system profile (wnos.ini) or by MetaFrame server s through
the MetaFrame printer configuration file (\winnt\system32\wtsprnt.inf).

e port you want from the list.

Enter the printer name.

Enter the type or model of the printer. This name should be

In an ICA environment, it is recommended that a
define printer driver mapping to maintain the consistency of usage from various ICA
client devices. In an RDP environment, administrators should use the wnos.ini file to
define printer driver mapping. If there is no mapping file, or if the mapping entry for the
printer is not found, the identification must be a supported driver name on the
connected hosts for the printer to be automatically created on the hosts.

• LPD Ho
address can also be entered.

• LPD Queue Name - An LPD host maintains a named queue for each supported
printer. Enter the name of the queue associated with the printer to be used.

• Printer Class - Select the printer class from the list.

• En

sts - The DNS or WINS name of the server for the network printer. An IP

Note

If the printer is attached to another thin client on your network, the entry in
the LPD Hosts box is the name or address of that thin client.

Note

The LPD Queue Name must match the content of the Printer Name box on
the thin client with the printer attached.

able the printer device - Must be selected to enable the directly-connected printer.

dministrators use the wtsprnt.inf file to

Setting Up the Thin Client 45

Figure 26 Printer Setup - SMBs tab

Use the following guidelines:

• Select SMB - Sele

• Printer Name -

• Printer Identification ­either the device driver name for the printer under the Microsoft Windows system, or a
key to map to the device driver. If not specified, the name will be defaulted to the
printer-supplied identification for standard direct-connected USB printers or Generic /
Text for non-USB or serial-connected printers upon connection to Windows hosts. The
driver name mapping takes place either through a printer-mapping file read by the
system as part of the Global system profile (wnos.ini) or by MetaFrame server s through
the MetaFrame printer configuration file (\winnt\system32\wtsprnt.inf).

ct the SMB you want from the list.

Enter the printer name.

Enter the type or model of the printer. This name should be

In an ICA environment, it is recommended that a
define printer driver mapping to maintain the consistency of usage from various ICA
client devices. In an RDP environment, administrators should use the wnos.ini file to
define printer driver mapping. If there is no mapping file, or if the mapping entry for the
printer is not found, the identification must be a supported driver name on the
connected hosts for the printer to be automatically created on the hosts.

ost\Printer - Enter the Host\Printer or use Browse next to the box to make the

• \\H
selection you want.

• Print

• En

• Enable LPD service - Select

er Class - Select the printer class from the list.

able the printer device - Must be selected to enable the directly-connected printer.

this to make the thin client an LPD (Line Printer Daemon)
server for LPD printing requests from the network (for more information refer to
"Configuring LPD Services."

dministrators use the wtsprnt.inf file to

46 Chapter 3

Figure 27 Printer Setup - Options tab

Use the following guidelines:

fault Printer - Select the printer you want to be the default printer from the list.

• De

• Enable .

Client and then enter the Port.

print Client and Port - If you want to enable .print Client, select Enable .print

Figure 28 Printer Setup - Help tab

The Help tab contains printer help information.

Configuring LPD Services

A thin client can be configured to provide LPD (Line Printer Daemon) services, making the
thin client a printer server on the network.

Set-up the thin client that is to provide LPD print services as follows:

1. Open the Network Setup dialog box (Desktop Menu | System Setup | Network) and
enter a static IP address for the thin client (ask your network administrator for an IP
address).

2. Open the Printer Setup dialog box (Desktop Menu | System Setup | Printer) and
select any of the listed ports.

3. Name the printer in the Printer Name box.

4. Select Enable LPD service for the printer.

Setting Up the Thin Client 47

5. Select Enable the Printer Device.

6. Set up the application server as described in either “Setting Up Wind ows NT4 Servers”

or “Setting Up Windows 2000/2003/2008 Servers” .

Setting Up Windows NT4 Servers

1. Navigate to Control Panel | Network | Services and ensure that 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. Nav

b. T

c. T

d. Click

3. Af

application server. For example, select the manufacturer printer type and printer name.

igate to Control Panel | Printers | Add Printers | My Computer | Add Port
and double-click LPR PORT (if you do not see LPR Port, ensure that the Microsoft
TCP/IP Printing service is installed correctly).

ype the thin client IP address or DNS name in the Name or address of host

providing LPD box.

ype the printer name (assigned in “Configuring LPD Services” ) in the Name of

printer on that machine box.

OK, and then click NEXT.

ter you have selected the printer, you can perform your normal printer setup for the

Setting Up Windows 2000/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. Nav

igate to Control Panel | Printers | Add Printers | Local Printer | Create a

new port and select LPR PORT.

Note

If you do not see LPR Port, ensure that the Microsof t TCP/IP Printing service
is installed correctly.

b. Type the thin client IP address or DNS name in the Name or address of host

providing LPD box.

ype the printer name (assigned in “Configuring LPD Services” ) in the Name of

c. T

printer on that machine box.

d. Click

3. Af

application server. For example, select the manufacturer printer type and printer name.

OK, and then click NEXT.

ter you have selected the printer, you can perform your normal printer setup for the

48 Chapter 3

Adding and Deleting TCX Licenses Manually

Although, Wyse recommends entering TCX licenses in the INI file (so they will be loaded
automatically upon thin client boot), the TCX License dialog box allows you to activate
TCX features by entering licenses manually.

To add TCX licenses manually:

1. Open the TCX License dialog box (Desktop Menu | System Setup | TCX License).

2. Enter the license in the Input TCX License box (you can enter more than one license

using commas for separation).

3. Click Add. The license will be added to the Licenses list.

Note

You can delete a license by selecting it from the Licenses list and clicking

Delete.

Configuring Touch Screens

The Touch Screen Setup window allows configuration of touch screens that are connected
to the thin client (USB and Serial). The setup window is automatically invoked when the
terminal detects that a touch screen is attached through a USB port and the setup (or
calibration) has not been performed. In addition, the calibration sequence is executed
whenever Touch Screen is selected from the Desktop menu.

Note

The Touch Screen Desktop menu item is grayed out until a touch screen is
connected. All ELO USB-based touch monitors and the M150-USB touch
monitor from MicroTouch are supported.

The Touch Setup window prompts you to touch
necessary calibration adjustment. Once calibrated, the adjustment values are saved in the
local terminal NVRAM until the system is reset to factory default, or another type of touch
monitor is connected.

two circles on the screen to make the

4 Using and Configuring Access

Connections

This chapter provides information and detailed instructions on using and configuring
connections to access the enterprise server environment available to the thin client.

This section includes information on:

• “Using Ethernet Direct Access”

• “Using Wireless Direct Access”

• “Configuring PP

• “Configuring Dialup Modem Access”

• “Configuring PPTP VPN Access”

Using Ethernet Direct Access

This is a direct connection from the thin client Ethernet port to the enterprise intranet. No
additional hardware is required.

PoE Access”

Using Wireless Direct Access

An 802.11b/g/n USB Wireless Adapter can be used to access the enterprise intranet. The
adapter connects to a USB port on the thin client and uses short- range wide-band radio to
communicate with a wireless access point. Typically, wireless access points are located at
several locations in the enterprise within range of the 802.11b/g/n USB Wireless Adapters
and directly connect to the enterprise intranet.

After a wireless connection is made to the enterprise intranet, operation o f the thin client
through the wireless link is the same as Ethernet direct access.

Note

The speed of the connection is a function o f signal streng th, with a maximum
of 11 Mbps for 802.11b and 54 Mbps for 802.11g/n.

For setup information, refer to "

Configuring Network Settings."

50 Chapter 4

Configuring PPPoE Access

PPPoE (Point-to-Point Protocol over Ethernet) is a specification for connecting users on
an Ethernet to the Internet or intranet through a common broadband medium, such as a
single DSL line, wireless device, or cable modem. PPPoE combines the Point-to-Point
Protocol (PPP), commonly used in dialup connections, with the Ethernet protocol, which
supports multiple users in a local area network. The PPP protocol information is
encapsulated within an Ethernet frame.

The PPPoE Manager is available from the desktop to configure and invoke PPPoE
connection to WAN. Once connected, all W AN packet s are though a PPP connection over
Ethernet to the DSL modem. The PPPoE Manager is not accessible for users with sign-on
privilege set to None.

Selecting PPPoE Manager in the Desktop menu opens the PPPoE Manager . The PPPoE
Manager can also be set to open automatically on thin client start as described in
"Configuring Network Settings."

Figure 29 PPPoE Manager

Use the following guidelines:

gin Username - Enter the login username required for this connection (up to 43

• Lo
characters).

gin Password - Enter the login password required for this connection (up to 15

• Lo
characters).

• Aut

• Use default

After configuring, click Connect to initiate a PPPoE connection.

o-connect on system startup - When selected, causes the connection to be

made automatically on system startup (default is cleared).

gateway on remote (PPPoE) network - When selected, causes the

connection to use the default gateway (default is cleared).

Using and Configuring Access Connections 51

Configuring Dialup Modem Access

A USB dial-up modem or a USB-to-Serial adapter connected to a serial modem can be
used with the thin client to access a dial-up server.

The dial-up server may provide either of two paths to the enterprise intranet:

• An enterprise dial-up server will directly

• An Internet Service Provider (ISP) dial-up server
which the thin client must access an enterprise PPTP VPN server that connects to the
enterprise intranet.

The Dialup Manager is used to initiate a connection to a dialup server through a modem.
Selecting Dialup Manager in the Desktop menu opens the Dialup Manager. The Dialup

Manager can also be set to open automatically on thin client start as described in
"Configuring Network Settings."

Note

Applications accessed through a dialup connection generally should have
the Optimize for low speed link option selected in the user profile or the
Connection Settings (ICA or RDP) dialog box.

connect to the enterprise intranet.

provides access to the Internet, from

Figure 30 Dialup Manager

Use the following guidelines:

• Dial Des
property entry created using the Dialup Property dialog box.

• Dial - Initiates dialing for a currently
dialog box opens displaying messages and allowing you to refresh, reset, or
disconnect the connection. If you are using a USB modem, the Serial Setup dialog
box must be configured correctly to initiate a successful connection.

• New ­connection entry in the list of connections.

• Edit - Ope
dialog box to edit the connection.

• Delete ­is displayed, asking you to confirm the deletion.

cription/Protocol area - Lists a description and protocol of each dialup

-selected list entry. After initiation, a Dialup Status

Opens the Dialup Property dialog box. Use this dialog box to create a new

ns the Dialup Property dialog box for a currently-selected list entry. Use this

Deletes the dialup property record for a currently-selected list entry. A warning

Caution

Deleting the record is irreversible. A deleted record must be recreated to be
made available again.

52 Chapter 4

Dialup parameters for each dialing entry are entered using the Dialup Prope rty dialog
box.

Figure 31 Dialup Property

Use the following guidelines:

• Dialup De
Manager list of entries.

• Phon

• Dialing Port ­is COM 1. For information on serial port configuration, refer to "Configuring Serial
Communications."

gin Username, Password, and Domain - Enter the login name, password, and

• Lo
domain required for this connection. This information is used for logging in to the PPP
session.

gin Script area - This feature provides a facility for logging in to systems which do

• Lo
not dedicate modem ports to the PPP protocol and require a serial login before
initiating the PPP protocol (typically *NIX systems). It provides for automation of
responses that otherwise must be entered manually in response to messages received
from the dialed server and displayed in the message box of the Dialup Status dialog
box. The specific scripts are unique to each target system. Using the escape codes
listed under the box, as needed, create the script as Expected S tring <space> Output
String pairs. Place quotation marks around strings that have spaces in them. The
required strings can be tested by entering them manually in the Dialup Progress
dialog box.

Note

Ask your network administrator for specific script requirements.

scription - Enter the descriptive name that will appear in the Dialup

e Prefix Number - Enter the phone number to be dialed.

Select the port through which this connection is to be made. The defa ult

• Interface login to the dialup server - This o ption is a n alte rn ative to providin g a lo gin
script. Enable (select Enable) the interactive login featur e on ly if the dial e d serv e r
requires it. The Dialup Status dial og box (w hich o pen s wh en th e con nection is diale d)

Using and Configuring Access Connections 53

will display prompts from the dialed machine. Type the appropriate responses directly
in the status display area.

Note

Ask your network administrator for the dialed server password and other
dialog requirements.

• Enable protocol compression - When selected, allows data that is being
communicated using the selected protocol (PPP or SLIP) to be compressed (default is
selected).

• Aut

o-dial on system startup - When selected, causes the connection to be dialed

automatically on system startup (default is cleared).

Note

When the Default Gateway, DNS Domain, DNS Server, and File Server
boxes in the Network Setup dialog box are configured and Auto-dial on
system startup is enabled, both firmware revision checking and thin client
sign-on are active (sign-on is only active if the profile on the FTP server
enables it).
The Default Gateway, DNS Domain, DNS Server, and File Server boxes
are required to enable access to an FTP server after the completion of
establishing a PPP connection. However, only the File Server path is
required to accomplish firmware revision checking and update (the more
complicated the network topology in the target network, the more values are
required in order to contact the FTP server).
If both Auto-dial on system startup is selected and Auto-connect on system
startup is selected in a PPTP connection, the dial-up connection will be
completed before the PPTP connection is initiated.

• Enable MPPE - When selected, enables MPPE (Microsoft Point-to-Point Encryption).
MPPE is a method of encrypting data transferred across Point-to-Point Protocol
(PPP)-based dial-up connections or Point-to-Point Tu nneling Protocol (PPTP) virtual
private network (VPN) connections. MPPE uses the RSA algorithm for encryption and
supports 40-bit and 128-bit session keys, which are changed frequently to ensure
security. MPPE does not compress or expand data.

After dialup initiation, the Dialup S
allowing you to refresh, reset, or disconnect the connection.

tatus dialog box opens displaying messages and

54 Chapter 4

Figure 32 Dialup Status

Use the following guidelines:

ssage area - Displays messages as dialing progresses and the connection is

• Me
established. If this is an interactive login connection, type appropriate responses to
messages if you are prompted (ask your network administrator for the dialed server
password and other dialog requirements).

• Data area - Displays data and statistics about the connection.

• Refresh - Updat

• Reset

• Disco

es the statistics display of the connection.

- Cancels dialing and resets the connection statistics area to 0.

nnect - Disconnects the connection.

Configuring PPTP VPN Access

PPTP (Point-to-Point Tunneling Protocol) is a network pro tocol that enables the secure
transfer of data between a remote client (in this case a thin client) and an enterp rise server
environment by creating a virtual private ne two rk (VPN) across TCP/IP-based data
networks such as the Internet. It provides a password-protected path through the
enterprise firewall to the enterprise server environment in which the network and session
services required by thin clients reside.

The PPTP Manager is used to initiate a connection to a virtual private network (VPN)
PPTP server through any of several access services (for example, dial-up, cable, or DSL).
Connection parameters are entered using the PPTP Property dialog box.

Note

Modem access to an Internet Service Provider (ISP) server must be
established before attempting to use this dialog box.

Selecting PPTP Manager in the Desktop menu opens the PPTP Manager. The PPTP
Manager can also be set to open automatically on thin client start as described in
"Configuring Network Settings."

Using and Configuring Access Connections 55

Figure 33 PPTP Manager

Use the following guidelines:

• Des

• Conn

• New -

• Edit -

• Delete - Deletes

cription/Protocol area - Lists a description and protocol of each PPTP property

entry created using the PPTP Property dialog box.

ect - Initiates a PPTP connection for a currently-selected list entry. After initiation,
a PPTP Status dialog box opens (if Show progress in detail is selected in the PPTP
Property dialog box and a path to an enterprise PPTP VPN server is available)
displaying messages and allowing you to refresh or disconnect the connection. A
PPTP connection is also initiated automatically on system start-up if this feature is
selected in the PPTP Property dialog box.

Opens the PPTP Property dialog box. Use this dialog box to create a new

connection entry in the list of connections.

Opens the PPTP Property dialog box for a currently-selected list entry. Use this
dialog box to edit the connection.

the PPTP property record for a currently-selected list entry. A warning

is displayed, asking you to confirm the deletion.

Caution

Deleting the record is irreversible. A deleted record must be recreated to be
made available again.

PPTP parameters for each PPTP entry are entered using the PPTP Property dialog box.

Figure 34 PPTP Property

56 Chapter 4

Use the following guidelines:

• PPTP Description - Enter the descriptive name that will appear in the PPTP Manager
list of

• PPTP Servers
PPTP 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.

gin Username, Password, and Domain - Enter the login name, password, and

• Lo
domain required for this connection.

• Aut

• Show progr

• Enable MPPC -

o-connect on system startup - When selected, causes the connection to be

made automatically on system startup. (default is cleared).

(after connection initiation and a path to an enterprise PPTP VPN server is available)
displaying messages and allowing you to refresh or disconnect the connection.

MPPC scheme is a means of representing arbitrary Point-to-Point Protocol (PPP)
packets in a compressed form. T he MPPC algorithm is de signed to optimize pr ocessor
utilization and bandwidth utilization in order to support a large number of simultaneous
connections. The MPPC algorithm is also optimized to work efficiently in typical PPP
scenarios (1500 byte MTU, and so on).

entries.

- List of IP addresses or host names with optional TCP port number of

ess in detail - When selected, enables a PPTP Status dialog box opens

When selected, enables Microsoft Point-to-Point Compression. The

After connection initiation, the PPTP S
allowing you to refresh or disconnect the connection.

Figure 35 PPTP Status

Use the following guidelines:

ssage area - Displays messages as the connection is established. If this is an

• Me
interactive login connection, type appropriate responses to messages if you are
prompted (ask your network administrator for the PPTP server password and other
dialog requirements).

a area - Displays data and statistics about the connection.

• Dat

• Refresh - Updat

• Disco

nnect - Disconnects the connection.

es the statistics display of the connection.

tatus dialog box opens displaying messages and

5 Using the Network Test Tools

This chapter contains information on using the network test tools available on the thin
client.

Ping (Packet InterNet Groper) and Trace Route can be used for checking the integrity of
the network connection (ping also checks the usability of the network configuration and
the availability of all equipment required to communicate between the thin client and the
ping destination). These tools can be accessed from the Network Test submenu of the
Desktop menu (generally, ping and Trace Route are used for system diagnostics by, or
under the direction of, a network administrator).

Using Ping

The Ping dialog box executes the ping diagnostic utility and displays response messages.
Ping is a diagnostic tool that sends an echo request to a networ k host. The host pa rameter
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. By default, echo requests are sent until interrupted (by
clicking Stop in the Ping dialog box). The ping utility sends one echo request per second
and calculates round trip times and packet loss statistics, and 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

• Test, measure, and manage networks

• Determine the IP address of a host if

Note

Not all network equipment will respond to ping packets, since this is a
common mechanism used in denial-of-service attacks. Lack of response
does not necessarily indicate that the target of the ping is unusable for other
purposes.

Figure 36 ping

only the hostname is known

58 Chapter 5

Use the following guidelines:

• Enter Hostname
WINS-registered host name of the target to be pinged.

• Data area - Displays ping response messages. The ping command sends one echo

equest per second, calculates round trip times and packet loss st atistics, and displays

r
a brief summary upon completing the calculation.

art - Executes the ping command. If the host is operational and on the network, it

• St
responds to the echo request. By default, echo requests are sent until interrupted by
clicking Stop.

op - Terminates the ping request and leaves the Ping dialog box open (so you can

• St
read the summary posted in the data area).

Using Trace Route

The Trace Route dialog box executes the tracert diagnostic utility and displays response
messages. 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.

or IP - Enter the IP address, DNS-registered host name, or

Figure 37 Trace Route

Use the following guidelines:

• Enter Hostname
WINS-registered host name of the target to be traced.

• Data area - Displays round-trip response time and identifying information for each

evice in the path.

d

art - Executes the tracert command.

• St

• St

op - Terminates the tracert command and leaves the Trace Ro ute dialog box open

(so you can read the information posted in the data area).

or IP - Enter the IP address, DNS-registered host name, or

Figures

1 Desktop example 11
2 Desktop menu 14
3 Connect Manager (High-privileged user example) 17
4 Connection Settings (ICA) - Server option 20
5 Connection Settings (ICA) - Published Application option 20
6 Connection Settings (ICA) - Options tab 22
7 Connection Settings (RDP) - Connection tab 24
8 Connection Settings (RDP) - Options tab 25
9 System Preference - General tab 28
10 System Preference - Advanced tab 29
11 System Preference - Session tab 30
12 Network Setup - General tab 31
13 Network Setup - Name Servers tab 33
14 Network Setup - Servers tab 34
15 Network Setup - Reconnect options 35
16 Network Setup - Options tab 35
17 Network Setup - Security tab 36
18 Import - USB 37
19 Import - File Server 37
20 Wireless Setup 38
21 Display Setup 39
22 DualHead Setup 40
23 Serial Setup 41
24 Printer Setup - Ports tab 42
25 Printer Setup - LPDs tab 44
26 Printer Setup - SMBs tab 45
27 Printer Setup - Options tab 46
28 Printer Setup - Help tab 46
29 PPPoE Manager 50
30 Dialup Manager 51
31 Dialup Property 52
32 Dialup Status 54
33 PPTP Manager 55
34 PPTP Property 55
35 PPTP Status 56
36 ping 57
37 Trace Route 58

60

Tables

1 Supported Keyboard Languages 29

Users Guide

Wyse ThinOS

TM

Issue: 020810

Written and published by:
Wyse Technology Inc., February 2010

Created using FrameMaker

®

and Acrobat

®