Dell Wyse C10LE, Wyse ThinOS D10D, Wyse ThinOS D10DP, Wyse ThinOS R10L, Wyse ThinOS T10, Wyse ThinOS T10D, Wyse ThinOS V10LE Administrator's Manual

PDF

Document

Administrators Guide

Dell

Wyse ThinOS

Products: C10LE, D10D, D10DP, R10L, T10, T10D, V10LE

Issue: 011614

PN: 883682-08 Rev. AF

Copyright Notices

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 End User License Agreement is included in the software and provided for your reference only.

The License at http://www.wyse.com/license as of the purchase date is the controlling licensing agreement. By copying, using, or installing the software or the product, you agree to be bound by those terms.

Trademarks

The Dell, Wyse, and PocketCloud logos and Wyse and PocketCloud are trademarks of Dell 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 .

Ordering Information

For availability, pricing, and ordering information in the United States and Canada, call 1-800-438-9973 or visit us at

Dell.com

. In all other countries, contact your sales representative.

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 Dell Inc, could void the user’s authority to operate the equipment.

Regulatory Compliance for Wyse 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.

Wireless Usage and Requirements

Radio transmitting type devices (RF module) are present in models with the wireless option. These devices operate in the 2.4 GHz band (i.e. 802.11 A/B/G/N & Bluetooth).

As a general guideline, a separation of 20 cm (8 inches) between the wireless device and the body, for use of a wireless device near the body (this does not include extremities) is typical. This device should be used more than 20 cm (8 inches) from the body when wireless devices are on and transmitting.

Some circumstances require restrictions on wireless devices. Examples of common restrictions include:

•

When in environments where you are uncertain of the sanction to use wireless devices, ask the applicable authority for authorization prior to use or turning on the wireless device.

•

Every country has different restrictions on the use of wireless devices. Since your system is equipped with a wireless device, when traveling between countries with your system, check with the local Radio Approval authorities prior to any move or trip for any restrictions on the use of a wireless device in the destination country.

•

Wireless devices are not user-serviceable. Do not modify them in any way. Modification to a wireless device will void the authorization to use it. Please contact the manufacturer for service.

Device Power Supply

Use only the external power supply that comes with your thin client. For power and voltage ratings, see the serial number label or regulatory label on your device. For power adapter replacement, contact your Service

Representative. For proper replacement compare the labels on both mobile thin client and power adapter to ensure that their voltages match.

WARNING

: Use of any other power adapter may damage your mobile thin client or the power adapter. The damage caused by an improper power adapter is not covered by warranty.

Battery Information

Models Cx0, Dx0D, Rx0L, T10, and VX0 contain an internal button cell battery replaceable by Dell or one of our

Authorized Service Centers. For service, visit http://www.wyse.com/support/authorized-service-centers .

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.

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.

1 Introduction

About this Guide 2

Finding the Information You Need in this Guide 2

Dell Technical Support 2

2 Getting Started: Quickly Learning the Basics

Connecting to a Remote Server 4

Manual Connection Procedures 5

Using Your Desktop 6

Configuring Thin Client Settings and Connection Settings 7

Connecting to a Printer 7

Connecting to a Monitor 7

Locking the Thin Client 7

Signing Off and Shutting Down 8

Additional Getting Started Details 9

Zero Desktop Features 9

Zero Interactive Desktop Guidelines 9

Zero Toolbar 10

List of Connections 11

Classic Desktop Features 12

Classic Interactive Desktop Guidelines 12

Shortcut Menu 13

Desktop Menu 14

Connect Manager 15

Accessing System Information 17

3 Configuring Thin Client Settings Locally

Local Settings Menu 20

System Preferences 21

Display 23

Peripherals 25

Printer 28

Reset Features 32

Resetting to Factory Defaults Using G-Key Reset 32

Resetting to Factory Defaults Using Shutdown Reset 32

Resetting Display Settings Using V-Key Reset 32

Accessing Thin Client BIOS Settings 32

4 Configuring Connection Settings Locally

Global Connection Settings 34

Connectivity Menu 37

Network Setup 38

Enabling a Disabled Network Setup Dialog Box 44

Remote Connections 45

Central Configuration 48

Advanced Details on Configuring ICA and RDP Connections 50

Configuring ICA Connections 50

Configuring RDP Connections 54

Contents

5 Performing Diagnostics

System Tools 58

Network Tools 61

Using Ping 61

Using Trace Route 62

A Central Configuration: Automating Updates and Configurations

How to Set Up Automatic Updates and Configurations 64

Step 1: Prepare the Root Directory and Folder Structure on the Server 64

Step 2: Direct the Thin Client to the Server Using DHCP Options 65

Step 3: Reboot or Start the Thin Client 68

B CMOS Management

CMOS Central Management: Extracting CMOS Settings to the File Server for

Distribution 70

CMOS Local Management: Extracting CMOS Settings to a USB Key for Distribution 72

C Examples of Common Printing Configurations

Printing to Local USB or Parallel Printers 74

Using the Printer Setup Dialog Box for Local USB or Parallel Printers 74

Using INI Parameters for Local USB or Parallel Printers 74

Printing to Non-Windows Network Printers (LPD) 76

Using the Printer Setup Dialog Box for Non-Windows Network Printers (LPD) 76

Using INI Parameters for Non-Windows Network Printers (LPD) 77

Printing to Windows Network Printers (SMB) 78

Using the Printer Setup Dialog Box for Windows Network Printers (SMB) 78

Using INI Parameters for Windows Network Printers (SMB) 81

Example 1: Defining an SMB Printer with Generic User Credentials in Plain

Text 81

Example 2: Defining an SMB Printer with Generic User Credentials that are

Encrypted 81

Example 3: Defining an SMB Printer to Use User Credentials Cached by ThinOS

(Advanced) 82

Using Your Thin Client as a Print Server (LPD) 83

Using the Printer Setup Dialog Box for Configuring LPD Services 83

Using INI Parameters for Configuring LPD Services 84

Configuring ThinPrint 85

Tables

Introduction

Wyse thin clients running Wyse ThinOS™ firmware are designed solely for optimal thin client security and performance. These extremely efficient purpose-built thin clients are virus- and malware-immune and offer ultra-fast access to applications, files, and network resources within Citrix, Microsoft, VMware and Dell vWorkspace environments, and other leading infrastructures. ThinOS-based thin clients are self-managed, go from power-on to fully productive in seconds, and with no published API, locally accessible file system or browser, require no local antivirus software or firewall to protect against viruses or malware.

Chapter 1

About this Guide

This guide is intended for administrators of thin clients running ThinOS. It provides information and detailed system configurations to help you design and manage a

ThinOS environment.

Finding the Information You Need in this Guide

You can use either the Search window or Find toolbar to locate a word, series of words, or partial word in an active PDF document. For detailed information on using these features, refer to the Help in your PDF reader.

Dell Technical Support

To access Dell technical resources, visit http://www.wyse.com/support

. If you still have questions, you can submit your questions using the Self-Service Center at http://support.wyse.com/selfservice.html

or call Customer Support at 1-800-800-9973

(toll free in U.S. and Canada). Hours of operation are from 6:00 A.M. to 5:00 P.M. Pacific

Time, Monday through Friday.

To access international support, visit http://www.wyse.com/global

Dell Online Community

Dell maintains an online community where users of our products can seek and exchange information on user forums. Visit the Online Community forums at: http://community.wyse.com/forum

Getting Started: Quickly Learning the Basics

Use the following information to quickly learn the basics and get started using your thin client:

•

"Connecting to a Remote Server"

•

"Using Your Desktop"

•

"Configuring Thin Client Settings and Connection Settings"

•

"Connecting to a Printer"

•

"Connecting to a Monitor"

•

"Locking the Thin Client"

•

"Signing Off and Shutting Down"

•

"Additional Getting Started Details"

TIP

: ThinOS is designed to be centrally managed and configured using INI files (to automatically push updates and any desired default configuration to all supported thin clients in your environment - see "Central Configuration: Automating Updates and

Configurations").

If no INI files are detected, you can use local dialog boxes (on each thin client) to make available configurations. ThinOS will save many of these locally configured settings

(common settings such as resolution, mouse, keyboard, and so on) to persist after reboot. However, once INI files are detected, rebooting causes ThinOS to become stateless (ignoring locally configured settings after a reboot) and the settings contained in the INI file will be used.

Chapter 2

Connecting to a Remote Server

TIP

: On your initial connection to central configuration it is recommended that you connect using a “wired connection” (plug in the network-connected ethernet cable to your thin client before starting the thin client) to obtain the configurations desired by the administrator. This “wired connection” will also provide any wireless configurations provided by the administrator through the INI files.

If you must initially connect to central configuration through wireless, use the Wireless tab in the

Network Setup

dialog box to enter the SSID and encryption configurations required/set up by the network administrator (see "Network Setup").

Central Configuration

- If you are set up for automatic detection (using INI files - see

Reference Guide: Wyse ThinOS

INI Files), your thin client will automatically detect and connect to the configured remote services during the boot-up process. Simply press the power button to turn on your thin client to see the

Login

dialog box. Enter your User name, Password, and Domain, and then click

Login

. After authentication is successful, your available connections are presented for use.

TIP

: Although the thin client will default to the Classic Desktop for INI backward compatibility, you can configure the thin client to display the Zero Desktop by using the

SysMode=VDI parameter in the INI files or by selecting the desktop option in a dialog box (see "Using Your Desktop").

Manual Connection

- If you are not yet set up for central configuration, you will see the Zero Toolbar, where you can configure the initial server connection you want using the

Remote Connections

dialog box before you can log in. See "Manual Connection

Procedures."

You only need to complete this manual configuration once (or after reboot to factory defaults). After the thin client “knows” the location of your server, it automatically connects to the server for login when you start the thin client in the future. After you confirm your environment is ready for deployment, you can create INI files for central configuration.

Getting Started: Quickly Learning the Basics

Manual Connection Procedures

Click the

System Settings

icon on the Zero Toolbar to open the System Settings menu, and then click

Remote

Connections

to open the

Remote Connections

dialog box.

Use the Broker Setup tab of the

Remote Connections

dialog box to configure one of the following connections:

•

ICA or RDP connection (select

None

, select

ICA

RDP

, click

Configure Connection

, and then follow the wizard).

•

A specific broker server connection (select

Microsoft

Citrix Xen

Dell vWorkspace

VMware

View

, or

Other

and then enter the IP Address for the server in the

Broker Server

box).

Note:

For more details, see "Remote Connections."

Click

, and then restart the thin client (click the

Shutdown

icon on the Zero Toolbar to open and use the

Shutdown

dialog box to restart the thin client).

(If You Configured an ICA or RDP Connection) After thin client restart, click the

Home

icon on the Zero

Toolbar to open the list of available connections, click the ICA or RDP connection you created, and then log in.

(If You Configured a Specific Broker Server Connection)

After thin client restart, the

Login

dialog box appears for your server.

Enter the User name, Password, and Domain and click

Login

After authentication is successful, your Zero Toolbar is presented with your assigned connections defined by the broker server.

Chapter 2

Using Your Desktop

What you see after logging on to the server depends on the administrator configurations.

Users with a Classic Desktop

- will see the classic ThinOS desktop with full taskbar, desktop, and Connect Manager familiar to ThinOS users. This option is the default out-of-the-box experience and is recommended for terminal server environments with published applications and for backward compatibility with ThinOS 6.x versions.

For more information on using the Classic Desktop, see

"Classic Desktop Features."

Users with a Zero Desktop

- will see the Zero Desktop with the Zero Toolbar showing the assigned list of connections from which to select. This option is recommended for VDI and any full-screen only connections.

For more information on using the Zero Desktop, see "Zero

Desktop Features."

In any desktop case, you can select the desktop option you want (Classic Desktop or

Zero Desktop) and create the connections you need using the Visual Experience tab on the

Remote Connections

dialog box (see "Remote Connections").

To open the

Remote Connections

dialog box, do one of the following:

•

Classic Desktop - Click User Name (User Name is the user who is logged-on and is located at the bottom-left side of the taskbar), and then select

System Setup >

Remote Connections

•

Zero Desktop - Click the

System Settings

icon on the Zero Toolbar, and then select

Remote Connections

Getting Started: Quickly Learning the Basics

Configuring Thin Client Settings and Connection Settings

While the use of INI files is recommended to configure thin client settings and connection settings available to users (see "How to Set Up Automatic Updates and

Configurations"), you can use dialog boxes on a thin client to:

•

Set up your thin client hardware, look and feel, and system settings (see

"Configuring Thin Client Settings Locally").

•

Configure connection settings (see "Configuring Connection Settings Locally").

Connecting to a Printer

To connect a parallel printer to your thin client through a USB port, you will need a

USB-to-printer adapter cable (not included). Before use, you may need to install the driver for the printer by following the printer driver installation instructions. For information on connecting to printers, refer to "Printer."

Connecting to a Monitor

Depending on your thin client model, connections to monitors can be made using either a VGA (analog) monitor port, a DVI (digital) monitor port, or a DisplayPort (digital) and the proper Dell monitor cables/splitters/adapters. For information on configuring dual display settings, see "Display."

TIP

: For dual-monitor supported thin clients using a DVI to DVI/VGA splitter, the VGA monitor will be the primary monitor. For dual-monitor supported thin clients using a

DisplayPort, the DisplayPort monitor will be the primary monitor.

Locking the Thin Client

To help ensure that no one else can access your private information without permission, 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-on smart card

- If an administrator has set SCRemovalBehavior=1 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 thin 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 an administrator has set the INI files to do so (in this case you must sign-on as usual to use the thin client).

•

Use LockTerminal from the Shortcut Menu and Shutdown dialog box

- On the

Classic Desktop, click on the desktop and select

Lock Terminal

, or use the

Shutdown

dialog box (see "Classic Desktop Features"). On the Zero Desktop, use the

Shutdown

dialog box (see "Signing Off and Shutting Down"). To open the thin client for use, you must use your correct password.

•

Use the screen saver

- If an 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.

Chapter 2

Signing Off and Shutting Down

Use the

Shutdown

dialog box to select the available option you want:

•

Classic Desktop - Click

Shutdown

in the Connect Manager or Desktop Menu.

•

Zero Desktop - Click the

Shutdown

icon on the Zero Toolbar.

TIP

: You can also configure automatic behavior after all desktop sessions are closed by using the

Remote Connections

dialog box (see "Remote Connections") or the

AutoSignoff parameter in a wnos.ini file (see "Central Configuration: Automating

Updates and Configurations").

TIP

: You can also display the

Shutdown

dialog box from the

Login

dialog box by pressing Ctrl+Alt+Delete.

Use the following guidelines (depending on user privilege, some options may not be available for use):

Table 1 Shutdown dialog box options

Option What It Does

Sign-off from account

Allows you to sign off from the current open account (the

Login

dialog box appears and is ready for another user).

Lock Terminal

Locks the thin client from use until you log in again.

Shutdown the system

Turns off the thin client.

Restart the system

Reset the system setting to factory default

Logs off the user account (the

Login

dialog box appears after the thin client restarts).

Appears for high-privileged users/administrators only. This option allows you to reset the thin client to factory defaults (see "Resetting to Factory Defaults Using

Shutdown Reset").

Getting Started: Quickly Learning the Basics

Additional Getting Started Details

This section includes additional details on the following:

•

"Zero Desktop Features"

•

"Classic Desktop Features"

•

"Login Dialog Box Features"

•

"Accessing System Information"

Zero Desktop Features

This section includes information on:

•

"Zero Interactive Desktop Guidelines"

•

"Zero Toolbar"

•

"List of Connections"

Zero Interactive Desktop Guidelines

The Zero Desktop has a default background with the Zero Toolbar at the left of the screen. Table 2 lists Zero Desktop available shortcuts.

Table 2 Zero Desktop Shortcut Keys

Action

Display the Zero Toolbar

Press

Ctrl+Alt+UpArrow

Open a selection box for toggling between the desktop and currently-active connections

Lock the thin client

Ctrl+Alt+DownArrow

Ctrl+Alt+LeftArrow or

Ctrl+Alt+RightArrow

Keyboard shortcuts to menu commands Left-Alt+UnderlinedLetter

Capture the full desktop to the clipboard

Capture the active window to the clipboard

NOTE

: Right-Alt+UnderlinedLetter combination is not currently supported

Print Screen

Alt+PrintScreen

CAUTION

: You can copy and paste between application sessions and between sessions and the desktop, however, this function depends on session server configurations.

TIP

: In addition to the standard two-button mouse, the thin client supports a Microsoft

Wheel Mouse (used for scrolling). Other similar types of a wheel mouse may or may not work.

To switch the left and right buttons, use the

Peripherals

dialog box (see "Peripherals").

Chapter 2

Zero Toolbar

The Zero Toolbar usually appears at the left edge of the Zero Desktop. However, depending on administrator configurations, the toolbar can be removed or hidden

(shown only when a user moves the mouse pointer over the left edge of the desktop screen).

TIP

: Administrators can configure the toolbar settings using either a dialog box (see

"Remote Connections") or the SysMode parameter in the wnos.ini file (see Reference

Guide: Wyse ThinOS

INI Files).

Table 3 Toolbar icons

Icon

Home

What It Does

Opens the list of available connections (see "List of

Connections").

System Information

Displays thin client system information (see "Accessing

System Information").

System Settings

Opens the System Settings menu to configure thin client system settings and perform diagnostics (see "Configuring

Connection Settings Locally," "Configuring Thin Client

Settings Locally," and "Central Configuration: Automating

Updates and Configurations").

Shutdown Terminal

Click the

Shutdown Terminal

icon to use the Shutdown options available on the thin client (see "Signing Off and

Shutting Down"). Note that the

Shutdown Terminal

icon does not display on the toolbar when using the

Admin

Mode

button to configure system settings.

TIP

: If configured to display (by an administrator), the current date and time are shown on the Zero Toolbar. The thin client is capable of synchronizing its clock to time provided by a Simple Network Time Protocol (SNTP) server.

Getting Started: Quickly Learning the Basics

List of Connections

On the Zero Toolbar, you can click the

Home

icon to open your list of assigned connections (in some cases the list may contain only default connections).

Use the following guidelines (depending on user privilege level, some options may not be available for use):

Table 4 Connection Options

Option

Name of the connection

Restart icon

Quick Disconnect icon

What It Does

Opens the connection you want to use (all open connections display a blue icon to the left of the connection name in the list).

Restarts the connection (useful when a connection is not functioning properly or you need to reboot the connection).

Closes the connection (the

Close

icon is grayed out for connections that are not open).

Edit icon

Configuring Global

Connection Settings

Opens the

Connection Settings

dialog box (see

"Advanced Details on Configuring ICA and RDP

Connections") to change the connection options

(depending on user privilege level, editing options may not be available for use).

If you do not use INI files to provide global connection settings, you can click

Global Connection Settings

to open and use the

Global Connection Settings

dialog box to configure settings that affect all of the connection in the list (see "Global Connection Settings").

Chapter 2

Classic Desktop Features

This section includes information on:

•

"Classic Interactive Desktop Guidelines"

•

"Shortcut Menu"

•

"Desktop Menu"

•

"Connect Manager"

Classic Interactive Desktop Guidelines

The Classic Desktop has a Wyse default background with a horizontal taskbar at the bottom of the screen.

Use the following guidelines:

•

Icons representing available server connections and published applications are displayed on the background. Hovering the mouse pointer over an icon pops-up information about the connection. Right-clicking on an icon opens a

Connection

Settings

dialog box which displays additional information about the connection.

The number of icons that can be displayed on the desktop depends on the desktop resolution and administrator configuration.

•

A server connection/published application can be opened by double-clicking a desktop icon or a user can navigate to the desktop icon they want by using tab key and pressing

Enter

to initiate the connection.

•

Right-clicking on the desktop provides a Shortcut Menu (see "Shortcut Menu").

•

Clicking the User Name (User Name is the user who is logged-on and is located at the bottom-left side of the taskbar), or clicking on the desktop, opens the Desktop

Menu (see "Desktop Menu").

TIP

: If configured to display (by an administrator), the volume control is displayed in the right corner of the taskbar and the current time and date are shown when the cursor is placed on the time; the thin client is capable of synchronizing its clock to time provided by a Simple Network Time Protocol (SNTP) server.

Table 5 lists Classic Desktop available shortcuts.

Table 5 Classic Desktop Shortcut Keys

Action

Toggle between window display modes

Open a selection box for toggling between the desktop, Connect

Manager, and currently-active connections

Lock the thin client

Press

Ctrl+Alt+UpArrow

Ctrl+Alt+DownArrow

Keyboard shortcuts to menu commands

Ctrl+Alt+LeftArrow or

Ctrl+Alt+RightArrow

Left-Alt+UnderlinedLetter

Capture a full desktop

Capture the active window

NOTE

: Right-Alt+UnderlinedLetter combination is not currently supported

Print Screen

Alt+PrintScreen

Getting Started: Quickly Learning the Basics

CAUTION

: You can copy and paste between application sessions and between sessions and the desktop, however, this function depends on session server configurations.

TIP

: In addition to the standard two-button mouse, the thin client supports a Microsoft

Wheel Mouse (used for scrolling). Other similar types of a wheel mouse may or may not work.

To switch the left and right buttons, use the

System Preference

dialog box (see "System

Preferences").

Shortcut Menu

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

•

Administrator Mode

- Allows administrators to configure various settings locally on thin client.

•

Hide all windows

- Brings the full desktop to the foreground.

•

Copy to clipboard

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

•

Purge clipboard

- Discards the contents of the clipboard in order to free up memory.

•

Lock Terminal

- Puts the thin client in a locked state if the user has signed on to the system with a password. The thin client can only be unlocked using the same password.

•

Group Sessions

- Enables you to open more than three ICA or three RDP or three

ICA seamless sessions. The sessions will be displayed as a group on the taskbar.

•

Write Event Log to USB

- Writes the event log of the thin client to the last connected USB device (see also "System Tools").

•

Network Capture to USB

- Captures network traces to the last connected USB device (see also "System Tools").

•

Trace Action

- Captures (capture option) or plays back (playback option) the network traces (see also "System Tools").

•

Delay on Trace

- Enables a time delay on traces (see also "System Tools").

•

Trace to/from USB

- Enables the capture of network information (a network trace of all traffic coming in and out of the thin client) to a USB drive that is inserted into the thin client (see also "System Tools").

Chapter 2

Desktop Menu

Clicking the User Name (User Name is the user who is logged-on and is located at the bottom-left side of the taskbar), or clicking on the desktop, opens the Desktop Menu with the following options (for High-privileged and Low-privileged users only):

•

System Setup

- Provides access to the following local system setup dialog boxes:

•

Network Setup

- Allows selection of DHCP or manual entry of network settings, as well as entry of locations of servers essential to thin client operation. This menu selection is disabled for Low-privileged users. See "Network Setup."

•

Remote Connections

- Allows you to configure thin client network connections including ICA, RDP, Citrix Xen, VMware View, and other broker server connections. See "Remote Connections."

•

Central Configuration

- Allows you to configure thin client central connection settings such as file server and optional WDM server settings. See "Central

Configuration."

•

WAN Setup

- Allows you to configure thin client WAN.

•

System Preference

- Allows user selection of thin client parameters that are a matter of personal preference. See "System Preferences."

•

Display

- Allows you to configure the monitor resolution and refresh rate. See

"Display."

•

Peripherals

- Allows you to select the peripherals settings such as keyboard, mouse, volume, and touch screen settings. See "Peripherals."

•

Printer

- Allows configuration of network printers and local printers that are connected to the thin client. See "Printer."

•

System Information

- Provides thin client system information. See "Accessing

System Information."

•

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.

•

Network Test

- Opens a submenu from which the

Ping

and

Trace Route

tools can be used to check the integrity of the network connection. See "Using Ping" and

"Using Trace Route."

•

System Tools

- Opens a submenu from which the

wnos.ini

and

user.ini

windows can be opened to view the contents of the files. See "System Tools."

•

Shutdown

- Opens the

Sign-off/Shutdown/Shutdown/Restart the System

dialog box. See "Signing Off and Shutting Down."

Getting Started: Quickly Learning the Basics

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 that non-privileged users cannot view the Connect

Manager.

The command buttons available depend on the privileges of the user and administrator configuration; the following default examples are typical:

•

High-privileged user

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

•

Low-privileged user

- Includes Connect, Settings, and Sign-off.

•

Stand-alone user

- Includes Connect, New, Settings, and Delete.

TIP

: If set by an 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).

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.

TIP

: Guest user privileges are determined by an administrator.

The Connect Manager command buttons include:

•

Connect

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

Connect

•

New

- 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 box, refer to

"Advanced Details on Configuring ICA and RDP Connections"). The new locally-defined connections are added to the connection list. Be aware of the following information:

•

High-privileged user

- Typically, all locally-defined connection definitions are temporary and are lost when the user logs off and when the thin client restarts or is shut down. However, if configured by an administrator

( enablelocal=yes

), locally-defined connection definitions can be saved in these cases.

•

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

•

Properties

- Clicking

Properties

opens the

Connection Settings

dialog box for the selected connection (for more information on the

Connection Settings

dialog box, refer to "Advanced Details on Configuring ICA and RDP Connections"). Be aware of the following information:

•

High-privileged user

- Can view and edit the definitions for the currently-selected connection. Edits are not permanently retained when the user signs-off.

Chapter 2

•

Low-privileged user

- Cannot create or edit connections, but can view connection definitions.

•

Stand-alone user

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

•

Sign-off

- To sign-off from the thin client, click

Sign-off

•

Delete

- To delete a connection, select a connection from the list and click

Delete

•

Reset VM

- To reset a virtual connection, select a virtual connection from the list and click

Reset VM

•

Global Connection Settings

- If you do not use INI files to provide global connection settings, you can click

Global Connection Settings

to open and use the

Global Connection Settings

dialog box to configure settings that affect all of the connections in the list (see "Global Connection Settings").

Login Dialog Box Features

While the

Login

dialog box allows you to log on to the server, it also allows you to:

•

Obtain system information.

•

Access Admin Mode to configure thin client settings.

•

Change or reset your own password and unlock your account.

•

Open the

Shutdown

dialog box by using CTRL+ALT+DELETE.

Use the following guidelines

•

Sys Info

- Click the

Sys Info

button to open the

System Information

dialog box and view the thin client system information such as System Version, IP Address, information on devices connected to your thin client, event logs, and so on (see

"Accessing System Information").

•

Admin Mode

- Click the

Admin Mode

button to configure various settings locally on the thin client (not broker desktop configurations). For example, you can choose to manually configure the Citrix Xen Broker Server URL (or override the URL that is centrally defined by file servers) by using the

Remote Connections

dialog box as described in "Remote Connections."

To exit Admin Mode:

Classic Desktop - Use the

Leave Administrator Mode

option on the

Shutdown

dialog box.

Zero Desktop - Use the

Leave Administrator Mode

option on the

Shutdown

dialog box, or use the

Leave Administrator Mode

icon (X) on the top right of the

System Settings menu.

TIP

: By default the Admin Mode button is not displayed on the

Log on

dialog box. You can display it by selecting the

Show local admin button

check box on the

Shutdown

dialog box (see "Signing Off and Shutting Down").

CAUTION

: By default there is no password needed for

Admin Mode

button use. You can password protect the

Admin Mode

button (to require login credentials) by using

Getting Started: Quickly Learning the Basics

the AdminMode parameter in a wnos.ini file (see Reference Guide: Wyse ThinOS

Files).

INI

•

Shutdown

- Click the

Shutdown

button to open and use the

Shutdown

dialog box to sign-off, shut down, restart, reset the system setting to factory defaults, and so on

(see "Signing Off and Shutting Down").

•

Account Self-Service

- Click the

Account Self-Service

icon (shown when configured using the AccountSelfService option of the PasswordServer INI parameter - see Reference Guide: Wyse ThinOS

INI Files) to open and use the

Account Self-Service

dialog box to change or reset your own password and unlock your account.

Note that this process assumes that the security questions and answers have been pre-registered by the user inside of their Windows environment. Users must use

HTTPS (not HTTP) for an account self-service server address (such as https://IPAddress) in the Broker Setup tab (see "Remote Connections").

After answering the security questions, your new password will be set or your account will be unlocked.

Accessing System Information

Use the

System Information

dialog box to view system information:

•

Classic Desktop - Click

System Information

in the Desktop Menu.

•

Zero Desktop - Click the

System Information

icon on the Zero Toolbar.

The

System Information

dialog box includes:

•

General Tab

- Displays general information such as System Version, Serial Number,

Boot From, Memory Size (Total and Free), Terminal Name, IP Address, Net Mask,

Gateway, and DHCP Lease.

•

Devices Tab

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

Monitor, Parallel Ports, Ethernet Speed, Memory Speed, NAND Size, Resolution, Serial

Ports, and the thin client MAC Address.

NOTE: Clicking the Device Viewer button allows you to easily view recognized devices (this screen will provide USB information—PIV,VID,etc—needed for forcelocal= or forceredirect= INI parameters).

•

Copyright/Patents Tab

- Displays the software copyright and patent notices.

•

Event Log Tab

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

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

•

Status Tab

- Displays status information about TCP performance-related parameters, CPU Busy, System Up Time, Wireless performance-related parameters,

Free Memory, and DHCP lease time remaining.

•

IPv6 Tab

- Displays IPv6 information such as Link-local Address, IPv6 Address, and

IPv6 Default Gateway.

NOTE

: This tab is displayed when IPv6 is enabled in the

General tab of the Network Setup dialog box (see "Network Setup").

Chapter 2

This page intentionally blank.

Configuring Thin Client Settings

Locally

You can configure available thin client settings on the thin client using the following

(depending on user privilege level, some dialog boxes and options may not be available for use):

•

"Local Settings Menu"

•

"Reset Features"

TIP

: While it is not recommended to use dialog boxes for configuring thin client settings, they are available in case you want to temporarily override central default configurations or you do not have the option to set up central configuration (smaller environments). In general, it is recommended that you use central configuration to enable you to automatically push updates and any desired default configuration to all supported thin clients in your environment (see "Central Configuration: Automating

Updates and Configurations").

Chapter 3

Local Settings Menu

Local Settings menu items include:

•

"System Preferences"

•

"Display"

•

"Peripherals"

•

“Printer”

To access the Local Settings menu:

•

Zero Desktop - click the

System Settings

icon on the Zero Toolbar (administrators can also click the

Admin Mode

button on the

Login

dialog box).

•

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

Configuring Thin Client Settings Locally

System Preferences

Use the

System Preference

dialog box (

System Settings icon > System Preferences

) to select personal preferences such as screen saver, time/date, and custom information settings.

Use the following guidelines for the General tab:

•

Screen Saver

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

Turn Off Screen

. Other selections available include

Flying Bubbles

and

Moving

Image

(which are screen savers with the monitor remaining on).

•

Timer

- Select a time after which the screen saver is to be activated (either

1 minute

5 minutes

10 minutes

, or default

20 minutes

). When the thin client is left idle for the specified idle time, the screen saver is initiated.

•

Locale

- Select a language to be activated for the user login-experience (either

French

German

, or default

English

). Note that Locale changes the language for the user login-experience screens only (displayed during boot-up and login) and not the configuration or administrator screens.

Only the following messages are applicable for French and German locales:

•

Username/Password/Domain

•

System Information

•

Shutdown the system, Restart the system, Reset the system setting to factory default

•

OK, Cancel

•

Initiating devices

•

Looking up IP address from DHCP, Note: Pressing CTRL-ESC keys will cancel out of network check

•

Retry DHCP for an IP address

•

Waiting for network link…. (Please verify network cable is plugged into back of unit)

•

Check Cable, No Ethernet link

•

Leave administrator mode

•

Connecting...

•

Sign off from account

•

Lock Terminal, Unlock Password

•

Terminal is locked, Invalid unlock password

•

Terminal Name

- Allows entry of a name for the thin client. The default is a

14-character string composed of the letters WT followed by the thin client Ethernet

MAC address. Some DHCP servers use this value to identify the IP address lease in the DHCP Manager display.

Chapter 3

Use the following guidelines for the Time/Date tab:

•

Time Zone

- Allows you to select a time zone where the thin client operates

(default is

Unspecified

•

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:

Month

- Specifies the month in the year from

January

through

December

Week

- Select

through

for the week in the month. Week

Last

denotes the last week in the month.

Day

- Specifies the day of the week from

Monday

through

Sunday

•

Time Format

- Allows you to select a 12 or 24 hour time format (default is

24-hour format

•

Date Format

- Allows you to select a yyyy/mm/dd (year/month/day) or dd/mm/ yyyy (day/month/year) date format (default is

yyyy/mm/dd

•

Time Servers

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

Time Servers. Each entry with optional port number is specified as Name-or-IP:port, where :port is optional. If not specified, port 80 is used. Locations can be supplied through user profiles if user profiles are used. The Time Servers provide the thin client time based on the settings of time zone and daylight saving information. If

DHCP is used, locations can be supplied through DHCP.

•

Change Date and Time

- Allows you to change date and time (for secure environments requiring a solution to outside server access) When connecting to a file server over HTTPS, the proper time must be defined on the thin client for SSL/ certification validation. Note that the year range is from 2000 to 2099.

Use the Custom Info tab to enter configuration strings for use by WDM software. The configuration strings can contain information about the location, user, administrator, and so on. Clicking

transfers the custom field information you enter in the dialog box to the Windows registry. The information is then available to the WDM Client

Manager. For more information on using Custom Fields and using WDM for remote administration and upgrading thin client software, see the WDM documentation.

Configuring Thin Client Settings Locally

Display

Use the

Display

dialog box (

System Settings icon > Display

) to select the resolution and refresh rate for the monitor used with the thin client. It also allows you to configure the way two monitors display.

TIP

: The number of icons that can be displayed on the desktop depends on the desktop resolution and administrator configuration. 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.

Use the following guidelines for the General tab:

•

Select best display setting on DDC monitor

- If the monitor is VESA DDC2B

(Display Data Channel) compatible, selection of this option allows the thin client to automatically select the best resolution and refresh rate. If your monitor is not DDC compatible, a Monitor does not support Plug and Play message is displayed (click

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.

•

User defined display setting

- Select this option and select the resolution and refresh rate supported by your monitor (all combinations are allowed):

Resolutions

include:

640 x 480 (not on T10D)

800 x 600 (not on T10D)

1024 x 768

1152 x 864

1280 x 720

1280 x 768 (not on T10)

1280 x 1024

1360 x 768 (not on T class)

1366 x 768

1368 x 768 (not on T class)

1400 x 1050

1440 x 900

1600 x 900

1600 x 1200

1680 x 1050

1920 x 1080

1920 x 1200

1920 x 1440 (R class only)

2560 x 1080 (Single monitor only; R class and D/Z class only)

2560 x 1440 (Single monitor only; R class only)

2560 x 1600 (Single monitor only; R class and D/Z class only)

Chapter 3

Refresh

rate list selections include:

60 Hz (default)

75 Hz

85 Hz

•

Rotation

- Select a rotation option (either

None

Right turn 90 degrees

•

Desktop Color

- Select the Desktop Color (either

16 bit

32 bit

•

Usage Help

area - Contains brief instructions for using the

Display

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

Use the following guidelines for the Dual Head tab (Supported Dual Monitor Capable

Thin Clients Only):

•

Dual Head

- Select

Mirror Mode

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

Span Mode

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

•

Main Screen

- Select which of the two monitors you want to be the main screen

(

Screen1

Screen2

). The other screen is extended from the main screen. Note that when using a DVI to DVI/VGA splitter with VGA and DVI monitors at the same time, the VGA monitor will be the primary monitor.

•

Layout

- Select how you want the two monitors to be oriented to each other

(

Horizontal

where you mouse between the monitors from the left and right of the screens or

Vertical

where you mouse between the monitors from the top and bottom of the screens).

•

Alignment

- Select how you want the monitors to be aligned (

Bottom

Center

, or

Top

). Bottom means screens are bottom-aligned in a horizontal orientation; Center means screens are center-aligned; Top means screens are top-aligned in a horizontal orientation.

•

(Classic Desktop Only)

Taskbar

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

Whole Screen

Main Screen

(Gamma Supported Monitors Only)

Use the Gamma Setup tab to adjust the saturation values for Red, Green and Blue on VGA connected monitors supporting gamma settings if you feel the default settings are too light. Be aware that the Gamma Setup tab will be disabled once you click

Save+Exit

. You can enable it again by setting rgamma={1-100} ggamma={1-100} bgamma={1-100} in the Resolution INI parameter

(see Reference Guide: Wyse ThinOS

INI Files).

Configuring Thin Client Settings Locally

Peripherals

Use the

Peripherals

dialog box (

System Settings icon > Peripherals

) to select the peripherals settings such as keyboard, mouse, volume, serial, camera, and touch screen settings.

Use the following guidelines for the Keyboard tab:

•

Character 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 represent 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).

•

Keyboard Language

- Currently the following keyboard languages are supported

(default i

s English (United States)

Table 6 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)

Dutch (Belgian Comma)

English (3270 Australian)

English (Australian)

English (New Zealand)

English (United Kingdom)

English (United States)

Finnish

French (Belgian)

French (Belgian Comma)

French (Canadian)

French (France)

French (Swiss)

German

German (IBM)

German (Swiss)

Greek

Hungarian

Italian

Italian (Swiss)

Japanese

Japanese_109a

Korean

Korean (MS-IME2002)

Norwegian

Polish (214)

Polish Programmers

Portuguese

Portuguese (Brazil)

Romanian

Russian

Slovakian

Slovakian (Qwerty)

Slovenian

Spanish

Spanish (Mexican) English

Spanish (Mexican) Localized

Swedish

Turkish

Turkish (QWERTY)

U.S. International

•

Delay before repeat

- Repeat parameters for held-down key. Select the 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

- Select

Slow

Medium

, or

Fast

. The default is

Medium

Chapter 3

Use the Mouse tab to select the Mouse Speed and mouse orientation (you can swap mouse buttons for left-handed operation by selecting

Swap left and right mouse buttons

Use the Audio tab to select the volume settings for connected devices. For example, connected USB headsets will be shown in the drop-down list for selection. Use the HD

Audio option for analog earphone use, and the Boost option for audio enhancement.

NOTE

: The sound recorder is contained in the Audio tab of the Peripherals dialog box.

It allows you to:

Collect information about the speaker and microphone currently being used.

Examine the performance of the speaker and microphone currently being used.

Export the recorded audio sample to a USB key for archiving and further analysis.

Use the following guidelines for the Serial tab:

•

Select Port

- Select the port to which this setup definition applies. Either

COM 1

COM 2

COM 3

, or

COM 4

can be selected (default is Port

COM 1

). For Models SX0 and VX0,

COM 1

COM 2

selects from either the USB or serial device.

•

Baud Rate

- Either

1200

2400

4800

9600

19200

38400

57600

, or

115200

baud can be selected (default is

9600

•

Parity

- Either

None

Even

, or

Odd

can be selected (default is

None

•

Stop

- Either

1.5

, or

stop bits can be selected (default is

Configuring Thin Client Settings Locally

•

Size

- Character size

, or

bits can be selected (default is

•

Flow Control

- Either

None

XON/XOFF

CTS/RTS

, or

Both

can be selected (default is

None

•

Serial Touch Screen selections

- Select the proper touch screen

ELO

MicroTouch

FastPoint

from the list.

•

Touch Screen on

- Select the proper serial port (COM port) or

None

from the list.

Use the Camera tab to interface with cameras (supported by a UVC driver) that are locally connected to the thin client (USB). When using the HDX RealTime webcam feature of XenDesktop 5 or XenApp 6, you can control options such as maximum resolution and frames per second (10 FPS is recommended) directly from the thin client

(if the webcam supports Universal Video Driver). Note that this feature is experimental and does not currently support central configuration (INI parameters). Also note that this feature is CPU intensive and is recommended for high performance products such as the D10D thin client.

Use the Touch Screen tab to configure touch screens that are connected to the thin client (USB). The tab is available (not grayed out) when the thin client detects that a touch screen is attached through a USB port and the setup (or calibration) has not been performed. The Touch Setup window prompts you to touch two circles on the screen to make the 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.

Chapter 3

Printer

IMPORTANT

: Host-based printers are not supported.

Use the

Printer Setup

dialog box (

System Settings icon > Printer

) to configure network printers and local printers that are connected to the thin client. Through its

USB ports, a thin client can support multiple printers. If more than one printer is to be used and another port is not 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.

IMPORTANT

: Microsoft Remote Desktop Session Host (RDSH), Microsoft Terminal

Services, and Citrix XenApp each have their own printing policies that must be configured properly to allow client side printing. For details on configuring printing in these environments, see your vendor instructions.

TIP

: This section details the tabs and fields of the

Printer Setup

dialog box. For examples on using the

Printer Setup

dialog box for common printing situations, see

"Examples of Common Printing Configurations."

Use the following guidelines for the Ports tab when printing to a local USB printer:

•

Select Port

- Select the port you want from the list (LPT1 or LPT2 selects the connection to a direct-connected USB printer).

•

Printer Name

- (Required) Enter name you want displayed in your list of printers

(most USB direct-connected printers report/fill in their printer name automatically).

NOTE

: If

Enable LPD service for the printer

is selected, the printer name becomes the queue name for other clients using LPR to print to this printer.

•

Printer Identification

- Enter the type or model of the printer in the exact text of the Windows printer driver name—including capitalizations and spaces (most USB direct-connected printers report/fill in their printer identifications automatically).

This entry must be 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 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 profile (wnos.ini) or by MetaFrame servers through the MetaFrame printer configuration file

(\winnt\system32\wtsprnt.inf).

•

Printer Class

- (Optional) Select the printer class from the list (

PCL5

, or

TXT

•

Enable the printer device

- Must be selected to enable the directly-connected printer (enables the device so it displays on the remote host).

•

Enable LPD service for the printer

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

Printer Daemon) network print server for LPR printing requests from the network

(see "Using Your Thin Client as a Print Server (LPD)").

CAUTION

: 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 client (see "Network Setup").

Configuring Thin Client Settings Locally

Use the following guidelines for the LPDs tab when printing to a non-Windows network printer (be sure to check with your vendor that the printer can accept Line Printer

Request print requests):

•

Select LPD

- Select the port you want from the list.

•

Printer Name

- (Required) Enter name you want displayed in your list of printers.

•

Printer Identification

- Enter the type or model of the printer in the exact text of the Windows printer driver name—including capitalizations and spaces. This name must be 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 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 profile (wnos.ini) or by

MetaFrame servers through the MetaFrame printer configuration file

(\winnt\system32\wtsprnt.inf).

•

LPD Hosts

- The DNS or WINS name of the server for the network printer. An IP address of the printer on the network can also be entered.

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.

•

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. This name can be different for each vendor. This is field is required and must be correct so that the network printer accepts incoming print jobs properly. For example,

auto

can be used for HP LaserJet 4200n PCL6 as per documentation found on the HP

Web site.

NOTE

: If the printer is attached to another thin client on your network, the LPD

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

•

Printer Class

- (Optional) Select the printer class from the list.

•

Enable the printer device

- Must be selected to enable the printer (enables the device so it displays on the remote host).

Chapter 3

Use the following guidelines for the SMBs tab when printing to a Windows network printer (

CAUTION

: The printer name shared by Windows must not contain any spaces or ThinOS will not be able to use it.):

•

Select SMB

- Select the SMB you want from the list.

•

Printer Name

- (Required) Enter name you want displayed in your list of printers.

•

Printer Identification

Generic / Text

for non-USB 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 profile (wnos.ini) or by

MetaFrame servers through the MetaFrame printer configuration file

(\winnt\system32\wtsprnt.inf).

•

\\Host\Printer

- Enter the Host\Printer or use the browse folder icon next to the box to browse your Microsoft Networks and make the printer selection you want from the network printers available (the DNS name or IP address of the Windows print server on the network).

•

Printer Class

- (Optional) Select the printer class from the list.

•

Enable the printer device

- Must be selected to enable the printer (enables the device so it displays on the remote host).

•

Enable LPD service for the printer

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

Printer Daemon) network print server for LPR printing requests from the network

(see "Using Your Thin Client as a Print Server (LPD)").

CAUTION

: 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 as described in

"Network Setup."

Configuring Thin Client Settings Locally

Use the following guidelines for the Options tab:

•

Default Printer

- Select the printer you want to be the default printer from your list of available printers.

•

Enable .print Client

and

Port

- If you want to enable .print Client, select

Enable

.print Client

and then enter the

Port

The Help tab contains printer help information.

Chapter 3

Reset Features

Reset features include:

•

"Resetting to Factory Defaults Using G-Key Reset"

•

"Resetting to Factory Defaults Using Shutdown Reset"

•

"Resetting Display Settings Using V-Key Reset"

•

"Accessing Thin Client BIOS Settings"

Resetting to Factory Defaults Using G-Key Reset

High-privileged or Stand-alone users can reset the thin client to factory default settings using the G-key reset feature.

To reset the thin client to factory default settings, restart the thin client and continuously tap the

key during the restart process. G-key reset impacts all configuration items, including, but not limited to, both network configuration and connections defined in local NV-RAM.

TIP

: G-key reset is disabled for Low-privileged and Non-privileged users in Lockdown mode.

Resetting to Factory Defaults Using Shutdown Reset

A High-privileged or Stand-alone user can reset the thin client to factory default settings from the

Shutdown

dialog box as follows:

Select either the

Shutdown the system

Restart the system

option.

Select the

Reset the system setting to factory default

check box.

Click

Shutdown reset impacts all configuration items, including, but not limited to, both network configuration and connections defined in local NV-RAM (Terminal name will not change).

TIP

: Shutdown reset is disabled for Low-privileged and Non-privileged users, regardless of lockdown state.

Resetting Display Settings Using V-Key Reset

If the display settings are inappropriate for the particular monitor that is connected, it is possible that the display will not function properly when the thin client restarts. To correct this, power-on the thin client while continuously tapping the

key. This will restart the thin client with a display resolution of 640 x 480 pixels and a 60 Hz refresh rate.

Accessing Thin Client BIOS Settings

After starting your thin client you will see a Wyse logo for a short period of time. During this period you can press and hold the

Delete

key to enter the BIOS to make your modifications (enter

Fireport

as the password). For example, you can use the F7 key to use Optimized Defaults (load optimal default values for all the items in the BIOS setup utility).

NOTE

: This does not apply to the T10 client (no BIOS on ARM).

Configuring Connection Settings

Locally

You can configure available connection settings on the thin client using the following

(depending on user privilege level, some dialog boxes and options may not be available for use):

•

"Global Connection Settings"

•

"Connectivity Menu"

TIP

: While it is not recommended to use dialog boxes for configuring thin client connection settings, they are available in case you want to temporarily override central default configurations or you do not have the option to set up central configuration

(smaller environments). In general, it is recommended that you use central configuration to enable you to automatically push updates and any desired default configuration to all supported thin clients in your environment (see "Central

Configuration: Automating Updates and Configurations").

Chapter 4

Global Connection Settings

If you do not use INI files to provide central configuration (global connection settings) to users, you can use the

Global Connection Settings

dialog box (

Home icon > Global

Connection Settings

) to configure settings that affect all of the connections in your list of connections:

•

Zero Desktop - Click

Global Connection Settings

in the List of Connections.

•

Classic Desktop - Click

Global Connection Settings

in the Connect Manager.

TIP

: For information on configuring the thin client using INI files (recommended), refer to Reference Guide: Wyse ThinOS

INI Files. For information on configuring the thin client locally using dialog boxes, refer to "Configuring Connection Settings Locally" and

"Configuring Thin Client Settings Locally."

Use the Session tab to select the check boxes you want for the options that are available to all sessions (the Smart Cards check box specifies the default setting for connecting to a smart card reader at startup).

TIP

: ICA sessions always have automatic connection to attached smart card readers.

When using the

Disks

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

- Support is for VFAT 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 server.

- Be sure to save all data and sign off from the session mapping the USB stick before removing the USB stick.

NOTE: Granular Control over USB Redirection

- By default, audio, video, and printer devices will not use HDX USB for redirection. You can make selections for

USB device redirection on the Session tab of the Global Connection Settings dialog box.

NOTE: For Web camera mapping, if the server does not support HDX USB redirection and you set this mode in the client, the client will use HDX Realtime

Webcam Compression.

Configuring Connection Settings Locally

Use the ICA tab to select the check boxes you want for the options that are available to all ICA sessions. Select the audio quality optimized for your connection.

Note the following:

Map to

- When a drive is entered, maps a disk under the drive.

Map all disks under

- When selected, you can use the drop-down list to select the drive under which you want to maps all disks.

Use the RDP tab to:

•

Enable or disable Network Level Authentication (NLA). The NLA authentication method verifies users before they are allowed to connect with a full Remote

Desktop connection.

•

Enable or disable ForceSpan. This dual-monitor feature allows you to span the session horizontally across two monitors (two monitors acting as one large monitor).

•

Enable or disable Terminal Service Multimedia Redirection (TSMM).

•

Enable or disable Record from Local (recording from local microphone).

•

Enable or disable RemoteFX.

•

Select the USB Redirection Type (TCX USB or RDP USB). TCX USB is the default. To use RDP USB you must use a RemoteFX session (RDP USB is not supported using a standard RDP session).

Chapter 4

Use the PCoIP tab to specify the channel of USB devices redirection (PCoIP USB or TCX

USB; default is PCoIP USB) for all PCoIP sessions.

Configuring Connection Settings Locally

Connectivity Menu

Connectivity menu items include:

•

"Network Setup"

•

"Remote Connections"

•

"Central Configuration"

To access the Connectivity menu:

•

Zero Desktop - click the

System Settings

icon on the Zero Toolbar (administrators can also click the

Admin Mode

button on the

Login

dialog box).

•

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

Chapter 4

Network Setup

Use the

Network Setup

dialog box (

System Settings icon > Network Setup

) to configure thin client network settings.

TIP

: 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. For more information, see "Enabling a Disabled Network Setup

Dialog Box."

Use the following guidelines for the General tab:

•

Ethernet Speed

- Normally the default (

Auto-Detect

) should be selected, but another selection can be made if automatic negotiation is not supported by your network equipment. Selections include

Auto-Detect

10 Mb Half-Duplex

10 Mb

Full-Duplex

100 Mb Half-Duplex

100 Mb Full-Duplex

TIP

: The

10 Mb Full-Duplex

option can be selected locally at the device, however, this mode may need to be negotiated through

Auto-Detect

•

IPV4

Properties

command button:

Dynamically allocated over DHCP/BOOTP

- Selecting this option enables your zero client to automatically receive information from the DHCP server. The network administrator must configure the DHCP server (using DHCP options) to provide information. Any value provided by the DHCP server will replace any value entered locally on the Options tab, however, locally entered values will be used if the DHCP server fails to provide replacement values.

Statically specified IP Address

- Select this option to manual enter the IP

Address, Subnet Mask, and Default Gateway:

IP Address

- Must be a valid network address in the server environment. The network administrator must provide this information.

Subnet Mask

- Enter the value of the subnet mask. A subnet mask is used to gain access to machines on other subnets. The subnet mask is used to differentiate the location of other IP addresses with two choices: same subnet or other subnet. 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. The network administrator must provide this value.

Default Gateway

- Use of gateways is optional. Gateways are used to interconnect multiple networks (routing or delivering IP packets between them).

The default gateway is used for accessing the Internet or an intranet with multiple subnets. 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.

Configuring Connection Settings Locally

•

IPV6

Advanced

command button: Allows you to select various setting options supported by IPV6.

•

IPV6

Properties

command button:

Wait DHCP

- Selecting this option enables your zero client to wait for IPV6 DHCP before signing on (if not selected the system will only wait for IPV4 DHCP if enabled).

Dynamically allocated over DHCP/BOOTP

Statically specified IP Address

- Select this option to manual enter the IP

Address, Subnet Mask, and Default Gateway:

IP Address

- Must be a valid network address in the server environment. The network administrator must provide this information.

Subnet Mask

Default Gateway

- Use of gateways is optional. Gateways are used to interconnect multiple networks (routing or delivering IP packets between them).

The default gateway is used for accessing the Internet or an intranet with multiple subnets. If no gateway is specified, your zero client can only address other systems on the same subnet. Enter the address of the router that connects your zero client to the Internet. The address must exist on the same subnet as your zero client as defined by the IP address and the subnet mask. If DHCP is used, the address can be supplied through DHCP.

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 network address of an available DNS Server. The value for this box may be supplied by a DHCP server. If the DHCP server supplies this value, it will replace any locally configured value. If the DHCP server does not supply this value, the locally configured value will be used.

TIP

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

•

Tcp Timeout

- Enter the number of 30 seconds for the timeout value of a TCP connection. The value must be

which means the connection timeout value is from 1x30= 30 seconds to 2x30= 60 seconds.

•

Show WAN configuration on System Settings

- Allows you to show the WAN configuration on the System Settings submenu.

Chapter 4

Use the following guidelines for the Name Servers tab:

•

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.

TIP

: You may enter two DNS Server addresses, separated by a semicolon, 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.

TIP

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

Use the following guidelines for the Options tab:

•

DHCP 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 "Step 2: Direct the Thin Client to the Server Using DHCP Options."

•

Interpret DHCP Vendor-Specific Info

- Automatically interprets Vendor information.

Configuring Connection Settings Locally

•

DHCP Vendor ID

- Shows the DHCP Vendor ID when the

Dynamically allocated over DHCP/BOOTP

option is selected.

•

DHCP UserClass ID

- Shows the DHCP UserClass ID when the

Dynamically allocated over DHCP/BOOTP

option is selected.

Use the following guidelines for the Security tab:

•

Access Type

- (For Wireless Option Only) Select the access type option (either

None

WPA_Personal

WPA2_Personal

WPA_Enterprise

, or

WPA2_Enterprise

) to be used for this wireless communication link.

WPA_Personal

and

WPA2_Personal

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

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

and

WPA2_Enterprise

- Wi-Fi Protected Access (WPA)_Enterprise encryption can be enabled by selecting one of these options (WPA2-Enterprise verifies network users through a server. WPA2 is backward compatible with WPA).

•

Enable IEEEE 802.1x authentication

- Select this check box to enable this authentication and activate the EAP Type list of options.

EAP Type

- If you have enabled the

Enable IEEEE 802.1x authentication

check box, select the EAP Type option you want (

TLS

LEAP

, or

PEAP

TLS

- If you select the

TLS

option, click

Properties

to open and configure the

Authentication Properties

dialog box (you can use

Browse

to find and select the Client Certificate file and Private Key file you want). Validate Server Certificate is mandatory (be sure the check box is selected/checked). Note that the CA certificate must be installed on the thin client. Also note that the server certificate text field supports a maximum of approximately 127 characters, and supports multiple server names.

The following kinds of server names are supported (all examples are based on

Cert Common name is "company.wyse.com").

NOTE

: Using only the FQDN, i.e. company.wyse.com will not work, you must use one of the options (note that

*.wyse.com is the most common option as multiple authentication servers may exist): servername.wyse.com

*.wyse.com

*wyse.com

*.com

LEAP

- If you select the

LEAP

option, click

Properties

to open and configure the

Authentication Properties

dialog box (be sure to use the correct Username and

Password for authentication). Note that the maximum length for the username or the password is 64 characters.

PEAP

- If you select the

PEAP

option, click

Properties

to open and configure the

Authentication Properties

dialog box (be sure to select either

EAP_GTC

EAP_MSCHAPv2

, and then use the correct Username, Password, and Domain, if

Chapter 4 necessary, for authentication). Validate Server Certificate is optional. Also note that the server certificate text field supports a maximum of approximately 127 characters, and supports multiple server names.

The following kinds of server names are supported (all examples are based on

Cert Common name is "company.wyse.com").

NOTE

: Using only the FQDN, i.e. company.wyse.com will not work, you must use one of the options (note that

*.wyse.com is the most common option as multiple authentication servers may exist): servername.wyse.com

*.wyse.com

*wyse.com

*.com

Properties dialog box (for PEEP IEEE802.1x authentication), an option to hide the domain is available for selection (the Username and Password text boxes are available for use, but the Domain text box displays gray).

•

Certificate Management

- Opens the Certificates Browser where you can select the

Import From

option you want to import a certificate (either

USB Storage

File

Server

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

- If you select the

File Server

option, click

Import

to open and use the

Import

dialog box to enter the detailed path to the certificate 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 name is limited to 64 characters.

Use the Wireless tab to view the Connected SSID, Connection Speed, Signal Strength, add (click

Add

and enter your configurations), remove (select an SSID and click

Remove

), check properties (select an SSID and click

Property

), move SSIDs up and down in the priority list (select an SSID and click

Down

) and to scan and list the wireless networks within range (click

Scan

—NOTE: the SSID, State, Type, and Signal of each wireless network will be detected and displayed in a Wireless Connections window).

Configuring Connection Settings Locally

Use the following guidelines when adding SSIDs manually:

TIP

: While Service Set Identification (SSID) and encryption configurations can be entered manually on the thin client (be sure that the corresponding entries are also made on the enterprise access point), ThinOS can also scan the wireless network and list all available connections within range of the thin client.

•

SSID

- Enter the Service Set Identification (name of the wireless network) set up by the network administrator for this wireless communication link (maximum is 32 characters).

•

Security Type

and

Encryption

- Select the encryption option (either

None

WPA-Personal

WPA2-Personal

WPA-Enterprise

, or

WPA2-Enterprise

) to be used for this wireless communication link (If a WPA option is selected, TKIP and CCMP encryption is supported; if a WPA2 option is selected, CCMP encryption is supported).

None

- Select None if encryption is not required.

WPA-Personal

and

WPA2-Personal

- Wi-Fi Protected Access (WPA and WPA2)

Personal encryption is designed to improve upon the security features of WEP but is still designed for home and small office networks that do not require the complexity of an authentication server (WPA2 provides more security than WPA).

WPA-Enterprise

and

WPA2-Enterprise

- Wi-Fi Protected Access (WPA and WPA2)

Enterprise encryption is designed to improve upon the security features of WEP but also verifies network users through an authentication server (WPA2 provides more security than WPA; WPA2 is backward compatible with WPA).

•

WEP Key

WPA Key

- If either box is active (depending on

Encryption

option), enter the key according to your Encryption selection. 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.

•

Enable IEEEE 802.1x authentication

- Select this check box to enable this authentication and activate the EAP Type list of options.

•

EAP Type

- If you have enabled the

Enable IEEEE 802.1x authentication

check box, select the EAP Type option you want (

TLS

LEAP

, or

PEAP

TLS

- If you select the

TLS

option, click

Properties

to open and configure the

Authentication Properties

dialog box (you can use

Browse

to find and select the

Client Certificate file and Private Key file you want). Validate Server Certificate is mandatory (be sure the check box is selected/checked). Note that the CA certificate must be installed on the thin client. Also note that the server certificate text field supports a maximum of approximately 127 characters, and supports multiple server names.

The following kinds of server names are supported (all examples are based on Cert

Common name is "company.wyse.com").

NOTE

: Using only the FQDN, i.e. company.wyse.com will not work, you must use one of the options (note that

*.wyse.com is the most common option as multiple authentication servers may exist): servername.wyse.com

*.wyse.com

*wyse.com

*.com

LEAP

- If you select the

LEAP

option, click

Properties

to open and configure the

Authentication Properties

dialog box (be sure to use the correct Username and

Password for authentication). Note that the maximum length for the username or the password is 64 characters.

PEAP

- If you select the

PEAP

option, click

Properties

to open and configure the

Authentication Properties

dialog box (be sure to select either

EAP_GTC

EAP_MSCHAPv2

, and then use the correct Username, Password, and Domain, if necessary, for authentication). Validate Server Certificate is optional. Also note that

Chapter 4 the server certificate text field supports a maximum of approximately 127 characters, and supports multiple server names.

The following kinds of server names are supported (all examples are based on Cert

Common name is "company.wyse.com").

NOTE

: Using only the FQDN, i.e. company.wyse.com will not work, you must use one of the options (note that

*.wyse.com is the most common option as multiple authentication servers may exist): servername.wyse.com

*.wyse.com

*wyse.com

*.com

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 on the thin client (the server certificate is forced to be validated). Also note that when EAP Type EAP-MSCCHAPV2 is selected on the Authentication Properties dialog box (for PEEP IEEE802.1x authentication), an option to hide the domain is available for selection (the Username and Password text boxes are available for use, but the Domain text box displays gray).

Enabling a Disabled Network Setup Dialog Box

Although there are privileges and user modes associated with user access to thin client resources, access to network setup (using the

Network Setup

dialog box) depends upon privilege level. A Stand-alone user either is by default a user with High privilege or has a thin client that is locked down. A Guest user has an implicit privilege of None and all access is governed by that privilege. A PNAgent/PNLite-only user has whatever privilege was set in the wnos.ini file at thin client boot, whatever privilege was locked down at the last access of a wnos.ini file, or High privilege (by default).

Example: High Privilege - Low Privilege - None

If the Privilege parameter is set to Low or None in the INI files, the thin client

Network

Setup

dialog box will be disabled (the user cannot access it). In such a case, there may be occasion to access the

Network Setup

dialog box without wanting to change the

INI files. For example, an occasion when you need to change to another FTP or Virtual

Desktop file server or add to the PNAgent/PNLite servers list. To access the

Network

Setup

dialog box in such a case, disconnect the network cable and reboot the thin client to Stand-alone user mode. The

Network Setup

dialog box displays after the thin client initializes and you can then make the required entries (be sure to reconnect the network cable and reboot when finished).

Configuring Connection Settings Locally

Remote Connections

Use the

Remote Connections

dialog box (

System Settings icon > Remote

Connections

) to configure thin client remote connections (including ICA, RDP, Citrix

XenDesktop, VMware View, Dell vWorkspace, and other broker server connections), visual options, and general connection settings.

TIP

: In the Classic Desktop option, the

Remote Connections

dialog box allows you to create default ICA and RDP connections for use. If you want to create several ICA and

RDP connections (more than the default connections), use the Connect Manager (see

"Connect Manager").

Use the following guidelines for the Broker Setup tab (

IMPORTANT

: for details on the latest options for each connection, see ThinOS release notes):

TIP

: Broker locations can be supplied through a wnos.ini file if it is used. If DHCP is used, broker locations can be supplied through DHCP. After creating an entry, be sure to reboot the thin client to have the changes take effect.

•

ICA Connection

- Select

None

, select

ICA

, click

Configure Connection

, and then follow the wizard (see "Configuring ICA Connections").

•

RDP Connection

- Select

None

, select

RDP

, click

Configure Connection

, and then follow the wizard (see "Configuring RDP Connections").

•

Microsoft Connection

- Select

Microsoft

, enter the IP Address for the server in the

Broker Server

box, and then click

•

Citrix Xen Connection

- Select

Citrix Xen

, enter the IP Address for the server in the

Broker Server

box, select your options, and then click

TIP

: You can also select the Enable StoreFront option to enable StoreFront feature (if selected, the Visual Experience tab will be disabled/grayed)

- Use the following guidelines for the Citrix Xen Broker Server:

- Enter the IP Address or host name for the server in the

Broker Server

box.

- Use the

Enable automatic reconnection at logon

and

Enable automatic reconnection from button menu

check boxes and options to further configure the connection for automatic reconnection.

- Use the

Account Self-Service Server

box to enter the Account Self-Service IP address (HTTPS only) such as https://IPAddress. Locations can be supplied through a wnos.ini file if it is used. If DHCP is used, locations can be supplied through DHCP.

After making an entry, be sure to reboot the thin client to have the changes take effect. This feature allows users to change or reset their own password and to unlock their account from the

Login

dialog box (see "Login Dialog Box Features").

NOTE

: The account self-service feature requires the usage of Citrix Password manager.

- Use the

XenApp

button to use the Wyse default settings for the XenApp default

Chapter 4 settings (

IMPORTANT

: Note that the system will restart to apply the new settings).

- Use the

XenDesktop

button to use the Wyse default settings for the XenDesktop default settings (

IMPORTANT

: Note that the system will restart to apply the new settings).

•

Dell vWorkspace Connection

- Select

Dell vWorkspace

, enter the IP Address for the server in the

Broker Server

box, and then click

TIP

: You can also select the Enable vWorkspace Gateway option to enable the vWorkspace Gateway feature (input the vWorkspace SSL Gateway URL through this

UI or by using INI files).

•

VMware View Connection

- Select

VMware View

, enter the IP Address for the server in the

Broker Server

box, select the Security Mode you want (to verify the identity of the servers to which it connects), and then click

•

Direct Connection

- Select

Other

, enter the IP Address for the broker server in the

Broker Server

box, and then click

TIP

: The broker supports both http and https, and depends on the broker server support. If http or https is not specified on the broker server, then http is used by default. If https is specified, the client side must install a corresponding root certificate locally. For details on installing a corresponding root certificate locally, refer to

Knowledge Base Solution #

15508

(go to the Knowledge Base at http://www.wyse.com/ kb

and search for

15508

Use the following guidelines for the Visual Experience tab (Note that the Visual

Experience tab is grayed out if the Enable StoreFront check box is selected for a Citrix

Broker Server is entered in the Broker Setup tab):

•

Classic Desktop

- Displays the full taskbar, desktop, and Connect Manager familiar to ThinOS users. This option is recommended for terminal server environments and for backward compatibility with ThinOS 6.x versions.

•

Zero Launchpad

- Displays the new launchpad style GUI designed for VDI use.

Functionality is accessed through an always available interface. This option is recommended for VDI and any full-screen only connections.

•

Toolbar, hotkey, and connection icon options are also available for configuration.

Configuring Connection Settings Locally

Use the General Options tab options to select the action after you exit all open desktops (by default, the thin client automatically returns to the

Login

dialog box and is ready for another user), to set the default sign-on credentials (Username, Password, and Domain), to set the One Sign Server Virtual Desktop Access, and to clear locally saved connections (use the Clear locally saved connections button to clear connections you no longer need).

TIP

: If you enter all three Default Sign-on credentials (Username, Password, and

Domain), you will be automatically logged on to your desktop upon system start.

NOTE

Imprivata™ OneSign Server Integration

- OneSign Virtual Desktop Access provides a seamless authentication experience and can be combined with single sign-on for No Click Access to desktops and applications in a virtual desktop environment. Configure the

OneSign Server

box enter either https://ip or https://FQDN values, reboot the client to display the

Log on

dialog box, and then enter credentials to open the

VDI broker

dialog box for log on use. You can also set this feature in your INI file (see Reference Guide: Wyse ThinOS

INI Files).

For details on Deployment in an Imprivata OneSign ProveID Environment, see

Knowledge Base Solution

#23254

(go to the Knowledge Base at http://www.wyse.com/kb

and search for

23254

The following OneSign features/actions are supported:

•

Client & Broker Authentication

Citrix Xen App

Citrix Xen Desktop

VMware View

•

Authenticate w/Password

•

Authenticate w/Password + Password Change

•

Authenticate w/Password + Password Change | New Password is Invalid

•

Authenticate w/Proximity Card + Password

•

Authenticate w/Proximity Card + Pin

•

Authenticate w/Proximity Card + Pin | Pin not enrolled

•

Interrupt Authentication

•

Authenticate w/Proximity Card Alone | Retrieve Password

•

Retrieve User Identity Password

•

Reset User Identity Password

•

Update User Identity Password

•

Enroll Proximity Card

•

Lock/Unlock Terminal with Proximity Card

Chapter 4

Central Configuration

Use the

Central Configuration

dialog box (

System Settings icon > Central

Configuration

) to configure thin client central connection settings such as file server, optional WDM server settings, and optional Cloud Client Manager.

Use the following guidelines:

•

File Servers/Path

Username

, and

Password

- IP address or host name of the file server that provides the system software and update images. The address can be supplied through DHCP if DHCP is used. Use the following guidelines:

File Servers/Path

- Allows 128 characters maximum. The data specifies part of the path to be used when the server is accessed. Multiple file servers/paths may be named, as long as all data fits in the length limitation.

Username

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

Password

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

•

WDM Servers

- List of IP addresses or host names if WDM is used. Locations can also be supplied through user profiles if user INI profiles are used.

•

Discovery Settings

area (For more information on setting up the discovery options, see Installation Guide: Wyse Device Manager

DNS Name Record

- (Dynamic Discovery) Allows devices to use the DNS

Hostname lookup method to discover a WDM Server.

DNS SRV Record

- (Dynamic Discovery) Allows devices to use the DNS SRV record lookup method to discover a WDM Server.

DHCP Inform

- (Dynamic Discovery) Allows devices to use DHCP option tags to discover a WDM Server.

Manual Discovery in Management Console

- (Manual Discovery from WDM) If no Dynamic Discovery method is used, you can use the

Find Devices

dialog box to discover devices from WDM (WDM Agents will respond to the server discovery

Configuring Connection Settings Locally by storing the discovered Web Server IP address and port and begin regular check-ins).

Enable Automatic Discovery After Missed Check-ins

- Select the number of missed check-ins after which you want the auto discovery options enabled.

•

Cloud Client Manager Service

- To register thin client devices with Cloud Client

Manager Service, ensure the

Enable Cloud Client Manager

check box is selected, enter the

Group Registration Key

(as configured by your Cloud Client Manager administrator) for the desired group, click

, and then follow the on-screen instructions. When prompted, log in with corporate credentials in order to complete the registration process.

TIP

: You can use the Validate Key button to verify your entry is correct. If you see a success message, click

to reboot the device and finish the registration process. If you see a failure message, double check the Group Registration Key you entered and verify you have the correct network connectivity (see your Cloud Client

Manager administrator).

Chapter 4

Advanced Details on Configuring ICA and RDP Connections

Use the following information when configuring ICA and RDP connections (this information assumes that the thin client does not have a locked down privilege level):

•

High-privileged user

- The additional functionality provided by the

Connection

Settings

dialog box allows testing of connection definitions before they are entered

(by a network administrator) into the user profile files.

•

Low-privileged user

- The settings for the selected connection can be viewed but cannot be edited, and new connections cannot be defined. Connection definitions are controlled by a network administrator and are accessed by the thin client from the user profiles located on a remote server.

•

Stand-alone user

- The Connect Manager is available to Stand-alone users because 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.

Configuring ICA Connections

To configure the ICA connection option you selected in the Remote Connections dialog box (see "Remote Connections"), use the following guidelines.

If you select the

Server

option, the Host Names box is displayed.

If you select the

Published Application

option, the Application Name box replaces the

Host Names box.

Configuring Connection Settings Locally

Use the following guidelines on the Connection tab:

•

Server

Published Application

- Select the type of connection to which the settings apply.

•

Connection Description

- Enter the descriptive name that is to appear in the connection list (38 characters maximum).

•

Browser Servers 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 program 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.

•

Host Name

Application Name

(title depends on the

Server

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

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.

TIP

: 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 the security level of communications between the thin client and the ICA server.

Basic

(the default option) is the lowest level of security. Basic allows faster communication between the device and the ICA server because it requires less processing than 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 example, most Web 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.

Chapter 4

•

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

•

Wyse VDA

- When selected, the thin client will use Virtual Desktop Accelerator software to provide an “accelerated” user experience on remote desktop sessions with high round-trip delay between the server and client.

•

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

Colors

- Select the color depth of the ICA session. If

High Colors

(16bits) or

True

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]).

•

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.

•

Auto-connect on start-up

- When selected, automatically connects the session on start-up.

•

Re-connect after disconnect

- When selected, causes the thin 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 (enter the number of seconds 1 to 3600) 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.

Use the following guidelines on the Logon tab:

•

Logging on

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

Mode (if the Login Username, Password, and Domain name boxes are not populated, you can enter the information manually in the ICA server login screen when the connection is made):

•

Login Username

- 31 characters maximum.

•

Password

- 19 characters maximum.

•

Domain Name

- 31 characters maximum.

•

Logon Mode

- Select

User-specified credentials

Smart Card

, or

Local User

•

Start Command

area - (Server Connection Option Only - This area is disabled

(grayed) for a Published Application option.)

•

Application

(127 characters maximum) and

Working Directory

(63 characters 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.

Configuring Connection Settings Locally

Use the following guidelines on the Options tab:

•

Auto-connect to local devices

- Select any options (

Printers

Serials

USB

Smart

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

•

Turn compression off

- When selected, turns compression off (intended for high-speed connections).

•

Optimize for low speed link

- When selected, allows optimization for low-speed connections, such as reducing audio quality and/or decreasing protocol-specific cache size. Intended for a connection spanning a WAN link or using dialup.

•

Map all disks under (z:)

- When selected, maps all disks under the Z drive.

•

Enable session reliability

- When enabled, session reliability allows a user to 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.

•

Allow font smoothing

- When selected, enables font smoothing (smooth type).

Chapter 4

Configuring RDP Connections

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

To configure the RDP connection option you selected in the Remote Connections dialog box (see "Remote Connections"), use the following guidelines.

Use the following guidelines on the Connection tab:

•

Connection Description

- Enter the descriptive name that is to appear in the connection list (38 characters maximum).

•

Host Names

- Use the list to select the valid DNS server name or the IP address of the server to which the thin client connection is to be made (you can also use

Browse

next to the box to make the selection you want). For example, a list of WTS servers on the local network from which you can select.

TIP

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

•

Enable Wyse VDA

- When selected, the thin client will use Virtual Desktop

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

•

Console mode -

Select to set the RDP connection with Windows Console mode.

•

Display Resolution

- Select the display resolution for this connection.

Colors

- Select the color depth of the RDP session. If

High Colors

(16 bits) or

True

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.

TIP

: For some thin clients versions, only the

256 Colors

(8 bits) selection is available for RDP connections. Also, for older versions of the server software (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 connection is established.

•

Full screen on 1 monitor

and

Span both monitors

- Select the initial view of the application in a full screen or span. You can toggle between viewing modes by using CTRL+ALT+UPARROW.

•

Auto-connect on start-up

- When selected, automatically connects the session on start-up.

•

Re-connect after disconnect

- When selected, causes the thin client to automatically reconnect to a session after a non-operator-initiated disconnect. If

Configuring Connection Settings Locally

selected, the wait interval is that set in the

Delay before re-connecting

TIP

: You can reset the options on the Connection tab of the

Connection Settings

(RDP)

dialog box. To do so, click the

Reset VM

command button. This command button is located in the upper-right of the dialog box. It appears only with a VDM broker connection.

Use the following guidelines on the Logon tab:

•

Logging on

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

•

Login Username

- 31 characters maximum.

•

Password

- 19 characters maximum.

•

Domain Name

- 31 characters maximum.

•

Application

(127 characters maximum) and

Working Directory

(63 characters 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.

•

Use TS Gateway

- Enables the use of Terminal Services Gateway (TS Gateway) server when connecting. If required, then enter the IP address or URL of the TS

Gateway server in the Server name box. You can also enable

Use Same Info

(if the server credentials are the same credentials as your Remote Desktop Credentials

(Host remote computer credentials) in the Login Username, Password, and Domain name fields) or disable

Use Same Info

and enter the Server name, User name,

Password, and Domain name of the TS Gateway server if required.

NOTE

: A TS Gateway server is a type of gateway that enables authorized users to connect to remote computers on a corporate network from any computer with an

Internet connection. A TS Gateway server enables Remote Desktop connections to a corporate network from the Internet without having to set up virtual private network (VPN) connections. Ask your network administrator whether you need to specify an TS Gateway server.

User Name

- Enter a user name for the connection.

Password

- Enter the password.

Domain

- Enter the domain name.

TIP

: The User name, Password, and Domain name fields are optional. If you leave any of these fields blank, interactive login is required (users must enter the information at login time).

Chapter 4

Use the following guidelines on the Options tab:

•

Wallpaper

- When selected, disables the desktop wallpaper.

•

Menu / Window animation

- When selected, disables the menu or window animation.

•

Theme

- When selected, disables the desktop themes.

•

Show content when dragging

- By default, when you “grab” a Window by the title bar and move it around, the contents of the window will move with it. Select this to disable this content view so that only the outline of the window moves when dragging it, until you drop the window. This option can be beneficial, as it uses less processing power.

•

Font smoothing

- Converts vector text to bitmap for better display.

•

Auto-connect to local devices

- Select any options (

Printers

Serials

USB

Smart

Cards

Sound

, and

Disks

) to have the thin client automatically connect to the devices (

USB

- Redirects locally attached USB devices on the thin client to a

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

•

RDP Audio Playback

and

RDP Audio Recording

- Select the audio options you want.

•

Turn compression off

- When selected, turns compression off (intended for high-speed connections).

•

Optimize for low speed link

•

Auto detect network

- When selected, turns on the auto detect network feature.

This feature is enabled by default. It also disables the Optimize for low speed link option and the Desktop Experience options by default.

•

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

Performing Diagnostics

Diagnostics menu items include:

•

“System Tools”

•

“Network Tools”

To access the Diagnostics menu:

•

Zero Desktop - click the

System Settings

icon on the Zero Toolbar (administrators can also click the

Admin Mode

button on the

Login

dialog box).

•

Classic Desktop - click User Name (User Name is the user who is logged-on and is located at the bottom-left side of the taskbar) to open the Desktop Menu, and select either

Network Test

(for network tools Ping and Trace Route) or

System Tools

(for system tools to configure Trace and Event log settings, and to view INI files).

TIP

: Additional system tool features such as Write Event Log to USB, Network Capture to USB, Trace Action, Delay on Trace, and Trace to/from USB, can be found in the

Shortcut Menu (right-click on the Classic Desktop) as described in "Shortcut Menu."

Chapter 5

System Tools

Use the

System Tools

dialog box (

System Settings icon > System Tools

) to configure

Trace and Event log settings, Performance Monitor graphs (graphs that display client

CPU, Memory, and Networking information), and for CMOS management (extract and restore cmos settings as described in "CMOS Local Management: Extracting CMOS

Settings to a USB Key for Distribution"). It also allows you to view wnos.ini cached information for troubleshooting purposes.

Use the Trace and Write Event log options on the General tab to configure the settings you want (be sure to enable the EnableTrace option of the Privilege parameter in a wnos.ini file - see Reference Guide: Wyse ThinOS

INI Files).

Use the Network capture to USB option on the General tab to enable the capture of network information (a network trace of all traffic coming in and out of the thin client) to a USB drive that is inserted into the thin client (after logon and use of the

XenDesktop server or network, you will see a WTOS_WS.pcap file in the USB drive which you can analyze using software such as a packet analyzer used for network troubleshooting, analysis, and so on).

IMPORTANT

: Be sure to insert the USB drive into the thin client before selecting the

Network capture to USB option. Note that the Network capture to USB option is automatically cleared if there is no USB drive inserted and you exit the dialog box, or after restarting the thin client (if needed, you must select the option again).

Use the Performance Monitor button on the General tab to display client CPU, Memory, and Networking information (graphs display on top of all windows).

Performing Diagnostics

Use the Device Viewer tab - Displays all the locally attached devices, including USB,

Serial, and Parallel on applicable platforms. The Device Viewer button was previously found in the Devices tab of the System Information dialog box.

IMPORTANT

: The

Mirror File Server tab has been removed from the System Tools dialog box as it can now be viewed in the Device Viewer tab.

If you are using global INI files, use the Global INI tab to view wnos.ini information.

If you are using username INI files, use the user.ini tab to view user.ini information.

Chapter 5

If you are using CCM INI files, use the CCM.ini tab to view CCM.ini information.

NOTE

: To display the Cloud Client Manager (CCM) tab, you must enable the

AdvancedConfig option of the CCMEnable parameter (see Reference Guide: Wyse

ThinOS

INI Files).

TIP

: For detailed instructions on how to configure CCM in a wnos.ini file to enable the

CCM Agent on supported ThinOS clients, refer to Knowledge Base Solution #

23875

(go to the Knowledge Base at http://www.wyse.com/kb

and search for

23875

IMPORTANT

: It is best practice to remove any ini parameters/options that you are using in CCM from other ini files such as Global and username INI files. For example, if you are using the Connect= parameter in CCM, it is best practice to remove the

Connect= parameter from the Global and username INI files.

Performing Diagnostics

Network Tools

Use the

Network Tools

dialog box (

System Settings icon > Network Tools

) to access

Ping (Packet InterNet Groper) and Trace Route tools 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). Generally, Ping and Trace Route are used for system diagnostics by, or under the direction of, a network administrator.

Using Ping

Use the

Ping

dialog box to execute the ping diagnostic utility and display response messages. Ping sends an echo request to a network host. The host parameter is either a valid host name or an IP address. If the host is operational and on the network, it responds to the echo request. By default, echo requests are sent until interrupted (by clicking

Stop

). Ping sends one echo request per second and calculates round trip times and packet loss statistics. It displays a brief summary upon completion of the calculation.

The ping utility can be used to:

•

Determine the status of the network and various foreign hosts

•

Track and isolate hardware and software problems

•

Test, measure, and manage networks

•

Determine the IP address of a host if only the hostname is known

TIP

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

Use the following guidelines:

•

Enter Hostname or IP

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

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

•

Data area - Displays ping response messages. The ping command sends one echo request per second, calculates round trip times and packet loss statistics, and displays a brief summary upon completing the calculation.

•

Start

- Executes the ping command. 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

•

Stop

- Terminates the ping request and leaves the

Ping

dialog box open (so you can read the summary posted in the data area).

Chapter 5

Using Trace Route

Use the

Trace Route

dialog box to execute the tracert diagnostic utility and display 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.

Use the following guidelines:

•

Enter Hostname or IP

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

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

•

Data area - Displays round-trip response time and identifying information for each device in the path.

•

Start

- Executes the tracert command.

•

Stop

- Terminates the tracert command and leaves the

Trace Route

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

Central Configuration: Automating

Updates and Configurations

This appendix describes how to set up your environment to provide your thin clients running ThinOS with automatic updates and configurations in three simple steps.

TIP

: Wyse thin clients do not require device management software. They are configured to obtain their IP address, as well as the location of firmware and configuration instructions, from a DHCP server. However, you can use WDM for a more hands-on management of your thin clients. For information about configuring your thin clients to communicate with a WDM server, see the WDM related INI parameters in

"Step 2: Direct the Thin Client to the Server Using DHCP Options" and Reference Guide:

Wyse ThinOS

INI Files.

Appendix A

How to Set Up Automatic Updates and Configurations

For a thin client running ThinOS to successfully access INI files and update itself from a server, you must set up the server with the correct folder structure (where the INI files and other update files are located), direct the thin client to the server, and then reboot or start the thin client.

After DHCP and servers are configured and available, the thin client checks (at each boot up) to see whether or not any updates are available on a predefined server (

DCHP

Option #161

specifies the server URL,

DCHP Option #162

specifies the root path to the server). If updates are available, the updates are automatically installed.

Step 1: Prepare the Root Directory and Folder Structure on the Server

Set up the following folder structure on your server under the C:/inetpub/ftproot folder

(for FTP) or C:/inetpub/wwwroot folder (for HTTP or HTTPS) and place your INI files and other necessary files inside the structure as noted (this list describes the folder structure, starting with the root directory).

/wyse/ (Required)

The root directory. It stores the wnos folder.

/wyse/wnos (Required)

The main INI configuration folder.

It stores the wnos.ini file, $MAC.ini file, firmware, and the following optional folders:

• bitmap folder

• cacerts folder

• font folder

• inc folder

• ini folder

• locale folder

• trace folder

/wyse/wnos/bitmap (Optional) The folder where you can place custom images you plan to use.

/wyse/wnos/cacerts (Optional) The folder where you can place the CA certificates that can be imported to a thin client.

Note:

Use the AddCertificate INI parameter in the wnos.ini file to import the certificates to thin clients.

/wyse/wnos/font (Optional) The folder where you can place font files for languages that require the file (Chinese Simplified, Chinese

Traditional, Japanese, Korean).

/wyse/wnos/inc

/wyse/wnos/ini

(Optional) The folder where you can place the mac.ini files

(note that the use of the parameter

Include=$mac.ini will load “/ wnos/inc/mac-address.ini” so that you can use inc in the folder structure and use $MAC.ini).

(Optional) The folder where you can place the {username}.ini files and {group} folder.

/wyse/wnos/locale

/wyse/wnos/trace

(Optional) The folder where you can place locale message files.

(Optional) The folder where you can place the trace files that you can capture and play back (be sure to enable the parameter, EnableTrace=yes).

Central Configuration: Automating Updates and Configurations

Be sure to create/activate the two required MIME Types (

.ini

and

) under IIS (on a per site basis) to enable downloading. Also be sure your Web server can identify the file types used by Wyse thin clients.

To create/activate

.ini

On your IIS server, use the

File Types

menu to add a New Type.

In the

File Type

dialog box, enter the Associated extension

.ini

and Content type

(MIME)

text/plain

Click

to apply the settings.

To create/activate

On your IIS server, use the

File Types

menu to add a New Type.

In the

File Type

dialog box, enter the Associated extension

and Content type

(MIME)

text/plain

Click

to apply the settings.

For detailed instructions on adding

.ini

and

, refer to Knowledge Base Solution #

15508

(go to the Knowledge Base at http://www.wyse.com/kb

and search for

15508

Step 2: Direct the Thin Client to the Server Using DHCP Options

After you set up the folder structure and populate it with the correct files, you must then direct the thin client to the location of the server using DHCP.

Information about the server and root directory is obtained from the following DHCP options:

•

161

- The server.

•

162

- Root path to the file server (ftp/http/https).

If no root path is defined, /wnos is assumed.

If a root path is defined, the additional path will be appended to the URL supplied by option 161.

•

184

- (Optional) Server username (to server specified in option 161).

•

185

- (Optional) Server password (to server specified in option 161).

Use the guidelines shown in Table 7 when creating and adding the DHCP options you need. Ensure that within the DHCP scope the new DHCP option tags you create are activated (this can be done using the

Scope Options

dialog box on the DHCP server after you add them, or the

Configure Options

command before you add them).

Appendix A

Table 7 DHCP Options

161

Option

Description

Subnet Mask

Notes

Required. However, it is not is not required unless the thin client must interact with servers on a different subnet (MS

DHCP requires a subnet mask and will always send one).

Time Offset

Router

Optional.

Optional, but recommended. It is not required unless the thin client must interact with servers on a different subnet.

Optional, but recommended.

Domain Name Server

(DNS)

Domain Name

Broadcast Address

Optional, but recommended. See Option 6.

Optional.

WINS servers IP Address Optional.

Lease Time Optional, but recommended.

Option Overload

DHCP Message Type

DHCP Server IP Address

Parameter Request List

Maximum DHCP

Message Size

Optional.

Recommended.

Sent by thin client.

Optional (always sent by thin client).

T1 (renew) Time

T2 (rebind) Time

Optional, but recommended.

Client identifier Always sent.

File server (ftp/http/https) Optional string. Can be either the name or the IP address of the file server. If a name is given, the name must be resolvable by the DNS server(s) specified in Option 6. If the option provided by the server is blank or the server provides no value for the field, the machine on which the

DHCP server resides is assumed to also be the file server.

Central Configuration: Automating Updates and Configurations

Table 7 DHCP Options, Continued

Option Description

162 Root path to the file server (ftp/http/https)

181

182

184

185

PNAgent/PNLite server list

NT domain list for

PNAgent/PNLite

File server Username

File server Password

Notes

Optional string. If the option provided by the server is blank and the server provides no value for the field, a null string is used.

\wyse\wnos

is automatically appended to the search path. For example, if you enter pub\serversoftware

, the path searched will be pub\serversoftware\wyse\wnos

Note:

You can have the

\wyse

automatic component of the search path omitted by appending a dollar sign (

) to the entered path. For example, if you enter pub\serversoftware$

, the path searched will be pub\serversoftware\wnos

Note:

The usage or omission of a leading slash (

) on the path is critical on some servers. Some servers limit access to the root path of the user specified at login. For those servers, the usage of the leading slash is optional. Some

*NIX servers can be configured to allow the file user access to the entire file system. For those servers, specifying a leading slash specifies that access is to start at the root file system. Proper matching of the file specification to the file server in use is critical to ensuring proper operation. A secured Windows server requires the slash be specified in order to complete proper access.

Optional string. The thin client uses the server to authenticate the Windows credentials of the user and to obtain a list of ICA published applications valid for the validated credentials. The user supplies those credentials when logging in to the thin client.

Optional string. The thin client creates a pull-down list of domains from the information supplied in option 182. This list is presented at thin client login in the order specified in the DHCP option (for example, the first domain specified becomes the default). The selected domain is the one which must authenticate the user ID and password. Only the selected domain is used in the authentication process.

If the domain list is incomplete and the user credentials must be verified against a domain not in the list (assuming that the server in option 181 is capable of authenticating against a domain not in the list), the user has the option of not using any of the domains specified in option 182 and typing a different domain name at the time of login.

Optional string. Username to use when authenticating to the server specified in Option 161.

Optional string. Password to use when authenticating to the server specified in Option 161.

188

190

192

Appendix A

Table 7 DHCP Options, Continued

Option Description

186 WDM server list

187

194

199

WDM server port

Virtual Desktop Broker server

WDM secure port

WDM server port

WDM FQDN

Cloud Client Manager

Group Key

Notes

Optional binary IP addresses of WDM. This option can specify up to two WDM servers. If two are specified, at boot time the thin client will attempt to check-in to the first server. If it cannot contact the first server it will try to check-in to the second server.

Optional number. Byte, word, or two-bytes array.

NOTE:

The value of this option tag, when not embedded in Vendor Class Specific Information option, is interpreted in reverse order when it is sent as 2 bytes (for example, the value of 0x0050 was interpreted as 0x5000). This option tag was used by old ThinOS releases. New ThinOS releases still accept this option tag for backward compatibility.

Optional string.

Optional number, word, or two-bytes array. Specifies to use HTTPS to communicate with WDM instead of HTTP.

Optional number, word, or two-bytes array.

NOTE:

The value of this option tag represents the same information as option tag 187. The difference is that

ThinOS interprets the value of this option tag in correct order (for example, the value of 0x0050 is interpreted as

0x0050). If the DHCP server provides both option tag 192 and 187, option tag 192 takes precedence.

Optional Fully Qualified Domain Name for the WDM server.

Optional string. Can provide a CCM Group Registration

Key for the Cloud Client Manager agent. When Cloud

Client Manager is disabled and the Group Key of Cloud

Client Manager is NULL, this option will take effect. Cloud

Client Manager will use the optional string as the Group

Registration Key. If the Cloud Client Manager server or

MQTT server is NULL, the Cloud Client Manager agent will set them to the default server values.

TIP

: The thin client conforms to both RFC-compliant DHCP servers (RFC numbers 2131 and 2132) and RFC-noncompliant Microsoft servers (which NULL terminate strings sent to the thin client). The thin client supports both infinite leases and leases that expire

(per RFC 2131 and others).

TIP

: Not all options in the range 128-254 are strings. Options 186, 190, and 192 are employed for all Wyse products that use WDM. Their format and content are determined by the WDM product.

Step 3: Reboot or Start the Thin Client

After you reboot or start the thin client, it will look in the defined root path for the latest available image and update if necessary.

CMOS Management

This appendix includes general CMOS management information for use with the following supported versions:

•

C10 BIOS version 1.0B_SPC001-0407 or later

•

D10D BIOS version 3.0D or later

•

R10 BIOS version 1.0H_SPC-0T51 or later

•

V10LE BIOS version 1.19R or later

Depending on the method of distribution you want to use, complete one of the following:

•

"CMOS Central Management: Extracting CMOS Settings to the File Server for

Distribution."

•

"CMOS Local Management: Extracting CMOS Settings to a USB Key for Distribution."

Appendix B

CMOS Central Management: Extracting CMOS Settings to the File Server for Distribution

CAUTION

: It is recommended to initially complete these procedures on a file server designated to test the success of your CMOS central management settings/process.

While the central configuration method can be used to enforce your CMOS settings in a production environment, be aware that any thin client that logs into the file server that contains the cmos.ini and its extract and restore commands will be subject to those commands (CMOS overwrites).

CMOS central management allows ThinOS administrators to easily manage CMOS settings for large deployments of thin clients using central configuration methodologies. This case example uses C10 BIOS version 1.0B_SPC001-0407. However, you can use these instructions for other supported BIOS versions.

Step 1: Prepare a Reference Device containing BIOS version 1.0B_SPC001-0407 or later

On the thin client you want to use as a Reference Device (the reference device will be the golden image you will use to distribute to other thin clients), enter the BIOS

Setup Utility (during boot, press and hold the

Delete

key, enter the password

Fireport

—this is case sensitive—and press

Enter

) and configure the CMOS settings you want (supported CMOS settings include: AutoPower, BootOrder, P-key setting,

BiosPassword—and for C10 BIOS version 1.0B_SPC001-0407 or later the

WakeOnLAN setting).

Save your CMOS settings before exiting the utility.

Shut down the thin client.

Step 2: Prepare a File Server containing a CMOS INI File

On your file server, create a cmos.ini file and place it in the wnos directory/folder under the file server ini directory (be sure the wnos directory on the file server has upload privilege).

In the cmos.ini file, write the following line:

Device=cmos Action=extract

Step 3: Reboot the Reference Device to the File Server containing the CMOS INI File

On the thin client you want to use as a Reference Device, start the thin client.

In the

Login

dialog box, enter the credentials you need to access the cmos.ini file.

After login, you can open the event log (

System Information icon > System

Information dialog box > Event Log tab

) to view a CMOS: extract to

C10_cmos.1.0B_SPC001 event. This means that the CMOS central management file

(containing the CMOS settings from your Reference Device) is now copied to the wnos directory/folder on the file server. As this is a C10 BIOS version

1.0B_SPC001-0407 example, the CMOS central management file name would be

C10_cmos.1.0B_SPC001. These CMOS settings are now ready for distribution to other thin clients.

Step 4: Prepare the File Server containing the CMOS INI File for Distribution

On your file server that contains the cmos.ini file for distribution, write the following line in the cmos.ini file:

Device=cmos Action=restore

Save the file.

CMOS Management

Step 5: Login All Target Devices to the File Server containing the CMOS INI File

On all of the target thin clients that you want to distribute the Reference Device

CMOS settings, start the thin client.

In the

Login

dialog box, enter the credentials you need to access the cmos.ini file.

After login, you can open the event log (

System Information icon > System

Information dialog box > Event Log tab

) to view a CMOS: restore from

C10_cmos.1.0B_SPC001 event. This means that your CMOS central management file (containing the CMOS settings from your Reference Device) has been written to your target thin client.

TIP

: After your target thin clients contain the CMOS settings you want, do not login to the file server containing the cmos.ini file with the restore action (unless you want to redo the restore process). Administrators can remove the cmos.ini file to be prevent unwanted CMOS overwrites.

Appendix B

CMOS Local Management: Extracting CMOS Settings to a USB Key for

Distribution

CMOS local management allows ThinOS administrators to easily manage CMOS settings for small deployments of thin clients using USB Key distribution methods.

This case example uses R10 BIOS version 1.0H_SPC-0T51. However, you can use these instructions for other supported BIOS versions.

Step 1: Prepare a Reference Device containing BIOS version 1.0H_SPC-0T517 or later

On the thin client you want to use as a Reference Device (the reference device will be the golden image you will use to distribute to other thin clients), enter the BIOS

Setup Utility (during boot, press and hold the

Delete

key, enter the password

Fireport

—this is case sensitive—and press

Enter

) and configure the CMOS settings you want (supported CMOS settings include: AutoPower, BootOrder, P-key setting,

BiosPassword—and for R10 BIOS version 1.0B_SPC001-0407 or later the

WakeOnLAN setting).

Save your CMOS settings before exiting the utility.

Step 2: Extract the CMOS Settings to a USB Key

On the thin client you want to use as a Reference Device, attach a formatted USB

Key (to format on Windows 7 computers for example: attach the USB Key, right-click on the USB key, select

Format

, click

Restore device defaults

, select

Quick Format

, click

Start

Use the

Extract CMOS to USB

GUI feature of ThinOS to extract the CMOS settings to the USB Key:

Classic Desktop

: Right-click the desktop and select

Extract CMOS to USB

Wyse Zero Desktop

: On the General tab of the

System Tools

dialog box (

System

Settings icon > System Tools > General tab

), click

Extract CMOS to USB

After successful extraction (you will see a pop-up message: CMOS: extract to

R10_cmos.1.0H_SPC), properly eject and detach the USB Key. The CMOS settings on the USB Key are now ready for distribution to other thin clients.

Step 3: Restore the CMOS Settings to Your Target Devices

On all of the target thin clients that you want to distribute the Reference Device

CMOS settings, start the thin client.

Use the

Restore CMOS from USB

GUI feature of ThinOS to write the CMOS settings from the USB Key to the target thin client:

Classic Desktop

: Right-click the desktop and select

Restore CMOS from USB

Wyse Zero Desktop

: On the General tab of the

System Tools

dialog box (

System

Settings icon > System Tools > General tab

), click

Restore CMOS from USB

After successful restoration (you will see a pop-up message: CMOS: restore from

R10_cmos.1.0H_SPC), properly eject and detach the USB Key. The CMOS settings on the USB Key are now written to your target thin client.

Examples of Common Printing

Configurations

This appendix provides examples on using the

Printer Setup

dialog box and ThinOS INI parameters for common printing situations. Use these general guidelines in addition to the information provided in "Printer."

IMPORTANT

: Host-based printers are not supported.

It includes:

•

"Printing to Local USB or Parallel Printers"

"Using the Printer Setup Dialog Box for Local USB or Parallel Printers"

"Using INI Parameters for Local USB or Parallel Printers"

•

"Printing to Non-Windows Network Printers (LPD)"

"Using the Printer Setup Dialog Box for Non-Windows Network Printers (LPD)"

"Using INI Parameters for Non-Windows Network Printers (LPD)"

•

"Printing to Windows Network Printers (SMB)"

"Using the Printer Setup Dialog Box for Windows Network Printers (SMB)"

"Using INI Parameters for Windows Network Printers (SMB)"

•

"Using Your Thin Client as a Print Server (LPD)"

"Using the Printer Setup Dialog Box for Configuring LPD Services"

"Using INI Parameters for Configuring LPD Services"

•

"Configuring ThinPrint"

Appendix C

Printing to Local USB or Parallel Printers

You can print to locally attached printers through USB or Parallel ports.

IMPORTANT

: Microsoft Remote Desktop Session Host (RDSH), Microsoft Terminal

Using the Printer Setup Dialog Box for Local USB or Parallel Printers

In this example we have an HP LaserJet 4000 attached to a thin client USB port. When connecting USB printers, some printers will fill out the Printer Name and Printer

Identification fields for you.

Use the

Printer Setup

dialog box (

System Settings icon > Printer

) and the following guidelines for the Ports tab when printing to a local USB printer:

•

Select Port

- Select LPT1 or LPT2 port.

•

Printer Name

- Enter name you want displayed in your list of printers (most USB direct-connected printers report/fill in their printer name automatically).

•

Printer Identification

•

Printer Class

- (Optional) You can leave this blank.

•

Enable the printer device

- Must be selected to enable the directly-connected printer (enables the device so it displays on the remote host).

Using INI Parameters for Local USB or Parallel Printers

Configuring local printing using ThinOS INI parameters is simple and an easy way to configure a printer for all clients in your environment assuming every printer is the same.

Your INI parameters will look something like the following:

Printer=LPT1 \

Name="HP LaserJet 4000" \

PrinterID="HP LaserJet 4000 Series PCL" \

Enabled=yes

Examples of Common Printing Configurations

NOTE

: The PrinterID is the exact text of the Windows printer driver name, so if a printer driver is named HP LaserJet 4000 Series PCL in Windows, then it must be exactly the same in the PrinterID field in the INI parameters including capitalizations and spaces.

For example, to find the Windows printer driver name on a Windows 2003 Server:

Click

Start > Printers and Faxes

Right-click in the window and select

Server Properties

3. Click the

Drivers

tab to view the printer driver name.

Appendix C

Printing to Non-Windows Network Printers (LPD)

ThinOS can print to non-Windows network printers as long as the printers can accept

LPR print requests. Most workgroup printers and large network printers have this capability (be sure to check with your vendor that the printer can accept Line Printer

Request print requests).

Once your thin client is configured to print to an LPR capable printer, the client will then redirect this printer through an RDP or ICA connection to your back end infrastructure. In this way the client will connect to your back end infrastructure and this network printer will appear as a client local printer.

Using the Printer Setup Dialog Box for Non-Windows Network Printers (LPD)

In this example we have an HP LaserJet 4200n attached to a thin client through LPR.

Use the

Printer Setup

dialog box (

System Settings icon > Printer

) and the following guidelines for the LPDs tab when printing to a non-Windows network printer:

•

Select LPD

- Select LPD1 or LPD2 port.

•

Printer Name

- Enter name you want displayed in your list of printers.

•

Printer Identification

- Enter the type or model of the printer in the exact text of the Windows printer driver name—including capitalizations and spaces. In our example case, enter HP LaserJet 4200n PCL6.

•

LPD Hosts

- The DNS or WINS name of the server for the network printer. An IP address of the printer on the network can also be entered as we have used in our case example.

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.

•

LPD Queue Name

auto

can be used for HP LaserJet 4200n PCL6 as per documentation found on the HP Web site.

NOTE

: If the printer is attached to another thin client on your network, the LPD

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

•

Printer Class

- (Optional) You can leave this blank.

•

Enable the printer device

- Must be selected to enable the printer (enables the device so it displays on the remote host).

Examples of Common Printing Configurations

Using INI Parameters for Non-Windows Network Printers (LPD)

Configuring network printing using ThinOS INI parameters is simple and an easy way to configure a printer for all clients in your environment assuming every printer is the same.

Your INI parameters will look something like the following:

Printer=LPD1 \

LocalName="HP LaserJet 4200n" \

Host=10.10.10.1 \

Queue=auto \

PrinterID="HP LaserJet 4200 PCL6" \

Enabled=yes

NOTE

: The PrinterID is the exact text of the Windows printer driver name, so if a printer driver is named HP LaserJet 4200n PCL6 in Windows, then it must be exactly the same in the PrinterID field in the INI parameters including capitalizations and spaces.

Appendix C

Printing to Windows Network Printers (SMB)

ThinOS can print to printers that are shared by Microsoft print servers. There are some configuration requirements that need to be considered when configuring SMB printing from ThinOS which may require changes to your thin client setup.

Since connecting to a Microsoft Windows Print Server requires domain credentials, you must provide the credentials to ThinOS either on demand as the printer is used or by administrator setup providing credentials cached from the Wyse login screen (see

"Example 3: Defining an SMB Printer to Use User Credentials Cached by ThinOS

(Advanced)"). This section will discuss both methods.

CAUTION

: The printer name shared by Windows must not contain any spaces or

ThinOS will not be able to use it.

Using the Printer Setup Dialog Box for Windows Network Printers (SMB)

Configuring an SMB printer is this manner forces users to enter their credentials before each printing; this means they will be temporarily pulled out of their remote session to enter their credentials (this can be avoided by using an INI file as discussed in "Using

INI Parameters for Windows Network Printers (SMB)."

Use the

Printer Setup

dialog box (

System Settings icon > Printer

) and the following guidelines for the SMBs tab when printing to a Windows network printer (

CAUTION

The printer name shared by Windows must not contain any spaces or ThinOS will not be able to use it.):

•

Select SMB

- Select the SMB you want from the list.

•

\\Host\Printer

- Click the browse folder icon next to the box to browse your

Microsoft Networks and make the printer selection you want from the network printers available (the DNS name or IP address of the Windows print server on the network).

Examples of Common Printing Configurations

After entering required domain credentials, the

Printer Setup

dialog box will display.

Appendix C

•

Printer Name

- Enter name you want displayed in your list of printers.

•

Printer Identification

- Enter the type or model of the printer in the exact text of the Windows printer driver name—including capitalizations and spaces. In our example case, enter HP LaserJet 4100 Series PCL.

•

Printer Class

- (Optional) You can leave this blank.

•

Enable the printer device

- Must be selected to enable the printer (enables the device so it displays on the remote host).

Click

Test Print

and you will be prompted to enter your Windows credentials, these credentials will be used to access the printer share. This is also the same dialog box that will display for a user when they attempt to print to this printer.

Examples of Common Printing Configurations

Using INI Parameters for Windows Network Printers (SMB)

Configuring SMB printing using ThinOS INI parameters is simple and an easy way to configure printers shared by a Windows server for all clients in your environment. The primary advantage of configuring SMB printing using ThinOS INI parameters is that you can pre-define the domain account to use to authenticate the printer. The following examples discuss how the credentials can be supplied.

Example 1: Defining an SMB Printer with Generic User Credentials in

Plain Text

Printer=SMB1 \

LocalName="Demo SMB Printer" \

Host=\\dp-dc-ftp \

Name="TechSupportPrinter" \

PrinterID="HP LaserJet 4100 Series PCL" \

Enabled=yes \

Username=Username1 \

Password=Password \

Domain=contoso

Example 2: Defining an SMB Printer with Generic User Credentials that are Encrypted

Printer=SMB1 \

LocalName="Demo SMB Printer"\

Host=\\dp-dc-ftp \

Name="TechSupportPrinter" \

PrinterID="HP LaserJet 4100 Series PCL"\

Enabled=yes \

Username-enc=PACGOGDBPKDOPGDGKC \

Password-enc=PFDBOHDBODCJPODP \

Domain=contoso

NOTE

: In order to create the encrypted passwords for use in an INI file you will want to use a program such as ConfGen. This application has built in support for creating the encrypted strings. ConfGen can be downloaded from http://technicalhelp.de.

CAUTION

: This is a non-supported tool that is linked solely for the purpose of this example.

Appendix C

Example 3: Defining an SMB Printer to Use User Credentials Cached by ThinOS (Advanced)

NOTE

: This method requires that the user log in to ThinOS so that the credentials can be cached for later use. The example INI section provided below provides the minimum requirements you need.

Signon=NTLM

Connect=RDP \

Host=1.2.3.4 \

Username=$UN \

Password=$PW \

Domain=$DN \

AutoConnect=1

Printer=SMB1 \

LocalName="Demo SMB Printer"\

Host=\\dp-dc-ftp \

Name="TechSupportPrinter" \

PrinterID="HP LaserJet 4100 Series PCL"\

Enabled=yes \

Username=$UN \

Password=$PW \

Domain=$DN

NOTE

: The PrinterID is the exact text of the Windows printer driver name, so if a printer driver is named HP LaserJet 4100 Series PCL in Windows, then it must be exactly the same in the PrinterID field in the INI parameters including capitalizations and spaces.

Examples of Common Printing Configurations

Using Your Thin Client as a Print Server (LPD)

A ThinOS thin client can be configured as a basic network print server, to share local printers with other thin clients.

Using the Printer Setup Dialog Box for Configuring LPD Services

From the Classic Desktop mode only, a thin client can be configured to provide LPD

(Line Printer Daemon) services (making the thin client a printer server on the network).

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

Open the

Network Setup

dialog box (

Desktop Menu > System Setup > Network

Setup

) and enter a static IP address for the thin client.

Open the

Printer Setup

dialog box (

Desktop Menu > System Setup > Printer

) and select any of the listed ports.

Select LPT.

Name the printer in the Printer Name box.

Enter the

Printer Identification

type or model of the printer in the exact text of the

Windows printer driver name—including capitalizations and spaces. In our example case, enter HP LaserJet 4000 Series PCL.

You can leave

Printer Class

blank.

Select

Enable the Printer Device

Select

Enable LPD service for the printer

Set up the application server (see “Setting Up Windows 2003/2008 Servers” ).

Setting Up Windows 2003/2008 Servers

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.

Add the thin client as the LPD printer by completing the following:

Navigate to

Control Panel > Printers > Add Printers > Local Printer > Create a new port

and select

LPR PORT

TIP

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

Type the thin client IP address or DNS name in the

Name or address of host providing LPD

box.

Appendix C

Type the printer name (assigned in “Using the Printer Setup Dialog Box for

Configuring LPD Services” ) in the

Name of printer on that machine

box.

Click

, and then click

NEXT

After you have selected the printer, you can perform your normal printer setup for the application server. For example, select the manufacturer printer type and printer name.

Using INI Parameters for Configuring LPD Services

Configuring LPD printing using ThinOS INI parameters is simple and an easy way to configure a ThinOS thin client to be a basic network print server, to share local printers with other thin clients.

Your INI parameters will look something like the following:

Printer=LPT1 \

Name="HP LaserJet 4000" \

PrinterID="HP LaserJet 4000 Series PCL" \

Enabled=yes \

EnableLPD=yes

NOTE

Examples of Common Printing Configurations

Configuring ThinPrint

No ThinPrint-specific configuration is available on the thin clients. Thus to be able to use ThinPrint, users must first set up their printers according to the user documentation, and then configure ThinPrint on the thin client using the

Printer

Setup

dialog box.

Use the following guidelines:

•

Use the

Printer Identification

field to enter a printer class (you can change the printer name as needed).

•

Printer IDs are assigned (depending on the physical port) as follows:

•

COM1 = 1

•

COM2 = 2

•

LPT1 = 3 (USB printers are detected automatically on LPT1)

•

LPT2 = 4

•

LPD0 = 5 (The LPD Queue name is transmitted as the printer name; the Printer

Identification as class)

•

LPD1 = 6 (The LPD Queue name is transmitted as the printer name; the Printer

Identification as class)

•

LPD2 = 7 (The LPD Queue name is transmitted as the printer name; the Printer

Identification as class)

•

LPD3 = 8 (The LPD Queue name is transmitted as the printer name; the Printer

Identification as class)

•

SMB1 = 9 (In the form \\host\printershare)

•

SMB2 = 10

•

SMB3 = 11

•

SMB4 = 12

To install the relevant ThinPrint product on the server use the following guidelines:

•

Printer Object(s) Created Manually by the Administrator

- After you install .print

Engine, create a printer object on the server to use the native driver and ThinPort as a printer port. You can use any protocol (TCP, RDP, or ICA) because ThinOS has

.print clients for all of the protocols. The printer object needs to observe ThinPrint naming conventions (for example,

HPLJ5#_:2

, in which case print jobs will be sent to the local printer that has ID number .

) by referring to .print client port ID. If no ID number is present, the .print client sends the print job to the printer set as current.

•

Printer Object(s) Created Automatically by ThinPrint AutoConnect

- When using

ThinPrint AutoConnect, the thin client identifies with the thin client ID number 84

(and thus is recognized as a thin client without a local spooler). You can also set up a template on the server that uses a native driver (for example,

HPLJ5

) and ThinPort, and then name this template as you want in the form _#AnyName. You can then make sure that the rules (on ThinPrint Autoconnect [1]) have been set to assign the desired local printers to use this server template. The assigned printer will then be shown in the user session using the HPLJ5 driver and ThinPort; it will be named automatically according to ThinPrint naming convention with the printer name from the client side included. Alternatively, you can also define a template name according to the client printer name (replace .AnyName. with printer name 4. and 5. above [for example,

_#HP Laserjet 5

]) so that the local printer object .HP Laserjet 5. will be mapped to this template without any rules defined on the ThinPrint

Autoconnect.

Appendix C

This page intentionally blank.

Tables

Shutdown dialog box options 8

Zero Desktop Shortcut Keys 9

Toolbar icons 10

Connection Options 11

Classic Desktop Shortcut Keys 12

Supported Keyboard Languages 25

DHCP Options 66

Administrators Guide

Dell

Wyse ThinOS

Issue: 011614

Written and published by:

Dell Inc., January 2014

Created using FrameMaker

® and Acrobat

Hello! I am an AI chatbot specifically trained to assist you with the Dell Wyse ThinOS D10DP Administrator's Guide. I have thoroughly reviewed the document and can help you locate the exact information you need or explain the content in clear and simple terms. Whether you’re looking for guidance on specific features, troubleshooting steps, or general usage, feel free to ask your questions. The more details you provide about your concerns or needs, the more accurately and effectively I can assist you!

Assistant typing

Assistant is out of keyboard. Please, try again later.

Administrators Guide

Dell

Wyse ThinOS

Issue: 011614

PN: 883682-08 Rev. AF

Contents

1 Introduction

2 Getting Started: Quickly Learning the Basics

3 Configuring Thin Client Settings Locally

4 Configuring Connection Settings Locally

5 Performing Diagnostics

A Central Configuration: Automating Updates and Configurations

B CMOS Management

C Examples of Common Printing Configurations

Tables

Introduction

About this Guide

Finding the Information You Need in this Guide

Dell Technical Support

Related Documentation and Services

Dell Online Community

Getting Started: Quickly Learning the Basics

Connecting to a Remote Server

Manual Connection Procedures

Using Your Desktop

Configuring Thin Client Settings and Connection Settings

Connecting to a Printer

Connecting to a Monitor

Locking the Thin Client

Signing Off and Shutting Down

Additional Getting Started Details

Zero Desktop Features

Zero Interactive Desktop Guidelines

Zero Toolbar

List of Connections

Classic Desktop Features

Classic Interactive Desktop Guidelines

Shortcut Menu

Desktop Menu

Connect Manager

Login Dialog Box Features

Accessing System Information

Configuring Thin Client Settings

Locally

Local Settings Menu

System Preferences

Display

Peripherals

Printer

Reset Features

Resetting to Factory Defaults Using G-Key Reset

Resetting to Factory Defaults Using Shutdown Reset

Resetting Display Settings Using V-Key Reset

Accessing Thin Client BIOS Settings

Configuring Connection Settings

Locally

Global Connection Settings

Connectivity Menu

Network Setup

Enabling a Disabled Network Setup Dialog Box

Remote Connections

Central Configuration

Advanced Details on Configuring ICA and RDP Connections

Configuring ICA Connections

Configuring RDP Connections

Performing Diagnostics

System Tools

Network Tools

Using Ping

Using Trace Route

Central Configuration: Automating

Updates and Configurations

How to Set Up Automatic Updates and Configurations

Step 1: Prepare the Root Directory and Folder Structure on the Server

Step 2: Direct the Thin Client to the Server Using DHCP Options

Step 3: Reboot or Start the Thin Client

CMOS Management

CMOS Central Management: Extracting CMOS Settings to the File Server for Distribution

Step 1: Prepare a Reference Device containing BIOS version 1.0B_SPC001-0407 or later

Step 2: Prepare a File Server containing a CMOS INI File