Specifications

18 Chapter 3
How to Store and Use Your Configuration Files
After creating your configuration file, you must place the file in the location you need, and
then complete the procedures required to apply the configurations to your thin clients.
You can have your thin clients apply your configuration files:
• Automatically (see "How to Set Up Automatic Configuration Updates")
• Manually (see "How to Set Up Manual Configuration Updates")
Tip
For more information on implementing Wyse Configuration Manager in
various environments, see
"Reference Information: Typical Use Case
Scenarios."
How to Set Up Automatic Configuration Updates
For your thin clients to access configuration files and update themselves from a server:
Step 1: Place Your Configuration Files on the Server
On your server, you must set up the <repository path>\Wyse\WES7 folder in which you will
place your WES7Config.xml file. Depending on the protocol you will use, do one of the
following (be sure to name your file WES7Config.xml):
• FTP: For FTP, the repository path is usually ftproot (for example,
C:\inetpub\ftproot\Wyse\WES7\WES7Config.xml).
• HTTP or HTTPS: For HTTP or HTTPS, the repository path is the path specified by the
virtual directory in IIS; usually wwwroot (for example,
C:\inetpub\wwwroot\Wyse\WES7\WES7Config.xml).
Step 2: Direct Your Thin Clients to the Server Using DHCP Options
Your thin clients check (at each boot up) to see whether or not any updates are available
on your predefined server (DCHP Option #195 specifies the server, DCHP Option #196
specifies the root path to the server). See also "Troubleshooting Devices that Cannot
Locate Configuration Files."
Server and root directory information is obtained from the following DHCP Options:
• 6 - (Optional) Domain Name Server (DNS).
• 183 - The protocol (ftp/http/https) used for downloading the configuration file (and any
custom items in the folder) from the server specified in DHCP Option 195 (the default
protocol is FTP).
• 184 - (Optional) Server username (of the server specified in Option 195).
• 185 - (Optional) Server password (of the server specified in Option 195; if the server
allows Anonymous login, you can leave this option blank).
• 195 - Server (ftp/http/https).
• 196 - Root path to the server (ftp/http/https).
Use the guidelines shown in Table 1 when creating and adding the DHCP Options you
need (see "Reference Information: DHCP Options You Can Use").
Step 3: Reboot or Start Your Thin Clients
After you reboot or start your network-connected thin clients, they will look in the defined
root path for the latest available WES7Config.xml file. If updates are available, the
updates are automatically installed (for example, new connections available to a user on
the WES7Config.xml file).