Specifications

C Troubleshooting
This appendix includes troubleshooting information.
Troubleshooting Devices that Cannot Locate Configuration Files
To successfully troubleshoot devices that cannot locate their configuration files, it is
important to understand the DNS-based discovery process used by the WCM agent on
the device.
If you use a server environment (FTP, HTTP, or HTTPS) to deploy your configuration files
(your thin clients access configuration files automatically to update themselves), the
process by which the configuration files are obtained by the WCM agent on the thin client
is the following (in order from first in the process to last):
1. DNS Service Lookup (see "About the DNS Service Lookup Method").
2. DNS Hostname Lookup (see DHCP Option 6 in Table 1).
3. DHCP Options (see "Reference Information: DHCP Options You Can Use").
4. Configured Location Where You Placed the Configuration File (either of the following):
• Local Location (such as a C: drive, local network folder, or USB drive that you set in
the Local option of the Import Configuration dialog box - see
"How to Import Thin
Client Configurations").
• Remote Location (such as a remote server location that you set in the Remote
option of the Import Configuration dialog box - see
"How to Import Thin Client
Configurations").
5. Local Default WES7Config.xml File (located in C:\Program Files\Wyse\ConfigMgmt).
Note that if the values necessary to find the configuration file are not successfully obtained
from DNS, the WCM agent next tries the DHCP Options, and so on. If there is no location
set in the Import Configuration dialog box on the thin client or if the thin client cannot reach
these locations, the thin client will ultimately use the default WES7Config.xml file on the
thin client (this is the latest WES7Config.xml file updated to the ConfigMgmt folder on the
thin client).
About the DNS Service Lookup Method
The DNS Service Lookup method obtains information about the WCM deployment server
and the configurations (configuration file and parameters) utilizing DNS. For example, the
information and parameters are obtained from a DNS server. The method uses a Uniform
Resource Locator (URL) for this purpose (for example, a URL obtained from the DNS
server). Due to the restrictions on the data that can be specified for DNS service record
and DNS hostname record, it is assumed that the authentication (username/login) used
on the deployment server is Anonymous.