Dell_Webcam_1.3.0.0

Notes

NOTE: A NOTE indicates important information that helps you make better use of your computer.

____________________

Trademarks used in this text: Dell???, the Dell logo, vWorkspace?? , and Wyse?? are trademarks of Dell Inc. Microsoft??,Windows?? Embedded Standard 2009, Windows?? Embedded Standard 7, Windows?? Embedded Standard 8, Windows Server??, and Internet Explorer??, are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Citrix??, Xen??, XenServer?? and XenMotion?? are either registered trademarks or trademarks of Citrix Systems, Inc. in the United States and/or other countries. VMware??, Virtual SMP??, vMotion??, vCenter?? and vSphere?? are registered trademarks or trademarks of VMware, Inc. in the United States or other countries. .

2013 - 10

Introduction

Dell Wyse Configuration Manager (WCM) is an innovative self-configuring client technology for the cloud and Dell Wyse Enhanced Embedded virtual desktop environments. WCM provides a simple solution to create and apply configuration files to Dell Wyse thin clients running supported Microsoft Windows Embedded operating systems.

WCM is mainly used by IT Administrators who create configuration files using a simple standalone GUI or capture them from an already configured Dell Wyse thin client running a supported Windows Embedded operating system. The thin client system connects to the remote file folder location that contains the configuration file and downloads the same to update the configuration. WCM enables configuration of multitude of thin clients without a management server.

This guide is intended for administrators of Wyse thin clients running WES2009, WES7, WES7p, or WE8S. It provides the necessary information for using the tool to create and apply configuration files to Wyse thin clients.

The supported Windows Embedded operating systems are:

???Wyse Embedded Standard 2009 (WES2009)

???Wyse Enhanced Microsoft Windows Embedded Standard 7 (WES7)

???Wyse Enhanced Microsoft Windows Embedded Standard 7 p (WES7p)

???Wyse Enhanced Microsoft Windows Embedded 8 Standard(WE8S) (32- bit and 64-bit)

Overview

WCM helps you to easily deploy thin client configurations either manually or through a server environment and is an easy-to-use solution for supported Windows Embedded thin clients from Dell Wyse.

WCM consists of two components:

Introduction 7

???WCM Application GUI ??? is a standalone GUI to create new configuration files as well as edit existing configuration files. These files can be placed on an FTP server (for FTP) or on a Web server (Microsoft IIS Web server for HTTP or HTTPS) in order to be deployed on thin clients running the WCM Client.

???WCM Client ??? is a client component that is pre-installed or deployed in the supported thin client systems by using the Dell Wyse Device Manager (WDM). After you log in to the thin client system, the WCM Client downloads the latest configuration file and applies the configurations. As an administrator, you can also use the WCM Client Control Panel applet to export the current customized configurations of a thin client as a configuration file, and to manually import configuration files into the thin client.

You can deploy the WCM configuration files to your thin clients both automatically and manually. For more information, see Setting Up Automatic Configuration, Setting Up Manual Configuration, and Importing Thin Client Configurations.

The following diagram describes the deployment of configuration files on a WCM thin client.

Key Features

The WCM has the following features:

???Provides granular control to deploy:

???Universal, or user-specific settings

???Stationary or mobile thin clients

???Local or remote devices

8 Introduction

???Provides the ability to:

???Create configuration files from a standalone GUI or capture the configuration from an already configured device

???Maintain history of configurations

???Update existing configurations or revert to previous configurations

???Use the Appliance mode to configure one or more Windows Embedded thin clients to function as a simple-to-use, dedicated kiosk for one of the following:

???Citrix Clients

???VMware View Clients

???vWorkspace Clients

???Microsoft RDS/RDP Clients

???Internet Explorer

???Use the Generic Appliance mode for any user-specified application.

What???s New

The new features in this release of WCM are:

???Support for thin clients running WE8S (32 bit and 64 bit)

???Support for Appliance Mode for any user-specified application (Generic Appliance Mode)

???Support for configuring Quest vWorkspace clients

???Support for creating Internet Explorer URL shortcuts on the desktop for the selected favorites

???Support for configuring an Exit button on the Citrix Enterprise Receiver Appliance Mode in the Published Apps or Desktops dialog box. This button enables you to exit from the Appliance Mode

Introduction 9

???Support for Exit button for all Appliance Modes applications. This allows the user to exit, log off, shut down or restart from the client while in Appliance Mode. This feature is also supported for other Citrix XenDesktop and VMware Horizon View Appliance Mode applications with some limitations. This release also supports the ability to configure the exit buttons and shortcuts per user.

???Support to configure share drives from the WCM Client. You can add or remove share drive connections and also map the remote machine drive by using Share Drive.

???Single sign-on (SSO) for domain joined devices. This version of WCM provides the single sign on feature for domain joined devices to connect using RDP, VMware View, Citrix Xenapp.

???Support for Adobe Flash Player settings. You can use the WCM 1.3 Client to configure Adobe Flash player for Citrix sessions.

???Flash Remoting: Enables HDX Media Stream Flash Redirection on the user device.

???Server Http Cookies: Enables synchronization of the client-side HTTP cookies with the server-side in order to download HTTP cookies from the server.

???Server Side Content Fetching: By default, the HDX Media Stream Flash Redirection downloads Adobe Flash content to the user device and plays the content.

???URL rewriting rules for client-side content fetching: One can redirect an attempt to obtain Flash content using the URL rewriting rules for client-side content fetching setting which is a second generation Flash Redirection feature.

???Removal of WebDAV dependency for both HTTP and HTTPS protocol to download the configuration files or resource files.

???Ability to block or unblock the popups on a Citrix Session when connecting to a full screen ICA session on the WCM Client.

???Support for RDP 8 settings.

10 Introduction

???WCM 1.3 client supports RDP8 and its new features. The settings given below are supported for RDP8 functionality by WCM.

???Detect Connection Quality automatically

???Remote Desktop Gateway KDC proxy and Edit box option for KDC Proxy Name

???Enable Workspace Reconnect

???Ability to configure Citrix Standard Receiver using the WCM Client.

???Enhanced speed of download and applying of configuration on the thin client systems.

Supported Dell Wyse Thin Client Systems

WCM is supported on the following thin client systems that run:

???Wyse Enhanced MicrosoftWindows Embedded Standard 2009 build 684, 685, 686, 703, 704, 716, 718, 719, 720, 723, 716, 727 or later:

???C90LEW

???D90DW

???R90LW

???R90LEW

???R90LW Fiber-NIC Ready

???V90LEW

???X90cw

???X90mw

???X90LW

???X90LeW

???Z90DW

???Z90SW

Introduction 11

???Wyse Enhanced MicrosoftWindows Embedded Standard 7 build 818, 827, 830, 832, 833, 846, 858 or later:

???C90LE7

???D90D7

???D90Q7

???R90L7

???R90LE7

???X90C7

???X90M7

???Z90D7

???Z90DE7

???Z90S7

???Z90Q7

???Wyse Enhanced MicrosoftWindows Embedded Standard 7p build 850 or later:

???X90M7p

???Z90D7p

???Z90DE7p

???Wyse Enhanced Microsoft Windows Embedded 8 Standard build 904, 907, and 908:

???D90D8

???D90D8x

???D90Q8

???Z90D8

???Z90D8x

???Z90Q8

12 Introduction

NOTE: If you have thin clients running earlier builds where the WCM Client was not pre-installed on your thin client, you can:

-Re-image the thin clients with the latest firmware to include the WCM Client in those builds.

-Use WDM to push the WCM Client package to each thin client.

-Install the WCM Client manually. Ensure that you disable the File Based Write Filter on the thin client before installing the WCM Client.

Supported Operating Systems

WCM is supported on Dell Wyse thin clients running the following operating systems:

???WE8S (32-bit and 64-bit)

???WES7P

???WES 7

???WES 2009

Dell Wyse Technical Support

To access Dell Wyse technical resources, visit http://www.wyse.com/support. If you still have questions, you can submit your questions using the Dell Wyse Self-Service Center at http://support.wyse.com/selfservice.html or call Customer Support at 1-800-800-WYSE (toll free in U.S. and Canada). Hours of operation are from 6:00 A.M. to 5:00 P.M. Pacific Time, Monday through Friday.

To access international support, visit http://www.wyse.com/global.

Related Documentation and Services

Fact Sheets containing features of hardware products are available on the Dell Wyse Web site. Go to http://www.wyse.com/products and use the Cloud clients tab to locate and download the Fact Sheet for your hardware product.

If you need to upgrade your Windows Embedded Standard operating system, contact Dell Wyse Customer Support at: http://www.wyse.com/support.

Introduction 13

Installing and Configuring Dell Wyse Configuration Manager (WCM)

This section provides information about installing and configuring WCM in your environment. Depending on your environment and intended deployment, you can choose one of the following:

???Server Deployment ??? if you want a server environment that uses FTP, HTTP, or HTTPS servers and intend to create configuration files that thin clients can access automatically to update themselves.

???Manual Deployment ??? if you want a non-server environment and intend to create configuration files that thin client systems can access locally to update themselves manually using the Import feature of the WCM Client Control Panel applet on the thin client system.

Pre-requisites to Install WCM

The pre-requisites mentioned in this section are applicable to both manual and server deployment modes.

To install WCM on a server, ensure that the server meets the following requirements:

1Ensure that the following hardware requirements are met on the server:

???CPU ??? A minimum of 1 GHz Intel or AMD X86. We recommend a 2.4 GHz Dual Core Intel or AMD X86 CPU.

???RAM ??? A minimum of 512 MB. We recommend 2GB.

???Free Space ??? A minimum of 500 MB. We recommend a free space of 720 MB. The actual free space required depends on:\

??? The number and size of the configuration files you store

??? The number of thin client devices you manage

Installing and Configuring Dell Wyse Configuration Man-

2Install the supported operating system on the server for the WCM Application. The supported operating systems are:

???Windows 7 Professional Enterprise Edition

???Windows Server 2008

???Windows Server 2008 R2

???Windows Server 2003

???Windows Server 2003 R2

The supported operating system languages to install the WCM Application are:

???Chinese Simplified

???English

???French

???German

???Japanese

???Spanish

???Russian

3Install Microsoft .NET framework 3.5 or higher on the server.

4Ensure that Internet Information Services (IIS) version 6.0, 7.0, or 7.5 is installed.

5Ensure that all required communication ports are available and open for proper communication between servers, routers, and switches. The server port requirements for FTP, HTTP, and HTTPS are:

???FTP ??? Port 21 with defaults

???HTTP ??? Port 80 with defaults

???HTTPS ??? Port 443 with defaults

NOTE: Steps 4 and 5 are not required for Manual Deployment.

Downloading and Installing WCM

Downloading WCM

The WCM software package includes:

???The installer for WCM Server Application

???The installer for locally installing the WCM Client on an individual thin client.

???Packages for remotely deploying the WCM Client onto multiple thin clients using Dell Wyse Device Manager (WDM).

To download the WCM software package:

1Launch the internet browser and navigate to the Dell Wyse support site at http://www.dellwyse.com/serviceandsupport/support/downloads.asp.

2Select Wyse Configuration Manager from the Product Downloads ???

Active drop-down box.

3Click Search. The downloads for WCM are displayed.

4Click the latest version of the WCM build. The EULA page is displayed.

5Select the I Agree option and click Next.

6Navigate to the location where you want to save the .zip file that contains the WCM installer.

7After you download the .zip file, extract the contents.

Installing WCM Server Application

To install the WCM server application, run the Wyse Configuration Manager Application.msi file and follow the wizard to install the application. The default location for installation is C:\Program Files\Wyse\WCM\Application.

Installing WCM Client

The WCM Client is included in supported Windows Embedded thin clients. To update them you can:

???Install them manually on each thin client, as an administrator.

???Deploy them remotely, to multiple thin clients, using the Dell Wyse Device Manager (WDM). Register the WCM Client into WDM and then deploy it to multiple devices remotely. For more information on registering the WCM Client into WDM, see the WDM Administrator???s Guide.

To install the WCM Client manually:

1Log in to the thin client system as an administrator.

2Disable the file based write filter (FBWF).

3Run the Wyse Configuration Manager Agent_LaunchPad.exe file and follow the wizard to install the WCM client.

4Restart the thin client system when prompted.

5When the installation is complete, re-nable the FBWF. The WCM service does not work when the FBWF is disabled as it does not download and apply the XML configuration file.

The WCM Environment

The WCM environment consists of the following components:

???Repository Server ??? This is the server where the WCM configuration files are copied and the WCM GUI is installed.

NOTE: You can install the WCM GUI on a separate server and store the WCM configuration files on a separate server.

???DNS/DHCP Server ??? This is the server where you configure the Domain Name Server (DNS) or the Domain Host Configuration Protocol(DHCP). DNS or DHCP settings are used by the WCM client to find the Repository server with WCM configuration files. For more information, see Discovery Settings for the WCM Server.

???WCM Client Software on Thin Client Systems ??? These are the thin clients with WCM Client software, which download the configuration files from the repository server.

For WCM to work, you need to configure each of the components.

Configuring the Repository Server

Configuring the Repository Server on a Windows 2003/Windows 2003 R2 Server

1Log in to the repository server as Administrator.

2On the Start menu, go to Control Panel ??? Add or Remove Programs and click Add/Remove Windows Components.

3Select Application Server in the Windows Components Wizard and click Details.

4In the Application Server window, select Internet Information Services (IIS) and click Details.

5In the Internet Information Services (IIS) window, select File Transfer Protocol (FTP) Service, Internet Information Services Manager, and WorldWide Web Service.

6Click OK to go back to the Application Server window, and OK again to go back to the Windows Components Wizard.

7Click Next to install IIS.

8Navigate to C:\inetpub\ftproot\ directory and create the following directory structure under them:

???Wyse

???WE8S

???WES

???WES7

9Launch IIS Manager, select Default Web Site, right click and select New

??? Virtual Directory on the menu.

aIn the Virtual Directory Creation Wizard, enter WCM under Alias and click Next.

bNavigate to the physical location of the Wyse folder structure that you created in step 8. For example, C:\inetpub\ftproot\.

cClick Next.

dEnter the type of access to the folder such as Read, Write, Browse etc.

eClick Next to complete the wizard. The virtual directory is created with the Wyse folder structure.

10Verify the FTP virtual directory structure under FTP Sites ??? Default FTP Site. It is automatically created.

a Right-click Default FTP Site and select Properties on the menu.

b In the Default FTP Site Properties window, click the Home Directory tab to verify the virtual directory.

11Set up the ports for FTP, HTTP, and HTTPS.

Setting up the FTP port on a Windows 2003 Server

1Launch IIS Manager, right click Default FTP.

2Select New ??? FTP Site on the menu. In the FTP Site Creation Wizard click Next.

3Type WCM in Description, and click Next.

4The default Port number is displayed as 21. Leave the default port number.

5Under Enter the IP address to use for this FTP site leave the default value and click Next.

6Leave the default settings for FTP User Isolation and click Next.

7Browse to the FTP Directory (C:\inetpub\ftproot\) and click Next.

8Enter access to the FTP Directory and click Next to complete the setup.

Setting up the HTTP and HTTPs Ports on a Windows 2003 Server

1Launch IIS Manager, select Default Web Site and right click.

2Select New ??? Web Site on the menu. In the Web Site Creation Wizard click Next.

3Type WCM in Description, and click Next.

4The default Port number is displayed as 80. Leave the default port number. This is the default HTTP port.

5Under Enter the IP address to use for this FTP site leave the default value and click Next.

6Browse to the website home directory C:\inetpub\ftproot\ and click Next.

7Enter access to the website home directory and click Next to complete the setup.

8To configure the HTTPS port:

a Right-click on the newly created website, and select Properties on the menu.

b In the Properties window, on the Web Site tab, enter the SSL port as 443.

c Click the Directory Security tab and click Edit in the Secure Communications section.

d In the Secure Communication window, select Require secure channel (SSL) and click OK.

e Click Server Certificate to create an SSL certificate, if you have not downloaded a certificate for the server. For more information on creating an SSL certificate, see Microsoft KB article 228991 available at http://support.microsoft.com/kb/228991.

Configuring the Repository Server on a Windows 2008/Windows 2008 R2 Server

1Log in to the repository server as administrator.

2Launch the Server Manager by navigating to Start??? Administrative Tools ??? Server Manager.

3Select Roles on the left pane and click Add Roles on the right pane to launch the Roles Wizard.

4Select Server Roles on the Roles Wizard and select the Web Server (IIS) option.

5Click Install to install the Web Server (IIS).

6Click Role Services on the Roles pane in Server Manager to launch the

Role Services Wizard.

7Select the FTP and HTTP options and click Install.

8Navigate to C:\inetpub\ftproot\ or C:\inetpub\ftproot\ directories and create the following directory structure under them:

???Wyse

???WE8S

???WES

???WES7

9Launch IIS Manager, right click Default Web Site and select Add Virtual Directory on the menu.

a In the Add Virtual Directory window, enter WCM under Alias.

b Navigate to the physical location of the Wyse folder structure that you created in step 8. For example, C:\inetpub\ftproot\.

c Click OK. The virtual directory is created with the Wyse folder structure.

10Verify the FTP virtual directory structure under defaultFTP. The virtual directory is automatically created.

11Set up the ports for FTP, HTTP, and HTTPS.

Setting up the FTP Port on a Windows 2008 Server

1Launch IIS Manager, right click defaultFTP.

2Select Bindings on the menu options.

3In the Site Bindings window, click Add. The Add Site Binding window is displayed.

a Select FTP under Type.

b The default Port number is displayed as 21. Leave the default port number.

c Click OK.

4Click Close to exit from the Site Bindings window.

Setting up the HTTP and HTTPs Ports on a Windows 2008 Server

1Launch IIS Manager, right click Default Web Site.

2Select Bindings on the menu options.

3In the Site Bindings window, click Add. The Add Site Binding window is displayed.

a Select http under Type.

b The default Port number is displayed as 80. Leave the default port number.

c Click OK.

d For setting up the HTTPS port, select https under Type.

e The default Port number is displayed as 443. Leave the default port number.

f Under SSL certificate, select the SSL certificate that you have downloaded for the server. For more information on creating an SSL certificate, see Microsoft KB article 228991 available at http://support.microsoft.com/kb/228991.

Configuring the Repository Server on a Windows 7 System

1Log in to the repository server as Administrator.

2Click Start ??? Control Panel ??? Programs and Features.

3Click Turn Windows features on or off to launch the Windows Features dialog box.

4Expand the Internet Information Services (IIS) option to display the additional categories of the IIS features.

5Select the following options under IIS:

???FTP Server

???Web Management Tools

???World Wide Web

6Ensure that the WebDAV Publishing option under World Wide Web Services ??? Common HTTP Features is unchecked.

7Click OK to start the installation. After the installation completes, IIS is installed with a default configuration on Window 7.

Setting up the FTP Port on a Windows 7 System

1Launch the IIS Manager.

2Under Connections, right click Sites and click Add FTP Site.

3In the FTP Site Window, enter FTP under FTP site name, and enter the physical path as C:\inetpub\ftproot, and click Next.

4Enter All Unassigned under IP Address, and 21 under Port.

5Select the option Start FTP Site Automatically.

6Select the No SSL radio button and click Next.

7Select Anonymous and Basic Authentication.

8Select Allow access to All Users.

9Grant the Read and Write permissions and click Finish.

Setting up the HTTP and HTTPS Ports on a Windows 7 System

1Launch the IIS Manager.

2Under Connections, right click Default Websites and click on Add Application.

3In the Add Application window, enter the following details:

???Alias Name ??? WCM

???Physical Path ??? C:\Inetpub\wwwroot

4Click OK and go to the WCM Directory created under Default Web Site.

5Expand Compression under the WCM Directory and uncheck the options Enable Dynamic Content Compression and Enable Statis Content Compression.

6Click Apply and confirm the IIS installation by typing http://localhost in your browser.

7Navigate back to the IIS Home Page and click Server Certificates.

8Click Create Domain Certificate on the right side of the window to display the Create Certificate window.

9Enter significant values for all the fields and click Next to display the

Online Certificate Authority Window.

10On the Online Certification Authority window, in the Specify Online Certification Authority box, select the Domain Certificate and click OK.

11Enter a user friendly name such as HTTPS and click Finish.

12Go to Default Web Site on the IIS Manager and right click.

13Select Bindings on the menu options.

14In the Site Bindings window, click Add. The Add Site Binding window is displayed.

a Select https under Type.

b The default Port number is displayed as 443. Leave the default port number.

c Under SSL certificate, select the SSL certificate that you have downloaded for the system. For more information on creating an SSL certificate, see Microsoft KB article 228991 available at http://support.microsoft.com/kb/228991.

d Click OK.

15Confirm the IIS installation by typing https://localhost in your browser.

Discovery Settings for the WCM Server

When the WCM client starts after log in it searches network services (DNS and DHCP) for an FTP/HTTP/HTTPS server to download the file, or uses a locally available file on the device. The process by which the configuration files are obtained by the WCM agent on the thin client is in the following order:

1DNS Service Record Lookup

2DNS Hostname Lookup

3DHCP Option Tags

DNS Service Record Lookup

The DNS Service Record Lookup method (also known as SRV record) obtains information about the WCM Repository Server and the configurations that utilize 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 a DNS hostname record, it is assumed that the authentication (username/log in) used on the Repository Server is Anonymous.

In the DNS service record lookup, an administrator can configure the DNS server to provide the server and port number for a service that is referred to as _WCM._tcp. Multiple configuration repository server/port values can be provided. The WCM agent accesses them in order, according to the weight and priority associated with each entry.

Since the DNS server may not supply a protocol string associated with each server/port entry, the WCM agent determines the protocol based on the port specified. For example, if port 80 is specified, the WCM agent determines that the protocol being used is HTTP. If the DNS service record lookup for _WCM._tcp <full domain> fails, the WCM agent attempts _WCM._tcp <sub-domain> and so on upon further failures. For example, if the domain name is x.y.z, the WCM agent issues a DNS service location lookup using the following names in the order shown until the DNS server returns a valid answer:

1_ WCM._tcp.x.y.z

2_ WCM._tcp.y.z

3_ WCM._tcp.z

Configuring the DNS Service Lookup

For more information on installing DNS on a Windows 2003 Server, go to http://support.microsoft.com/kb/814591.

For more information on installing DNS on a Windows 2008 Server, go to http://technet.microsoft.com/en-us/library/cc725925.aspx.

To configure the DNS Service (SRV) lookup:

1Open the DNS Manager after installing the DNS Server.

2Under the Domain, right click and select Other New Records.

4In the New Resource Record dialog box, enter the following values:

???Service Name ??? _WCM

???Protocol ??? _tcp

???Port Number ??? either 21, 80, or 443 depending on whether you choose FTP, HTTP, or HTTPS protocols.

???Host Offering this Service ??? enter the hostname of the repository server.

5 Click OK.

DNS Hostname Lookup

If the WCM agent is unable to obtain a valid answer to DNS service record lookup requests, it then attempts a DNS Hostname lookup.

An administrator can configure the DNS server to provide the server IP for a host name. With the DNS Hostname record it is not possible to supply protocol or port. Therefore, the retrieval module first uses the HTTPS on port 443. If this fails, the WCM agent then uses the HTTP on port 80. If the lookup for host name WCM in the client???s domain fails, the WCM agent then attempts to look for WCM for each sub-domain name. For example, if the domain name is x.y.z, the WCM agent issues a DNS host name lookup using the following names in the order shown until the DNS server returns a valid answer:

1WCM.x.y.z

2WCM.y.z

3WCM.z

Configuring the DNS Hostname

To configure the DNS Hostname:

1 Under DNS Host, select New Host. The New Host dialog box is displayed.

2In the New Host dialog box, enter wcm under Name and provide the IP address of the IIS Server.

3 Click Add Host.

DHCP Option Tags Lookup

When configuring the DHCP server for use with WCM, use the DHCP option tags listed in Table 2-1.

Ensure that the DHCP option tags that you create are activated within the DHCP scope. This can be done using the Scope Options dialog box on the DHCP server (after you add them) or the Configure Options command (before you add them). For details on your network environment and DHCP layout, contact your network administrator.

Table 2-1. DHCP Option Tags

authenticating to the server specified in Option 195. If the server allows Anonymous log in, you can leave this option blank.

195Server (ftp/http/https). Optional IP Address or string. Can be either the IP Address or the fully qualified domain name (FQDN) of the Repository server. If a name is given, the name must be resolvable by the DNS server(s) specified in Option 6. If the option provided by the server is blank or the server provides no value for the field, the machine on which the DHCP server resides is assumed to be the server.

IP Address example: 192.168.100.7

String example: MyServer.com

Table 2-1. DHCP Option Tags

???FTP: For FTP, the default HTTP custom example: configuration path is

C:\inetpub\ftproot\Wyse\ C:\inetpub\ftproot\Wyse\WES7\Fin

Configuring DHCP Options

On the DHCP server, you need to add three Wyse vendor tags ??? 183, 195 & 196. Option Tag 183 defines the protocol to use with WCM. Valid protocols are FTP, HTTP, and HTTPS. Option Tag 195 identifies the IP address of the FTP server that the thin client system connects to. Option Tag 196 contains the directory details of the configuration file that the thin client system downloads.

Configuring DHCP Options on a Windows 2003 Server

1Right-click My Computer and select Manage.

2Expand Services and Applications.

3Highlight DHCP and click Set Predefined Options. The Predefined Options and Values screen is displayed.

4Click Add to add an option in the Option Type window.

5Add the following details one at a time in the Option Type window:

Table 2-2. DHCP Options

6On the Predefined Options and Values screen, scroll down to verify that the options have been added.

7Select option tag 6 and enter the IP address of the DNS Server or the name of the DNS Server.

8Select option tag 183, and enter the protocol you will be using on your server.

9Select option tag 195 and enter the IP address of your FTP, HTTP or HTTPS server that contains the WCM configuration files and press OK.

10Select option tag 196 and enter the string ???/ ??? (forward slash) and press OK. This sets the default path to ftproot/wyse/wes7 directory if you are using FTP as the protocol or webroot/wyse/wes7 if using HTTP or HTTPS as the protocol.

11Select option tag 184 and enter the username to use when authenticating to the server specified in step 9 (option tag 195). If the server allows Anonymous log in, you can enter the value Anonymous.

12Select option tag 185 and enter the password to use when authenticating to the server specified in step 9 (option tag 195). If the server allows Anonymous log in, leave this field blank.

13Add the options to the DHCP scope. Navigate back to DHCP in the Computer Management screen, right click Scope Options and select

Configure Options.

14Ensure to select options 183, 195, and 196. Press OK to save and exit.

Configuring DHCP Options on a Windows 2008 Server

1Launch Server Manager from the Start menu.

2Under Roles, expand the DHCP Server, select your server and expand it.

3Select IPv4 and expand it.

4Right click Scope Options and select Configure Options. The Scope Options window is displayed.

5Select option tag 6 and enter the IP address of the DNS Server or the name of the DNS Server.

6Select option tag 183, and enter the protocol that you want to use on your server.

7Select option tag 195 and enter the IP address of your FTP, HTTP or HTTPS server that contains the WCM configuration files and click OK.

8Select option tag 196 and enter the string ???/ ??? (forward slash) and click OK. This sets the default path to the ftproot/wyse/wes7 directory if using FTP as the protocol or webroot/wyse/wes7 if using HTTP or HTTPS as the protocol.

9Select option tag 184 and enter the username to use when authenticating to the server specified in step 9 (option tag 195). If the server allows Anonymous log in, enter the value Anonymous.

10Select option tag 185 and enter the password to use when authenticating to the server specified in step 9 (option tag 195). If the server allows Anonymous log in, leave this field blank.

11Click OK.

Configuring the WCM Thin Client Systems

To manually configure the DHCP options on thin client systems:

1Log in as Administrator into the thin client systems and launch the WCM from the Control Panel.

2Click Advanced Options and set the following values:

???Server ??? The default DHCP option is 195. This is the server IP Address or the fully qualified domain name (FQDN) of the server.

???Path ??? The default DHCP option is 196. This is the root path to the server; ftp, http, or https.

???Username ??? (Optional) The default DHCP option is 184. This is the server username of the server specified in DHCP option 195.

???Password ??? The default DHCP option is 185. This is the password of the server specified in DHCP option 195. If the server allows Anonymous log in, leave this option blank.

???Protocol ??? The default DHCP option is 183. This is 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)

3Click Save Settings.

NOTE: You must ensure that the DHCP options that you specify in the thin client systems are identical to the options specified in the DHCP server. This is needed for the discovery of the thin clients by the Repository Server.

Configuring the Dell Wyse Device Manager

(WDM) Server

If you are using the WDM Server to push the configuration files to the thin clients, you need to edit the WES_ApplyConf.rsp, WES7_ApplyConf.rsp, or

WE8S_ApplyConf.rsp files for the WES2009, WES7 or WE8S thin client systems respectively.

There are two ways in which you can push the configuration files to the thin clients:

???Through the Remote Path (RP) Command ??? This method sets the repository path to that of WDM server and the thin client system picks up the latest configuration from this path on every log in.

???Through the Apply Configuration (AC) Command ??? This method enables the thin client system to download the configuration file from the WDM server and apply it on every log in.

To register the RP Command package in the WDM server:

1Create an XML file from the WCM Application GUI by enabling the Use WDM option under Agent Settings.

2Log in to the WDM Server system as an Administrator.

3Place the XML file in the RP Command folder. For example, C:\Program

Files\WDM\WDM_WCM\RP Command\TestRP_WES\Wyse\WES\WESConfig.xml.

4Register the .rsp package in the WDM server and apply it on the thin client system.

5Restart the thin client system for the changes to take effect. You will notice that the Remote/WDM option in the Import Configuration screen of the WCM Client is disabled and populated with the WDM server details.

To register the AC Command:

1Create an XML file from the WCM Application GUI by editing any of the existing XML files.

2Open the XML file in a text editor and change the <uiProtocol> tag to

<uiProtocol>local</uiProtocol>. Save the file.

3Log in to the WDM Server system as an Administrator.

4Place the XML file in the AC Command folder. For example, C:\Program

Files\WDM\WDM_WCM\AC Command\WES7_AC\WES7_AC\temp\WES7Config.xml.

5Open the WES_ApplyConf.rsp, WES7_ApplyConf.rsp, or

WE8S_ApplyConf.rsp file from the location where you have installed WDM in a text editor. For example, C:\Program Files\WDM\WDM_WCM\WES_ApplyConf\WES_ApplyConf.rsp.

6Under the Copy over new files section, enter the location of the configuration XML file against the AC command. For example: AC "C:\temp\WES7Config.xml". This is the local path on the thin client system to which the configuration file gets downloaded.

7Save and close the file.

Your WDM server is now configured to push the configuration files to the thin clients. You also need to configure the Agent Settings in the WCM Application GUI to complete the setup. For more information, see Agent Settings. For more information on registering a .rsp package, see the WDM Administrator???s Guide.

Using the Dell Wyse Configuration

Manager (WCM) GUI Application

This chapter discusses in detail how to use the WCM GUI Application that is installed on the Repository Server. You can create configuration files, edit existing configuration files, and save the configuration files in a central location. The thin client system connects to the central location and downloads the respective configurations.

About the WCM Application GUI

The WCM Application GUI is installed and available on the repository server. You must log in to the repository server as the administrator to launch and access the WCM Application GUI. The GUI consists of the following components:

???Configuration Explorer ??? Contains the Configurations tab that consists of the names of the areas you can configure for your configuration files. The names of the areas that you can configure are displayed as a tree structure with the main areas as the main nodes and the sub-areas as sub- nodes.

???Toolbar ??? Contains icons that are located on top of the Configurations tab and can be used for the main nodes and sub-nodes in the Configurations tab. Each icon has a tool-tip description for easy identification.

???Right-click Menus ??? Provides easy access to perform the various tasks. You can right-click certain items on the Configurations tab to view the menu of the available tasks.

???Details Pane ??? Displays the detailed configuration settings for the selected nodes and sub-nodes in the Configurations tab on the right pane of the GUI. You can modify these settings to create a new configuration file or edit an existing configuration file.

???Menu Bar ??? Provides the various menu options for you to effectively use the WCM Application GUI.

Using the Dell Wyse Configuration Manager (WCM) GUI

Creating New Configuration Files

You can use the WCM Application GUI to create new configuration files to be applied to thin clients.

To create new configuration files:

1Log in to the repository server or the system where you have installed WCM and launch the WCM Application GUI.

2Click one of the following options to create a new configuration file:

???New Windows Embedded Standard 8 Configuration (WE8S)

???New Windows Embedded Standard 7 Configuration (WES7)

???New Windows Embedded Standard Configuration (WES2009) You can also choose the preceding options from the New menu.

3In the Configurations tab, check the options that you need to configure and provide the corresponding values in the Details pane.

For more information, see Configuration Details.

4After providing the Configuration details, click the Save menu and enter a name for the configuration file.

The path where the file is saved is dependent on the option you choose in step 1 and the protocol you have chosen for the file transfer.

If you are using the Repository Server for automatic upgrades, then the default folder locations are:

???For FTP:

???C:\inetpub\ftproot\Wyse\WES\WESConfig.xml

???C:\inetpub\ftproot\Wyse\WES7\WES7Config.xml

???C:\inetpub\ftproot\Wyse\WE8S\WE8SConfig.xml

???For HTTP/HTTPS:

???C:\inetpub\ftproot\Wyse\WES\WESConfig.xml

???C:\inetpub\ftproot\Wyse\WES7\WES7Config.xml

???C:\inetpub\ftproot\Wyse\WE8S\WE8SConfig.xml

NOTE: The required names for each of the configuration files for each platform should be WE8S - WE8SConfig.xml, WES7 - WES7Config.xml, and WES2009 - WES2009Config.xml respectively. If the thin client system is a domain user, then the name of the configuration file should be administrator.xml to enable the domain user client systems to download the configurations.

If you are using the WCM Client to import the files, then you can save the configuration files in a local or remote folder location that is easily accessible by the thin clients.

Editing Existing Configuration Files

To edit an existing configuration file:

1Launch the WCM Application GUI and click the Open an Existing Configuration option in the Details pane. You can also click the Open menu to open an existing configuration file.

2Navigate to the location to select your configuration file. For more information on the default location, see step 4 in Creating New Configuration Files.

3Modify the configuration details and click the Save menu to save the file. You can choose to save the file with the same name or with a different name.

Configuration Details

You need to configure the various configuration areas to create or modify the configuration files to be deployed on the thin client systems.

The Configurations tab on the WCM Application GUI displays the configuration areas with the corresponding details on the Details pane. The configuration areas are broadly classified as:

???Connections

???Device Configuration

???OS Configuration

To enter configuration details:

1Select the configuration area in the Configurations tab, and enter the values in the Details pane for the selected area.

When you select any of the details in the Details pane, the corresponding description is displayed at the bottom of the screen.

2After you enter the values for the details, ensure that you click Apply Changes to save your changes.

3Click Discard Changes to reset the values back to the defaults.

NOTE: If you use a server environment (FTP, HTTP, or HTTPS) and intend to create configuration files that thin clients can access automatically to update themselves, ensure to name your file WESConfig.xml for WES2009, or WES7Config.xml for WES7/WES7p, or WE8SConfig.xml for WE8S and place the file into the correct folder according to the protocol you use. If the thin client system is a domain user, then the name of the configuration file should be administrator.xml to enable the domain user client systems to download the configurations.

Connections

The Connections area enables you to set the configurations for the different types of connections that the thin client can use to connect to the servers. This area consists of:

???RDP ??? to configure the remote desktop protocol settings to connect to any remote computer.

???VMware View ??? to configure the VMware View client to connect to the VMware View Connection Server.

???Citrix??? to configure the Citrix client to connect to the Citrix server.

???vWorkspace ??? to configure the vWorkspace to connect to any Quest vWorkspace server in your environment.

RDP

The RDP settings are grouped under Basic Settings, Display, Local Resources, Other RDP Settings, and Unrecognized Settings.

Table 3-5. vWorkspace Details (continued)

NOTE: You can use the existing Quest vWorkspace configuration XML file or create it using the Quest vWorkspace AppPortal installed on any system.

Device Configuration

The Device Configuration area enables you to set the configurations for the hardware connected to or located on the thin client devices.

This area includes:

???Display ??? to configure the display settings.

???Mouse ??? to configure the mouse settings.

???Keyboard ??? to configure the keyboard settings.

???Share - New Share ??? to configure the share drives and create new file share locations.

???Timezone ??? to configure the timezone.

???Ethernet??? to configure the ethernet settings.

???Wireless Profile??? to configure wireless profiles.

???Audio ??? to configure audio settings.

???Power??? to configure power settings.

Display

Table 3-6. Display Setting Details

Monitor1 and Monitor2 Display Settings

NOTE: Monitor2 display settings are applicable only if there are multiple monitors attached to the device.

OS Configuration

The OS Configuration area enables you to set the configurations for various settings on the operating system that includes:

???Browser, Firewall, and Aero: to configure browser, firewall, and aero related settings.

???Clocks: to configure the clock settings. This is not applicable to WES2009 systems.

???Other Settings : to configure the Appliance Mode settings.

Browser, Firewall, and Aero

Table 3-15. Browser, Firewall, and Aero Details

Clocks

Table 3-16. Clock Details

Other Settings

You can enter the Appliance Mode settings in this area. Appliance mode allows a supported thin client to be used as a dedicated device for a specific application. You can log in to the device to be immediately presented with your remote client log in, a local full-screen, Internet Explorer, or are logged into a remote session. Appliance mode can be especially beneficial for kiosks, digital displays, advertising displays, and dedicated usage.

NOTE: Appliance mode requires that WCM settings are not applied in Append mode. To disable Append mode, open the Options menu and clear/uncheck Append Settings.

Table 3-17. Other Setting Details (continued)

Appliance Mode is supported for:

???VMware View connections

???Citrix XenApp, XenDesktop, and Secure Gateway connections

???One or more RDP/RDS/Terminal Server connections

???Internet Explorer

???Quest vWorkspace

???Any locally installed application on the thin client. (Generic Appliance Mode).

NOTE: Appliance Mode for Internet Explorer does not support Citrix sessions launched from Internet Explorer.

An Exit button is now available for all Appliance Mode applications. This allows you to exit, log out, shut down, or restart from the client while in Appliance Mode.

The Exit button is supported for Citrix XenDesktop, and VMware Horizon View Appliance Mode applications with some limitations. You can also configure the exit buttons and shortcuts as per user requirements.

Appliance Mode Workflow on Thin Client Devices

1Boot the operating system on the thin client system.

2Log in to the system.

3The WCM automatically downloads the WCM XML configuration file from the FTP or IIS Web Server or uses a locally stored file on the thin client.

4WCM applies the XML file settings including the Appliance mode.

5Use the thin client system with the configured Appliance mode session.

6Log off from the system or session.

After you log out from the system or session, you can again log in to the system at a later point. In Appliance mode, you only need to press the Ctrl-Alt-Del keys to shut down the current session or restart the system again.

Disabling or Stopping the Appliance Mode

You need to log in as Administrator to disable or log out of the Appliance mode by using one of the following options:

???Server deployed WCM XML files ??? Change the WCM XML file from WCM Application ??? OS Configuration ??? Other Settings on the deployment server.

???By using the thin client ??? On the thin client:

a Hold down the Shift key while logging off the server.

b Log in as an Administrator and while the WCM Appliance mode is downloading or applying the XML file, select the WCM splash screen with your mouse and press the Esc key.

This disables Appliance mode in that session. You can then disable the Write-Filter and make the necessary changes.

Agent Settings

You can use this option in the Options menu to configure your default client agent settings. These settings are required if you are using Dell Wyse Device Manager (WDM) to push the configuration files to your thin clients.

NOTE: You must configure the WDM Server if you want to use it to push the configuration files to the thin clients. For more information, see Configuring the Dell Wyse Device Manager (WDM) Server.

To configure Agent Settings:

1Log in to the Repository Server as Administrator and launch the WCM Application GUI.

2Select Options ??? Agent Settings on the menu.

3In the Agent Settings dialog box, enter the following:

???Protocol ??? Select an option from the drop-down box.

???Server IP ??? Enter the IP address of the Repository Server.

???Port ??? This is entered by default based on the protocol you choose.

???Path ??? Enter the path of the configuration file. This is optional.

???User Name ???Enter the server username. This is optional.

???Password ??? Enter the server password. This is optional.

4Select one or more of the following options:

???Import Configuration on Every Boot ??? if you want to download the configuration file everytime the thin client system reboots.

???Use WDM ??? if you want to use the WDM server to push the configuration file to the thin client.

???Enable Balloon Tips ??? if you want a balloon tip to indicate the status of download on the thin clients.

5Click Apply to save your settings.

Using Your Configuration Files

After you create the configuration file, you must store the file in the location you need, and then complete the procedures required to apply the configurations to the thin clients systems.

You can deploy WCM configuration files to your thin clients:

???Automatically ??? For more information, see Setting Up Automatic Configuration.

???Manually ??? For more information, see Setting Up Manual Configuration.

NOTE: Ensure that the File Based Write Filter of the thin client is enabled. The WCM Client will not download and apply settings if the File Based Write Filter is disabled.

Setting Up Automatic Configuration

For the thin client systems to access configuration files from a server and update themselves automatically:

1Place your configuration files on the server. On your server, you must set up the correct folder. For more information on setting up the folder structure, see step 8 under Configuring the Repository Server.

2Direct your thin client systems to the server using the DNS SRV, DNS Hostname, or DHCP Options. For more information, see Discovery Settings for the WCM Server and Configuring the WCM Thin Client Systems.

Your thin client systems check at each boot up to see if updates are available on your predefined server.

3Reboot or log out from your thin client systems.

A system reboot generates the Discovery.ini file, which redirects the system to download the configuration file from the repository server. If updates are available, the updates are automatically installed. For example, new connections available to a user on the configuration file.

Setting Up Manual Configuration

For the thin client systems to successfully access configuration files and update themselves manually using the Import feature of the WCM Client on the thin client:

1Place your configuration files in a local or remote location that is accessible by the thin client.

2Import the configuration file by using the Import feature on the WCM Client. For more information, see Importing Thin Client Configurations.

Using the Dell Wyse Configuration

Manager (WCM) Client

This chapter discusses how to use the WCM Client that is installed on the thin client systems. You can manually import configuration files, export configuration files, view configuration history, and configure the DHCP settings on the client system.

Launching the WCM Client

You need to log in to the thin client system as an Administrator to launch the WCM Client.

The WCM Client does not have any shortcuts on the thin client desktop.

To launch the WCM Client, navigate to the Control Panel from the Start menu and click the WCM icon.

The top panel of the application displays the details of the configuration file that is currently being applied to the thin client system.

Importing Thin Client Configurations

To manually import the configuration file:

1Launch the WCM Client from the control panel.

2Click Import Configuration. The fields are displayed on the right panel.

3Select one of the following options:

???Local ??? if you have saved the configuration files locally on the thin client system, a network drive, or on a USB drive and want to download the configuration files . Browse to the location, select the file, and click Open.

???Remote ??? if you have saved the configuration files on the repository server in a remote location. Follow the steps given below:

???Select the Protocol from the drop-down list.

???Enter the Server IP address of the repository server.

Using the Dell Wyse Configuration Manager (WCM) Client

???The Port is displayed by default. The default ports for FTP, HTTP, and HTTPS are 21, 80, and 443 respectively.

???Enter the folder Path where the configuration file is saved in the remote location if you have not used the default path.

???Enter the Username and Password to access the Repository server.

NOTE: If you have been deploying your configuration files locally and the Protocol is set to Local in the Agent Settings dialog box of the WCM Application GUI and Import Configuration is set to Local in the Import Configuration dialog box of the WCM Client, you can switch back to a remote download of the configuration files. You must set the Protocol to FTP, HTTP, or HTTPS using the Agent Settings dialog box of the WCM Application GUI. You must also ensure that you set the Import Configuration to Remote in the Import Configuration dialog box of the WCM Client. You cannot switch back to a remote download using only the Agent Settings dialog box of the WCM Application GUI.

4If you want the configuration file to be imported everytime the thin client system boots, check the Import configuration on every boot option.

NOTE: If the Import configuration on every boot option is selected, the WCM remote repository is discovered in the following order of preference DNS- SRV, DNS-Host, DHCP Options, Registry Settings in the remote settings. If none of the above are configured, then the Import configuration on every boot option is not implemented.

5Click Save Settings.

6Click Import to apply the settings in the configuration file to the thin client system immediately.

Fallback Mechanism for Failed Download of Configuration File

If you have configured the DNS-SRV, DNS-Host, DHCP Options, and Registry Settings in the remote settings, and the configuration file does not download, then the fallback mechanism for each of the preceding mechanisms is as follows:

1For a device specific configuration or for a local user, if the

WE8SConfig.xml, or WES7Config.xml, or WESConfig.xml fails to download from the remote path, check the configuration history for the same named latest configuration and apply that file.

2For a domain-joined user, if the administrator.xml fails to download from the remote path, download the WE8SConfig.xml, or WES7Config.xml, or WESConfig.xml from the same remote path and apply that file.

If that too fails to download, check the configuration history for the

WE8SConfig.xml, or WES7Config.xml, or WESConfig.xml latest configuration and apply that file.

3If the xml fallback for each discovery method also fails, then the Factory Default file is applied.

Exporting Thin Client Configurations

To export the configurations on a thin client system to a configuration file:

1Launch the WCM Client from the control panel.

2Click Export Configuration.

3Enter the file name with a .xml extension. For example, TestWES.xml (for WES2009) or TestWES7.xml (for WES7) or TestWES8.xml (for WE8S).

4Use the Browse command button to select the local location where you want to save the file (such as a USB drive).

5Click Export to export and save the current configurations of the thin client to the configuration file.

Using Configuration History

You can use the Configuration History option to apply a configuration file that was previously used on the thin client. This option is useful when a new file did not get applied successfully.

To apply the configuration file:

1Launch the WCM Client from the control panel.

2Click Configuration History.

The five most recent and successfully imported configuration files are displayed.

3Select the configuration file you want to import from the list.

4Click Import to apply the file to the thin client system immediately.

5Click Delete to delete a configuration file from the list. If you have downloaded the file from a remote server, then it does not delete the file from the server.

NOTE: You cannot delete the factory default configuration file.

Manually Setting Debug Options on a Thin Client

The WCM Debugging dialog box allows you to manually set debug options on the thin client. Setting the debug options enables you to troubleshoot issues with the thin client by reviewing the debug log file that is created if this option is configured.

To set the debug options:

1Launch the WCM Client from the control panel.

2Click Debug Settings to launch the WCM Debugging window.

3Select the Debug Mode from one of the following options:

???File Logging ??? This is the default option and stores debug messages in the wcmdebug file in C:\Users\Public\Documents on WE8S and WES7 thin clients, or in C:\Documents and Settings\All Users\Documents\Wyse on WES2009 thin clients.

???Verbose ??? This option sends debug messages to the Microsoft DbgView utility running locally on the thin client.

4Select the Debug Level from one of the following options:

???Level 1 (Informational) ??? Includes informational messages only.

???Level 2 (Errors) ??? Includes informational messages and error messages only.

???Level 3 (Debug) ??? Includes informational messages, error messages, and debugging messages.

5Click OK to apply the debug settings.

Typical Use Case Scenarios

This section describes the typical use case scenarios that can be performed using the Wyse Configuration Manager (WCM).

Case 1 - Using a Single Configuration for Multiple Thin Client Users

If you have multiple thin client systems with the same operating system installed on them (WE8S,WES7, or WES2009), you can use a single configuration to configure all the systems.

To perform this activity:

1Log in as Administrator into any one of the thin client systems.

2Ensure that the thin client system has the latest version of WCM Client installed on it.

3Configure the thin client using the operating system functions.

4Launch the WCM Client from the control panel.

5Click Export Configuration to export the configuration file to a remote location on the repository server. For more information, see Exporting Thin Client Configurations.

6Ensure that the other thin client systems are able to connect to the repository server.

For more information on configuring the repository and the DNS/DHCP servers, see Configuring the Repository Server and Discovery Settings for the WCM Server.

The thin client systems can connect to the Repository Server, download the exported configuration file, and apply the configurations automatically.

Case 2 - Using Multiple Configuration Files for Multiple Thin Client Users

If you have multiple thin client systems with the same operating system installed on them (WE8S,WES7, or WES2009), you can create multiple user specific configuration files and configure other thin clients running the same operating system.

To perform this activity:

1Log in as Administrator into the thin client systems.

2Ensure that the thin client systems have the latest version of WCM Client installed on them.

3Configure multiple thin client systems using the Operating System functions.

4Use the Export Configuration option on the WCM Client to export the configuration files to a remote location on the Repository Server. For more information, see Exporting Thin Client Configurations.

5Ensure that you place the configuration files in user specific folders on the Repository Server.

The other thin clients running WE8S, WES7, WES2009 run the WCM Client to retrieve and apply user specific configuration files through the network using their specified user log-in credentials.

Case 3 - Editing Specific Configuration Files for Thin Client Users

If you have created user specific configuration files for thin client users, then you can edit specific files and update the configurations as per the request of the users and enable them to update their systems.

To perform this activity:

1Log in as Administrator into the specific thin client system where you have created a user specific configuration file.

2Change the configuration of the system using the Operating System functions.

3Use the Export Configuration option on the WCM Client to export the changed configuration file to the user specific folder on the Repository Server.

4You can then log out and log in to the thin client system where you want the changes, and retrieve the configuration file from the Repository Server through the DNS/DHCP connection. For more information on configuring the Repository and the DNS/DHCP servers, see Configuring the Repository Server and Discovery Settings for the WCM Server.

Case 4 - Selecting Specific Configuration Files Using a Thin Client on the Network

If you want to revert to any of the previous configurations for the thin client system, perform the following steps:

1Log in as Administrator into the thin client system.

2Launch the WCM Client on the system.

3Click Configuration History. The five most recent and successfully imported configuration files are displayed.

4Select configuration file you want to import from the list.

5Click Import to apply the file to the thin client system immediately.

6You can check the Import configuration on every boot option in the

Import Configuration screen to import the configuration everytime you log in to the system.

Case 5 - Applying Specific Configuration Files to a Mobile Thin Client

If you receive a user request to access a user specific configuration file from a home network, perform the following steps:

1Log in to the Repository Server as an administrator.

2Navigate to the user specific folder location to access the configuration file.

3Place the file on a HTTP server in a demilitarized zone (DMZ).

A DMZ is a computer host or a small network inserted as a neutral zone between a private network within the company and the public network outside the company.

4Instruct the user to log in and connect to the HTTP server through the home network.

5When the user logs in, the configuration settings are applied to the mobile thin client from the HTTP server over the home network.

Case 6 - Applying Configuration Files for New or Different Thin Client Users

If you want to re-configure a thin client for a new or a different user, perform the following steps:

1Log in to the Repository Server as administrator and launch the WCM GUI.

2Edit the configuration settings in an existing file. For more information, see Editing Existing Configuration Files.

3Copy the configuration file to a USB key.

4Log in as administrator into the thin client system that you want to re- configure.

5Launch the WCM Client on the thin client system and click the Import Configuration option.

6Insert the USB key to the thin client, select Local, and enter the USB path of the configuration file.

7Click Import to remove all the previous configurations and apply the desired configurations from the local USB key.

Appendix

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 the repository server to deploy your configuration files and your thin clients access the configuration files automatically through FTP, HTTP, or HTTPS, the process by which the configuration files are obtained by the WCM agent on the thin client is in the following order:

1DNS Service Lookup ??? Note that this is only if the remote deployment option is implemented. For more information, see DNS Service Record Lookup.

2DNS Hostname Lookup ??? Note that this is only if the remote deployment option is implemented. For more information, see For more information, see DNS Service Record Lookup.

3DHCP Options ??? For more information, see DHCP Option Tags Lookup.

4Configured location where you placed the configuration file, which could be 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 screen in the WCM Client.

For more information, see Importing Thin Client Configurations.

???Remote Location ??? such as a remote server location that you set in the Remote option of the Import Configuration screen in the WCM Client.

For more information, see Importing Thin Client Configurations.

Appendix 81

5Local Factory Default Files ??? If the values necessary to find the configuration file are not successfully obtained from DNS, the WCM agent tries the DHCP Options, and so on.

If there is no location set in the Import Configuration screen on the thin client, or if the thin client cannot reach these locations, the thin client uses the factory default WESConfig.xml, or WES7Config.xml, or the WESConfig.xml file on the thin client. This is the latest configuration file updated to the folder on the thin client.

The local default configuration file location for the WES2009 (WESConfig.xml), WES7 (WES7Config.xml), WE8S (WE8SConfig) files is C:\Program Files\Wyse\WCM\Agent.

82 Appendix