geh-6849 control server dell wyse windows 7 thin client€¦ · 8 geh-6849d control server dell...

GEH-6849D

Control ServerDell™ Wyse™ Windows® Embedded Standard 7Thin Client HMI SystemSupport and Maintenance Guide

Feb 2019

Public Information

These instructions do not purport to cover all details or variations in equipment, nor to provide for every possiblecontingency to be met during installation, operation, and maintenance. The information is supplied for informationalpurposes only, and GE makes no warranty as to the accuracy of the information included herein. Changes, modifications,and/or improvements to equipment and specifications are made periodically and these changes may or may not be reflectedherein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or tothe document itself at any time. This document is intended for trained personnel familiar with the GE products referencedherein.

GE may have patents or pending patent applications covering subject matter in this document. The furnishing of thisdocument does not provide any license whatsoever to any of these patents.

Public Information – This document contains non-sensitive information approved for public disclosure.

GE provides the following document and the information included therein as is and without warranty of any kind,expressed or implied, including but not limited to any implied statutory warranty of merchantability or fitness forparticular purpose.

For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE SalesRepresentative.

Revised: Feb 2019Issued: Dec 2016

© 2016 - 2019 General Electric Company.___________________________________* Indicates a trademark of General Electric Company and/or its subsidiaries.All other trademarks are the property of their respective owners.

We would appreciate your feedback about our documentation.Please send comments or suggestions to [email protected]

Public Information

mailto:[email protected]

Document UpdatesRevision Location Description

DThin Client Terminal Reported as Offline

New sectionsThin Client Host Name Modification

C

Edit Timezone Settings

Removed content and replaced with a reference to the section ConfigureDomain Controllers to Synchronize to Site Time References for theprocedure to configure the Domain Controllers to synchronize to thesystem Time Server

Verify Thin Client Time Synchronization to DomainControllers

Changed the title of this section from Configure Thin Clients to Follow theSystem Time Server, and provide the procedure to verify the successfulsynchronization of the Thin Client to the Domain Controllers

Verify Domain Controller Time Synchronization

Added a reference to the Control Server — Domain Services MaintenanceGuide (GEH-6845), the section Configure Time on Domain Controllers forthe procedures to verify the Domain Controller time synchronizationconfiguration and status, as well as to modify the Domain Controller timesettings if required.

Remote Desktop Connection Unknown PublisherWarnings

Added this section to provide information on the warning displayed whenlaunching a Remote Desktop Connection from a desktop link

B

Edit Display Settings

Replaced the figure Default Display Settings showing updated defaultsettings such as the Default Display Configuration setting for Monitor 1Display Settings

Added references to sections containing additional information on monitorconnection and arrangement, and configuring Thin Client display settingsbased on monitor connection and arrangement

Common Procedures

Added the following sections with procedures for monitor connection andarrangement, and display setting configuration:

• Connect Monitors to Thin Client Terminal

• Configure Thin Client Display Settings

A

Remote Desktop Services OverviewAdded this chapter with an overview on system setup for multipleconfigurations for Remote Desktop Services (RDS)

Remote Desktop Services Connection IssuesAdded this section to provide details on possible connection errors andissue resolution

Launch RD Licensing Diagnoser ToolAdded this section with the procedure to launch the RD LicensingDiagnoser tool

Check Location and Status of RDS License ServerAdded this section with the procedure to check the Location and Status ofthe RDS License Server

Restart RDS License ServerAdded this section with the procedure to restart the RDS License serviceon the VM hosting the RDS License Server information

Determine Number of Available Client Licenses inRDS License Server

Added this section with the procedure to determine the number of installedand available RDS Per Device CAL licenses

Manage RDS Per Device CALs

Added the following sections containing procedures:

• Launch RD Licensing Manager

• Determine Number of Available (Unused) RDS Per Device CALs

• Revoke Unused Device CAL

Manage User Sessions on HMI VMsAdded the following sections containing procedures:

• View Active and Disconnected User Sessions

• Close Disconnected User Sessions

Glossary of Terms

Added the following definitions:

• Client Access License (CAL

• Remote Desktop Session Host Server

• RDS Per Device CAL

GEH-6849D Support and Maintenance Guide 3Public Information

Acronyms and AbbreviationsCAL Client Access LicenseDHCP Dynamic Host Configuration ProtocolEWS Engineering WorkstationFBWF File Based Write FilterHEX Hexadecimal {0-9, A-F}HMI Human-machine InterfaceHTTPS Hypertext Transfer Protocol SecureMAC Media Access ControlPDH Plant Data HighwayRDP Remote Desktop ProtocolRDS Remote Desktop ServicesUDH Unit Data HighwayVM Virtual MachineWCM Wyse Configuration ManagerWES Windows Embedded Standard

Related DocumentsDocument # TitleGEH-6840 NetworkST 3.1/4.0 for Mark VIe Controls Application GuideGEH-6846 Control Server Installation and Startup GuideGEH-6847 Control Server Dell Wyse Windows Thin Client Secure Deployment Guide

GEH-6850 Control Server Dell Wyse Windows Thin Client User GuideGEH-6721_Vol_I Mark VIe and VIeS Controls Volume I: System Guide

4 GEH-6849D Control Server Dell Wyse Windows 7 Thin Client GEH-6849Public Information

Contents1 Thin Client HMI System Overview................................................................................................ 91.1 Introduction............................................................................................................................................91.2 HMI Architecture ....................................................................................................................................91.3 Thin Client Operation and Support Infrastructure ......................................................................................... 121.4 System Configuration and Maintenance Requirements .................................................................................. 14

2 Thin Client Configuration Overview .......................................................................................... 153 Thin Client Configuration Procedures ...................................................................................... 173.1 Configure Thin Client Configuration Server................................................................................................ 173.1.1 Thin Client Configuration Server Information File................................................................................. 173.1.2 Define Thin Client Topology - Create Clients.csv File............................................................................ 18

3.2 Integrate and Deploy Thin Client Terminal ................................................................................................. 193.2.1 Thin Client Terminal Preparation and Integration .................................................................................. 193.2.2 Thin Client Terminal Deployment ...................................................................................................... 29

3.3 Create and Deploy Thin Client Configuration Files ...................................................................................... 313.3.1 Add Resource Files ......................................................................................................................... 323.3.2 Create Thin Client Configuration Template Files................................................................................... 323.3.3 Assign Template Files to Thin Clients (Edit Clients.csv) ......................................................................... 333.3.4 Deploy Thin Client Configuration Files ............................................................................................... 33

4 Dell Wyse Configuration Manager (WCM)................................................................................ 374.1 Launch WCM ....................................................................................................................................... 374.2 Edit a Configuration File ......................................................................................................................... 384.3 Default Configuration Template File Overview............................................................................................ 404.4 Example: Edit Default Configuration Template File for Common Thin Client Settings for Site ............................. 414.4.1 Edit Display Settings ....................................................................................................................... 424.4.2 Edit Mouse Settings......................................................................................................................... 434.4.3 Edit Keyboard Settings..................................................................................................................... 434.4.4 Edit Timezone Settings .................................................................................................................... 444.4.5 Edit Ethernet Settings ...................................................................................................................... 444.4.6 Edit Wireless Settings ...................................................................................................................... 454.4.7 Edit Audio Settings ......................................................................................................................... 454.4.8 Edit Power Settings ......................................................................................................................... 464.4.9 Edit Options/Agent Settings .............................................................................................................. 46

4.5 Example: Create a Client-specific Template File from the Default Template File................................................ 484.6 Example: Create a New Client Specific Template File from an Existing Site Specific Template File ...................... 52

5 USB Drive Support ......................................................................................................................... 535.1 Enable File Sharing................................................................................................................................ 535.2 File Share Persistence ............................................................................................................................. 545.3 File Share Removal................................................................................................................................ 54

6 Remote Desktop Services Overview ......................................................................................... 557 Troubleshooting Thin Client Configuration Server Issues.................................................. 577.1 Successful Thin Client Configuration Download Sequence Example ............................................................... 577.2 Failed Thin Client Configuration Download Sequence Example ..................................................................... 587.3 No Client Requests Received ................................................................................................................... 59


7.4 Configuration Files Cannot Be Found ........................................................................................................ 59

8 System Configuration and Maintenance Use Cases............................................................. 618.1 Failed Dell Wyse Thin Client ................................................................................................................... 618.2 Deploy New Thin Clients at Site Following Factory Acceptance Test .............................................................. 638.3 Deploy All Thin Client Terminals Example ................................................................................................ 638.4 Deploy Thin Client Terminals by Name Example......................................................................................... 658.5 Deploy Thin Client Terminals by MAC Address Example ............................................................................. 668.6 Change Local Thin Client Default Account Passwords.................................................................................. 668.7 Verify Thin Client Time Synchronization to Domain Controllers..................................................................... 668.8 Verify Domain Controller Time Synchronization ......................................................................................... 67

9 Troubleshooting Scenarios ......................................................................................................... 699.1 Thin Client Login Failure ........................................................................................................................ 699.2 Failure to Establish RDP Connection to Host .............................................................................................. 709.2.1 Incorrect User Credentials ................................................................................................................ 709.2.2 Network Connection Issue or Target Host (VM) is Offline ...................................................................... 719.2.3 Remote Desktop Services Connection Issues ........................................................................................ 71

9.3 Failure to Update Thin Client Configuration ............................................................................................... 729.4 Remote Desktop Connection Unknown Publisher Warning ............................................................................ 729.5 Thin Client Terminal Reported as Offline ................................................................................................... 73

10 Common Procedures .................................................................................................................. 7510.1 Thin Client Account Login ...................................................................................................................... 7510.1.1 Local User Account Login ................................................................................................................ 7510.1.2 Local Administrator Account Login.................................................................................................... 75

10.2 Local Thin Client Account Password Reset................................................................................................. 7610.2.1 Thin Client Local User Account Password Reset ................................................................................... 7610.2.2 Thin Client Local Administrator Account Password Reset ...................................................................... 77

10.3 Thin Client Hardware and Software Information.......................................................................................... 7810.3.1 Product Information Tag................................................................................................................... 7810.3.2 System Information ......................................................................................................................... 79

10.4 Verify Thin Client Network Connection ..................................................................................................... 8010.4.1 Verify Connection Status .................................................................................................................. 8010.4.2 Verify IPAddress Assignment from DHCP .......................................................................................... 81

10.5 Verify Domain Name Server (DNS) Status ................................................................................................. 8210.6 Verify DHCP Server Status...................................................................................................................... 8210.7 Verify Thin Client Domain Network.......................................................................................................... 8310.8 Thin Client Configuration Server Files Location .......................................................................................... 8510.9 File Based Write Filter............................................................................................................................ 8610.9.1 File Based Write Filter Status ............................................................................................................ 8610.9.2 Enable/Disable File Based Write Filter ................................................................................................ 86

10.10Open Administrator Mode PowerShell Window on Thin Client ..................................................................... 8710.11Open Administrator Mode PowerShell Window on Windows Server 2012 R2 .................................................. 8710.12Launch RD Licensing Diagnoser Tool ...................................................................................................... 8710.13Check Location and Status of RDS License Server ...................................................................................... 8910.14Restart RDS License Server.................................................................................................................... 9210.15Determine Number of Available Client Licenses in RDS License Server ......................................................... 9310.16Manage RDS Per Device CALs ............................................................................................................... 93


10.16.1Launch RD Licensing Manager ......................................................................................................... 9310.16.2Determine Number of Available (Unused) RDS Per Device CALs............................................................ 9310.16.3Revoke Unused Device CAL............................................................................................................. 94

10.17Manage User Sessions on HMI VMs ........................................................................................................ 9510.17.1View Active and Disconnected User Sessions....................................................................................... 9510.17.2Close Disconnected User Sessions ..................................................................................................... 95

10.18Connect Monitors to Thin Client Terminal................................................................................................. 9610.19Configure Thin Client Display Settings ..................................................................................................... 9710.19.1Single and Dual Monitor Configurations ............................................................................................. 9710.19.2Configure Three or More Monitors (Local Configuration of Thin Client Terminal) ...................................... 99

10.20Thin Client Host Name Modification .......................................................................................................101

Glossary of Terms ..............................................................................................................................103


Notes


1 Thin Client HMI System Overview1.1 IntroductionControl Server is a virtualized platform that can be used to integrate the traditional features provided by Workstations,Historians, and Communication Gateways. The Human-machine Interface (HMI) architecture involves a client-server system,using Thin Client terminals, that view virtual HMIs through a centralized Control Server. This system also provides anintegrated, supervisory control platform, which allows control applications to be developed and deployed in an integrated,tiered control architecture.

The intended audience of this document is the site maintenance engineer responsible for ensuring proper system operation.The document scope is limited to Thin Client terminals and the Thin Client support infrastructure. Procedures such as thefollowing examples are provided in this document:

• How to diagnose and fix issues that may occur as the result of component failures over time• How to make small system configuration changes to support changes in the plant over time

1.2 HMI ArchitectureTraditional control system architecture uses stand-alone HMI desktop computers (thick clients) to provide physical interfaceto the system. Control system software processes are distributed across the HMI computers on the plant network (PDH).

Traditional Thick Client Control System Architecture

The Control Server approach uses HMI Virtual Machines (VMs) running on a server and Thin Client terminals in place ofstand-alone HMIs (thick clients).

Thin Client HMI System Overview GEH-6849D Support and Maintenance Guide 9Public Information

The following figure displays a Control Server architecture that uses a dedicated Thin Client terminal for each HMI VM. Inthis example, Thin Client 1 is dedicated to hosting connections to HMI1 VM, while Thin Client 2 is dedicated to HMI2 VM,and so forth.

HMI1

VM

HMI2

VM

HMI3

VM

��

��

��

� ��

��

One Thin Client to One HMI VM (One-to-One) Architecture


Another architecture choice is the many-to-one architecture, multiple Thin Clients connect to a single HMI VM as shown inthe following figure. Each Thin Client establishes a user session over an Remote Desktop Protocol (RDP) connection to theHMI VM, resulting in concurrent user sessions on the VMs. Typical systems will have more than one HMI VM.

HMI1

VM

��

��

��

� ��

��

HMI2

VM

Many Thin Clients to One HMI VM (Many-to-One) Architecture


1.3 Thin Client Operation and Support InfrastructureThin Client configurations are centrally managed from the Control Server. Thin Client configurations are used to manage theconnections to the VMs running on the Control Server. From the user’s perspective, the Thin Clients are merely remoteterminals that provide the interface to the system and provide no useful functionality when disconnected from the system. TheThin Clients function as plug-and-play devices that do not rely on persistent local configuration information. The followinginfrastructure is maintained in the system to achieve the central management and client plug-and-play deployment of the ThinClients:

• Dynamic Host Configuration Protocol (DHCP) Server: the Thin Clients use DHCP to obtain their networkconfiguration. Thin Clients are configured out of the box to use DHCP. In the Controls Server architecture, the domainservers act as the DHCP servers.

• Thin Client Configuration Server: the Hypertext Transfer Protocol Secure (HTTPS) server hosting the Thin Clientconfiguration and software files is typically hosted on the Engineering Workstation (EWS) VM, since the EWS providesmost of the centralized configuration and Change Management System services.

The following figure illustrates a simple system with both the HMI VMs and infrastructure VMs required to use and managethe Thin Clients.

Example Thin Client System HMI VM Infrastructure


A general overview of system components and data flow are provided in the following diagram. This is an example scenariowhen one of the Thin Clients in the system has been powered off for some time and is restarting. The numbered sequence forstartup and data flow between the Thin Clients and the VMs (running within the Control Server) is explained in the followingtable.

System Components and Data Flow Overview Diagram

Startup Numbered Sequence and Data Flow Diagram Notes

# Description

1The Thin Client starts up, then broadcasts a DHCP request for its network configuration. DC1 (the system domaincontroller) responds to this request with the IP address assigned to the Thin Client.

2The Thin Client connects to the Thin Client configuration server and downloads and executes its client-specificconfiguration file stored on the server.

3The connection to the target VM is automatically established by the Thin Client or manually by the user according tothe configuration file settings.

The Thin Client has completely configured itself using the configuration files on the EWS server. From the user’s perspective,there is little difference between the legacy thick client system (the user interacts directly with the local HMI), and the ThinClient HMI system (the user interacts with the remote HMI VM on the Control Server from the local Thin Client terminal).


1.4 System Configuration and Maintenance RequirementsThe system elements related to supporting the Thin Clients and an overview of their configuration and maintenancerequirements are provided in the following table.

System Element Description

DHCP ServersThe Domain Controller VMs (DC1 and DC2) are configured as redundant DHCP servers used byThin Clients to retrieve their IP Address.

Thin ClientConfiguration Server

The Thin Client’s configuration is centrally managed from the Configuration Server. The majority ofThin Client configuration work is done by managing the files on the Thin Client Configuration Server.The Thin Client configuration files are downloaded from the server and processed as part of the ThinClient startup sequence. The Thin Client configuration is entirely driven by the configuration files thatare created and maintained on the server.

Thin Client Terminals

AThin Client is a purpose-built computer with a keyboard, mouse, monitor, and an Ethernetconnection to the plant network. The Thin Client’s primary function is to provide an access point tothe Control Server VMs and other servers. Thin Clients are configured by the System Administratorto provide a predefined set of server connections through managing the entries in the configurationfiles stored on the Thin Client Configuration Server. Thin Client terminals can be configured toprovide a dedicated connection to a single VM, or to allow the user to initiate connections asneeded. Over the life of the system, circumstances can arise that may require minor modifications tothe INI files, such as the need to replace a failed Thin Client terminal. These scenarios and therequired INI file modifications are documented in this manual.


2 Thin Client Configuration OverviewThin Client configuration is performed in two stages: Stage one involves integration and deployment of the terminals into theControl Server infrastructure. This process is only required to be done once on each terminal. Stage two includes creating theThin Client terminal specific configuration files and deploying them on the Thin Client Configuration Server. Theconfiguration files are used to define the appearance and behavior of the Thin Client terminals. Each Thin Client downloadsthe configuration files from the Configuration Server. Configuration file editing and deployment is performed during initialconfiguration of the terminals and whenever configuration changes are made over the life of the system.

System Level Configuration

• If the system is not set up with a standard server configuration, create and edit the Server.csv file to reflect the Thin ClientConfiguration Server address, protocol, and port.

• Create and edit the Clients.csv file to manage the Thin Client terminals.

Stage 1: Prepare and Deploy Thin Client Terminals (performed once per terminal)

• Prepare the Thin Client terminals (add each terminal to the domain network and remove unused software for securityhardening purposes).

• Deploy the Thin Client terminals (server information is pushed to the clients from the server).

Stage 2: Create and Deploy Thin Client Configuration Files (performed during initial configuration andwhenever configuration changes are made)

• Use the Dell Wyse Configuration Manager (WCM) tool to create Thin Client configuration template files.• Edit Clients.csv to assign the configuration template files to the Thin Client terminals.• Deploy the Thin Client configuration template files to the Thin Client Configuration Server for download by the Thin

Clients.

Note There is no dependency between the two stages of Thin Client configuration. The configuration files can be createdand deployed on the Thin Client Configuration Server regardless of whether the physical Thin Client terminals have beendeployed. Conversely, Thin Client terminals can be deployed regardless of whether the configuration files have been createdfor them; they will download a default configuration until a specific configuration file becomes available for them on the ThinClient Configuration Server.

Thin Client Configuration Overview GEH-6849D Support and Maintenance Guide 15Public Information

Notes


3 Thin Client ConfigurationProceduresThis chapter provides the standard procedures required to configure the Thin Client Configuration Server and the Thin Client:

• Configure Thin Client Configuration Server• Integrate and Deploy Thin Client Terminal• Create and Deploy Thin Client Configuration Files

3.1 Configure Thin Client Configuration ServerThe Thin Client Configuration Server is used to create the Thin Client configuration files and make them available to the ThinClients for download as needed. The Thin Client Configuration Server is typically hosted by the EWS VM, and is loaded withtemplate configuration files and Windows PowerShell scripts used to manage Thin Client configurations.

3.1.1 Thin Client Configuration Server Information FileThe Server.csv file can be used to change the Thin Client Configuration Server information for the site in the rare event thatthe default values are not used at the site. Default values are provided in the ServerTemplate.csv file, as follows:

Protocol, Server, Port#—————— ———————————— ——HTTPS, 172.16.201.22, 924

If the default values must be changed for the site, open the %SystemDrive%\intepub\WCM-Templates folder, copy theServerTemplate.csv file to Server.csv, and edit the values to match those used by the site. The Server.csv file is used as thesource for the utilities that need the server information.

Thin Client Configuration Procedures GEH-6849D Support and Maintenance Guide 17Public Information

3.1.2 Define Thin Client Topology - Create Clients.csv FileThe Clients.csv file is the central point for managing the Thin Clients and their configurations. The%SystemDrive%\intepub\WCM-Templates folder contains an empty ClientsTemplate.csv file as a starting point for creating the site-specific Clients.csvfile. The first step in configuring the Thin Clients in a new system is to copy ClientsTemplate.csv to Clients.csv, then addentries for each Thin Client. The Clients.csv file provides the inventory of Thin Client terminals at the site and should includeentries for any spare terminals available at the site. The following example is a Clients.csv file that has been configured withsite information:

Example Clients.csv FileClient, Type, MACAddress, Template, Description#——————— ——— —————————— —————————— ————————————————————————Default7, WES7, *, Default, Default WES7 ConfigurationGT1, WES7, 008064F60EFE, Default, PECC for GT1GT2, WES7, 008064F60F8D, Default, PECC for GT2ST1, WES7, 008064F6129E, Default, PECC for ST1CRM-Main, WES7, 008064F6100D, Default, Control Room Main DisplayCRM-Eng, WES7, 008064F612AF, Default, Control Room EngineeringSpare1, WES7, 008064F609D1, Default, Spare Windows Thin Client #1Spare2, WES7, 008064F61028, Default, Spare Windows Thin Client #2

Clients.csv File ColumnsColumn DescriptionClient Descriptive name used to uniquely identify each Thin ClientType Thin Client type must be either WES7 (Windows 7) or WES10 (Windows 10)MACAddress MAC address of the Thin Client terminal to be applied to this location (12 HEX digits)Template Name of the configuration template file used by the clientDescription Free-form description of the client

Note Additional information and examples are provided in the ClientsTemplate.csv file.

Note In many circumstances, the physical Thin Client terminals will not be available at the time the system is beingconfigured. Enter the MAC addresses of any temporary terminals that will be used during staging of the system, before theactual Thin Client terminals become available in the lab or at the site. Leave the MAC entries blank for any terminals that arenot part of the system staging activity or have not arrived at the site.

Note It is recommended that Clients.csv file include entries for all spare terminals so that a spare terminal can be quicklyapplied since all of the information about the spare terminal will already be available in Clients.csv. This also allows Clients.csv to act as the centralized database for the Thin Client terminals at the site.


3.2 Integrate and Deploy Thin Client TerminalThin Clients must be integrated and deployed into the Control Server infrastructure before they can download theirconfiguration files from the Thin Client Configuration Server.

3.2.1 Thin Client Terminal Preparation and IntegrationThe Thin Client terminals must go through a preparation process that integrates them into the Control Server infrastructurebefore they can be deployed in the Control Server infrastructure. Preparation procedures include adding the terminals to thedomain network and removing unused software for security hardening purposes. Preparation procedures must be performedon each Thin Client and are independent of any site-specific configuration, which allows them to be performed on the ThinClient terminals as soon as they (and the Control Server infrastructure) become available.

Attention

It is critical to perform all procedures outlined in the following sections. All stepswithin each section must be performed exactly as documented and in the orderprovided. The overall procedure is divided into three parts to make the process moreunderstandable, but the sections are interdependent and must be performed fromstart to finish as a coherent set in the following order:

1.) Connect the Thin Client to the PDH network.

2.) Remove unused software.

3.) Join the Domain Network and apply group policy.

Note It is recommended that these procedures be performed on all available clients, including spare units, so that in theevent of a terminal failure the prepared spare can replace the failed unit without having to go through the preparation processin a potentially time critical situation. Spare units can be temporarily connected to the network, configured, and returned tostorage until they are needed.

3.2.1.1 Determine if Preparation is RequiredAny Thin Client terminal that has just been removed from its sealed packaging needs to be prepared. If the state of the clientis unclear, preparation must be verified before the terminal can be deployed in the system. The terminal’s preparation statuscan be checked by verifying the terminal’s Domain network membership. For instructions, refer to the section Verify ThinClient Domain Network.

Note If the terminal is a member of the default WORKGROUP domain it needs to be added to the domain network.


3.2.1.2 Connect Thin Client to PDH Network

➢➢ To connect the Thin Client to the PDH network and verify the connection

1. Connect the monitor(s), keyboard, and mouse to the client and connect the client to the PDH network.

2. Connect the power supply and turn on the client.

3. The Thin Client will automatically log in to the local User account. Use the Start menu Log off button or the [CTRL][ALT] [DEL] key sequence to log out.

4. Hold the shift key down until the User and Administrator log in buttons are displayed on the desktop.

5. Select the Administrator button to log in as the local Administrator.

Note The default local Administrator password and User password is DellCCCvdi.

6. Disable the File Based Write Filter and reboot the Thin Client. Refer to the procedure To disable the File Based WriteFilter.

7. The Thin Client will automatically log in to the local User account. Log off and hold the shift key down and log in to thelocal Administrator account (steps 3 – 5).

8. From the Start menu, launch theWindows Control Panel and select Network and Sharing Center.

9. Select Public network and change it toWork network.

Windows Control Panel Network and Sharing Center Public Network


Windows Control Panel Network and Sharing Center Work Network

10. Click Cancel to close the dialog box.

11. Select Change Adapter Settings.

Windows Control Panel Network and Sharing Center Change Adapter Settings


12. Right-click Local Area Connection, select Rename and enter PDH for the network connection name.

Windows Control Panel Network Connections

13. Right-click the PDH network connection, select Properties, and select the items as follows:

a. Deselect (uncheck) the following items:

i. Link-Layer Topology Discovery Mapper I/O Driver

ii. Link-Layer Topology Discovery Responder

iii. Reliable Multicast Protocol

iv. Internet Protocol Version 6 (TCP/IPv6)

b. Verify the following items are selected (checked):

i. Client for Microsoft Networks

ii. File and Printer Sharing for Microsoft Networks

iii. QoS Packet Scheduler

iv. Internet Protocol Version 4 (TCP/IPv4)


PDH Network Properties Dialog Box

14. Select OK to accept the changes and close the PDH Properties dialog box.

15. Right-click on the PDH Network and select Disable.

16. Right-click on the PDH Network and select Enable.

17. Close the Control Panel window.

18. Verify the PDH Network connection is active. For instructions, refer to section Verify Thin Client Network Connection.


3.2.1.3 Remove Unused SoftwareThe next step in preparing the Thin Clients is to remove unused software.

➢➢ To remove unused software

Attention

Uninstall the software packages exactly as instructed in the order given.

Note xx or x.x represents software application versions.

1. From the Start menu, launch theWindows Control Panel and select Programs and Features.

Windows Control Panel Programs and Features

2. Uninstall VMware Horizon Client as follows:

a. Right-click VMware Horizon Client and select Uninstall.

b. Click Yes to confirm the uninstall.

c. Click No when the dialog is presented asking whether to reboot the Thin Client.

d. Press the F5 or refresh to update the display and verify the uninstall was successful.


3. Uninstall Citrix Receiver as follows:

a. Right-click Citrix Receiver and select Uninstall.


Expect a delay of ~60 seconds before the uninstall begins. Citrix Receiver will be removed from the displayed list ofinstalled programs.

4. Uninstall Citrix HDX RealTime Media Engine x.x as follows:

a. Right-click Citrix HDX RealTime Media Engine x.x and select Uninstall.


Citrix HDX RealTime Media Engine x.x will be automatically removed from the displayed list of installed programs.

5. Uninstall vWorkspace Connector for Windows as follows:

a. Right-click vWorkspace Connector for Windows and select Uninstall.


c. Close applications if prompted.

d. Click No when the dialog is presented asking whether to reboot the Thin Client.

e. Press the F5 or refresh to update the display and verify the uninstall was successful.

6. UninstallMicrosoft Lync VDI 2013 as follows:

a. Right-click Microsoft Lync VDI 2013 and select Uninstall.

b. Click Yes to confirm the uninstall from the Microsoft Lync Vdi 2013 dialog box.

c. Click Close after the uninstall is finished.

Microsoft Lync VDI 2013 will be automatically removed from the displayed list of installed programs.

7. Uninstall Adobe Flash Player xx ActiveX as follows:

a. Right-click Adobe Flash Player xx ActiveX and select Uninstall.

b. Click UNINSTALL in the Uninstall dialog box.

c. Click DONE after the uninstall is finished.

Adobe Flash Player xx ActiveX will be automatically removed from the displayed list of installed programs.

8. Uninstall Adobe Flash Player xx NPAPI as follows:

a. Right-click Adobe Flash Player xx NPAPI and select Uninstall.

b. Click UNINSTALL in the Uninstall dialog box.

c. Click DONE after the uninstall is finished.

Adobe Flash Player xx NPAPI will be automatically removed from the displayed list of installed programs.

9. UninstallMicrosoft Silverlight as follows:

a. Right-click Microsoft Silverlight and select Uninstall.


Microsoft Silverlight will be automatically removed from the displayed list of installed programs.

10. Close the Programs and Features window.


3.2.1.4 Join Domain Network and Apply Group PolicyThe final step in the preparation process is adding the Thin Client terminal to the domain network for security hardening andremote configuration management. The Join-WES7.ps1 PowerShell script hosted on the Thin Client Configuration Server isused to perform this procedure.

➢➢ To join the domain network and apply group policy

1. Copy the Join-WES7.ps1 script from the Thin Client Configuration Server to the C:\Wyse folder as follows:

a. Open Windows Explorer and enter the URL of the WES-Procedures shared directory on the Virtual Machine hostingthe Thin Client Configuration Server (typically \\ews\WES-Procedures).

WES-Procedures URL

b. Enter the credentials for a Domain Administrator account when prompted.

Account Credentials Dialog Box

c. Copy the Join-WES7.ps1 script to the C:\Wyse folder of the Thin Client.


Join-WES7.ps1 Script in Thin Client Server’s WES-Procedures Folder

2. Open Windows PowerShell in Administrator mode. For instructions, refer to the section Open Administrator ModePowerShell Window on Thin Client.

3. Issue the Set-ExecutionPolicy Unrestricted –Scope Process -Force command from the PowerShell prompt as shown inthe following figure:

Set-ExecutionPolicy Unrestricted –Scope Process -Force Command

4. Issue the cd c:\Wyse command from the PowerShell prompt as shown in the following figure:

cd c:\Wyse Command

5. Enter Join and press the [tab] key to create the command to run the Join-WES7.ps1 script, followed by the [Enter] keyto execute the command.

Join-WES7.ps1 Script Command


6. When prompted, enter the password for a Domain Administrator account.

PowerShell Domain Administrator Account Credentials

7. The Thin Client will restart, then automatically log in to the local User account. Log in to the Thin Client using the localAdministrator account. For instructions, refer to the section Local Administrator Account Login.

8. Open Windows PowerShell in Administrator mode.

9. Issue the gpupdate /force command from the PowerShell prompt as shown in the figure below. Expect a delay of at least60 seconds for the command to complete.

gpupdate /force Command

10. Enable the File Based Write Filter and reboot the Thin Client. Refer to the procedure To enable the File Based WriteFilter.

11. Allow the client to automatically log in to the Local User account.


3.2.2 Thin Client Terminal DeploymentOnce the preparation process is complete, the Thin Clients can be deployed into the Control Server infrastructure. Thin Clientdeployment involves pushing the Thin Client Configuration Server information to the clients so they know how to get theirconfiguration files. Thin Clients can be deployed individually or as a group after they have been prepared.

Note It is recommended that all Thin Clients (or at least all of the ones that are available) be prepared then deployed as agroup from the Thin Client Configuration Server.

EWS VM

Thin Clients

Clients.csv+

Windows Thin Client Deployment

Configure-WCMClient.ps1

Server Info is pushed to the clients

Legend

Server.csv*

Server.csv is used if it exists, otherwise defaults are used*+ Only clients found in Clients .csv will be configured

The Configure-WCMClient.ps1 script is run from the EWS VM and configures the Thin Clients found in the Clients.csv filewith the required Configuration Server information. The Configure-WCMClient.ps1 script provided in the %SystemDrive%\inetpub\WCM-Templates folder is used to push the Thin Client Configuration Server info to the Thin Clients. TheConfigure-WCMClient.ps1 script uses the entries in the Clients.csv file to discover the Thin Clients. Executing the script withthe –All command line option will remotely configure the Thin Client Configuration Server information for all of the clientslisted in Clients.csv. The –Client option can be used to specify a particular client or group of clients by name. Clients that arenot entered in Clients.csv can be configured by MAC address using the –MAC option.


3.2.2.1 Deploy All Thin clientsAll of the Thin Clients for the system (as defined in the Clients.csv file) can be deployed at one time. Refer to the sectionDeploy All Thin Client Terminals Example for complete details.

➢➢ To deploy all Thin Clients at one time

1. Log in to the VM hosting the Thin Client Configuration Server and launch Windows PowerShell in Administrator mode.Refer to the section Open Administrator Mode PowerShell Window on Windows Server 2012 R2.

2. Move to the %SystemDrive%\inetpub\WCM-Templates directory.

3. Launch the Configure-WCMClient.ps1 script using the –All option.

3.2.2.2 Deploy Thin Clients by NameThin Clients can be deployed individually or in groups by name (as defined in the Clients.csv file). Refer to the sectionDeploy Thin Client Terminals by Name Example.

➢➢ To deploy Thin Clients by name



3. Launch the Configure-WCMClient.ps1 script using the –Client [name] option.

3.2.2.3 Deploy Thin Clients by MAC AddressThin Clients can be deployed individually or in groups by MAC address. Refer to the section Deploy Thin Client Terminals byMAC Address Example.

➢➢ To deploy Thin Clients by MAC address



3. Launch the Configure-WCMClient.ps1 script using the –MACAddress [MAC address] option.

3.2.2.4 Configure-WCMClient.ps1 Status Values

Status Value DescriptionBad MAC Address The MAC address was incorrectly formatted. MAC addresses must contain 12 valid HEX digits.

Cannot Resolve HostnameThe hostname could not be resolved over DNS. This error will occur if the Thin Client has notbeen joined to the domain, which is most likely an indication that the Thin Client preparationprocedure was not performed on the target Thin Client terminal.

Cannot Contact Hostname The Thin Client is offline.Cannot Authenticate toHostname

The user credentials provided were invalid or did not provide administrator privileges on the ThinClient.

Already Configured The Thin Client Configuration Server information was read from the Thin Client and found to becorrect- no action was needed.

Configured The Thin Client Configuration Server information was successfully written to the Thin Client.


3.3 Create and Deploy Thin Client Configuration FilesThe Thin Clients download their configuration files from a web server running on the Thin Client Configuration Server VM.The Thin Client configuration files are created and deployed to the Configuration Server as part of the system requisitionprocess.

The Thin Client configuration files are created and deployed on the VM acting as the Thin Client Configuration Server(typically the EWS VM) as part of the site-specific requisition engineering process. Template files and the configurationscripts used to create the configurations are installed in the%SystemDrive%\inetpub\WCM-Templates folder. Refer to sectionThin Client Configuration Server Files Location for the procedure to locate the configuration files on the server.

The following figure provides an overview of the template files and utilities used to create the Thin Client configuration files.

EWS VM

Thin Client Configuration Server

Configuration (XML) Files

Image Files

Thin Clients

Default.xml

Template.xmlf iles

Image Files

Clients.csv

Deploy-WCMConfiguration .ps1

Windows Thin Client Configuration

Clients download their configuration files at user login

Legend

Note The procedures in this section can be performed without access to the Thin Client terminals. The configurationtemplate files are created and deployed on the server for future download by the Thin Clients when they are deployed in thesystem.


3.3.1 Add Resource FilesThe primary resource file used in the Thin Client configuration is the image used for the desktop wallpaper. A default desktopwallpaper image file (GEDesktop.jpg) is provided in the WCM-Templates\Resources folder. This folder serves as the sourcefor all Thin Client related image files.

Note All custom or client specific images used in the Thin Client configurations should be copied to this location so theycan easily be located when using the Wyse Configuration Manager (WCM) tool to configure the Thin Client template files.

3.3.2 Create Thin Client Configuration Template FilesTheWindows Thin Client Configuration figure shows that the Thin Client configuration files are generated from the Template.xml files. The Template.xml files are configuration files that can be specific to a particular Thin Client or can be used togenerate the configuration files for a group of Thin Clients as shown in the following example Clients.csv file:

Client, Type, MACAddress, Template, Description#———————— ——— —————————— ————————— ———————————————————Default7, WES7, *, Default, Default WES7 ConfigurationGT1, WES7, 008064F60EFE, ToHMI1, PECC for GT1GT2, WES7, 008064F60F8D, ToHMI2, PECC for GT2ST1, WES7, 008064F6129E, ToHMI2, PECC for ST1CRM-Main, WES7, 008064F6100D, ToHMI1, Control Room Main DisplayCRM-Eng, WES7, 008064F612AF, ToEWS1, Control Room EngineeringSpare1, WES7, 008064F609D1, Default, Spare Windows Thin Client #1Spare2, WES7, 008064F61028, Default, Spare Windows Thin Client #2

In this example of a Clients.csv file, the ToHMI1 template file, which creates an RDP connection to the HMI1 VM, is sharedby the GT1 and CRM-Main Thin Clients. The ToHMI2 template file, which creates an RDP connection to the HMI2 VM, isshared by the GT2 and ST1 Thin Clients. The ToEWS1 template file, which creates an RDP connection to the EWS1 VM, isonly applied to the CRM-ENG Thin Client. The use of template files allows sharing of common configuration templates sothat a specific template file does not need to be created for every terminal.

The configuration template file location is dependent on the Thin Client operating system. Windows Embedded Standard 7(WES7) configuration files are located in the %SystemDrive%\intpub\WCM-Templates\WES7 folder. This folder contains thedefault configuration template file (default.xml), which serves as the default configuration used by clients that have not beenassociated with a site-specific configuration. The default configuration template file also serves as the starting point for sitespecific configuration template files.

➢➢ To create Thin Client Configuration template files

1. Edit the default template file to reflect the settings common to all Thin Clients at the site (for example: Timezone).

2. Create client or group specific template files from the default template.

3. Create client or group specific template files from the newly created client or group specific template files.

Note Refer to the chapter Dell Wyse Configuration Manager (WCM) for detailed information about the tool interface and thetemplate file settings, along with examples of using the WCM tool.


3.3.3 Assign Template Files to Thin Clients (Edit Clients.csv)The example Clients.csv file demonstrates how the template files are associated to individual Thin Clients. The configurationtemplate files can be specific to a particular Thin Client terminal, or they can be shared between multiple terminals.

3.3.4 Deploy Thin Client Configuration FilesThe template files must be deployed to the Thin Client Configuration Server to make them available for download by theThin Clients. This is done using the Deploy-WCMConfiguration.ps1 script provided in the %SystemDrive%\inetpub\WCM-Templates folder on the Thin Client Configuration Server.

➢➢ To deploy Thin Client configuration files: launch Windows PowerShell in Administrator mode and execute theDeploy-WCMConfiguration.ps1 script.

Note Refer to the section Open Administrator Mode PowerShell Window on Thin Client for the procedure to launchWindows PowerShell in Administrator mode and execute PowerShell script files.

The Deploy-WCMConfiguration.ps1 script uses the entries in the Clients.csv file to create the required directory structure andcopy the necessary files to the Thin Client Configuration Server. Executing the Deploy-WCMConfiguration.ps1 script willdeploy the configuration files for all of the clients listed in Clients.csv.

Running Deploy-WCMConfiguration.ps1 Script

The script will run silently unless there are errors that need to be addressed. In the following example, there is an error due toa missing template file.

Deploy-WCMConfiguration.ps1 Script Error - Missing Template File


The –Verbose command line option can be used show all of the steps in the deployment process.

–Verbose Command

Additional command line options are available and documented in the Deploy-WCMConfiguration.ps1 script file, whichallow targeted deployment of individual or groups of Thin Clients; however, there is no problem with deploying theconfiguration files multiple times.

Note It is recommended to run Deploy-WCMConfiguration.ps1 against all clients defined in Clients.csv so that all issueswith all client configurations can be addressed.


The following figure shows the results of running the Deploy-WCMConfiguration.ps1 script.

Deploy-WCMConfiguration.ps1 Script Results


A directory based on the MAC Address is created for each Thin Client terminal in the%SystemDrive%\inetpub\wwwroot\WCM\Wyse\WES7\ folder. The terminal specific configuration file (WES7Config.xml) is located at the top level, and theresource files are found in theWES7Config folder.

WES7Config Resource Files

Attention

The directories and files under the configuration deployment folder (%SystemDrive%\inetpub\wwwroot\WCM\Wyse\) must not be changed in any way. The template filescreated and edited in the%SystemDrive\inetpub\WCM-Templates folder serve as theconfiguration source files. They are deployed here in their required format anddownloaded to the Thin Clients using the Deploy-WCMConfiguration.ps1 script.Changes made to these files and directories outside of the Deploy-WCMConfiguraiton.ps1 script will result in Thin Client configuration errors.


4 Dell Wyse Configuration Manager(WCM)The Dell Wyse Configuration Manager (WCM) tool is used to create and edit the Thin Client configuration template files.The WCM tool is installed on the Virtual Machine (typically the EWS VM) where the Thin Client Configuration Server ishosted.

4.1 Launch WCMWCM must be launched in Administrator mode.

➢➢ To launch WCM: right-click the WCM icon on the desktop or Start menu and select Run as administrator. Provideadministrator credentials if requested.

Launching WCM in Administrator Mode

Dell Wyse Configuration Manager (WCM) GEH-6849D Support and Maintenance Guide 37Public Information

4.2 Edit a Configuration File➢➢ To edit a configuration file

1. From the WCM tool, select Open an Existing Configuration.

Open Existing Configuration File from WCM

2. Navigate to and select the template file to be edited, then click Open.


The selected configuration opens and is ready for editing.

Open Configuration File


4.3 Default Configuration Template File OverviewWhen the configuration template file is open in WCM, the left hand navigation pane shows the main configuration areas, andthe right hand pane contains the configuration parameters of the selected configuration area.

Default Configuration Template File Opened in WCM

Main Configuration Areas

Item Description

ConnectionsThe primary focus of the Thin Client configuration. This is where the RDP Connections that will be madeavailable from the Thin Client are added. The default template does not include any preconfigured RDPconnections.

DeviceConfiguration

These are the terminal level settings. Some settings, like the Display settings, can be different betweenclients- for example, multiple monitor settings. Other settings will be common to all Thin Clients at thesite. Only the common parameters should be set in the default configuration template file- these will bediscussed further in the next section.

OS Configuration These settings are typically not used.

Note The blue area under the property grid in the right hand pane displays additional information for the selected property.

Note VMWare View, Citrix, and vWorkspace connections are not used.


4.4 Example: Edit Default Configuration Template File forCommon Thin Client Settings for SiteThe first step in creating the Thin Client configuration template files for the site is to edit the default configuration templatefile. The default configuration template file is used to set the system level settings that are common to all of the Thin Clientsat the site, such as the timezone or server location settings. The default configuration template file is installed on the ThinClient Configuration Server as part of the system configuration, and it provides the typical default values for the commonThin Client configuration values.

The default configuration template file is located at Wyse\WCM\WCM-Templates\WES7\default.xml.

➢➢ To edit default configuration template files: launch the WCM tool in Administrator mode and open the default.xmltemplate file.

Default.xml Template File

Note The common client settings are found in the Device Configuration area.


4.4.1 Edit Display SettingsThe display settings will need to be changed in some cases to match differences in the number of connected monitors andother display considerations, but the baseline display configuration is set up here.

➢➢ To edit the display settings: select the Display setting (check the Display box) in the left hand pane and makechanges as needed.

Default Display Settings

The primary setting to note is the Desktop Wallpaper Settings. The GEDesktop.jpg file is set as the default. A custom imagethat would be applied to all clients can be substituted here. Note also that the Multiple Displays setting is set to Extend thesedisplays by default. This setting works correctly with single and multiple monitors. In some circumstances it might beappropriate to use the Duplicate these displays setting, but this would be a custom setting that would be overridden in anothertemplate created from this one for a specific client or group of clients. The Monitor Display Settings are also set to defaultvalues that are appropriate for most clients which can be overridden as needed in template files created from this defaulttemplate.

Note For additional details on monitor connection and arrangement, refer to the section Connect Monitors to Thin ClientTerminal. For details on configuring the Thin Client display settings based on the resolution and physical arrangement of themonitors connected to the Thin Client terminal, refer to the section Configure Thin Client Display Settings.


4.4.2 Edit Mouse SettingsThe Mouse settings typically do not need to be modified, and are therefore not included (not checked) in the template file.

➢➢ To enable the Mouse settings to make changes: select the Mouse setting (check the Mouse box) in the left handpane and make changes as needed.

Mouse Settings

4.4.3 Edit Keyboard SettingsThe Keyboard settings are defaulted to the English language and are not included (not checked) in the template file.

➢➢ To change the keyboard to a different language for non-English sites or modify the keyboard rate anddelay settings: select the Keyboard setting (check the Keyboard box) in the left hand pane and make changes asneeded.

Keyboard Settings


4.4.4 Edit Timezone SettingsThe Timezone settings are included in the template and are set to Eastern Standard Time by default. Modify the Timezonesetting to reflect the location of the site.

Note The Time Server setting has no effect. The Thin Clients ignore the Time Server setting and synchronize to the DomainControllers because they are domain members. Refer to the section Configure Domain Controllers to Synchronize to Site TimeReferences for the procedure to configure the Domain Controllers to synchronize to the system Time Server.

➢➢ To edit Timezone settings: select the Timezone setting (check the Timezone box) in the left hand pane and makechanges as needed.

Timezone Settings

4.4.5 Edit Ethernet SettingsThe Ethernet settings are included in the template and are set to enable DHCP by default. This value must be set to True forall clients. The other values are not used and should be left blank.

Ethernet Settings


4.4.6 Edit Wireless SettingsThe Wireless Settings are disabled and cannot be edited. The clients are not equipped with wireless adapters, so this sectiondoes not apply.

4.4.7 Edit Audio SettingsThe Audio settings are included in the template and are set to the values shown by default. These values would likely bemodified in other templates depending on the environment the client is in and whether sound is required from the client.

Audio Settings


4.4.8 Edit Power SettingsThe Power settings are included in the template and are defaulted to the values shown. The clients are set to never sleep orturn off their displays by default. This behavior can be modified based on the requirements of the site and the location of theclient. Clients that are in remote locations and are rarely used may be configured to sleep after a period of inactivity, whileclients in the main control room may be required to stay active at all times.

Power Settings

4.4.9 Edit Options/Agent SettingsThe Agent Settings provide the information required for downloading the configuration files from the Thin ClientConfiguration Server. These settings should not be modified for most systems, however these values must be edited to matchthe entries in the Server.csv file in the rare case that a system is using a non-standard Thin Client Configuration Server addressand/ or HTTPS port. The Agent Settings dialog is launched from Options\Agent Settings on the main menu.

➢➢ To launch the Agent settings: from the WCM main application menu, click Options and select Agent Settings.


Agent Settings

Note The default server settings are shown in the figure Agent Settings. Import configuration on every boot and EnableBalloon Tips should always be enabled. Use WDM should always be disabled. The DHCP Tag No. fields do not apply.


4.5 Example: Create a Client-specific Template File fromthe Default Template FileThe default configuration template provides the typical default values for the Thin Client configuration values common to allclients at the site and is used as the starting point for all of the Thin Client configuration files. The primary difference betweenthe different template files is the RDP connections that are created on the Thin Client desktop, and the number of monitorsconnected to the Thin Client. In the following procedure, as an example, we will add an RDP connection to the CRM1 VM.

➢➢ To create a client-specific template file

1. Open the default.xml template file.

2. From the Connections area, right-click RDP and select Add a New RDP Connection.

A new connection named RDP1 is created.

RDP1 Created


3. Rename the connection to CRM1 and add the CRM1 hostname or address and the system domain name.

User Name and Password fields must be left blank. Single sign on should be left as False. Setting the Auto Start property toTrue will cause the connection to be launched whenever the user is logged in to the client. The Display settings can bemodified to meet the requirements of the site. Setting Multi-Monitor Support and Full Screen Mode to True will cause theRDP client to use all available monitor space.

4. After the RDP Connections are configured, edit Device Configuration parameters as necessary for the target client(s).In this example, the site is in the Pacific time zone and the client is in the main control room driving a large wall-mountedmonitor that is mirroring the local monitor.


5. Select the Display area and set theMultiple Displays property to Duplicate these displays.

6. Select the Timezone area and set the Timezone Name property.


Since this template is for a client in the main control room driving a wall-mounted display we will leave the power settingswith the default values that prevent the client and its displays from sleeping.

7. From the main menu, select Save/Save As and give the template a descriptive name - ToCRM1.xml for this example.Since we started with the default.xml template the path will already be set to the inetpub\WCM-Templates\WES7\ folder.

Template Saved in inetpub\WCM-Templates\WES7\ Folder


4.6 Example: Create a New Client Specific Template Filefrom an Existing Site Specific Template FileIn this example, we will create a template file for a client exactly like the ToCRM1.xml template created in the previousexample, except that it should support an RDP connection to the CRM2 VM instead of CRM1.

➢➢ To create a new client-specific template file from an existing site-specific template file

1. Open the ToCRM1.xml template file in the WCM tool.

2. Edit the Connection Name and Host Name or IPAddress properties.

3. Click Apply Changes to modify the template to connect to CRM2 instead of CRM1.

4. The changes to the template file are finished since, for this example, we want the rest of the configuration to remain thesame as the ToCRM1.xml template. Select Save/Save As from the main menu and give the template a descriptive namelike ToCRM2 for this example. Since we started with the ToCRM1.xml template the path will already be set to theinetpub\WCM-Templates\WES7\ folder.


5 USB Drive SupportUSB drives that are plugged into the Thin Client can be shared for access by the VMs in the Control Server. The Windowsoperating system automatically detects and mounts USB drives plugged into the USB port. A local Thin Client Administratorcan then set up shared file access to the contents of the USB drive.

5.1 Enable File Sharing➢➢ To enable the USB device for shared file access

1. Log in to the local Administrator account. Refer to the section Local Administrator Account Login.

2. Plug in the USB device.

3. Open File Explorer, select the drive, and create a share to enable access to the device from other VM’s.

4. Verify the permissions on the share have Everyone with Read permission (the default). If the USB contents requireupdating, add Administrators with Change permission (requires Domain Administrator credentials).

The contents of the USB device can now be accessed by any VM in the Control Server using Windows standard shared fileaccess with the appropriate credentials.

➢➢ To access the USB contents: right-click on the shared drive and select the Sharing tab to find the Network Path tothe shared drive.

USB Drive Support GEH-6849D Support and Maintenance Guide 53Public Information

Note The Thin Client local Administrator account credentials are required when accessing the shared directory from a VMor another Thin Client.

5.2 File Share PersistenceThe following summarizes USB drive file share persistence.

The file share:

• will persist if the USB drive is removed and reinserted at a later time.• will persist between user logins.• will not persist between reboots. The share will be removed and the device will not be accessible to other VM’s in the

system.

Note Although it is not recommended, the file share can be made to persist across reboots by turning off the File BasedWrite Filter, creating the share, then turning the File Based Write Filter back on.

5.3 File Share RemovalLeaving the USB device shared is a security risk. Use one of the following procedures to remove the file share when finished:

• Remove the file share, then remove the USB device.• Remove the USB device and reboot the Thin Client.

Note If the file share was created to persist across reboots, turn off the File Based Write Filter, remove the file share, thenturn the File Based Write Filter back on.


6 Remote Desktop Services OverviewSystems can be set up for one Thin Client terminal to one HMI VM operation (one-to-one), or many Thin Client terminals toone HMI VM operation (many-to-one). Windows Thin Client terminals connect to the VMs using Remote Desktop sessions.For the many-to-one case, Remote Desktop Services (RDS) is enabled on the HMI VMs, and a Remote Desktop ServicesLicense Server is configured on the Engineering Workstation (EWS) VM. The HMI VMs are configured as Remote DesktopSession Host Servers using the Per Device licensing mode. The Thin Client terminals are issued RDS Per Device ClientAccess Licenses (CALs) by the Remote Desktop License Server. When a Thin Client terminal connects to an RD SessionHost server (HMI VM) for the first time, the client is issued a temporary license. When a client connects to an RD SessionHost server (HMI VM) for the second time, the license server issues it a permanent RDS Per Device CAL, providing there areCALs in the pool of available RDS Per Device CALs on the license server.

Note The use of RDP connections between VMs should be limited, as this may prematurely deplete the pool of availableRDS Per Device CALs on the license server and lead to RDP connection issues. Per Device CALs are purchased based onlyon the number of Thin Client terminals. VM to VM RDP connections are also allocated licenses from this pool and shouldtherefore only be initiated from a single VM in the system, and it is recommended that only the EWS VM be used for thispurpose.

User Sessions

The HMI VMs run within the Windows Server operating system. Windows Server supports up to two concurrent usersessions by default, and supports an unlimited number of user sessions when RDS is enabled. Typically, whenever a RemoteDesktop connection is established with the VM, a new user session is created based on the user credentials provided when theconnection is established. In this case, the user session is in the Connected state because it is associated with an active RemoteDesktop connection. If the user logs out of the connection, the user session is terminated and the Remote Desktop connectionis closed. However, if the user simply closes the Remote Desktop connection without logging out, the user session remainsactive on the server in a Disconnected state. The user can establish a new Remote Desktop connection and resume theDisconnected session by logging with the same user credentials.

Windows Task Manager can be used to display the user sessions, as shown in the following figure. Windows Task Managercan also be used to close Disconnected sessions. Refer to the section Manage User Sessions on HMI VMs for detailedprocedures.

Windows Task Manager

Remote Desktop Services Overview GEH-6849D Support and Maintenance Guide 55Public Information

Notes


7 Troubleshooting Thin ClientConfiguration Server IssuesThe Thin Client Configuration Server is an IIS Server typically running on the site’s Engineering Workstation (EWS). TheThin Clients download their software and configuration files from the server.

The IIS logs on the server can be used to troubleshoot most Thin Client configuration update issues. The log files can be usedto determine if the Thin Clients are attempting to download files from the server, what files are being requested, and anindication of the problem if a failure occurs. The log files are stored in the directory /intepub/logs/LogFiles/W3SVC1/. The logfiles contain time-stamped entries for all client requests.

The following example log file entries show a typical sequence of Thin Client requests to the server after a client reboot, withthe return status in bold. Each highlighted entry is followed by an explanation of what was requested and why.

Status Entry Indication200 Success - the file was successfully retrieved by the client.404 File not found error - the file was not found and the client received an error in response to the request.405 (Method NotAllowed)

Requests that were rejected

7.1 Successful Thin Client Configuration DownloadSequence ExampleThe following example shows the typical sequence as observed in the web server log files during a successful Thin Clientconfiguration file download.

2016-11-08 22:55:06 172.16.201.22 PROPFIND /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml - 924 -172.16.200.19 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) - 405 0 1 1

The client at address 172.16.200.19 issues a PROPFIND request for the /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml file to the server at address 172.16.201.22 at Port 924. The PROPFIND is not supported by the server, so Error 405(Method Not Allowed) is returned. Error 405 is expected behavior for all PROPFIND requests from the client.

2016-11-08 22:55:06 172.16.201.22 GET /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml - 924 - 172.16.200.19Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) - 200 0 02

The client at address 172.16.200.19 issues a Get request for the /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml file tothe server at address 172.16.201.22 at Port 924. The GET request is successful as indicated by the 200 return value. Thissequence shows that the Thin Client successfully downloaded its configuration file.

Troubleshooting Thin Client Configuration Server Issues GEH-6849D Support and Maintenance Guide 57Public Information

7.2 Failed Thin Client Configuration Download SequenceExampleThe following example shows a typical sequence as observed in the web server log files when the Thin Client configurationfiles have not been deployed to the Thin Client Configuration Server. The Thin Client requests its configuration files, but theydo not exist on the server.


The client at address 172.16.200.19 issues a PROPFIND request for the /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml file to the server at address 172.16.201.22 at Port 924. The 404 return value (File Not Found Error) indicates that therequested file could not be found at the given URL.


The client at address 172.16.200.19 issues a GET request for the /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml fileto the server at address 172.16.201.22 at Port 924. The 404 return value (File Not Found Error) indicates that the requestedfile could not be found at the given URL.

The sequence above is repeated four more times as the client retries the requests as a result of the failures, then stops makingnew requests.










7.3 No Client Requests ReceivedIf no Thin Client requests are logged after restarting a Thin Client, the Thin Client(s) may not be configured with the correctThin Client Configuration Server information. Refer to the sections Configure Thin Client Configuration Server InformationFile and Integrate and Deploy Thin Client Terminal to verify the Thin Client preparation and deployment state.

7.4 Configuration Files Cannot Be FoundIf the server returns 404 File Not Found errors for the Thin Client requests, the configuration files cannot be found on theThin Client Configuration Server and need to be deployed to the server. Refer to the section Deploy Thin Client ConfigurationFiles and verify that the Thin Client configuration files have been successfully deployed to the Thin Client ConfigurationServer.

Troubleshooting Thin Client Configuration Server Issues GEH-6849D Support and Maintenance Guide 59Public Information

Notes


8 System Configuration andMaintenance Use CasesThis chapter describes scenarios related to both initial site installation and long-term maintenance of the site that a plantmaintenance engineer is likely to encounter.

8.1 Failed Dell Wyse Thin ClientIf a Thin Client terminal fails, it must be replaced.

➢➢ To replace a failed Thin Client terminal

1. Prepare the replacement Thin Client terminal if required. (Refer to the section Thin Client Terminal Preparation andIntegration for instructions.)

• If the terminal is new out of the box, preparation will be required.• If the replacement terminal is a spare, preparation may already have been performed.

2. Determine the MAC address of the replacement Thin Client terminal. Refer to section Thin Client Hardware andSoftware Information for the procedure to get the MAC Address from the Product Information Tag of the Thin Clientterminal.

3. Edit Clients.csv on the Thin Client Configuration Server to reflect the MAC Address of the replacement terminal.

4. Deploy the Thin Client terminal. Refer to the procedure To deploy an individual Thin Client.

5. Update the Thin Client configuration files on the Thin Client Configuration Server. Refer to the section Deploy ThinClient Configuration Files for the procedure to deploy the configuration files for the new terminal.

6. Log off, then log back in to the Thin Client or restart it, to force it to download its configuration from the Thin ClientConfiguration Server.

System Configuration and Maintenance Use Cases GEH-6849D Support and Maintenance Guide 61Public Information

Example: Replace a Thin Client with a Spare Terminal

Note In this example, steps 1– 3 in the procedure To replace a failed Thin Client terminal can be skipped because the spareterminal already has an entry in the Clients.csv file and has been prepared and deployed into the Control Server infrastructure.

➢➢ To replace a Thin Client with a spare terminal

1. Log in to the VM hosting the Thin Client Configuration Server with a domain administrator account.

2. Open the %SystemDrive%\intepub\WCM-Templates\Clients.csv file in a text editor.

Client, Type, MACAddress, Template, Description#————————— ——— —————————— ———————— ——————————————————Default7, WES7, *, Default, Default WES7 ConfigurationGT1, WES7, 008064F60EFE, Default, PECC for GT1GT2, WES7, 008064F60F8D, Default, PECC for GT2ST1, WES7, 008064F6129E, Default, PECC for ST1CRM-Main, WES7, 008064F6100D, Default, Control Room Main DisplayCRM-Eng, WES7, 008064F612AF, Default, Control Room EngineeringSpare1, WES7, 008064F609D1, Default, Spare Windows Thin Client #1Spare2, WES7, 008064F61028, Default, Spare Windows Thin Client #2

3. In this example, the CRM-Main Thin Client terminal has failed and will be replaced with the Spare2 terminal. Copy theMAC Address for Spare2 and replace the CRM_Main MAC Address with it. Blank out the Spare2 MAC Address.

Clients.csv now looks as follows:

Client, Type, MACAddress, Template, Description#————————— ——— —————————— ———————— ——————————————————————Default7, WES7, *, Default, Default WES7 ConfiguratinGT1, WES7, 008064F60EFE, Default, PECC for GT1GT2, WES7, 008064F60F8D, Default, PECC for GT2ST1, WES7, 008064F6129E, Default, PECC for ST1CRM-Main, WES7, 008064F61028, Default, Control Room Main DisplayCRM-Eng, WES7, 008064F612AF, Default, Control Room EngineeringSpare1, WES7, 008064F609D1, Default, Spare Windows Thin Client #1Spare2, WES7, Default, Spare Windows Thin Client #2

4. Save the changes to Clients.csv.

5. Launch a PowerShell Window in administrative mode, issue the cd c:\inetpub\WCM-Templates command, and run theDeploy-WCMConfiguration.ps1 script to update the configuration files on the Thin Client Configuration Server.

Deploy-WCMConfiguration.ps1 Script

6. Log off and back in to the Thin Client or reboot it to force it to download its configuration from the Thin ClientConfiguration Server.

7. When a new spare arrives at the site, perform the procedures in the section Integrate and Deploy Thin Client Terminal todeploy the terminal into the Control Server infrastructure. Enter the MAC Address of the new terminal in the Spare2entry in Clients.csv.The new terminal is ready to replace the next failed terminal.


8.2 Deploy New Thin Clients at Site Following FactoryAcceptance TestIn many cases, the Control Server will be configured and staged in the factory using temporary Thin Client terminals, whichwill be replaced with the actual terminals when the Control Server arrives at the site.

• Clients.csv must be updated to reflect the MAC Addresses of the new terminals.• The new terminals must be deployed into the Control Server infrastructure by following the procedures the section

Integrate and Deploy Thin Client Terminal.• The Thin Client Configuration Files must be deployed on the Thin Client Configuration Server using the procedures in

the section Deploy Thin Client Configuration Files.

Note Clients.csv can be edited to reflect the new Thin Client terminals before deploying the configuration files.

8.3 Deploy All Thin Client Terminals ExampleThe following example shows how to configure the Thin Client terminals using the Thin Client Configuration Serverinformation. In this example system, the Thin Clients have been defined and associated with physical terminals in thefollowing Clients.csv file.

## WCM Client File (Clients.csv)## Edit this file to deploy client configurations built from template files.# Client........An arbitrary name given to this Thin Client terminal# Type..........The Thin Client Type, must be one of: { WES7 | WES8 | WES10 }# MACAddress....The MAC address of this Thin Client (12 HEX digits)# Template......The name of the WCM template to use for this client# Description...A free-form description of the client#Client, Type, MACAddress, Template, Description#————————— ——— —————————— —————————— ————————————————————————Default7, WES7, *, Default, Default WES7 ConfigurationGT1, WES7, 008064F60EFE, Default, PECC for GT1GT2, WES7, 008064F60F8D, Default, PECC for GT2ST1, WES7, 008064F6129E, Default, PECC for ST1CRM-Main, WES7, 008064F6100D, Default, Control Room Main Display

In this example, all four Thin Clients have been powered up, connected to the PDH network, and prepared. The spare ThinClient has been prepared and returned to the store room so it is not connected to the PDH network.


➢➢ To configure the Thin Client Configuration Server information in the Thin Client terminal

1. Launch Windows PowerShell in Administrator mode. Refer to the section Open an Administrator Mode PowerShellWindow on a Thin Client.

2. Move to the %SystemDrive%\intepub\WCM-Templates directory.

3. Launch the Configure-WCMClient.ps1 script with the –All option.

4. Enter your Domain Administrator account credentials to continue processing.

Windows PowerShell Credential Request

Running Configure-WCMClient.ps1 Script with –All Option

The update results are displayed as each client is updated, and a summary is provided at the end. In the example Clients.csvfile, GT1 was successfully deployed (updated with the Thin Client Configuration Server information), and the remaining ThinClients were already up to date. Running the script again shows that all clients are up-to-date and do not need to beconfigured.

Clients Already Configured


8.4 Deploy Thin Client Terminals by Name ExampleThe following example shows how to deploy an individual Thin Client. In this example system, the Thin Clients have beendefined and associated with physical terminals in the following example Clients.csv file.

## WCM Client File (Clients.csv)## Edit this file to deploy client configurations built from template files.# Client........An arbitrary name given to this Thin Client terminal# Type..........The Thin Client Type, must be one of: { WES7 | WES8 | WES10 }# MACAddress....The MAC address of this Thin Client (12 HEX digits)# Template......The name of the WCM template to use for this client# Description...A free-form description of the client#Client, Type, MACAddress, Template, Description#————————— ——— —————————— —————————— ————————————————————————Default7, WES7, *, Default, Default WES7 ConfigurationGT1, WES7, 008064F60EFE, Default, PECC for GT1GT2, WES7, 008064F60F8D, Default, PECC for GT2ST1, WES7, 008064F6129E, Default, PECC for ST1CRM-Main, WES7, 008064F6100D, Default, Control Room Main Display

➢➢ To deploy an individual Thin Client

1. Determine the name of the Thin Client terminal from the Clients.csv file.

2. Log in as a domain administrator on the VM hosting the Thin Client Configuration Server (typically the EWS VM).

3. Launch Windows PowerShell in Administrator mode. Refer to the section Open an Administrator Mode PowerShellWindow on a Thin Client.

4. Move to the %SystemDrive%\intepub\WCM-Templates directory using the cd c:\inetpub\WCM-Templates command.

5. Run the Configure-WCMClient.ps1 script with the Client parameter as follows:.\Configure-WCMClient.ps1 -Client <name>.

6. Enter the domain account credentials as prompted. Refer to the figure Windows PowerShell Credential Request.

Running Configure-WCMClient.ps1 Script

Note Multiple Thin Client terminals can be deployed by specifying multiple Thin Client names separated by commas as inthe following example: Configure-WCMClient.ps1 –Client GT1,GT2


8.5 Deploy Thin Client Terminals by MAC AddressExampleThe following example shows how to deploy an individual Thin Client.

➢➢ To deploy an individual Thin Client by MAC Address

1. Determine the MAC Address of the terminal. Refer to section Thin Client Hardware and Software Information.

2. Log in as a domain administrator on the VM hosting the Thin Client Configuration Server (typically the EWS VM).

3. Launch Windows PowerShell in Administrator mode. Refer to the section Open Administrator Mode PowerShell Windowon Virtual Machine.

4. Move to the %SystemDrive%\intepub\WCM-Templates directory using the cd c:\inetpub\WCM-Templates command.

5. Run the Configure-WCMClient.ps1 script with the MACAddress parameter as follows: .\Configure-WCMClient.ps1-MACAddress <macAddress>.

6. Enter the domain account credentials as prompted. Refer to the figure Windows PowerShell Credential Request.

Running Configure-WCMClient.ps1 Script

Note Multiple Thin Client terminals can be deployed by specifying multiple MAC Addresses separated by commas as in thefollowing example: Configure-WCMClient.ps1 –MACAddress 008064F60EFE,008064F608FD

8.6 Change Local Thin Client Default Account PasswordsThin Clients are shipped from the factory with a Local User and Administrator account. The default password for both ofthese accounts is DellCCCvdi. This widely-shared default password must be changed on all of the Thin Clients at the site aspart of the handover procedure in order to prevent unauthorized users from logging in to the Thin Client terminals. Refer tothe section Change Local Thin Client Default Account Passwords for the procedure to modify the default account passwords.

8.7 Verify Thin Client Time Synchronization to DomainControllersBecause the Thin Clients are members of the Domain, they will only use the system Domain Controllers to synchronize theirtime. This requires the Domain Controllers to be configured to synchronize to the site time sources to provide a consistenttime reference between the Thin Clients (which use the Domain Controller time) and the HMIs (which use the site timesources as the time reference). Perform the following procedure to verify the successful synchronization of the Thin Client tothe Domain Controllers.


➢➢ To verify the successful synchronization of the Thin Client to the Domain Controllers


2. Open a Windows Command window.

3. Issue the command w32tm /query /status. The command output (illustrated in the following figure) shows that the ThinClient is successfully synchronized to DC2. Thin Client synchronization to either DC1 or DC2 is expected.

Time Sync Verification Command

8.8 Verify Domain Controller Time SynchronizationRefer to the Control Server — Domain Services Maintenance Guide (GEH-6845), the section Configure Time on DomainControllers, for the procedures to verify the Domain Controller time synchronization configuration and status, as well as tomodify the Domain Controller time settings, if required.


Notes


9 Troubleshooting ScenariosThis chapter describes potential failure modes and provides procedures to determine root cause and issue resolution.

9.1 Thin Client Login FailureThe user can log in to the Thin Clients using one of the default local accounts, or using a Domain account configured in theDomain Controllers.

Failure to log in to the Local User or Administrator account is the result of using an incorrect password.

Incorrect Password Dialog Box

Troubleshooting Scenarios GEH-6849D Support and Maintenance Guide 69Public Information

9.2 Failure to Establish RDP Connection to HostThin Clients typically communicate with VMs running on the Control Server, as well as servers on other systems. After loginto the Thin Client is successful, a connection to a host is initiated. The connections can be launched automatically or they canbe manually initiated by the user, depending on how they are set up in the configuration file.

Failure to establish a connection to a host can be caused by many issues, such as:

• Incorrect user credentials• Loss of network connection• Target Host (VM) is offline

9.2.1 Incorrect User CredentialsIf login to the host fails, the following dialog box displays. Verify that the username, domain, and password information arecorrect.

Login Attempt Failed


9.2.2 Network Connection Issue or Target Host (VM) is OfflineIf the Thin Client network connection has been lost (refer to the section Verify Thin Client Network Connection), or the targetVM is offline, the Remote Desktop Connection displays the following error dialog box. Follow the instructions provided inthe Remote Desktop Connection Error Message.

Remote Desktop Connection Error Message

9.2.3 Remote Desktop Services Connection IssuesRemote Desktop Services (RDS) connection-related errors, like the following example, may occur on systems configured formany Thin Client terminals to one HMI VM operation (many-to-one).

RDS Connection Error Message

RDS connection issues can be caused by Remote Desktop License Server issues or an insufficient number of RDS Per DeviceCALs. Use the following procedures to resolve License Server or available license pool issues.

➢➢ To resolve License Server or available license pool issues

1. Verify the operation of the RDS License Server and restart it if necessary.Refer to the section Check Location and Status of RDS License Server.

2. Determine the number of client licenses available on the RDS License Server.Refer to the section Determine Number of Available Client Licenses in RDS License Server.

3. Free up unused client licenses and/or purchase additional RDS Per Device CALs if the number of RDS Per Device CALsis not sufficient to cover the number of device connections required by the site.Refer to the section Manage RDS Per Device CALs.


9.3 Failure to Update Thin Client ConfigurationThin Clients download their configuration files from the server. If the server is unavailable, the Thin Clients will use locallycached copies of the configuration files that were downloaded from the server on the last successful attempt. If the ThinClients are not updating their configuration files after changes have been made on the server, the problem may a result of anyof the following situations:

• A network issue is preventing the Thin Client from downloading the files from the server. Refer to the sectionVerify Thin Client Network Connection.

• The VM hosting the Thin Client Configuration Server is down.• The IIS service on the VM hosting the configuration server is down.• The configuration files may be missing or incorrectly installed on the configuration server. Refer to the section

Troubleshooting Thin Client Configuration Server Issues.

9.4 Remote Desktop Connection Unknown PublisherWarningThe Remote Desktop Connection Unknown Publisher warning message is typically displayed when a Remote Desktopconnection is launched using a desktop icon. The Unknown Publisher message indicates that the desktop RDP file has notbeen signed. This is not an indication of an authentication failure between the Thin Client and the Remote Host.

➢➢ To proceed with the connection process from the Remote Desktop Connection Unknown Publisherdialog box: click Connect.

Remote Desktop Connection Unknown Publisher Warning


9.5 Thin Client Terminal Reported as OfflineAn incorrectly configured Thin Client host name can result in the Control System Health (CSH) feature reporting that theThin Client terminal is offline, even though it is communicating on the network. In WorkstationST releases prior toV07.04.02C (included in ControlST versions prior to V07.04.00C SP01), the CSH feature required the use of a standard hostname to communicate with the Thin Clients. The standard name provided a mechanism for CSH to manufacture a host namefor the client to compensate for the fact that the Thin Clients IP addresses are dynamically assigned via DHCP. This standardhost name is also required by the Wyse Configuration Manager software used to create and deploy the Thin Clientconfiguration.

The Dell Wyse Thin Clients come configured with the default host name out of the box, but in some instances these nameshave been modified in the field. Thin Clients deployed in a system with CSH prior to WorkstationST V07.04.02C must beconfigured with the standard Thin Client name in order to be monitored by the CSH feature. The Windows 7 Client host namemust start with WES, followed by the MAC address of the Thin Client as reported on the Thin Client pullout information tag(refer to the section Thin Client Hardware and Software Information). For example, a Windows 7 Thin Client with MACaddress 00:80:64:F6:10:1D must be configured with a host name of WES008064F6101D. Refer to the section Thin ClientHost Name Modification for the procedure to configure the host name with the required value.


Notes


10 Common ProceduresThis chapter contains common procedures used for maintenance and debugging.

10.1 Thin Client Account Login

10.1.1 Local User Account LoginThin Clients are configured to automatically log in to the Local User account. The auto login does not require the user to enterthe Local User account password.

Note The default user password is set to DellCCCvdi from the factory.

10.1.2 Local Administrator Account LoginChanges to the Thin Client can only be made using the Local Administrator account.

➢➢ To login to a Local Administrator account

1. From the Start menu, select Log off.

Note Thin Clients are configured to automatically log in to the Local User account so log off this account to log in tothe Local Administrator account.

2. Hold down the shift key until the Press [CTRL] + [ALT] + [DELETE] to log on window is displayed.

3. Press [CTRL] + [ALT] + [DELETE], enter .\Administrator (Administrator preceded by the dot and backslashcharacters) in the User name field, and enter the Local Administrator password in the Password field.

Note The default administrator password is set to DellCCCvdi from the factory.

Common Procedures GEH-6849D Support and Maintenance Guide 75Public Information

10.2 Local Thin Client Account Password ResetThin Clients come with a well-known default Local User and Administrator account password configured from the factory(DellCCCvdi), which must be changed in order to reduce the risk of unauthorized users gaining access to the Thin Clientterminals at the site.

10.2.1 Thin Client Local User Account Password ResetUse the following procedure to change the local User account password and update the auto login password setting with thenewly created password.

➢➢ To change the Local User account password or update auto login password setting

1. Log in to the Local Administrator account. Refer to the section Local Thin Client Administrator Account Login.


3. The Thin Client will restart and automatically log in to the Local User account.

4. Log in to the Local Administrator account.

5. Press [CTRL] + [ALT] + [DELETE] and select Change a password….

6. Enter .\User for the user name.

7. Enter the old and new passwords and confirm the new password.

8. Click the arrow to make the change.

9. Launch the Dell Thin Client Application from the toolbar menu.

10. Enter the new User account password in the Default Password field and click Apply.

Default Password Field

11. Close the Dell Thin Client Application.



13. Verify that the auto login is successful after reboot.

10.2.2 Thin Client Local Administrator Account Password ResetUse the following procedure to change the Local Administrator account password.

➢➢ To change the Thin Client Local Administrator account password

1. Log in to the Local Administrator account. Refer to the section Local Thin Client Administrator Account Login.


3. The Thin Client will restart and automatically log in to the Local User account.

4. Press [CTRL] + [ALT] + [DELETE] and select Change a password….

5. Enter .\Administrator for the user name.

6. Enter the old and new passwords and confirm the new password.

7. Select the arrow to make the change.


9. Verify the new password by logging in to the Local Administrator account using the new password.


10.3 Thin Client Hardware and Software Information

10.3.1 Product Information TagThe first level of Thin Client information can be found on the pull-out tag on the back of the chassis. The pull-out tag containsthe model number and the MAC address (physical address of the internal NIC). The Thin Client can be uniquely identifiedand tracked using the MAC address.

��

Product Information Tag


10.3.2 System InformationThe next level of information requires logging into the Thin Client to get further information about the hardware andoperating system.

Note Additional information is available in the Dell Thin Client Application when logged in to the Thin Client with anadministrator account.

➢➢ To view system information: click Dell Thin Client Application on the toolbar to launch the information viewer.

System Information Viewer


10.4 Verify Thin Client Network Connection

10.4.1 Verify Connection StatusMost Thin Client functionality depends on its connection to the Plant Network (PDH). The Thin Client displays the iconshown in the following figure in the status tray when it is connected to the PDH network. The No Internet access warning istypical.

No Internet Access

The Thin Client displays the icon shown in the following figure in the status tray when the network connection is lost. Thenetwork connection icon in the system tray is displayed with a red X when the network is disconnected. Hovering over theicon with the mouse generates the tooltip. If the icon is displayed, the Thin Client has lost its connection to the PDH. Verifythat the network cable is plugged in to the Thin Client. If the network cable is connected and the problem persists, theproblem could be a Thin Client or network issue.

Not Connected Network Connection Icon


10.4.2 Verify IPAddress Assignment from DHCPBoth the network connection status and the IP address assignment from DHCP can be verified using the Dell Thin ClientApplication.

➢➢ To verify the IP address assignment form DHCP

1. Click Dell Thin Client Application on the toolbar.

2. Verify that an IP address has been assigned as displayed in the following figure.

Assigned IPAddress

The Dell Thin Client Application will display the following network information if the network is disconnected:

Disconnected Network Information


10.5 Verify Domain Name Server (DNS) Status➢➢ To verify DNS status

1. Log in to the DC1 VM.

2. From the Control Panel, select Administrative Tasks, then select Services.

3. Verify that the Active Directory Domain Service is running.

Active Directory Domain Service

10.6 Verify DHCP Server StatusThe system uses redundant DHCP Servers, hosted on the DC1 and DC2 VMs, to provide DHCP services to the Thin Clients.The Thin Clients rely on DHCP to get their IP addresses. If the Thin Client cannot access the DHCP Servers, the Thin Clientwill be unable to communicate on the network.

➢➢ To verify DHCP Server status

1. Establish a remote session with the DHCP Server VM.

2. Verify that the DHCP Server service is running.

3. Repeat for both the DC1 and DC2 VMs.

DHCP Server Service


10.7 Verify Thin Client Domain NetworkThe Thin Client domain network membership can be found using the Dell Thin Client Application.

Note This procedure can be performed with the terminal disconnected from the network.

➢➢ To verify Thin Client domain network

1. Right-click Dell Thin Client Application icon on the toolbar.

Dell Thin Client Application Icon

2. Verify that the domain is not set to WORKGROUP.

The following figure shows that the terminal has been joined to the Control Server HMI.local domain.

Thin Client Jointed to Control Server HMI.local Domain


The following figure shows that the terminal is a member of the default WORKGROUP domain and has not been joined tothe Control Server HMI.local domain.

Thin Client Jointed to WORKGROUP Domain


10.8 Thin Client Configuration Server Files Location➢➢ To locate the Thin Client Configuration Server files

1. Connect and log in to the VM that is hosting the Thin Client Configuration Server website (typically the EWS).

2. Open the Server Manager and select Tools, then select Internet Information Services (IIS) Manager.

Thin Client Configuration Server Files Location


10.9 File Based Write FilterWhen enabled on Windows 7 Embedded Standard Thin Clients, the File Based Write Filter (FBWF) prevents changes frombeing made to the Thin Client. Any changes made while the File Based Write Filter is enabled are lost when the Thin Client isrestarted. Changes are only persisted when the File Based Write Filter is disabled.

10.9.1 File Based Write Filter StatusWhen logged in with the local User account, the Write Filter status is displayed in the system tray. A green circle iconindicates that the Write Filter is enabled (ON), and a red circle icon indicates that the Write Filter is disabled (OFF).

File Based Write Filter Enabled System Tray Icon

Attention

When logged in with the local Administrator account, the system tray icons are notavailable. You must use the desktop icons to enable/disable the File Based Write Filter.

10.9.2 Enable/Disable File Based Write Filter➢➢ To enable the File Based Write Filter

1. Log in to the local Administrator account. Refer to the section Local Administrator AccountLogin.

2. Right-click on the FBWF Enable desktop icon and select Run as administrator.The Thin Client will restart and the Write Filter will be enabled after the reboot is complete.

FBWF EnableDesktop Icon

➢➢ To disable the File Based Write Filter

1. Log in to the local Administrator account. Refer to the section Local Administrator AccountLogin.

2. Right-click on the FBWF Disable desktop icon and select Run as administrator.The Thin Client will restart and the Write Filter will be disabled after the reboot is complete.

FBWF DisableDesktop Icon


10.10 Open Administrator Mode PowerShell Window onThin ClientPerform the following procedure to open a PowerShell window in Administrator mode on a Thin Client.

➢➢ To open an Administrator mode PowerShell window


2. From the Start menu Search area, type PowerShell.

3. Right-click onWindows PowerShell and select Run as administrator.

Note You must be logged in to an Administrator account on the Thin Client to run PowerShell.

10.11 Open Administrator Mode PowerShell Window onWindows Server 2012 R2The EWS VM and other Windows-based VMs are hosted by the Control Server on Windows Server 2012 R2. Perform thefollowing procedure to open an Administrator mode PowerShell window on Windows Server 2012 R2.

➢➢ To open an Administrator mode PowerShell window using Windows Server 2012 R2

1. From the Start menu search area, type PowerShell.

2. Right-clickWindows PowerShell and select Run as administrator.

3. Supply a Domain Administrator account if prompted (standard is HMI\admin).

Administrator Mode PowerShell Window

10.12 Launch RD Licensing Diagnoser ToolThe RD Licensing Diagnoser tool provides information to help identify possible licensing problems for the Remote DesktopSession Host server.

➢➢ To launch the RD Licensing Diagnoser tool

1. Establish a Remote Desktop connection to one of the HMI VMs. If RDS License Server issues are preventing RemoteDesktop connections, connect to one of the HMI VMs using a Remote Console launched from VMware vSphere Clientor vSphere web client.

2. Log in to a Domain Administrator account.

3. Launch the Windows Server Manager tool.


4. From the Tools menu, select Terminal Services.

Note If Terminal Services does not display in the Tools menu, RDS is not enabled on the VM, and is a likely indicationthat the site is using a one Thin Client to one HMI VM (one-to-one) architecture and RDS licensing does not apply.

5. Select RD Licensing Diagnoser.


10.13 Check Location and Status of RDS License ServerThe RD Licensing Diagnoser tool can be used to display information about the Remote Desktop Session Host Server on thelocal VM, as well as the location and status of the RDS License Server. (Refer to the procedure To launch the RD LicensingDiagnoser Tool to launch the application.)

In the example in the following figure, no problems were detected and the location and status of the RDS License Server isdisplayed.


Select the license server entry to view further details.


If a problem is detected, the RD Licensing Diagnoser tool provides a description of the problem and instructions to resolvethe problem. The following figure illustrates the RD Licensing Diagnoser tool display after the Remote Desktop Licensingservice was stopped. Perform the steps in the Suggested Resolution area to resolve any existing issues.


10.14 Restart RDS License Server➢➢ To restart the RDS License service on the VM hosting the RDS License Server information

1. Establish a Remote Desktop connection to the VM hosting the RDS License Server.

a. If RDS License Server issues are preventing Remote Desktop Connections, connect to one of the HMI VMs using aRemote Console launched from VMware vSphere Client or vSphere web client.

b. If the location of the RDS License Server is not known, refer to section Check Location and Status of RDS LicenseServer to determine which VM is hosting the license server.

2. Log in to the VM hosting the RDS License Server with a Domain Administrator account.

3. From the Windows Control Panel, select Administrative Tools, then select Services.

4. Locate the Remote Desktop Licensing service.

Note If the service cannot be found, the RDS License Server is not installed on this VM.

5. Right-click Remote Desktop Licensing service and select Start ( if it is not running).

6. Verify that it successfully starts up.

7. Verify that the service Startup Type is configured as Automatic. If not, right-click, and select Properties and changeStartup Type to Automatic.


10.15 Determine Number of Available Client Licenses inRDS License ServerRefer to the section Check the Location and Status of the RDS License Server for the procedure to launch the RD LicensingDiagnoser tool and display the license server status, including the number of installed and available RDS Per Device CALlicenses.

10.16 Manage RDS Per Device CALs

10.16.1 Launch RD Licensing Manager➢➢ To launch the RD Licensing Manager

1. Establish a Remote Desktop connection to the VM hosting the RDS License Server. If the location of the RDS LicenseServer is not known, refer to section Check the Location and Status of the RDS License Server to determine which VM ishosting the license server.

2. Log in to the VM hosting the RDS License Server with a Domain Administrator account.

3. Launch the Windows Server Manager tool.

4. From the Tools menu, select Terminal Services.

Note If Terminal Services does not display in the Tools menu, Remote Desktop Services are not enabled on the VM, andis a likely indication that the site is using a one Thin Client to one HMI VM (one-to-one) architecture and RDS licensingdoes not apply.

5. Select Remote Desktop Licensing Manager.

10.16.2 Determine Number of Available (Unused) RDS Per Device CALs➢➢ To determine the number of available RDS Per Device CALs

1. Launch RD Licensing Manager.

2. Select the server node from the tree view to display the overview of the installed and temporary RDS Per Device CALs.


10.16.3 Revoke Unused Device CAL➢➢ To revoke an unused Device CAL

1. Launch RD Licensing Manager.

2. Expand the server node and select the Installed node to display the details for each installed RDS Per Device CAL andto which device it is allocated.

If a device is no longer available (for example, a Thin Client terminal has failed and has been replaced by a new terminal), theRDS Per Device CAL allocated to it can be revoked. Revoking a license returns it to the available license pool, making itavailable to be reassigned to a new device.

Note Additional RDS Per Device CAL licenses can be purchased and added to the available license pool if required by thesite.


10.17 Manage User Sessions on HMI VMsThis section provides the following procedures:

• View Active and Disconnected User Sessions• Close Disconnected User Sessions

10.17.1 View Active and Disconnected User Sessions➢➢ To view Active and Disconnected user sessions on an HMI VM

1. Establish a Remote Desktop connection to the HMI VM.

2. Log in to the HMI VM with an Administrator account.

3. Launch the Windows Task Manager.

4. Select the Users tab to display the active user sessions on the VM.The following figure shows that the admin user session is connected to a Remote Desktop (or another type) connection,and the TSUser4 user session is active but is running in Disconnected mode.

10.17.2 Close Disconnected User Sessions➢➢ To close Disconnected user sessions: right-click a Disconnected user session and select Sign off to terminate it.


10.18 Connect Monitors to Thin Client TerminalThe video ports are located on the back of the Thin Client terminal as shown in the following figure. The Windows operatingsystem assigns the Display numbers based on the physical video ports that are connected.

When connecting monitors to the Thin Client terminal, it is recommended that they be connected in physical port order. Forexample, the monitor plugged into the first physical port connected will be assigned to Display 1, and the monitor pluggedinto the next physical port will be assigned to Display 2, and so forth.

Display Port Connector (Physical Port 1)

DVI Port Connector (Physical Port 2)

Display Port Connector(Physical Port 3)

Display Port Connector (Physical Port 4)

Note If all of the physical ports are not connected, it may be necessary to shift the display port connections between themonitors to achieve the correct display order.


10.19 Configure Thin Client Display SettingsThe display settings should be configured from the Wyse Configuration Manager (WCM) tool as part of the overall ThinClient terminal configuration procedure outlined in the section Create and Deploy Thin Client Configuration Files.

After the display settings are configured, they are deployed to the Thin Client Configuration Server. The settings aredownloaded and applied by the Thin Client terminal when a user logs in to the terminal. Configurations with more than twomonitors are not supported by the WCM tool and may require additional local configuration of the display settings at theterminal. For detailed information and examples of the WCM tool, refer to the chapter Dell Wyse Configuration Manager(WCM).

10.19.1 Single and Dual Monitor ConfigurationsThe WCM tool is used to configure the Thin Client terminal display settings, including display resolution and displayposition. The display settings are then deployed to the Thin Client Configuration Server. The Thin Client terminals downloadand apply the configuration settings when a user logs in to the terminal. The following figure shows the display settings in theWCM tool.

Display Settings in WCM Tool


➢➢ To configure the display settings or a terminal with one or two monitors

1. Launch the WCM and open the template file associated with the Thin Client terminal.

2. Select Display under Device Configuration.

3. Configure the display settings to match the resolution and position of each monitor.

4. Enable or disable the Default Display Configuration setting. It is recommended to leave the Default DisplayConfiguration setting enabled (True).

a. To enable the Default Display Configuration mode to allow the Resolution, Color Depth, and Refresh Rate to beautomatically adapted to the capabilities of the connected monitor, select True from the Default DisplayConfiguration drop-down menu.

b. To disable the Default Display Configuration mode to manually set Resolution, Color Depth, and Refresh Rate,select False from the Default Display Configuration drop-down menu.

5. Click Apply Changes to save the changes, then close the WCM.

6. Deploy the configuration to the Thin Client Configuration Server. Refer to the procedure in the section Deploy ThinClient Configuration Files.

Note The configuration deployment can be performed on an individual terminal basis, or the configuration can be donein WCM for all terminals and deployed as a group.


10.19.2 Configure Three or More Monitors (Local Configuration of ThinClient Terminal)The WCM tool only supports configuration for two displays, or in the limited case in which the Windows desktop extendsover four displays of equal resolution arranged horizontally. Any other configuration involving mixed display resolutions,display duplication, non-horizontal, or non-linear monitor arrangement will require the WCM tool to use the Windowsdefaults and Windows must be configured manually. These configurations require reconfiguring Windows display settingswith the Write Filter disabled.

Attention

The WCM tool must be configured for default display settings so that the local ThinClient terminal settings are not overridden by the WCM settings.

➢➢ To configure three or more monitors

1. Launch the WMC and open the template file associated with the Thin Client terminal.

2. Select Display under Device Configuration.

3. Enable the Default Display Settings for Monitor 1 and Monitor 2 in WCM as shown in the following figure.

Display Settings for Multiple Monitors in WCM Tool


4. Click Apply Changes to save the changes, then close WCM.

5. Deploy the template file to the Thin Client Configuration Server. Refer to the procedure in the section Deploy Thin ClientConfiguration Files.

6. Log in to the Thin Client terminal using the local administrator account. Refer to the procedure in the section LocalAdministrator Account Login.

7. Disable the File Based Write Filter. Refer to the procedure To disable the File Based Write Filter. This will reboot theThin Client Terminal and automatically log in as a local user.

8. Log in to the Thin Client terminal using the local administrator account.

9. From the Start menu, select Control Panel , Display, then select Adjust resolution.

10. Configure the resolution and layout of the displays.

11. Click Apply to accept the changes.

12. Close the Control Panel window.

13. Enable the File Based Write Filter. Refer to the procedure in the section Enable File Based Write Filter. This will rebootthe Thin Client Terminal and auto login as a local user.

14. Verify correct display position and cursor movement.

Note If all of the physical ports are not connected, it may be necessary to shift the display port connections between themonitors to achieve the correct display order.


10.20 Thin Client Host Name Modification➢➢ To modify the Thin Client host name



3. Open the Control Panel and select System.

4. Scroll to the Computer name, domain, and workgroup settings area and select Change settings.

5. From the System Properties dialog box Computer Name tab, click Change.


6. Enter the appropriate computer name and click OK to save it.

7. Enable the File Based Write Filter. Refer to the procedure To enable the File Based Write Filter.


Glossary of TermsClient Access License (CAL) A license that grants a client device access to the services provided by the Windows Server.

Domain Controller (DC) A domain controller is a server that responds to security authentication requests (logging in,checking permissions, and so forth) within a Windows domain.

Dynamic Host Configuration Protocol (DHCP) A protocol used to automatically assign and manage dynamic IPaddresses to devices on a network.

Hypertext Transfer Protocol Secure (HTTPS) A protocol for secure communication over a computer network.

Plant Data Highway (PDH) The plant level supervisory network. PDH connects the HMI server with remote viewers,printers, historians, and external interfaces. Usually there is no direct connection to the Mark VIe controllers, whichcommunicate over the UDH. Use of Ethernet with the TCP/IP protocol over PDH provides an open system for third-partyinterfaces

Remote Desktop Protocol (RDP) A proprietary protocol that provides a user with a graphical interface to connect toanother computer over a network connection.

RDS Per Device CAL A Client Access License (CAL) that allows a Thin Client terminal or other device to establish aRemote Desktop session with a Windows Server that has Remote Desktop Services enabled.

Remote Desktop Services (RDS) Allows a user to operate a virtual machine over a network connection.

Remote Desktop Session Host Server AWindows Server with Remote Desktop Services enabled. The Windows Serverwill work in coordination with the Remote Desktop License Server to verify that a device has a valid license before allowingit to establish a Remote Desktop session.

Terminal Services (TS) was renamed Remote Desktop Services in Windows Server 2008 R2.

Virtual Machine (VM) Avirtual computer that emulates a physical computer.

GEH-6849D Glossary of Terms 103Public Information

Notes

104 Control Server Dell Wyse Windows 7 Thin Client GEH-6849Public Information

Public Information