14 Chapter 2
Configuring Virtual Desktop Infrastructure Servers
When the thin client boots, it accesses the INI files from a Virtual Desktop Infrastructure
(VDI) server. VDI servers are available through DHCP vendor option 188 (see
"Configuring DHCP").
The thin client communicates with a 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 file (if a broker
connection cannot be made, the thin client will attempt to connect to an FTP or PNLite
server). 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 sign-on is successful, the
Virtual Desktop Broker server will send back the {username}.ini file (if the sign-on 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. The
shutdown command will be sent when a user turns off the thin client power.
Configuring XenDesktop Support
XenDesktop is supported in Wyse ThinOS versions 6.2 and later without the need to use a
Web browser. To connect to XenDesktop, do not use the VDI Broker parameter. Instead,
use the same parameter and configuration that is used when connecting to a PNAgent/
Lite server.
Configuring DHCP
Before you use the information in this section to configure your DHCP server, be sure you
understand and use the following guidelines:
General Guidelines - 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
using the thin client Network Setup dialog box as described in "FTP Server Available
(DHCP Server Unavailable)" and "Virtual Desktop Server Available (DHCP Server
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
replace the information contained in the UI. However, if the thin client does not receive
information from the DHCP server about a particular function, the information manually
entered in the UI will remain and will be used.
LPD Print Server Guidelines - 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 always have the same IP address 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
Terms of Use | Privacy Policy | DMCA Policy
2006-2020 Rsmanuals.com