GEH-6849C For public disclosure

Transcription

1 GEH-6849C Control Server Dell Wyse Windows Embedded Standard 7 Thin Client HMI System Support and Maintenance Guide Sept 2017

2 These instructions do not purport to cover all details or variations in equipment, nor to provide for every possible contingency to be met during installation, operation, and maintenance. The information is supplied for informational purposes 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 reflected herein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or to the document itself at any time. This document is intended for trained personnel familiar with the GE products referenced herein. GE may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not provide any license whatsoever to any of these patents. Public This document is 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 for particular purpose. For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE Sales Representative. Revised: Sept 2017 Issued: Dec 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 controls.doc@ge.com

3 Document Updates Revision Location Description Edit Timezone Settings Removed content and replaced with a reference to the section Configure Domain Controllers to Synchronize to Site Time References for the procedure to configure the Domain Controllers to synchronize to the system Time Server Changed the title of this section from Configure Thin Clients to Follow the Verify Thin Client Time Synchronization to Domain System Time Server, and provide the procedure to verify the successful Controllers synchronization of the Thin Client to the Domain Controllers C Added a reference to the Control Server Domain Services Maintenance Guide (GEH-6845), the section Configure Time on Domain Controllers for Verify Domain Controller Time Synchronization the procedures to verify the Domain Controller time synchronization configuration and status, as well as to modify the Domain Controller time settings if required. Remote Desktop Connection Unknown Publisher Warnings Added this section to provide information on the warning displayed when launching a Remote Desktop Connection from a desktop link Replaced the figure Default Display Settings showing updated default settings such as the Default Display Configuration setting for Monitor 1 Edit Display Settings Display Settings Added references to sections containing additional information on monitor connection and arrangement, and configuring Thin Client display settings B based on monitor connection and arrangement Added the following sections with procedures for monitor connection and arrangement, and display setting configuration: Common Procedures Connect Monitors to Thin Client Terminal Configure Thin Client Display Settings Remote Desktop Services Overview Added this chapter with an overview on system setup for multiple configurations for Remote Desktop Services (RDS) Remote Desktop Services Connection Issues Added this section to provide details on possible connection errors and issue resolution Launch RD Licensing Diagnoser Tool Added this section with the procedure to launch the RD Licensing Diagnoser tool Check Location and Status of RDS License Server Added this section with the procedure to check the Location and Status of the RDS License Server Added this section with the procedure to restart the RDS License service Restart RDS License Server on the VM hosting the RDS License Server information A Determine Number of Available Client Licenses in RDS License Server Added this section with the procedure to determine the number of installed and 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 Added the following sections containing procedures: Manage User Sessions on HMI VMs View Active and Disconnected User Sessions Close Disconnected User Sessions Added the following definitions: Glossary of Terms Client Access License (CAL Remote Desktop Session Host Server RDS Per Device CAL GEH-6849C Support and Maintenance Guide 3

4 Acronyms and Abbreviations CAL DHCP EWS FBWF HEX HMI HTTPS MAC PDH RDP RDS UDH VM WCM WES Client Access License Dynamic Host Configuration Protocol Engineering Workstation File Based Write Filter Hexadecimal {0-9, A-F} Human-machine Interface Hypertext Transfer Protocol Secure Media Access Control Plant Data Highway Remote Desktop Protocol Remote Desktop Services Unit Data Highway Virtual Machine Wyse Configuration Manager Windows Embedded Standard Related Documents Document # Title GEH-6840 NetworkST 3.1/4.0 for Mark VIe Controls Application Guide GEH-6846 Control Server Installation and Startup Guide GEH-6847 Control Server Dell Wyse Windows Thin Client Secure Deployment Guide GEH-6850 Control Server Dell Wyse Windows Thin Client User Guide GEH-6721_Vol_I Mark VIe and VIeS Controls Volume I: System Guide 4 GEH-6849C Control Server Dell Wyse WES7 Thin Client

5 Contents 1 Thin Client HMI System Overview Introduction HMI Architecture Thin Client Operation and Support Infrastructure System Configuration and Maintenance Requirements Thin Client Configuration Overview Thin Client Configuration Procedures Configure Thin Client Configuration Server Thin Client Configuration Server Information File Define Thin Client Topology - Create Clients.csv File Integrate and Deploy Thin Client Terminal Thin Client Terminal Preparation and Integration Thin Client Terminal Deployment Create and Deploy Thin Client Configuration Files Add Resource Files Create Thin Client Configuration Template Files Assign Template Files to Thin Clients (Edit Clients.csv) Deploy Thin Client Configuration Files Dell Wyse Configuration Manager (WCM) Launch WCM Edit a Configuration File Default Configuration Template File Overview Example: Edit Default Configuration Template File for Common Thin Client Settings for Site Edit Display Settings Edit Mouse Settings Edit Keyboard Settings Edit Timezone Settings Edit Ethernet Settings Edit Wireless Settings Edit Audio Settings Edit Power Settings Edit Options/Agent Settings Example: Create a Client-specific Template File from the Default Template File Example: Create a New Client Specific Template File from an Existing Site Specific Template File USB Drive Support Enable File Sharing File Share Persistence File Share Removal Remote Desktop Services Overview Troubleshooting Thin Client Configuration Server Issues Successful Thin Client Configuration Download Sequence Example Failed Thin Client Configuration Download Sequence Example No Client Requests Received GEH-6849C Support and Maintenance Guide 5

6 7.4 Configuration Files Cannot Be Found System Configuration and Maintenance Use Cases Failed Dell Wyse Thin Client Deploy New Thin Clients at Site Following a Factory Acceptance Test Deploy All Thin Client Terminals Example Deploy Thin Client Terminals by Name Example Deploy Thin Client Terminals by MAC Address Example Change Local Thin Client Default Account Passwords Verify Thin Client Time Synchronization to Domain Controllers Verify Domain Controller Time Synchronization Troubleshooting Scenarios Failure to Log In to Thin Client Failure to Establish an RDP Connection to a Host Incorrect User Credentials Network Connection Issue or Target Host (VM) is Offline Remote Desktop Services Connection Issues Failure to Update Thin Client Configuration Remote Desktop Connection Unknown Publisher Warning Common Procedures Thin Client Account Login Local User Account Login Local Administrator Account Login Change Local Thin Client User Account Passwords Change Thin Client Local User Account Password Change Thin Client Local Administrator Account Password Get Thin Client Hardware and Software Information Product Information Tag System Information Verify Thin Client Network Connection Verify Connection Status Verify IP Address Assignment from DHCP Verify Domain Name Server (DNS) Status Verify DHCP Server Status Verify Thin Client Domain Network Thin Client Configuration Server Files Location Enable/Disable File Based Write Filter Enable File Based Write Filter Disable File Based Write Filter Check File Based Write Filter Status Open Administrator Mode PowerShell Window on Thin Client Open Administrator Mode PowerShell Window on Windows Server 2012 R Launch RD Licensing Diagnoser Tool Check Location and Status of RDS License Server Restart RDS License Server Determine Number of Available Client Licenses in RDS License Server Manage RDS Per Device CALs GEH-6849C Control Server Dell Wyse WES7 Thin Client

7 Launch RD Licensing Manager Determine Number of Available (Unused) RDS Per Device CALs Revoke Unused Device CAL Manage User Sessions on HMI VMs View Active and Disconnected User Sessions Close Disconnected User Sessions Connect Monitors to Thin Client Terminal Configure Thin Client Display Settings Single and Dual Monitor Configurations Configure Three or More Monitors (Local Configuration of Thin Client Terminal) Glossary of Terms GEH-6849C Support and Maintenance Guide 7

8 Notes 8 GEH-6849C Control Server Dell Wyse WES7 Thin Client

9 1 Thin Client HMI System Overview 1.1 Introduction Control 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 an integrated supervisory control platform, allowing 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 operation of the system. The document scope is limited to the Thin Client terminals and Thin Client support infrastructure. Procedures such as the following 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 Architecture Traditional control system architecture uses stand-alone HMI desktop computers (thick clients) to provide physical interface to 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 of stand-alone HMIs (thick clients). The following figure displays a Control Server architecture that uses a dedicated Thin Client terminal for each HMI VM. In this example, Thin Client 1 is dedicated to hosting connections to HMI1 VM, while Thin Client 2 is dedicated to HMI2 VM, and so forth. Thin Client HMI System Overview GEH-6849C Support and Maintenance Guide 9

10 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 in the following figure. Each Thin Client establishes a user session over an RDP connection to the HMI VM, resulting in concurrent user sessions on the VMs. Typical systems will have more than one HMI VM, and each Thin Client can be configured to connect to one or more of the VMs running on the server. Many Thin Clients to One HMI VM (Many-to-One) Architecture 10 GEH-6849C Control Server Dell Wyse WES7 Thin Client

11 1.3 Thin Client Operation and Support Infrastructure Thin Client configurations are centrally managed from the Control Server. Thin Client configurations are used to manage the connections to the VMs running on the Control Server. From the user s perspective, the Thin Clients are merely remote terminals that provide the interface to the system and provide no useful functionality when disconnected from the system. The Thin Clients function as plug-and-play devices that do not rely on persistent local configuration information. The following infrastructure is maintained in the system to achieve the central management and client plug-and-play deployment of the Thin Clients: Dynamic Host Configuration Protocol (DHCP) Server: the Thin Clients use DHCP to obtain their network configuration. Thin Clients are configured out of the box to use DHCP. In the Controls Server architecture, the domain servers act as the DHCP servers. Thin Client Configuration Server: the Hypertext Transfer Protocol Secure (HTTPS) server hosting the Thin Client configuration and software files is typically hosted on the Engineering Workstation (EWS) VM, since the EWS provides most 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 manage the Thin Clients. Example Thin Client System HMI VM Infrastructure Thin Client HMI System Overview GEH-6849C Support and Maintenance Guide 11

12 A general overview of system components and data flow are provided in the following diagram. This is an example scenario when one of the Thin Clients in the system has been powered off for some time and is restarting. The numbered sequence for startup and data flow between the Thin Clients and the VMs (running within the Control Server) is explained in the following table. # Description System Components and Data Flow Overview Diagram Startup Numbered Sequence and Data Flow Diagram Notes The Thin Client starts up, then broadcasts a DHCP request for its network configuration. DC1 (the system domain controller) responds to this request with the IP address assigned to the Thin Client. The Thin Client connects to the Thin Client configuration server and downloads and executes its client-specific configuration file stored on the server. The connection to the target VM is automatically established by the Thin Client or manually by the user according to the 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 Thin Client HMI system (the user interacts with the remote HMI VM on the Control Server from the local Thin Client terminal). 12 GEH-6849C Control Server Dell Wyse WES7 Thin Client

13 1.4 System Configuration and Maintenance Requirements The system elements related to supporting the Thin Clients and an overview of their configuration and maintenance requirements are provided in the following table. System Element DHCP Servers Thin Client Configuration Server Thin Client Terminals Description The Domain Controller VMs (DC1 and DC2) are configured as redundant DHCP servers used by Thin Clients to retrieve their IP Address. The Thin Client s configuration is centrally managed from the Configuration Server. The majority of Thin 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 Thin Client startup sequence. The Thin Client configuration is entirely driven by the configuration files that are created and maintained on the server. A Thin Client is a purpose-built computer with a keyboard, mouse, monitor, and an Ethernet connection to the plant network. The Thin Client s primary function is to provide an access point to the Control Server VMs and other servers. Thin Clients are configured by the System Administrator to provide a predefined set of server connections through managing the entries in the configuration files stored on the Thin Client Configuration Server. Thin Client terminals can be configured to provide a dedicated connection to a single VM, or to allow the user to initiate connections as needed. Over the life of the system, circumstances can arise that may require minor modifications to the INI files, such as the need to replace a failed Thin Client terminal. These scenarios and the required INI file modifications are documented in this manual. Thin Client HMI System Overview GEH-6849C Support and Maintenance Guide 13

14 Notes 14 GEH-6849C Control Server Dell Wyse WES7 Thin Client

15 2 Thin Client Configuration Overview Thin Client configuration is performed in two stages: Stage one involves integration and deployment of the terminals into the Control Server infrastructure. This process is only required to be done once on each terminal. Stage two includes creating the Thin Client terminal specific configuration files and deploying them on the Thin Client Configuration Server. The configuration files are used to define the appearance and behavior of the Thin Client terminals. Each Thin Client downloads the configuration files from the Configuration Server. Configuration file editing and deployment is performed during initial configuration 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 Client Configuration 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 security hardening 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 and whenever 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 created and deployed on the Thin Client Configuration Server regardless of whether the physical Thin Client terminals have been deployed. Conversely, Thin Client terminals can be deployed regardless of whether the configuration files have been created for them; they will download a default configuration until a specific configuration file becomes available for them on the Thin Client Configuration Server. Thin Client Configuration Overview GEH-6849C Support and Maintenance Guide 15

16 Notes 16 GEH-6849C Control Server Dell Wyse WES7 Thin Client

17 3 Thin Client Configuration Procedures This 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 Server The Thin Client Configuration Server is used to create the Thin Client configuration files and make them available to the Thin Clients for download as needed. The Thin Client Configuration Server is typically hosted by the EWS VM, and is loaded with template configuration files and Windows PowerShell scripts used to manage Thin Client configurations Thin Client Configuration Server Information File The Server.csv file can be used to change the Thin Client Configuration Server information for the site in the rare event that the default values are not used at the site. Default values are provided in the ServerTemplate.csv file, as follows: Protocol, Server, Port # HTTPS, , 924 If the default values must be changed for the site, open the %SystemDrive%\intepub\WCM-Templates folder, copy the ServerTemplate.csv file to Server.csv, and edit the values to match those used by the site. The Server.csv file is used as the source for the utilities that need the server information. Thin Client Configuration Procedures GEH-6849C Support and Maintenance Guide 17

18 3.1.2 Define Thin Client Topology - Create Clients.csv File The 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.csv file. The first step in configuring the Thin Clients in a new system is to copy ClientsTemplate.csv to Clients.csv, then add entries for each Thin Client. The Clients.csv file provides the inventory of Thin Client terminals at the site and should include entries for any spare terminals available at the site. The following example is a Clients.csv file that has been configured with site information: Example Clients.csv File Client, Type, MACAddress, Template, Description # Default7, WES7, *, Default, Default WES7 Configuration GT1, WES7, F60EFE, Default, PECC for GT1 GT2, WES7, F60F8D, Default, PECC for GT2 ST1, WES7, F6129E, Default, PECC for ST1 CRM-Main, WES7, F6100D, Default, Control Room Main Display CRM-Eng, WES7, F612AF, Default, Control Room Engineering Spare1, WES7, F609D1, Default, Spare Windows Thin Client #1 Spare2, WES7, F61028, Default, Spare Windows Thin Client #2 Clients.csv File Columns Column Description Client Descriptive name used to uniquely identify each Thin Client Type 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 client Description 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 being configured. Enter the MAC addresses of any temporary terminals that will be used during staging of the system, before the actual Thin Client terminals become available in the lab or at the site. Leave the MAC entries blank for any terminals that are not 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 quickly applied 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. 18 GEH-6849C Control Server Dell Wyse WES7 Thin Client

19 3.2 Integrate and Deploy Thin Client Terminal Thin Clients must be integrated and deployed into the Control Server infrastructure before they can download their configuration files from the Thin Client Configuration Server Thin Client Terminal Preparation and Integration The Thin Client terminals must go through a preparation process that integrates them into the Control Server infrastructure before they can be deployed in the Control Server infrastructure. Preparation procedures include adding the terminals to the domain network and removing unused software for security hardening purposes. Preparation procedures must be performed on each Thin Client and are independent of any site-specific configuration, which allows them to be performed on the Thin Client terminals as soon as they (and the Control Server infrastructure) become available. It is critical to perform all procedures outlined in the following sections. All steps within each section must be performed exactly as documented and in the order provided. The overall procedure is divided into three parts to make the process more understandable, but the sections are interdependent and must be performed from start to finish as a coherent set in the following order: Attention 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 the event of a terminal failure the prepared spare can replace the failed unit without having to go through the preparation process in a potentially time critical situation. Spare units can be temporarily connected to the network, configured, and returned to storage until they are needed Determine if Preparation is Required Any Thin Client terminal that has just been removed from its sealed packaging needs to be prepared. If the state of the client is unclear, preparation must be verified before the terminal can be deployed in the system. The terminal s preparation status can be checked by verifying the terminal s Domain network membership. For instructions, refer to the section Verify Thin Client Domain Network. Note If the terminal is a member of the default WORKGROUP domain it needs to be added to the domain network. Thin Client Configuration Procedures GEH-6849C Support and Maintenance Guide 19

20 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 (FBWF) (the Thin Client will reboot). For instructions, refer to the section Enable/Disable File Based Write Filter. 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 the local Administrator account (steps 3 5). 8. From the Start menu, launch the Windows Control Panel and select Network and Sharing Center. 9. Select Public network and change it to Work network. Windows Control Panel Network and Sharing Center Public Network 20 GEH-6849C Control Server Dell Wyse WES7 Thin Client

21 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 Thin Client Configuration Procedures GEH-6849C Support and Maintenance Guide 21

22 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) 22 GEH-6849C Control Server Dell Wyse WES7 Thin Client

23 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. Thin Client Configuration Procedures GEH-6849C Support and Maintenance Guide 23

24 Remove Unused Software The 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 the Windows 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. 24 GEH-6849C Control Server Dell Wyse WES7 Thin Client

25 3. Uninstall Citrix Receiver as follows: a. Right-click Citrix Receiver and select Uninstall. b. Click Yes to confirm the uninstall. Expect a delay of ~60 seconds before the uninstall begins. Citrix Receiver will be removed from the displayed list of installed 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. b. Click Yes to confirm the 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. b. Click Yes to confirm the 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. Uninstall Microsoft 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 NP API as follows: a. Right-click Adobe Flash Player xx NP API 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. Uninstall Microsoft Silverlight as follows: a. Right-click Microsoft Silverlight and select Uninstall. b. Click Yes to confirm the uninstall. Microsoft Silverlight will be automatically removed from the displayed list of installed programs. 10. Close the Programs and Features window. Thin Client Configuration Procedures GEH-6849C Support and Maintenance Guide 25

26 Join Domain Network and Apply Group Policy The final step in the preparation process is adding the Thin Client terminal to the domain network for security hardening and remote configuration management. The Join-WES7.ps1 PowerShell script hosted on the Thin Client Configuration Server is used 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 hosting the 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. 26 GEH-6849C Control Server Dell Wyse WES7 Thin Client

27 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 Mode PowerShell Window on Thin Client. 3. Issue the Set-ExecutionPolicy Unrestricted Scope Process -Force command from the PowerShell prompt as shown in the 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] key to execute the command. Join-WES7.ps1 Script Command Thin Client Configuration Procedures GEH-6849C Support and Maintenance Guide 27

28 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 local Administrator 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 least 60 seconds for the command to complete. gpupdate /force Command 10. Enable the File Based Write Filter (FBWR) (the Thin Client will reboot). Refer to the section Enable/Disable File Based Write Filter. 11. Allow the client to automatically log in to the Local User account. 28 GEH-6849C Control Server Dell Wyse WES7 Thin Client

29 3.2.2 Thin Client Terminal Deployment Once the preparation process is complete, the Thin Clients can be deployed into the Control Server infrastructure. Thin Client deployment involves pushing the Thin Client Configuration Server information to the clients so they know how to get their configuration 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 a group from the Thin Client Configuration Server. Windows Thin Client Deployment Clients.csv+ EWS VM Server.csv* Legend * + Server Info is pushed to the clients Server.csv is used if it exists, otherwise defaults are used Only clients found in Clients.csv will be configured Thin Clients Configure-WCMClient.ps1 The Configure-WCMClient.ps1 script is run from the EWS VM and configures the Thin Clients found in the Clients.csv file with 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. The Configure-WCMClient.ps1 script uses the entries in the Clients.csv file to discover the Thin Clients. Executing the script with the All command line option will remotely configure the Thin Client Configuration Server information for all of the clients listed in Clients.csv. The Client option can be used to specify a particular client or group of clients by name. Clients that are not entered in Clients.csv can be configured by MAC address using the MAC option. Thin Client Configuration Procedures GEH-6849C Support and Maintenance Guide 29

30 Deploy All Thin clients All of the Thin Clients for the system (as defined in the Clients.csv file) can be deployed at one time. Refer to the section Deploy 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 Deploy Thin Clients by Name Thin Clients can be deployed individually or in groups by name (as defined in the Clients.csv file). Refer to the section Deploy Thin Client Terminals by Name Example. To deploy Thin Clients by name 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 Client [name] option Deploy Thin Clients by MAC Address Thin Clients can be deployed individually or in groups by MAC address. Refer to the section Deploy Thin Client Terminals by MAC Address Example. To deploy Thin Clients by MAC address 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 MACAddress [MAC address] option Configure-WCMClient.ps1 Status Values Status Value Bad MAC Address Cannot Resolve Hostname Cannot Contact Hostname Cannot Authenticate to Hostname Already Configured Configured Description The MAC address was incorrectly formatted. MAC addresses must contain 12 valid HEX digits. The hostname could not be resolved over DNS. This error will occur if the Thin Client has not been joined to the domain, which is most likely an indication that the Thin Client preparation procedure was not performed on the target Thin Client terminal. The Thin Client is offline. The user credentials provided were invalid or did not provide administrator privileges on the Thin Client. The Thin Client Configuration Server information was read from the Thin Client and found to be correct- no action was needed. The Thin Client Configuration Server information was successfully written to the Thin Client. 30 GEH-6849C Control Server Dell Wyse WES7 Thin Client

31 3.3 Create and Deploy Thin Client Configuration Files The 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 requisition process. 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 configuration scripts used to create the configurations are installed in the %SystemDrive%\inetpub\WCM-Templates folder. Refer to section Thin 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. Windows Thin Client Configuration EWS VM Legend Clients download their configuration files at user login Default.xml Thin Clients Clients.csv Template.xml files Image Files Deploy-WCMConfiguration.ps1 Configuration (XML) Files Image Files Thin Client Configuration Server Note The procedures in this section can be performed without access to the Thin Client terminals. The configuration template files are created and deployed on the server for future download by the Thin Clients when they are deployed in the system. Thin Client Configuration Procedures GEH-6849C Support and Maintenance Guide 31

32 3.3.1 Add Resource Files The primary resource file used in the Thin Client configuration is the image used for the desktop wallpaper. A default desktop wallpaper image file (GEDesktop.jpg) is provided in the WCM-Templates\Resources folder. This folder serves as the source for 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 they can easily be located when using the Wyse Configuration Manager (WCM) tool to configure the Thin Client template files Create Thin Client Configuration Template Files The Windows 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 to generate 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 Configuration GT1, WES7, F60EFE, ToHMI1, PECC for GT1 GT2, WES7, F60F8D, ToHMI2, PECC for GT2 ST1, WES7, F6129E, ToHMI2, PECC for ST1 CRM-Main, WES7, F6100D, ToHMI1, Control Room Main Display CRM-Eng, WES7, F612AF, ToEWS1, Control Room Engineering Spare1, WES7, F609D1, Default, Spare Windows Thin Client #1 Spare2, WES7, F61028, 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 shared by the GT1 and CRM-Main Thin Clients. The ToHMI2 template file, which creates an RDP connection to the HMI2 VM, is shared by the GT2 and ST1 Thin Clients. The ToEWS1 template file, which creates an RDP connection to the EWS1 VM, is only applied to the CRM-ENG Thin Client. The use of template files allows sharing of common configuration templates so that 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 the default configuration template file (default.xml), which serves as the default configuration used by clients that have not been associated with a site-specific configuration. The default configuration template file also serves as the starting point for site specific 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 the template file settings, along with examples of using the WCM tool. 32 GEH-6849C Control Server Dell Wyse WES7 Thin Client

33 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 configuration template files can be specific to a particular Thin Client terminal, or they can be shared between multiple terminals Deploy Thin Client Configuration Files The template files must be deployed to the Thin Client Configuration Server to make them available for download by the Thin 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 the Deploy-WCMConfiguration.ps1 script. Note Refer to the section Open Administrator Mode PowerShell Window on Thin Client for the procedure to launch Windows 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 and copy the necessary files to the Thin Client Configuration Server. Executing the Deploy-WCMConfiguration.ps1 script will deploy 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 to a missing template file. Deploy-WCMConfiguration.ps1 Script Error - Missing Template File Thin Client Configuration Procedures GEH-6849C Support and Maintenance Guide 33

34 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, which allow targeted deployment of individual or groups of Thin Clients; however, there is no problem with deploying the configuration files multiple times. Note It is recommended to run Deploy-WCMConfiguration.ps1 against all clients defined in Clients.csv so that all issues with all client configurations can be addressed. 34 GEH-6849C Control Server Dell Wyse WES7 Thin Client

35 The following figure shows the results of running the Deploy-WCMConfiguration.ps1 script. Deploy-WCMConfiguration.ps1 Script Results Thin Client Configuration Procedures GEH-6849C Support and Maintenance Guide 35

36 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 the resource files are found in the WES7Config 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 files created and edited in the %SystemDrive\inetpub\WCM-Templates folder serve as the configuration source files. They are deployed here in their required format and downloaded 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. 36 GEH-6849C Control Server Dell Wyse WES7 Thin Client

37 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 is hosted. 4.1 Launch WCM WCM 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. Provide administrator credentials if requested. Launching WCM in Administrator Mode Dell Wyse Configuration Manager (WCM) GEH-6849C Support and Maintenance Guide 37

38 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. 38 GEH-6849C Control Server Dell Wyse WES7 Thin Client

39 The selected configuration opens and is ready for editing. Open Configuration File Dell Wyse Configuration Manager (WCM) GEH-6849C Support and Maintenance Guide 39

40 4.3 Default Configuration Template File Overview When the configuration template file is open in WCM, the left hand navigation pane shows the main configuration areas, and the right hand pane contains the configuration parameters of the selected configuration area. Default Configuration Template File Opened in WCM Main Configuration Areas Item Connections Device Configuration OS Configuration Description The primary focus of the Thin Client configuration. This is where the RDP Connections that will be made available from the Thin Client are added. The default template does not include any preconfigured RDP connections. These are the terminal level settings. Some settings, like the Display settings, can be different between clients- for example, multiple monitor settings. Other settings will be common to all Thin Clients at the site. Only the common parameters should be set in the default configuration template file- these will be discussed further in the next section. 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. 40 GEH-6849C Control Server Dell Wyse WES7 Thin Client

41 4.4 Example: Edit Default Configuration Template File for Common Thin Client Settings for Site The first step in creating the Thin Client configuration template files for the site is to edit the default configuration template file. The default configuration template file is used to set the system level settings that are common to all of the Thin Clients at the site, such as the timezone or server location settings. The default configuration template file is installed on the Thin Client Configuration Server as part of the system configuration, and it provides the typical default values for the common Thin 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.xml template file. Default.xml Template File Note The common client settings are found in the Device Configuration area. Dell Wyse Configuration Manager (WCM) GEH-6849C Support and Maintenance Guide 41

42 4.4.1 Edit Display Settings The display settings will need to be changed in some cases to match differences in the number of connected monitors and other 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 make changes 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 image that would be applied to all clients can be substituted here. Note also that the Multiple Displays setting is set to Extend these displays by default. This setting works correctly with single and multiple monitors. In some circumstances it might be appropriate to use the Duplicate these displays setting, but this would be a custom setting that would be overridden in another template created from this one for a specific client or group of clients. The Monitor Display Settings are also set to default values that are appropriate for most clients which can be overridden as needed in template files created from this default template. Note For additional details on monitor connection and arrangement, refer to the section Connect Monitors to Thin Client Terminal. For details on configuring the Thin Client display settings based on the resolution and physical arrangement of the monitors connected to the Thin Client terminal, refer to the section Configure Thin Client Display Settings. 42 GEH-6849C Control Server Dell Wyse WES7 Thin Client

43 4.4.2 Edit Mouse Settings The 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 hand pane and make changes as needed. Mouse Settings Edit Keyboard Settings The 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 and delay settings: select the Keyboard setting (check the Keyboard box) in the left hand pane and make changes as needed. Keyboard Settings Dell Wyse Configuration Manager (WCM) GEH-6849C Support and Maintenance Guide 43

44 4.4.4 Edit Timezone Settings The Timezone settings are included in the template and are set to Eastern Standard Time by default. Modify the Timezone setting 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 Domain Controllers because they are domain members. Refer to the section Configure Domain Controllers to Synchronize to Site Time References 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 make changes as needed. Timezone Settings Edit Ethernet Settings The Ethernet settings are included in the template and are set to enable DHCP by default. This value must be set to True for all clients. The other values are not used and should be left blank. Ethernet Settings 44 GEH-6849C Control Server Dell Wyse WES7 Thin Client

45 4.4.6 Edit Wireless Settings The Wireless Settings are disabled and cannot be edited. The clients are not equipped with wireless adapters, so this section does not apply Edit Audio Settings The Audio settings are included in the template and are set to the values shown by default. These values would likely be modified in other templates depending on the environment the client is in and whether sound is required from the client. Audio Settings Dell Wyse Configuration Manager (WCM) GEH-6849C Support and Maintenance Guide 45

46 4.4.8 Edit Power Settings The Power settings are included in the template and are defaulted to the values shown. The clients are set to never sleep or turn off their displays by default. This behavior can be modified based on the requirements of the site and the location of the client. Clients that are in remote locations and are rarely used may be configured to sleep after a period of inactivity, while clients in the main control room may be required to stay active at all times. Power Settings Edit Options/Agent Settings The Agent Settings provide the information required for downloading the configuration files from the Thin Client Configuration Server. These settings should not be modified for most systems, however these values must be edited to match the entries in the Server.csv file in the rare case that a system is using a non-standard Thin Client Configuration Server address and/ 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. 46 GEH-6849C Control Server Dell Wyse WES7 Thin Client

47 Agent Settings Note The default server settings are shown in the figure Agent Settings. Import configuration on every boot and Enable Balloon Tips should always be enabled. Use WDM should always be disabled. The DHCP Tag No. fields do not apply. Dell Wyse Configuration Manager (WCM) GEH-6849C Support and Maintenance Guide 47

48 4.5 Example: Create a Client-specific Template File from the Default Template File The default configuration template provides the typical default values for the Thin Client configuration values common to all clients at the site and is used as the starting point for all of the Thin Client configuration files. The primary difference between the different template files is the RDP connections that are created on the Thin Client desktop, and the number of monitors connected 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 48 GEH-6849C Control Server Dell Wyse WES7 Thin Client

49 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 to True will cause the connection to be launched whenever the user is logged in to the client. The Display settings can be modified to meet the requirements of the site. Setting Multi-Monitor Support and Full Screen Mode to True will cause the RDP 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-mounted monitor that is mirroring the local monitor. Dell Wyse Configuration Manager (WCM) GEH-6849C Support and Maintenance Guide 49

50 5. Select the Display area and set the Multiple Displays property to Duplicate these displays. 6. Select the Timezone area and set the Timezone Name property. 50 GEH-6849C Control Server Dell Wyse WES7 Thin Client

51 Since this template is for a client in the main control room driving a wall-mounted display we will leave the power settings with 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 Dell Wyse Configuration Manager (WCM) GEH-6849C Support and Maintenance Guide 51

52 4.6 Example: Create a New Client Specific Template File from an Existing Site Specific Template File In this example, we will create a template file for a client exactly like the ToCRM1.xml template created in the previous example, 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 IP Address 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 the same as the ToCRM1.xml template. Select Save/Save As from the main menu and give the template a descriptive name like ToCRM2 for this example. Since we started with the ToCRM1.xml template the path will already be set to the inetpub\wcm-templates\wes7\ folder. 52 GEH-6849C Control Server Dell Wyse WES7 Thin Client

53 5 USB Drive Support USB drives plugged into the Thin Client can be shared for access by the VMs in the Control Server. The Windows operating system automatically detects and mounts USB drives plugged into the USB port. A local Thin Client Administrator can 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 on as a Local Administrator to the Thin Client. 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 require updating, 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 file access 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 to the shared drive. USB Drive Support GEH-6849C Support and Maintenance Guide 53

54 Note The Thin Client local Administrator account credentials are required when accessing the shared directory from a VM or another Thin Client. 5.2 File Share Persistence The 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 Based Write Filter, creating the share, then turning the File Based Write Filter back on. 5.3 File Share Removal Leaving 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, then turn the File Based Write Filter back on. 54 GEH-6849C Control Server Dell Wyse WES7 Thin Client

55 6 Remote Desktop Services Overview Systems can be set up for one Thin Client terminal to one HMI VM operation (one-to-one), or many Thin Client terminals to one 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 Services License Server is configured on the Engineering Workstation (EWS) VM. The HMI VMs are configured as Remote Desktop Session Host Servers using the Per Device licensing mode. The Thin Client terminals are issued RDS Per Device Client Access Licenses (CALs) by the Remote Desktop License Server. When a Thin Client terminal connects to an RD Session Host server (HMI VM) for the first time, the client is issued a temporary license. When a client connects to an RD Session Host server (HMI VM) for the second time, the license server issues it a permanent RDS Per Device CAL, providing there are CALs 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 available RDS Per Device CALs on the license server and lead to RDP connection issues. Per Device CALs are purchased based only on the number of Thin Client terminals. VM to VM RDP connections are also allocated licenses from this pool and should therefore only be initiated from a single VM in the system, and it is recommended that only the EWS VM be used for this purpose. User Sessions The HMI VMs run within the Windows Server operating system. Windows Server supports up to two concurrent user sessions by default, and supports an unlimited number of user sessions when RDS is enabled. Typically, whenever a Remote Desktop connection is established with the VM, a new user session is created based on the user credentials provided when the connection is established. In this case, the user session is in the Connected state because it is associated with an active Remote Desktop connection. If the user logs out of the connection, the user session is terminated and the Remote Desktop connection is closed. However, if the user simply closes the Remote Desktop connection without logging out, the user session remains active on the server in a Disconnected state. The user can establish a new Remote Desktop connection and resume the Disconnected 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 Manager can also be used to close Disconnected sessions. Refer to the section Manage User Sessions on HMI VMs for detailed procedures. Windows Task Manager Remote Desktop Services Overview GEH-6849C Support and Maintenance Guide 55

56 Notes 56 GEH-6849C Control Server Dell Wyse WES7 Thin Client

57 7 Troubleshooting Thin Client Configuration Server Issues The Thin Client Configuration Server is an IIS Server typically running on the site s Engineering Workstation (EWS). The Thin 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 used to determine if the Thin Clients are attempting to download files from the server, what files are being requested, and an indication of the problem if a failure occurs. The log files are stored in the directory /intepub/logs/logfiles/w3svc1/. The log files 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, with the return status in bold. Each highlighted entry is followed by an explanation of what was requested and why. Status Entry Indication 200 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 Not Allowed) Requests that were rejected 7.1 Successful Thin Client Configuration Download Sequence Example The following example shows the typical sequence as observed in the web server log files during a successful Thin Client configuration file download :55: PROPFIND /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) The client at address issues a PROPFIND request for the /WCM/Wyse/WES7/008064F60EFE/WES7Config. xml file to the server at address 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 :55: GET /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) The client at address issues a Get request for the /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml file to the server at address at Port 924. The GET request is successful as indicated by the 200 return value. This sequence shows that the Thin Client successfully downloaded its configuration file. Troubleshooting Thin Client Configuration Server Issues GEH-6849C Support and Maintenance Guide 57

58 7.2 Failed Thin Client Configuration Download Sequence Example The following example shows a typical sequence as observed in the web server log files when the Thin Client configuration files have not been deployed to the Thin Client Configuration Server. The Thin Client requests its configuration files, but they do not exist on the server :56: PROPFIND /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) The client at address issues a PROPFIND request for the /WCM/Wyse/WES7/008064F60EFE/WES7Config. xml file to the server at address at Port 924. The 404 return value (File Not Found Error) indicates that the requested file could not be found at the given URL :56: GET /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) The client at address issues a GET request for the /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml file to the server at address at Port 924. The 404 return value (File Not Found Error) indicates that the requested file 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 making new requests :56: PROPFIND /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) :56: GET /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) :56: PROPFIND /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) :56: GET /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) :56: PROPFIND /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) :56: GET /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) :56: PROPFIND /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) :56: GET /WCM/Wyse/WES7/008064F60EFE/WES7Config.xml Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR ;+.NET+CLR ) GEH-6849C Control Server Dell Wyse WES7 Thin Client

59 7.3 No Client Requests Received If no Thin Client requests are logged after restarting a Thin Client, the Thin Client(s) may not be configured with the correct Thin Client Configuration Server information. Refer to the sections Configure Thin Client Configuration Server Information File and Integrate and Deploy Thin Client Terminal to verify the Thin Client preparation and deployment state. 7.4 Configuration Files Cannot Be Found If the server returns 404 File Not Found errors for the Thin Client requests, the configuration files cannot be found on the Thin Client Configuration Server and need to be deployed to the server. Refer to the section Deploy Thin Client Configuration Files and verify that the Thin Client configuration files have been successfully deployed to the Thin Client Configuration Server. Troubleshooting Thin Client Configuration Server Issues GEH-6849C Support and Maintenance Guide 59

60 Notes 60 GEH-6849C Control Server Dell Wyse WES7 Thin Client

61 8 System Configuration and Maintenance Use Cases This chapter describes scenarios related to both initial site installation and long term maintenance of the site that a plant maintenance engineer is likely to encounter. 8.1 Failed Dell Wyse Thin Client If 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 and Integration 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 Get Thin Client Hardware and Software Information for the procedure to get the MAC Address from the Product Information Tag of the Thin Client terminal. 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 Thin Client 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 Client Configuration Server. System Configuration and Maintenance Use Cases GEH-6849C Support and Maintenance Guide 61

62 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 spare terminal 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 Configuration GT1, WES7, F60EFE, Default, PECC for GT1 GT2, WES7, F60F8D, Default, PECC for GT2 ST1, WES7, F6129E, Default, PECC for ST1 CRM-Main, WES7, F6100D, Default, Control Room Main Display CRM-Eng, WES7, F612AF, Default, Control Room Engineering Spare1, WES7, F609D1, Default, Spare Windows Thin Client #1 Spare2, WES7, F61028, 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 the MAC 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 Configuratin GT1, WES7, F60EFE, Default, PECC for GT1 GT2, WES7, F60F8D, Default, PECC for GT2 ST1, WES7, F6129E, Default, PECC for ST1 CRM-Main, WES7, F61028, Default, Control Room Main Display CRM-Eng, WES7, F612AF, Default, Control Room Engineering Spare1, WES7, F609D1, Default, Spare Windows Thin Client #1 Spare2, 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 the Deploy-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 Client Configuration Server. 7. When a new spare arrives at the site, perform the procedures in the section Integrate and Deploy Thin Client Terminal to deploy the terminal into the Control Server infrastructure. Enter the MAC Address of the new terminal in the Spare2 entry in Clients.csv. The new terminal is ready to replace the next failed terminal. 62 GEH-6849C Control Server Dell Wyse WES7 Thin Client

63 8.2 Deploy New Thin Clients at Site Following a Factory Acceptance Test In many cases, the Control Server will be configured and staged in the factory using temporary Thin Client terminals, which will 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 Example The following example shows how to configure the Thin Client terminals using the Thin Client Configuration Server information. In this example system, the Thin Clients have been defined and associated with physical terminals in the following 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 Configuration GT1, WES7, F60EFE, Default, PECC for GT1 GT2, WES7, F60F8D, Default, PECC for GT2 ST1, WES7, F6129E, Default, PECC for ST1 CRM-Main, WES7, F6100D, 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 Thin Client has been prepared and returned to the store room so it is not connected to the PDH network. System Configuration and Maintenance Use Cases GEH-6849C Support and Maintenance Guide 63

64 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 PowerShell Window 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.csv file, GT1 was successfully deployed (updated with the Thin Client Configuration Server information), and the remaining Thin Clients were already up to date. Running the script again shows that all clients are up-to-date and do not need to be configured. Clients Already Configured 64 GEH-6849C Control Server Dell Wyse WES7 Thin Client

65 8.4 Deploy Thin Client Terminals by Name Example The following example shows how to deploy an individual Thin Client. In this example system, the Thin Clients have been defined 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 Configuration GT1, WES7, F60EFE, Default, PECC for GT1 GT2, WES7, F60F8D, Default, PECC for GT2 ST1, WES7, F6129E, Default, PECC for ST1 CRM-Main, WES7, F6100D, 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 PowerShell Window 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 in the following example: Configure-WCMClient.ps1 Client GT1,GT2 System Configuration and Maintenance Use Cases GEH-6849C Support and Maintenance Guide 65

66 8.5 Deploy Thin Client Terminals by MAC Address Example The 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 Get 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 Window on 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 the following example: Configure-WCMClient.ps1 MACAddress F60EFE,008064F608FD 8.6 Change Local Thin Client Default Account Passwords Thin Clients are shipped from the factory with a Local User and Administrator account. The default password for both of these accounts is DellCCCvdi. This widely-shared default password must be changed on all of the Thin Clients at the site as part of the handover procedure in order to prevent unauthorized users from logging in to the Thin Client terminals. Refer to the section Change Local Thin Client Default Account Passwords for the procedure to modify the default account passwords. 66 GEH-6849C Control Server Dell Wyse WES7 Thin Client

67 8.7 Verify Thin Client Time Synchronization to Domain Controllers Because the Thin Clients are members of the Domain, they will only use the system Domain Controllers to synchronize their time. This requires the Domain Controllers to be configured to synchronize to the site time sources to provide a consistent time reference between the Thin Clients (which use the Domain Controller time) and the HMIs (which use the site time sources as the time reference). Perform the following procedure to verify the successful synchronization of the Thin Client to the Domain Controllers. To verify the successful synchronization of the Thin Client to the Domain Controllers 1. Log in to the Thin Client s local administrator account. Refer to the section Local Administrator Account Login. 2. Open a Windows Command window. 3. Issue the command w32tm /query /status. The command output (illustrated in the following figure) shows that the Thin Client is successfully synchronized to DC2. Thin Client synchronization to either DC1 or DC2 is expected. Refer to Control Server Domain Services Maintenance Guide (GEH-6845), the section Configure Time on Domain Controllers for the procedures to verify the Domain Controller time synchronization configuration and status, as well as to modify the configuration if required. Time Sync Verification Command 8.8 Verify Domain Controller Time Synchronization Refer to the Control Server Domain Services Maintenance Guide (GEH-6845), the section Configure Time on Domain Controllers, for the procedures to verify the Domain Controller time synchronization configuration and status, as well as to modify the Domain Controller time settings if required. System Configuration and Maintenance Use Cases GEH-6849C Support and Maintenance Guide 67

68 Notes 68 GEH-6849C Control Server Dell Wyse WES7 Thin Client

69 9 Troubleshooting Scenarios This chapter describes potential failure modes and provides procedures to determine root cause and issue resolution. 9.1 Failure to Log In to Thin Client The user can log in to the Thin Clients using one of the default local accounts, or using a Domain account configured in the Domain 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-6849C Support and Maintenance Guide 69

70 9.2 Failure to Establish an RDP Connection to a Host Thin Clients typically communicate with VMs running on the Control Server and can also include servers on other systems. After the login to the Thin Client is successful, a connection to a host is initiated. The connections can be launched automatically or they can be initiated manually 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 Incorrect User Credentials If login to the host fails, the following dialog box displays. Verify that the username, domain, and password information are correct. Login Attempt Failed 70 GEH-6849C Control Server Dell Wyse WES7 Thin Client

71 9.2.2 Network Connection Issue or Target Host (VM) is Offline If the Thin Client network connection has been lost (refer to the section Verify Thin Client Network Connection), or the target VM is offline, the Remote Desktop Connection displays the following error dialog box. Follow the instructions provided in the Remote Desktop Connection Error Message. Remote Desktop Connection Error Message Remote Desktop Services Connection Issues Remote Desktop Services (RDS) connection related errors, similar to the following example, may occur on systems configured for many Thin Client terminals to one HMI VM operation (many-to-one). RDS connection issues can be caused by Remote Desktop License Server issues or an insufficient number of RDS Per Device CALs. 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 CALs is not sufficient to cover the number device connections required by the site. Refer to the section Manage RDS Per Device CALs. Troubleshooting Scenarios GEH-6849C Support and Maintenance Guide 71

72 9.3 Failure to Update Thin Client Configuration Thin Clients download their configuration files from the server. If the server is unavailable, the Thin Clients will use locally cached copies of the configuration files that were downloaded from the server on the last successful attempt. If the Thin Clients are not updating their configuration files after changes have been made on the server, the problem may a result of any of the following situations: A network issue is preventing the Thin Client from downloading the files from the server. Refer to the section Verify 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 Publisher Warning The Remote Desktop Connection Unknown Publisher warning message is typically displayed when a Remote Desktop connection is launched using a desktop icon. The Unknown Publisher message indicates that the desktop RDP file has not been signed. This is not an indication of an authentication failure between the Thin Client and the Remote Host. Click the Connect button if you want to proceed with the connection process. Remote Desktop Connection Unknown Publisher Warning 72 GEH-6849C Control Server Dell Wyse WES7 Thin Client

73 10 Common Procedures This chapter contains common procedures used for maintenance and debugging Thin Client Account Login Local User Account Login Thin Clients are configured to automatically log in to the Local User account. The auto login does not require the user to enter the Local User account password. Note The default user password is set to DellCCCvdi from the factory Local Administrator Account Login Changes 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 to the 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 backslash characters) 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-6849C Support and Maintenance Guide 73

74 10.2 Change Local Thin Client User Account Passwords Thin 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 Client terminals at the site Change Thin Client Local User Account Password Use the following procedure to change the local User account password and update the auto login password setting with the newly 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. 2. Disable the Filter Based Write Filter. Refer to the section Enable/Disable File Based Write Filter. 3. The Thin Client will restart and automatically log in to the Local User account. 4. Log in to the Local Administrator account. Refer to the section Local Thin Client Administrator Account Login. 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. 11. Close the Dell Thin Client Application. Default Password Field 74 GEH-6849C Control Server Dell Wyse WES7 Thin Client

75 12. Enable the Filter Based Write Filter (client will reboot). 13. Verify that the auto login is successful after reboot Change Thin Client Local Administrator Account Password Use 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. 2. Disable the Filter Based Write Filter. Refer to the section Enable/Disable File Based Write Filter. 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.\Administrator for the user name. 7. Enter the old and new passwords and confirm the new password. 8. Select the arrow to make the change. 9. Enable the Filter Based Write Filter (client will reboot). 10. Verify the new password by logging in to the Local Administrator account using the new password. Common Procedures GEH-6849C Support and Maintenance Guide 75

76 10.3 Get Thin Client Hardware and Software Information Product Information Tag The first level of Thin Client information can be found on the pullout tag on the back of the chassis. The pull out tag contains the partial model number and the MAC address (physical address of the internal NIC). The Thin Client can be uniquely identified and tracked using the MAC address. Product Information Tag 76 GEH-6849C Control Server Dell Wyse WES7 Thin Client

77 System Information The next level of information requires logging into the Thin Client to get further information about the hardware and operating system. Note Additional information is available in the Dell Thin Client Application when logged in to the Thin Client with an administrator account. To view system information: click Dell Thin Client Application on the toolbar to launch the information viewer. System Information Viewer Common Procedures GEH-6849C Support and Maintenance Guide 77

78 10.4 Verify Thin Client Network Connection Verify Connection Status Most Thin Client functionality depends on its connection to the Plant Network (PDH). The Thin Client will display the following icon in the status tray when it is connected to the PDH network. The No Internet access warning is typical. No Internet Access The Thin Client will display the following icon in the status tray when it has lost its network connection. The network connection icon in the system tray is displayed with a red X when the network is disconnected. Hovering over the icon with the mouse will generate the tooltip shown in the following figure. Not Connected Network Connection Icon If the icon is displayed, the Thin Client has lost its connection to the PDH. Verify that the network cable is plugged in to the Thin Client. If the network cable is connected and the problem persists, the problem could be a Thin Client or network issue. 78 GEH-6849C Control Server Dell Wyse WES7 Thin Client

79 Verify IP Address Assignment from DHCP Both the network connection status and the IP address assignment from DHCP can be verified using the Dell Thin Client Application. 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 IP Address The Dell Thin Client Application will display the following network information if the network is disconnected: Disconnected Network Information Common Procedures GEH-6849C Support and Maintenance Guide 79

80 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 Status The 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 Client will 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 80 GEH-6849C Control Server Dell Wyse WES7 Thin Client

81 10.7 Verify Thin Client Domain Network The 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. 2. Verify that the domain is not set to WORKGROUP. Dell Thin Client Application Icon 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 Common Procedures GEH-6849C Support and Maintenance Guide 81

82 The following figure shows that the terminal is a member of the default WORKGROUP domain and has not been joined to the Control Server HMI.local domain. Thin Client Jointed to WORKGROUP Domain 82 GEH-6849C Control Server Dell Wyse WES7 Thin Client

83 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 Common Procedures GEH-6849C Support and Maintenance Guide 83

84 10.9 Enable/Disable File Based Write Filter The File Based Write Filter (FBWF) on the Windows 7 Embedded Standard Thin Clients prevents changes from being made to the Thin Client when it is enabled. All changes made while the Write Filter is enabled are lost when the Thin Client is restarted. Changes are only persisted when the Write Filter is disabled Enable File Based Write Filter To enable the File Based Write Filter (FBWF) 1. Log in to the local Administrator account. 2. Right-click on the FBWF Enable icon and select Run as administrator. The Thin Client will restart and the write filter will be enabled after the restart is complete Disable File Based Write Filter The Write Filter status is displayed in the system tray. A green circle indicates that the Write Filter is enabled (ON), and a red circle indicates that the Write Filter is disabled (OFF). To disable the File Based Write Filter (FBWF) Write Filter Status Icon in System Tray 1. Log in to the local Administrator account. 2. Right-click on the FBWF Disable icon and select Run as administrator. The Thin Client will reboot, and the write filter will be disabled after the reboot is complete. 84 GEH-6849C Control Server Dell Wyse WES7 Thin Client

85 10.10 Check File Based Write Filter Status The Write Filter status is displayed in the system tray. A green circle indicates that the Write Filter is enabled (ON), and a red circle indicates that the Write Filter is disabled (OFF). Refer to the figure Write Filter Status Icon in System Tray Open Administrator Mode PowerShell Window on Thin Client Perform the following procedure to open a PowerShell window in Administrator mode on a Windows Embedded Standard 7 (WES7) Thin Client. To open an Administrator mode PowerShell window using WES7 based Thin Client 1. Log in to the Thin Client with an administrator account. Refer to the section Thin Client Account Login. 2. From the Start menu search area, type PowerShell. 3. Right-click on Windows PowerShell and select Run as administrator. Note You must be logged in to an Administrator account on the Thin Client to run PowerShell Open Administrator Mode PowerShell Window on Windows Server 2012 R2 The EWS VM and other Windows-based VMs are hosted by the Control Server on Windows Server 2012 R2. Perform the following 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-click Windows PowerShell and select Run as administrator. 3. Supply a Domain Administrator account if prompted (standard is HMI\admin). Administrator Mode PowerShell Window Common Procedures GEH-6849C Support and Maintenance Guide 85

86 10.13 Launch RD Licensing Diagnoser Tool The RD Licensing Diagnoser tool provides information to help identify possible licensing problems for the Remote Desktop Session 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 Remote Desktop connections, connect to one of the HMI VMs using a Remote Console launched from VMWare vsphere Client or 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, Remote Desktop Services are not enabled on the VM, and is a likely indication that 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. 86 GEH-6849C Control Server Dell Wyse WES7 Thin Client

87 10.14 Check Location and Status of RDS License Server The RD Licensing Diagnoser tool can be used to display information about the Remote Desktop Session Host Server on the local VM, as well as the location and status of the RDS License Server. (Refer to the procedure To launch the RD Licensing Diagnoser 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 is displayed. Common Procedures GEH-6849C Support and Maintenance Guide 87

88 The license server entry can be selected to see further details. 88 GEH-6849C Control Server Dell Wyse WES7 Thin Client

89 If a problem is detected, the RD Licensing Diagnoser tool provides a description of the problem and instructions to resolve the problem. The following figure illustrates the RD Licensing Diagnoser tool display after the Remote Desktop Licensing service was stopped. Perform the steps in the Suggested Resolution area to resolve any existing issues. Common Procedures GEH-6849C Support and Maintenance Guide 89

90 10.15 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 a Remote 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 License Server 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 change Startup Type to Automatic. 90 GEH-6849C Control Server Dell Wyse WES7 Thin Client

91 10.16 Determine Number of Available Client Licenses in RDS License Server Refer to the section Check the Location and Status of the RDS License Server for the procedure to launch the RD Licensing Diagnoser tool and display the license server status, including the number of installed and available RDS Per Device CAL licenses Manage RDS Per Device CALs 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 License Server is not known, refer to section Check the Location and Status of the RDS License Server 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. 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, and is a likely indication that the site is using a one Thin Client to one HMI VM (one-to-one) architecture and RDS licensing does not apply. 5. Select Remote Desktop Licensing Manager 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. Common Procedures GEH-6849C Support and Maintenance Guide 91

92 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 and to 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), the RDS Per Device CAL allocated to it can be revoked. Revoking a license returns it to the available license pool, making it available 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 the site. 92 GEH-6849C Control Server Dell Wyse WES7 Thin Client

93 10.18 Manage User Sessions on HMI VMs This section provides the following procedures: View Active and Disconnected User Sessions Close Disconnected User Sessions 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. Common Procedures GEH-6849C Support and Maintenance Guide 93

94 Close Disconnected User Sessions To close Disconnected user sessions: right-click a Disconnected user session and select Sign off to terminate it. 94 GEH-6849C Control Server Dell Wyse WES7 Thin Client

95 10.19 Connect Monitors to Thin Client Terminal The video ports are located on the back of the Thin Client terminal as shown in the following figure. The Windows operating system 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. For example, the monitor plugged into the first physical port connected will be assigned to Display 1, and the monitor plugged into 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 the monitors to achieve the correct display order. Common Procedures GEH-6849C Support and Maintenance Guide 95