Administrator Guide

Network architecture and server environment
This section contains information about the network architecture and enterprise server environment needed to provide network and
session services for your thin client. It includes:
• Understanding how to congure your network services
• Using Dynamic Host Conguration Protocol (DHCP)
• DHCP Options
• Using Domain Name System (DNS)
• About Citrix Studio
• About VMware Horizon View Manager Services
Understanding how to congure your network
services
Network services provided to thin clients can include DHCP, FTP le services, and DNS. You can congure, design, and manage your
network services depending on the availability in your environment.
You can congure your network services using:
• Dynamic Host Conguration Protocol (DHCP)
• Domain Name System (DNS)
Using Dynamic Host Conguration Protocol
A thin client is initially congured to obtain its IP address and network congurations from a Dynamic Host Conguration Protocol (DHCP)
server. A DHCP server provides the IP address or DNS name of the FTP server and the FTP root-path location of software in
Microsoft.msi form to access the IP address and network congurations through the DHCP upgrade process.
DHCP is recommended to congure and upgrade thin clients as it saves time and eorts needed to complete these processes locally on
multiple thin clients. If a DHCP server is not available, xed IP addresses can be assigned and it must be entered locally for each device.
A DHCP server can also provide the IP address of the WMS server.
DHCP options
The DHCP options listed in the following table are accepted by the thin clients.
Table 12. DHCP options
Option Description Notes
1 Subnet Mask Required
3 Router Optional but recommended. It is not
required unless the thin client must interact
with servers on a dierent subnet.
7
44 Network architecture and server environment