Posts Tagged ‘WTOS’
How to configure the Wyse Thin OS to connect to Provision Networks Connection Brokers May 28th, 2008 by Patrick Rouse
Configuration of the Wyse Thin OS (WTOS) is completely controlled via DHCP and ini files on the connection broker, so these devices can literally be taken out of the box, plugged in and they will automatically boot, download new firmware (if available), contact a connection broker, then launch a desktop.
So what needs to be configured in DHCP:

DHCP Option 188 is used to list the addresses of each connection broker, and the XML Communication Port. DHCP Option 161 lists the servers that hold updated WTOS Firmware. Since Provision Networks Connection Brokers can do both of these, once may configure either or both options. In the screenshot above, only option 188 is configured.
On the connection broker(s) browse to %ProgramFiles%\Provision Networks\Wyse. Create a sub-directory named “WNOS” (case sensitive). In the WNOS directory, create two sub-directories, “ini” and “bitmap“
Use notepad to create the two ini files listed in the WNOS directory.
wnos.ini contents:
signon=1
autoload=1
autosignoff=yes
privilege=High
Domainlist=YourDomainName
————————————————–
rdp.ini contents:
Fullscreen=yes
Colors=high
Encryption=128
Experience=15
Lowband=no
Autoconnect=1
————————————————–
To update the WTOS Firmware, copy the new firmware (RCA_wnos) to the WNOS directory, and set “autoload=1″ on the wnos.ini file.
At this point, the basic configuration is completed to connect a WTOS Thin Client to a Provision Networks Connection Broker. If one has multiple connection brokers, list them in the DHCP options and copy the contents of the Wyse Directory to each additional connection broker. There are many options available in the ini files, so detailed instructions are in the documents listed below:
- Comments: 1 Comment
- Categories: best practices, client configuration, tips
- Tags: WTOS, Wyse Thin OS
-
Comments RSS
-
Trackback
