Thursday, November 8, 2012

Basic Setup for Wyse ThinOS + Windows Terminal Server

[Originally posted February 23, 2010]

Consider this a quick start guide for a particular scenario: you want multiple Wyse ThinOS terminals to automatically log into a Windows Terminal Server with terminal-specific user accounts.


In this example, the user accounts "Front Desk" and "Utilities Console" are already configured on the Terminal Server (or its domain). Here's what needs to happen when one of the thin clients is powered on:
  1. Client looks for DHCP services and configures basic network parameters. (Client IP can be dynamic.)
  2. Client checks DHCP option 161 and finds the static IP address of the FTP server.
  3. Client logs into the FTP server anonymously and runs /wyse/wnos/wnos.ini which contains the settings for all Wyse ThinOS clients.
  4. wnos.ini includes a line which causes the client to look for /wyse/wnos/inc/[MAC].ini where "MAC" is its own MAC address. This contains client specific settings, e.g. "Front Desk" credentials. Either wnos.ini or [MAC].ini will instruct the client to connect to the Terminal Server.
Note: The Terminal Server, DHCP server, and FTP server may all be the same host or three separate hosts. Or a 2 / 1 split. It just doesn't matter.

Terminal Server Setup

Make sure the user profiles are set up correctly on the Terminal Server by using any RDP client.

DHCP Setup

Check the scope options on the DHCP server. For Windows 2003 Server, this will be under [Server]->Scope->Scope Options->Configure Options->General tab->Available options. Option 161 is not defined by default, so it will probably not be on this list.

To define a new DHCP option in Windows 2003 Server, right click on [Server] and select Set Predefined Options. Click Add.

Name: Wyse FTP Server
Data Type: String
Code: 161
Description: FTP Server for Wyse ThinOS Clients

(Only the Code value is vital.)

DHCP services may need a restart. Go back to the scope options, enable the newly defined option, and enter the IP address of the FTP server.

FTP Setup

Use any familiar FTP server. The following just needs to work:

> ftp [FTP server]
> Name: anonymous
> Password: anonymous
> cd wyse
> cd wnos
> ascii
> get wnos.ini
> cd ini
> get [MAC].ini

Both wnos.ini and [MAC].ini are going to be plaintext configs. Feel free to make test versions with any content to make sure the FTP is working right.

Example Network Values

User: Front Desk
Pass: easyPass8
MAC: 0123456789AB

User: Utilities Console
Pass: easyPass4
MAC: 1023456789CC

Domain: toasterco.local

FTP IP: 192.168.1.40 (not used in the configs below, to avoid paradox)

Terminal Server IP: 192.168.1.50
Terminal Server Name: Legion-srv

Example wnos.ini

AutoLoad=0
AutoPower=yes
SignOn=no

include=$mac.ini

connect=rdp \
icon=default \
description= "Legion-srv" \
host=192.168.1.50 \
Fullscreen=yes \
Reconnect=yes \
Autoconnect=yes

Example 0123456789AB.ini

connect=rdp \
description= "Legion-srv" \
host=192.168.1.50 \
icon=default \
username="Front Desk" \
password=easyPass8 \
domainname=toasterco.local \
Fullscreen=yes \
Reconnect=yes \
Autoconnect=yes

Exit=all

Example 1023456789CC.ini

connect=rdp \
description= "Legion-srv" \
host=192.168.1.50 \
icon=default \
username="Utilities Console" \
password=easyPass4 \
domainname=toasterco.local \
Fullscreen=yes \
Reconnect=yes \
Autoconnect=yes

Exit=all

Final Comments

The line "include=$mac.ini" in wnos.ini will cause execution to jump to the individual config file if the MAC match is successful. The line "Exit=all" at the end of an individual config will stop execution. Otherwise, it would return to the general config file and individual settings would be overwritten.

Wyse Support has plenty of reference documentation covering these config file options and many more. Don't even have to log into the support site to access this material. Yay for that.

2 comments:

  1. Thanks very much for this!

    ReplyDelete
  2. There's a "cd ini" in here that should be cd INC. Set me back 2 hours!!!

    ReplyDelete