
58
Appendix A
FTP and Virtual Desktop Servers Unavailable (Stand-alone User or PNAgent/
PNLite-only User)
In an environment where FTP and Virtual Desktop Broker servers are not available (for
example, Stand-alone User or PNAgent/PNLite-only User situations), configuration files
are not available and network information must be entered locally at the thin client as
follows:
•
Stand-alone User
- This user does not access user profiles or PNAgent/
PNLite-published applications.
New
and
Settings
command buttons appear in the
Connect Manager for use (if the Connect Manager does not open automatically, open it
from Desktop menu). These command buttons are also available to low-privileged and
non-privileged users. Locally entered connection definitions (using these command
buttons) are preserved for the next thin client use after the thin client is powered off and
restated (automatic software updates, however, are not available when the thin client is
powered on again).
•
PNAgent/PNLite-only User
- This user does not access user profiles, but applications
(published by Citrix PNAgent/PNLite services) are available (the IP address of a
PNAgent/PNLite server and Domain are entered into the
Network Setup
dialog box or
available through DHCP options 181 and 182). A log-on dialog box (similar to the
standard log-on dialog box) opens for logging on to the PNAgent/PNLite server.
Applications published by PNAgent/PNLite are listed in the Connect Manager
(Published applications that add a shortcut to the client desktop will have an icon on
the desktop which you can double-click to open). Locally entered connection
definitions are not preserved for the next thin client use after the thin client is powered
off and restated.
Configuring Network Services
Before
you use the information in this section to configure your network services, be sure
you have read "Understanding How to Configure Your Network Services" and remember
the following important issues:
•
Restrictions to Network Services can Exist
- 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.
•
Know How Your Environment Works
- Either the FTP server or the Virtual Desktop
server (depending on your environment) holds the INI files, while the FTP server (if
available) holds the current and upgrade versions of the thin client software.
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 INI files on the file servers. Under
direction of the INI files 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.
•
Functionality Depends on You
- The Wyse ThinOS INI files contain the parameters
and associated values necessary for the various functionality you want. The INI files
(wnos.ini file and {username}.ini file) are constructed and maintained by you and are
stored on the file server for use with thin clients running Wyse ThinOS.