Wyse V10LE, Руководство администратора, Страница: 59 / 92

A
Central Configuration: Automating
Updates and Configurations
This appendix contains information on the network architecture and enterprise server
environment needed to provide network and session services for Wyse thin clients running
Wyse ThinOS. It also includes information to help you address important considerations
when configuring the services to be provided by the server environment. Use this chapter
in conjunction with the
Getting Started Guide: Wyse ThinOS
TM
and the Reference Guide:
Wyse ThinOS
TM
INI Files to set up and configure your Wyse ThinOS server environment.
It includes:
• "Understanding How to Configure Your Network Services"
• "Configuring Network Services"
• "Configuring Session Services"
Understanding How to Configure Your Network Services
Network services used by the thin client can include DHCP, FTP file services, Virtual
Desktop file services, DNS, and so on. How you configure your network services depends
on what you have available in your Wyse ThinOS environment and how you want to
design and manage it.
The following topics in this section provide important overview information on the
supported service situations you may have when configuring the network services for your
Wyse ThinOS environment (after becoming familiar with your environment requirements,
refer to "Configuring Network Services" for detailed instructions):
• "DHCP and FTP Servers Available"
• "FTP Server Available (DHCP Server Unavailable)"
• "DHCP and Virtual Desktop Servers Available"
• "Virtual Desktop Server Available (DHCP Server Unavailable)"
• "FTP and Virtual Desktop Servers Unavailable (Stand-alone User or PNAgent/
PNLite-only User)"
Caution
If a thin client accesses the enterprise intranet through PPPoE or PPTP VPN
and the thin client is locked-down, a non-privileged or low-privileged user
attempting to reboot to Stand-alone user mode will disable the
Network
Setup dialog box and system reset capabilities. The user will not be able to
re-access the enterprise intranet through this path. If this happens, the thin
client must be moved to a location where it can access the enterprise intranet
directly (Ethernet cable) and reboot so that an administrator can make any
required changes to the thin client operating configurations through the user
profiles (for example, set the user profile to unlock the thin client).