Dell Latitude 5280 Microsoft Windows 10 IoT Enterprise for Wyse Thin Clients A - Page 44
Network architecture and server environment, Understanding how to con your network services
View all Dell Latitude 5280 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 44 highlights
7 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 configure your network services • Using Dynamic Host Configuration Protocol (DHCP) • DHCP Options • Using Domain Name System (DNS) • About Citrix Studio • About VMware Horizon View Manager Services Understanding how to configure your network services Network services provided to thin clients can include DHCP, FTP file services, and DNS. You can configure, design, and manage your network services depending on the availability in your environment. You can configure your network services using: • Dynamic Host Configuration Protocol (DHCP) • Domain Name System (DNS) Using Dynamic Host Configuration Protocol A thin client is initially configured to obtain its IP address and network configurations from a Dynamic Host Configuration 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 configurations through the DHCP upgrade process. DHCP is recommended to configure and upgrade thin clients as it saves time and efforts needed to complete these processes locally on multiple thin clients. If a DHCP server is not available, fixed 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 1 3 Description Subnet Mask Router Notes Required Optional but recommended. It is not required unless the thin client must interact with servers on a different subnet. 44 Network architecture and server environment