Specifications

20 Chapter 3
Reference Information: Typical Use Case Scenarios
Typical use case scenarios include:
• Case 1 - Using a Single Configuration File for Multiple Thin Client Users:
An administrator, with multiple thin clients running WES7, configures one thin client
running WES7 using the operating system functions. The administrator then exports
the configurations to a configuration file (using Wyse Configuration Manager) and
places it on a server where the other thin clients running WES7 (containing the WCM
Client) can power on and retrieve and apply the configuration file through the network
using DHCP.
• Case 2 - Using Multiple Configuration Files for Multiple Thin Client Users:
(For Users that have Joined the Domain) An administrator, with multiple thin clients
running WES7, configures several thin client running WES7 using the operating
system functions. The administrator then exports all of the configuration files (using
Wyse Configuration Manager) and places them on a server in user-specific folders
where other thin clients running WES7 (containing the WCM Client) can 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:
(For Users that have Joined the Domain) An administrator, using Wyse Configuration
Manager, changes a configuration in an existing configuration file (for example, a user
request for a monitor resolution change). The administrator then exports the modified
configuration file and places it in the user’s folder. The user can then log off and log on
to retrieve and apply the configuration file through the network using DHCP.
• Case 4 - Selecting Specific Configuration Files Using a Thin Client on the
Network:
An administrator feels that a change in an existing configuration file (for example, a
monitor resolution change) is no longer desired and they want to return a previous
configuration. The administrator can open and use the installed WCM Client
(administrator Control Panel applet on the thin client) to select the previous/desired
configuration file (from the Configuration History dialog box) and apply it on every boot
using the Import feature.
• Case 5 - Applying Specific Configuration Files to a Mobile Thin Client:
(For Users that have Joined the Domain) An administrator receives a user request to
access the user’s specific configuration file from a home network. The administrator
places the user-specific configuration file on an HTTP server (on a demilitarized zone/
DMZ - a computer host or small network inserted as a “neutral zone” between a
company’s private network and the outside public network) and then instructs the user
to log in and connect to the HTTP server through the home network. Upon logon, the
user settings are applied to the mobile thin client by HTTPS on the home network.
• Case 6 - Applying Configuration Files for New/Different Thin Client Users:
An administrator using Wyse Configuration Manager needs to re-configure a thin client
for a new/different user (for example, a previous user is no longer with the company).
The administrator changes the required configurations in an existing configuration file
(for example, RDP connections) and selects a Wyse Configuration Manager option to
remove any previous settings before applying the new configuration file. The
administrator then copies the configuration file onto a USB key, opens the installed
WCM Client (administrator Control Panel applet on the thin client), uses the Import
Configuration dialog box (to select the local option and specify the USB path of the
configuration file to be imported), and then uses the Import command button to remove
all previous configurations and apply the desired configurations from the local USB
key.