VMware VDM and WTOS Best

Practices Guide
A Technote by
Jason Propsner
Wyse Sales Engineer

April 2008
Contents

Optional setup #1 – Manually configure WTOS to connect to your VDM server............ 3

Optional setup #2 – Configure DHCP to connect WTOS to your VDM server................ 5
Optional setup #3 – Configure DHCP to connect WTOS to VDM using an FTP server
(recommended)………………………………………………………………………….. 7
Wnos.ini commands and best practices……………………...………………………….. 9
Configure the XP Pro VM to use 24bit color…………………………………………... 10
Reference links………………………………………………………………………….. 10

This guide will help with setting up Wyse WTOS in a VMware VDM environment.
It is assumed that you have completed the install and configuration of ESX, VDM
with desktop VMs built, and they are entitled to your AD users and/or groups.

Prerequisites:
VDM 2.1
WTOS 6.2

VMware VDM and WTOS Best Practices Guide Page 2 of 10

Optional setup #1 – Manually configure WTOS to connect to your VDM
server.
1. Once you have the WTOS thin client booted up, access the network setting under
the “Desktop” button – “System Setup” – “Network”.

2. Select the “Servers” tab and type in the URL of your VDM server.

In the above example we are connecting with SSL. If you decide to disable SSL
inside the VDM console you will use HTTP:// in the VDI Broker field.

VMware VDM and WTOS Best Practices Guide Page 3 of 10

 3. If the address was correctly entered the user will be presented with a login prompt
with your AD domain automatically populated.

4. Enter the AD login credentials and the user’s entitled desktop will start
automatically.

5. To use TCX, you need to enter your evaluation key manually into the device. If
you need to enter more than one key, for example to use TCX MMR and TCX
USB, separate the keys with a comma.

Note: Use the key combination CTRL+ALT+Downarrow to minimize the VM and

access the WTOS desktop.

VMware VDM and WTOS Best Practices Guide Page 4 of 10

 Optional setup #2 – Configure DHCP to connect WTOS to your VDM
server.
Configure your network’s DHCP server using a String DHCP option tag 188. WTOS
will read the DHCP option tag at boot up, thus connecting to the VDM server “out of
the box”. Below we show how to create the tag on a MS DHCP server.
1. In the DHCP server console highlight the DHCP server, right click, and select
“Set Predefined Options”

2. Select the add button.

3. Enter the Name, Description, Change Data Type to “String”, and enter the code as
188. Click OK and close the Predefined options and Values window.

VMware VDM and WTOS Best Practices Guide Page 5 of 10

 4. Now expand your scope and select the “Scope Options”. Then right click to
configure the options.

5. Scroll to the bottom of the list and check the box next to 188 and enter the server
address for your VDM server using either http or https depending on your
encryption choice.

6. Now you boot up your thin client and it should present you with a login box to
your VDM server without any local configuration on the device.

VMware VDM and WTOS Best Practices Guide Page 6 of 10

Optional setup #3 – Configure DHCP to connect WTOS to FTP server
(recommended).
Configure your network’s DHCP server using a String DHCP option tag 161. WTOS
will read the DHCP option tag at boot up.

1. Use the steps outlined in Option #2 except create the tag as a string value for
option 161. The value of the option will point to a FTP server on your network.

2. Setup FTP Server by creating a directory <FTPROOT>\Wyse\wnos (i.e.

C:\inetpub\ftproot\Wyse\wnos). In this folder you will place the firmware files
and the configuration file, called WNOS.ini, used to setup the units.

3. In your wnos.ini you will add a few lines of text that will direct the thin client
to your VDM server, set the resolution, feed the TCX license keys, and many,
many, more possible commands based on your desired setup.

VMware VDM and WTOS Best Practices Guide Page 7 of 10

 4. Use the following example to build your own ini. Please reference the WTOS
admin guide for a detailed explanation about each command.
This ini will attach to the VDibroker, allow usb thumb drives, TCX usb, TCX
Multimedia support, set the display resolution, give a background image, a
login box logo, and the time zone with DST.

5. The desktop will look like this after the unit reads the ini file.

6. The background and login logo are stored in a folder called Bitmap under
your <FTProot>\Wyse\Wnos folder. It can be a bitmap or jpg. The command
used in this example is Desktop=1280-1024v2.jpg Layout=Center and
FormURL=Vmware.JPG.

VMware VDM and WTOS Best Practices Guide Page 8 of 10

 7. The login box has been configured with an OK and Cancel button from the
command SignOn=yes EnableOK=Yes .

8. The time server information is needed on order for the demo licenses for TCX
to function. You will know that the time is pulled correctly when the thin
client clock shows the correct time, instead of uptime.

Use some of the following ini commands to future configure and secure the
thin client.

a. Domainlist= Use this command to specify the domain and override the
domain displayed by VDM.
b. AdminMode=yes Username= Password= This command will give you,
as an administrator, control over a secure desktop. You will provide
the login id and password in the ini. You can encrypt this if desired.
c. Privilege=None Lockdown=yes Use this command to protect the thin
client desktop from being changed by users.
d. KeySequence=yes Ctrl+Alt+Up=no Ctrl+Alt+Down=no
Ctrl+Alt+Left=no Ctrl+Alt+Right=no This will prevent the users
from being able to minimize the VM session to gain access to the thin
client desktop.
e. Dualhead=yes Mainscreen=2 Orientation=horizontal
Taskbar=wholescreen This command is necessary to use the dual
monitor feature of the V10L. This must be set on the thin client and
the VDM session will launch the desktop in full screen, giving your
users a true spanned dual display.

VMware VDM and WTOS Best Practices Guide Page 9 of 10

 Configure the XP Pro VM to use 24bit color
By default, using Windows XP as a virtual desktop, the desktop color depth in a remote
session will be 15bit. There are two ways to increase the color depth for a more true color
experience.

1. You can set the color depth to 24bit, by editing the following registry key in the XP
VM:

Open up the Registry Editor (Start -> Run -> regedit) and navigate to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal

Server\WinStations\RDP-Tcp

Change “color depth” to 4.

Reboot Windows XP to have the change take effect.

OR

2. Using MS GPO:

http://support.microsoft.com/default.aspx/kb/278502

Reference the following for more information:

http://www.vmware.com/files/pdf/VDM_Wyse_tech_note.pdf

www.wyse.com>Support>Knowledgebase>Reference Guides

http://www.youtube.com/user/WyseTechnology

http://www.wyse.com/products/software/os/index.asp

http://www.wyse.com/products/software/tcx/index.asp

VMware VDM and WTOS Best Practices Guide Page 10 of 10