Specifications

Establishing a Server Environment 13
About Configuring Virtual Desktop Infrastructure Servers
When the thin client boots, it accesses the Global and User configuration profile files from
a Virtual Desktop Infrastructure server. Virtual Desktop Infrastructure servers are available
through DHCP vendor option 188 (see "Configuring DHCP").
The thin client communicates with Virtual Desktop Broker server by the sysinit, signon,
signoff, and shutdown commands. When the thin client boots and successfully connects in
a Virtual Desktop environment, it sends the sysinit command to the Virtual Desktop
Broker, which then sends back the wnos.ini (Global profile) file (if a Broker connection
cannot be made, the thin client will attempt to connect to FTP or PNLite servers). After the
thin client successfully receives the wnos.ini from the Virtual Desktop Broker, a sign-on
window displays, prompting the user for username and password credentials. The thin
client then sends the signon command to the Virtual Desktop Broker with the username
and password as its parameter. If the signon is successful, the Virtual Desktop Broker
server will send back the user.ini (User profile) file (if the signon is unsuccessful, the user
is prompted again for username and password credentials). The signoff command will be
sent when a user disconnects from the connection; and the shutdown command will be
sent when a user turns off the thin client power.
For Virtual Desktop Broker features and information (including configuration and server
support), refer to: http://www.leostream.com
.
Configuring DHCP
The DHCP service provides all thin clients on the network with their IP addresses and
related network information when the thin clients boot. DHCP also supplies the IP address
and directory path to the thin client software images and user profiles located on the file
servers.
Use of DHCP is recommended. However, if a DHCP server is not available, fixed IP
addresses can be assigned (this does, however, reduce the stateless functionality of the
thin clients) and the fixed IP addresses must be entered locally for each device (as
described in "FTP Server Available (DHCP Server Unavailable)" and "Virtual Desktop
Server Available (DHCP Server Unavailable)").
Be aware of the following:
• If a particular thin client is to function as an LPD print server, it can be assigned a fixed
IP address. However, you can also guarantee that an LPD server will get the same IP
address every time by making a reservation for that thin client in the DHCP server. In
that way, you can preserve the stateless nature of the thin client and still guarantee a
fixed address for the server. In fact, you can assign a symbolic name to the reservation
address so that other thin clients can reference the LPD server by name rather than by
static IP address (the symbolic name must be registered with a DNS server before
other thin clients will be able to locate this LPD server). The thin client does not
dynamically register its name and the DNS registration must be manual.
• The thin client uses port 80 as the default to access a Wyse Device Manager (formerly
known as Rapport) server. If a port other than 80 is used to access a Wyse Device
Manager server, use option 187 in the list of DHCP options in Table 1 (option for Wyse
Device Manager server is option 186 in the list of DHCP options). Wyse Device
Manager options are the only options used by the thin client that are not in text form.
• The thin client uses port 80 as the default to access a PNAgent/PNLite server. If a port
other than 80 is used to access a PNAgent/PNLite server, the port number must be
specified explicitly with the server location in the form IP:port or name:port (option for
PNAgent/PNLite server is option 181 in the list of DHCP options in Table 1).
• Many DHCP options correspond to places in the network configuration UI where the
thin client user can enter information manually. Be aware that wherever there is
information in the UI and the thin client receives information about the same function
from one or more DHCP options, the information received from the DHCP server will