OpenLAB CDS ChemStation - Distributed system Best practices 1/34 Contents Scope..................................................................................................................................................................................... 4 Revision History ......................................................................................................................................................... 4 OpenLAB CDS ChemStation Instrument Controller (AIC) ............................................................................................ 5 1. Basics ...................................................................................................................................................................... 5 2. Licensing ................................................................................................................................................................. 6 Device-based or User-based Windows Client Access Licenses ....................................................................... 6 3. Configuration .......................................................................................................................................................... 7 Instrument Names ..................................................................................................................................................... 8 Network Printers ........................................................................................................................................................ 8 Disc configuration ...................................................................................................................................................... 8 Anti-virus interference with system operations ................................................................................................... 9 Windows File indexing ............................................................................................................................................ 11 RDP-TCP Properties ................................................................................................................................................. 12 Virtualization of AICs............................................................................................................................................... 13 4. Maintenance ........................................................................................................................................................ 13 Planned reboots on variable schedule/reboot procedure ................................................................................ 13 Disk clean-up ............................................................................................................................................................ 14 Disk defragmentation .............................................................................................................................................. 16 Virus scanning .......................................................................................................................................................... 16 Performance benchmarking ................................................................................................................................... 16 5. Troubleshooting ................................................................................................................................................... 16 Starting instruments on the AIC ........................................................................................................................... 16 Identifying the CSIUser assigned to an instrument ........................................................................................... 17 Sandbox system ....................................................................................................................................................... 17 6. Performance monitoring .................................................................................................................................... 18 7. Performance tuning ............................................................................................................................................ 19 2/34 Optimize disc configuration ................................................................................................................................... 19 Minimize CPU usage ............................................................................................................................................... 19 8. Known Problems ................................................................................................................................................. 21 KPR#: 1617 AIC can experience communication loss if Application Experience service is running ........ 21 KPR#: 1842 Memory leak in RDPShell.exe may cause significant performance decrease ..................... 21 Password policy not satisfied by default passwords......................................................................................... 22 “Allow log-on through Remote Desktop Services” not granted ...................................................................... 22 Remote Desktop Users group is emptied by Group Policy ............................................................................... 22 Error message “Your credentials did not work” ................................................................................................. 23 Error message “Program Execution Failed” ........................................................................................................ 23 Login delay ................................................................................................................................................................ 24 OpenLAB CDS ChemStation Clients .............................................................................................................................. 25 1. Configuration ........................................................................................................................................................ 25 Visual effects ............................................................................................................................................................ 25 Virus Scanning ......................................................................................................................................................... 25 9. Maintenance ........................................................................................................................................................ 25 10. Troubleshooting .............................................................................................................................................. 26 Reference PC ............................................................................................................................................................ 26 11. Known Problems ............................................................................................................................................. 26 Distorted graphics in chromatogram window ..................................................................................................... 26 Sequence table does not allow entering long sample names ......................................................................... 28 KPR#: 1863 ChemStation CDS client appears to freeze after hiding a save as dialog ............................ 28 Appendix ............................................................................................................................................................................. 30 1. Default RDP configuration ................................................................................................................................. 30 3/34 Scope This document is a collection of recommendations for the optimized usage of OpenLAB CDS ChemStation Instrument Controllers. It doesn’t claim completeness nor does it overrule the Distributed System Installation Guide. It is a living document to be developed further to become an Administrator’s Guide. The intended audience are system owners and administrators as well as Agilent PSO consultants. Revision History Revision Author Comment 1.0 Bernhard Etrich, Abel de Oliveira 4/34 OpenLAB CDS ChemStation Instrument Controller (AIC) 1. Basics With OpenLAB CDS installed as a distributed system, you are able to access and run instruments from any PC in the system. As in case of networked workstations installation, the OpenLAB Shared Services provide an overview of all instruments in the system. You can access all information provided by the Shared Services from any CDS client. For example, you can see which instruments are available in which location and which status (Online, Offline, Error, In Run, Not Ready, etc.) the instruments currently have. In contrast to the networked workstations installation, you can configure and launch all instruments in the network. The instrument hardware configuration is installed on Agilent Instrument Control (AIC) machines. You can access the ChemStation instance on the AIC machine from any CDS client via a Remote Desktop Services client. Accessing ChemStation via a Remote Desktop connection enables you to work more flexible with ChemStation sessions. You can, for example, launch an online ChemStation, start a sequence, and then disconnect only the Remote Desktop connection while ChemStation continues running on the AIC machine. You or another user can later connect to this session again from a different CDS client, finish work in the online ChemStation, and then shutdown ChemStation. In Windows Server 2008, Microsoft Terminal Services introduced RemoteApp programs, which are programs that are accessed remotely through Remote Desktop Services and appear as if they are running on the end user's local computer. A single server behaves like multiple workstations whose output is redirected to multiple external devices. Each client transmits all input from the user to the server, such as keystrokes and mouse movements, and all output from the server such as application display information and print streams. For each ChemStation instrument, an instrument account is created at installation in order to establish RDS (Remote Desktop Services) session. The default account names are CSIUser0 to CSIUser10. CSIUser0 will be used for the Instrument configuration while CSIUserX will be used to start Instrument X (Online and Offline). When using these default accounts, the system will add these accounts to windows and it will assign randomly generated passwords. Optionally you can override these default accounts by customized accounts. Please read the OpenLAB CDS Distributed System Installation Guide for further details. 5/34 2. Licensing Device-based or User-based Windows Client Access Licenses There are two types of Windows Client Access Licenses from which to choose: device-based or user-based, also known as Windows Device CALs or Windows User CALs. This means you can choose to acquire a Windows CAL for every device (used by any user) accessing your servers or you can choose to acquire a Windows CAL for every named user accessing your servers (from any device). The option to choose between the two types of Windows CALs offers you the flexibility to use the licensing that best suits the needs of your organization. For example: Windows Device CALs might make most economic and administrative sense for an organization with multiple users for one device, such as shift workers. Whereas, Windows User CALs might make most sense for an organization with many employees who need access to the corporate network from unknown devices (for example, when traveling) and/or an organization with employees who access the network from multiple devices. (http://www.microsoft.com/windowsserver2008/en/us/client-licensing.aspx) When Per Device licensing mode is used, and a client computer or device connects to an RD Session Host server for the first time, the client computer or device is issued a temporary license by default. When a client computer or device connects to an RD Session Host server for the second time, if the license server is activated and enough RDS Per Device CALs are available, the license server issues the client computer or device a permanent, RDS Per Device CAL. An RDS Per User CAL gives one user the right to access an RD Session Host server from an unlimited number of client computers or devices. RDS Per User CALs are not enforced by RD Licensing. As a result, client connections can occur regardless of the number of RDS Per User CALs installed on the license server. This does not absolve administrators from Microsoft Software License Terms requirements to have a valid RDS Per User CAL for each user. Failure to have an RDS Per User CAL for each user, if Per User licensing mode is being used, is a violation of the license terms. 6/34 To ensure that you are in compliance with the license terms, make sure that you track the number of RDS Per User CALs being used in your organization and that you have a sufficient number of RDS Per User CALs installed on the license server to provide an RDS Per User CAL for each user that needs to connect to the RD Session Host server. You can use the Remote Desktop Licensing Manager (RD Licensing Manager) tool to track and generate reports on the issuance of RDS Per User CALs. To use Remote Desktop Services, you must also have at least one license server deployed in your environment. For small deployments, you can install both the RD Session Host role service and the RD Licensing role service on the same computer. For larger deployments, it is recommended that the RD Licensing role service be installed on a separate computer from the RD Session Host role service. 3. Configuration This chapter describes additional configuration steps and details that help simplifying administration of the system. 7/34 Instrument Names When setting up new instruments in the OpenLAB Control Panel the instrument’s file infrastructure on the AIC does not get setup until the instrument gets configured. Hence, the internal instrument numbers are ordered by the order of configuring the instruments and can be organized as such. When setting up a new instrument it is recommended to write the instrument’s IP address to its description field in the Shared Services control panel. Network Printers There are three methods that you can use to assign server-based printers to users of Terminal Services 1. Map printers in user’s logon scripts in a batch file use the command rundll32 printui.dll PrintUIEntry /in /n \\printserver\printer (see http://technet.microsoft.com/fr-fr/library/ee624057(WS.10).aspx) 2. Map printers as part of a user's profile and policy settings. 3. Install the printer locally on the server The network printer will be configured as a local printer, print jobs will be handled locally on the Terminal Server print queue and will be sent to the printer using a TCP/IP port. a. Logon to the Terminal Server as an administrator. b. Click on Start > Devices and Printers c. Start the Add Printer wizard. d. Select Add a Local printer e. Select Create a new port instead of using an existing port. f. Select Standard TCP/IP port, press Next g. Type in the IP address or the hostname of the printer. h. Select and install the printer driver corresponding to the printer Disc configuration If OpenLAB CDS ChemStation gets installed on a single disc drive, this disc has to handle the following I/O intensive processes:  Windows pagefile (virtual memory)  Windows user's temp directories (used for unzipping of data downloaded from OpenLAB ECM)  ChemStation raw data writing 8/34 The load on this disk gets additionally increased if the ChemStation data storage location is not excluded from real-time protection of virus scanners as recommended. The main goal is to keep the AIC disks as empty as possible and to distribute I/O intensive processes across multiple disk drives. This can be achieved by various means:  delete locally stored data after transfer to OpenLAB ECM or OpenLAB data store  Install or configure OpenLAB CDS ChemStation on a drive that do not host the Windows page file or the Windows user's temp directories (default: c:\users\<current user\AppData\Local\Temp)  Install OpenLAB CDS ChemStation on the c:\drive and change the default paths for sequences methods and data files after configuring a new instrument. The ChemStation default data path can also be changed on systems being used for a while. Use the following procedure:  Windows explorer on the AIC: Create new data directories chem32\<InstNumber>\Data  On the clients: Shut down all instruments  Open OLSS control panel and change the data path preferences in the configuration of each instrument. (Do not change the paths for methods sequences etc.)  Start each instrument and go to View > Preferences…  Select the new data path and leave the preferences window by pressing o.k. Now the ChemStation explorer shows the content of the new and the initial data path. If data gets deleted after upload to ECM the initial data path can be removed from ChemStation’s path preferences after a transition period. Anti-virus interference with system operations A large test campaign has been performed by Agilent to measure the impact of various software and hardware settings on AIC performance. The following recommendations have been concluded from these tests. Further details on each of this topic are listed in the following sections. Running AntiVirus programs might influence the behaviour and performance of your computer. To demonstrate the impact of active virus scanning the following test scenario was performed on a virtual OpenLAB CDS ChemStation AIC ‘AIC008’: Reprocessing of a defined test sequence of 100 runs and extracting the run times for each sequence line from the sequence log files. The following graph shows the progress of sequence reprocessing while turning the on-demand virus scanning on and off at dedicated position: 9/34 Pict. 1: Sequence reprocessing progress with and without on demand scanning and file indexing Recommendation: Agilent OpenLAB CDS was tested to run with Symantec’s Norton Antivirus. In order for the OpenLAB software to function correctly any Anti-Virus real time protection software and “on access” scanning should be configured with the following list of folder exclusions. These folders listed below should only be scanned while the AIC is idle and no data acquisition takes place. Please refer to your specific Anti- Virus software user’s guide on how to configure folder exclusions. Process Directory Filename OpenLAB CDS ChemStation C:\chem32 (default, see *.D *.CH *.UV *.MS Data Acquisition ChemStation Preferences for current settings) ECM upload / download %temp% for AIC users CSIuser1 – *.ssizip CSIuser10 (=Users-temp- Standard Reports ~p3d*.tmp ~job*.tmp directory) /chem32/core Hpspl00.que CDS intelligent reports %LOCALAPPDATA% Files on: %APPDATA%  Agilent %PROGRAMDATA%  Agilent Technologies  Agilent_Technologies  Agilent_Technologies,_Inc  IsolatedStorage  Temp e.g.: C:\Users\xxxxx\AppData\Local\ Agilent Technologies\Intelligent Reporting\RawDataFileCache 10/34