Specifications

10 Chapter 2
Configuring Network Services
Thin client network services reside on the enterprise intranet. When setting up thin client
network services, remember that if thin clients are to access the enterprise intranet
through Dial-up, PPPoE, or PPTP VPN, restrictions imposed by these access paths must
be considered.
Note
Be sure you have read "About Configuring Network Services" before you
begin configuring network services.
The FTP server or the Virtual Desktop server holds the user configuration profile files,
while the FTP server holds the current and upgrade versions of the thin client software.
Note
For more information on the installation of software update images, refer to
"Updating Software." For more information on user configuration files, refer
to "Understanding User Accounts and User Profile Ini Files."
The thin client software is acquired from either local flash memory or the FTP server.
During the boot process, the local image is transferred to RAM and executed far enough
for the thin client to check the image and the profiles on the file servers. Under direction of
the profile parameters and the version of the remote image, the image in RAM can be
replaced with the remote image; and separately, the remote image can update the local
flash-memory.
Note
New software images can be obtained from Wyse as they become available.
User configuration profile (.ini) files are created and maintained by you, the network
administrator, and are stored on the file server. There is one Global .ini file for all users of
a given file server and, if configured, unique User .ini file for each user. The thin client
accesses the Global .ini files upon thin client initialization and accesses any individual
User .ini file when the user logs on (if user log-on is required, the User .ini file must exist
before that user can log on). The .ini files contain connection definitions and thin client
settings. These text-based files must be created and maintained by using an ASCII text
editor. If the .ini files are omitted or they cannot be accessed because a file server is not
used, the thin client user must enter connection definitions locally (or for FTP servers, use
what is published by PNAgent/PNLite servers residing on the network).
Note
You can also define connections in the ini files which are to be stored in local
NV-RAM and used in cases where the file server fails.
To configure network services, use the information in the following sections:
• "About Configuring FTP Servers"
• "About Configuring Virtual Desktop Infrastructure Servers"
• "Configuring DHCP"
• "Configuring DNS"
• "Configuring WINS"
• "Configuring Wyse Device Manager Servers"