CDS v2.7 WorkstationPlusGuide en
CDS v2.7 WorkstationPlusGuide en
Term Description
1 Prepare your PC
This chapter describes how to configure a non-Agilent-delivered PC.
Agilent-delivered PC Bundle systems are delivered with the supported pre-installed
Windows operating system and are configured for optimum performance.
Non-Agilent PCs require some manual configuration changes in order to provide
optimum performance.
5 Licensing
This chapter provides basic information on OpenLab licensing. It describes how
you generate a license file with SubscribeNet and install the license in the Control
Panel.
1 Prepare your PC 7
Install and Update Windows 8
Install the .NET 3.5 and 4.x Framework 9
Before You Begin the Installation of OpenLab CDS 11
Run the System Preparation Tool 12
4 Optional Procedures 39
Install OpenLab Help and Learning Only 40
Improve Performance on Offline Machines 41
Set up NIST Library Search 42
5 Licensing 43
About OpenLab CDS Licensing 44
Get a License 46
Install Your License 50
11 Appendix 103
Privileges in the Control Panel 104
Sales and Support Assistance 113
1 Install the Windows operating system from the Microsoft installation media or
qualified PC image media provided by your IT department. During the setup,
provide the computer name, administrator password, and network settings.
For the computer name, do not use underscores; installation is not possible if
the computer name contains an underscore.
Choose to either join an existing domain or set up the system in a workgroup
mode. Domain naming has to be consistent with RFC-1034.
2 In the Microsoft Control Panel under System >Windows activation, click
Change product key. Enter a valid value to activate Windows.
3 Update to the recommended version of Windows. See the FAQ section of the
OpenLab CDS page (https://www.agilent.com/ under Products >Software &
Informatics >Chromatography Software >Chromatography Data
Systems >OpenLab CDS >Support).
4 Check for Windows quality updates, and apply all critical security patches. Do
not choose to install a newer version of Windows (see previous step). Make
sure the Windows quality updates have finished installing before proceeding
to install OpenLab CDS.
5 Check that your computer meets all requirements. You can access the
Requirements and Supported Instruments for Instrument Controllers, Clients,
or Workstations guide (CDS_v2.7_Requirements_en.pdf) from the Setup\Docs
folder on the installation media.
Use this PDF to check that your settings comply with the network
requirements, and to determine whether your hardware and software will
support the system.
6 Install an antivirus program.
7 Be sure to open the firewall ports listed in the Firewall Settings in the
Requirements and Supported Instruments for Instrument Controllers, Clients,
or Workstations guide (CDS_v2.7_Requirements_en.pdf).
Make sure that the TCP ports 80 and 443 are available.
If these ports are occupied by other programs: Try setting the startup type of the
NOTE World Wide Web Publishing Service to Manual or Disabled, or disable Internet
Information Services (IIS).
8 In the Microsoft Control Panel under Date and Time: Choose the time zone of
your regional location.
If .NET 3.5 and .NET 4.x are not installed on your system, their installation will
automatically be triggered by the installation wizard. However, this may require a
system reboot. To avoid the system reboot during installation, install .NET in
advance.
1 Go to the Microsoft Control Panel.
In the Windows Start menu, enter "Control Panel" in the Search programs and
files field (alternatively, press [Win+R] and enter "Control panel"). To view all
items in the Control Panel view, select Small icons in the View by field.
2 Go to Programs and Features.
3 Go to Turn Windows features on or off.
4 Enable .NET 3.5 as follows:
a Expand the .NET Framework 3.5 (includes .NET 2.0 and 3.0) node.
b Select the Windows Communication Foundation Non-HTTP Activation check
box.
5 Select the .NET Framework 4.8 Advanced Services check box. Use the default
values for sub items.
To make sure that a DNS server can resolve the computer name, follow the
NOTE internet standard for protocols (RFC952) and use only the following characters:
• Letters (a-z, A-Z)
• Digits (0-9)
• Hyphen (-)
Do not use an underscore. Installation is not possible if the computer name
contains an underscore.
2 Install all required hardware, including any cables, instrument detectors, and
communication cables. GPIB interfaces may be required for some non-Agilent
instruments.
3 Prepare an account with administrative privileges to run the installation.
4 To allow the successful installation and activation of all components, make
sure that the LAN-cable is connected and a network is available. A local
network is sufficient. If you install the workstation without a network cable,
the activation of the Content Management component will fail, and trying to
run the database will return an error.
5 Make sure that the antivirus software is disabled during the installation.
6 Check the Agilent Service Notes for software updates for your installation
package and software products. Service Notes are available from your Agilent
support representative.
7 If you use Trend MicroTM as an antivirus software, turn off Web Reputation to
allow the installation of all components.
8 If you plan to upgrade from a previous version of OpenLab CDS please refer to
the Upgrade OpenLab CDS chapter.
The System Preparation Tool (SPT) checks and applies Windows settings on
your machine. The settings are also applied automatically when you run the
OpenLab installer. Running the SPT in advance helps you to shorten the
installation process. For an overview of both mandatory and recommended
settings, refer to the chapter System Preparation Tool in the OpenLab CDS
Workstations, Clients, and Instrument Controller Requirements and Supported
Instruments guide (CDS_v2.7_Requirements_en.pdf).
1 Optional: Copy the entire content of the USB media to a local drive or
centralized folder, then remove the USB media from the PC.
2 To open the installer, right-click the setup.exe file, and run it as administrator.
If User Account Control (UAC) is switched on, this step requires active
NOTE confirmation to continue.
You can clear the check boxes for recommended settings. Mandatory
settings cannot be cleared. Recommended actions are selected by default
and will be applied unless they are cleared.
7 Click Apply Fixes to apply the correct settings.
The System Preparation Tool attempts to fix the selected settings and
displays the new status on the Update Configuration page. All actions are
saved to a log file. A link to the log file is provided at the bottom of the page.
8 Click Next to proceed to the System Preparation Report page.
The System Preparation Report is displayed. It lists the new status for all
selected settings.
The System Preparation Report is saved to disk. Its location is shown at the
top of the page.
9 Click Print Report to print the System Preparation Report.
You may print to a file, for example, using the Adobe PDF printer, and add
comments.
10 The System Preparation Report lists any mandatory or recommended
settings that are not automatically updated by the System Preparation Tool.
Follow the instructions provided in the Actions Required section of the System
Preparation report to manually update operating system settings.
11 Click Finish.
12 Reboot your system if requested to do so.
1 Make sure that the antivirus software is disabled during the installation.
2 Ensure that .NET pipe communication is allowed among the OpenLab
components.
3 Do not run the Windows Update Service during installation. Make sure that no
Windows updates are performed during the installation.
4 Make sure that no system reboot is pending.
Pending reboots are indicated in the System Preparation Tool (see “Run the
System Preparation Tool” on page 12).
Options to proceed
• Recommended: Click Open SPT Report to view instructions to complete
these actions. In the report, check the Required Actions section. After
completing the operations, click Resume Installation.
• Cancel Installation: Installation is aborted. Make necessary updates and
restart installation.
• Resume Installation: The dialog is closed, and installation continues with
the installation of the CDS components even if a setting was not applied. If
needed, the settings can be updated after the installation has been
completed.
11 Install: After the installation has completed, click Next.
12 Configure: Configuration tools run in the background to configure Content
Management. This takes about 10 min. When finished, click Next.
In case of registration problems, a potential conflict may be a blocked firewall
port. For example, check if ports 80 and 443 are open. If they are blocked by
the World Wide Web Publishing service, stop this service.
13 Finish:
• To view the report of the applied Windows settings, click the link under
System Preparation. If you still need to apply settings manually, a warning
will be displayed. You will find details in the linked report.
• To confirm everything has been installed correctly, click Run Software
Verification1.
• To complete the installation, select the Reboot the computer now check
box, and click Finish.
14 In case of errors during the installation: Check the installation log files under
C:\ProgramData\Agilent\InstallLogs\<date and time>. Note that ProgramData
is a hidden folder.
The installation includes a set of standard instrument drivers. If you need other
instrument driver software, install it in a separate step. See “Install or Upgrade
Driver Software” on page 26.
1
To start the tool separately at a later point in time, select Start > Agilent Technologies > Software
Verification Tool.
Silent Installation
Run Installation
Prerequisites • You have prepared a properties file for silent installation. See “Export
Properties File” on page 22.
• .Net Framework is present on your system.
If it is not present, it will automatically be installed. You must then manually
select Accept to agree with the license agreement.
Return Codes
After installation, uninstallation, or upgrade in the command-line mode, the
system will return a number code which is explained below.
Table 2 Return codes
Failure. Verify against the log file to see what any other number
failed.
The following driver software packages are automatically installed with OpenLab
CDS. For details, refer to the Requirements and Supported Instruments Instrument
Controllers, Clients, or Workstations guide (CDS_v2.7_Requirements_en.pdf).
• Agilent GC & GC/MS
• Agilent LC & LC/MS
• Agilent 35900 A/D
• Agilent SS420x
• Agilent Data Player (Virtual Instruments)
Other instrument driver software, add-on software, or upgrades to existing driver
software, must be installed and configured manually. Instrument driver software
and add-on software packages can be found on the installation media under
Setup\Packages\Add-Ons.
The latest Agilent drivers are available in SubscribeNet. To manage software
entitlements and download software, log in to SubscribeNet by pasting this link in
your browser: http://agilent.subscribenet.com. In the Product List, select
OpenLab Software >OpenLab Agilent Instrument Drivers.
3 Click Connect to enable the input boxes for the user credentials.
4 Under Step 2 - Authentication, enter your user credentials.
5 Make sure the Register as Instrument Controller check box is cleared.
6 Click Register.
A Registration Results dialog will be shown.
7 Reboot the PC.
This chapter describes tasks that are relevant after finishing the installation.
The Software Verification Tool (SVT) provides documentary evidence that your
system has been built and installed correctly, and that all design specifications
have been met. You do not need to run the software verification again if it has run
successfully at the end of the installation.
1 Using your Windows operating system, go to Start >All Programs >Agilent
Technologies >Software Verification Tool.
2 Select the components to qualify.
3 Select Qualify.
The system will run the application and generate a Software Verification
Report. Reports are automatically saved to C:\SVReports.
4 If the report indicates failure, verify the computer requirements and reinstall
the data system.
Do not use the system until the Software Verification Report gives a ‘pass’
result.
1 Be sure to open the firewall ports listed in the Firewall Settings in the OpenLab
CDS Workstation Requirements and Supported Instruments guide
(CDS_v2.7_Requirements_en.pdf).
2 The following folders should be excluded from Antivirus scan. If you want to
have these folders scanned, you should do this while the system is not
acquiring or doing data Analysis as scanning may cause slowness and runs
to be aborted due to concurrent access to the same file by the AV program
and the CDS Application.
• [C:\]DsData\DsArchive
• [C:\]DsData\DsContent
• [C:\]DsData\DsIndex
• [C:\]Program Files (x86)\Agilent Technologies
• [C:\]ProgramData\Agilent
• [C:\]ProgramData\Agilent IPB Files
• [C:\]ProgramData\Agilent Technologies
• [C:\]ProgramData\ChromatographySystem
• [C:\]ProgramData\Firebird
• [C:\]ProgramData\IsolatedStorage
Refer to your specific antivirus software documentation on how to configure
folder exclusions.
For antivirus software with network intrusion prevention, expect to see some
NOTE degradation in general system performance. To disable network intrusion
prevention, refer to your antivirus software instructions.
OpenLab CDS allows you to automatically process your data during acquisition,
without opening Data Analysis. During this processing, injection reports may
need to be printed. With centralized printing, these reports are copied into shared
print folders. A third party program such as FolderMill then accesses the shared
folders and sends the contained files to a printer.
1 In the Microsoft Control Panel, navigate to All Control Panel
Items >Administrative Tools, and double-click Services.
2 Right-click Agilent OpenLab Copy To Server and select Properties.
3 Click the Log On tab, select This account and enter the login credentials of a
domain user. The user must be a member of the local Administrators group
and must have the privileges to write into the print folders.
4 Confirm your settings, and restart the service.
5 Set up the shared print folders in the OpenLab Control Panel under
Administration >Print Folders.
a Click Add Print Folder.
b Provide a name, folder path (UNC format), and description (optional), and
click Save.
c If you set up multiple print folders, you can designate a specific one as
default by selecting the desired print folder and clicking Set Default Print
Folder.
6 Optional: Configure queue size.
Each Print Folder will have its own queue. The size of each queue is defined in
the configuration file C:\ProgramData\Agilent\CopyToServer\
CacheSizeLimit.ini. The parameter CacheSizeLimit can be configured to
change the size of the queue.
The default value is 500 MB, which means that each queue (print folder) will
have a size limit of 500 MB by default. Files will enter the queue until the
maximum size of the cache is reached. When this happens, the queue will
stop accepting requests. The queue will automatically restart and begin
accepting requests after it has been cleared.
The Agilent OpenLab CopyTo Client or Agilent The service should automatically restart.
OpenLab CopyTo Server service has crashed
Network issue between workstation and print Centralized printing requests will be buffered on
folder the workstation. The files will be automatically
copied to the print folder as soon as the network
is back.
Print folder cache full Check print folder access. Consider increasing
the cache size (see “Prepare Centralized
Printing” on page 33).
Print folders are not accessible due to Check that the domain user logged into the
insufficient permissions Agilent OpenLab CopyTo Server service is a local
administrator and has permissions to write into
the print folders.
Reports are stuck in print folders Check that the third party software being used to
access print folders for printing is functioning
correctly. Check that there are no printer errors.
4 Click the Log On tab, select This account and enter the login credentials of a
domain user who has network printing privileges.
The user must be a member of the local Administrators group on the AIC.
NOTE
Click OK.
5 The Services window confirms that the account has been granted the Log On
As A Service right. Click OK.
6 Click OK in the Services window to acknowledge that The new logon name will
not take effect until you stop and restart the service.
7 Restart the PC. This will enable the Log On user specified in Instrument
Service to automatically export files to network shares in Data Acquisition.
Prerequisites You have set up a domain user account (see “Prepare Exports to Network Shares
During Unattended Processing” on page 35).
1 Log in using the domain user account specified in the Log On tab of Agilent
OpenLab Instrument Service Properties window.
2 Go to Control Panel >All Control Panel Items >Devices and Printers and click Add
a printer.
3 Select Add a network, wireless or Bluetooth printer and browse or type a shared
printer name that you want to add. Once the printer is added, print a test page.
4 In the Windows printer settings, set the shared printer as the local default
printer.
Use this option to install OpenLab Help and Learning content without installing
OpenLab CDS applications.
Do not use this option on a machine where OpenLab CDS is, or will be, installed.
1 Insert the USB media, right-click the setup.exe file, and run it as administrator.
2 On the start screen, select OpenLab CDS, and click OK.
3 In the OpenLab CDS Installer, click Installation.
4 Click OpenLab Help and Learning Only.
5 Select your language, and click Next.
6 Accept the terms on the License agreement page, and click Next.
7 Review the installation directory. If desired, click Change... to specify a
different directory.
8 Click Install.
9 When the installation is complete, click Finish.
You can uninstall or repair OpenLab Help and Learning from the same link in the
installer (see “Uninstall OpenLab Help and Learning Only” on page 101).
Computers running OpenLab CDS may exhibit slow performance when they are
not connected to the Internet.
The windows operating system has routines built into its operation that causes it
to continuously search for an online connection in order to update to all the latest
Windows security certificates when using secure software.
Use the following system settings on all workstations to remedy this problem.
1 In the Windows Settings, search for Internet Options. The Internet Properties
dialog opens. In the Advanced tab, clear the following check boxes:
• Security >Check for publisher's certificate revocation
• Security >Check for server certificate revocation
2 Change or add the following registry keys:
• [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\
SystemCertificates\AuthRoot]
"DisableRootAutoUpdate"=dword:00000001
• [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\
Microsoft\SystemCertificates\AuthRoot]
"DisableRootAutoUpdate"=dword:00000001
3 Document that you turned off the Root Certificates, as this will cause the
OpenLab CDS installer to fail. The root certificates need to be turned on to
prevent installation failures.
In order to use MS library searching within OpenLab CDS, the NIST MS Search
program must be installed locally on the workstation (or, in a Client/Server setup,
on the client or AIC) which is to perform the library search.
For details on the installation and configuration of the NIST library framework
within standalone, Client/Server, or Citrix/Terminal Server setups, please refer to
Setup and Configuration of MS Library Search (CDS_Configure_MS_Libraries.pdf).
That document also discusses the use and management of other commercial
and user-created libraries with OpenLab CDS MS library search.
License Types
The license file is a collection of Product, Instruments and Add-on licenses (or
activation keys), and is installed to your OpenLab CDS System.
The licenses or activation keys in the license file can either be Shared or Counted:
• Shared licenses — system computers and other components can have
shared, or add-on, licenses — because they share a core license.
• Counted licenses — these licenses are part of the OpenLab CDS floating
licensing strategy. They are not permanently assigned to any one component.
Instead they are automatically assigned to components, such as AICs and
instruments, while the components are starting up. The licenses are
automatically returned when the component is closed. The license
management program controls license issuance and retrieval.
In this case, the only requirement is that a component is licensed while
running. You only need enough licenses for all components running
concurrently, rather than for each installed component.
A startup license for the system allows you to run OpenLab CDS for 60 days after
the installation. In order to run the data system software after the 60-day period,
you must install your license file.
License File
A license file will contain your software license. This file is installed on the
workstation. The license file is bound to this computer, and cannot be moved to
another workstation without regenerating the license in SubscribeNet.
Information in the license file defines the number of instruments and other
options that may be used concurrently with your system.
The most efficient way to manage and maintain your licensing is through the
Internet.
Get a License
Prerequisites To generate, download, and install a final license for your product, you will need:
• The authorization code label provided in the lavender envelope containing
your Software Entitlement Certificate.
If you have not received a lavender envelope for your product, contact your
vendor or internal support.
• The URL for SubscribeNet from the Software Entitlement Certificate.
• The host name of the computer where the Control Panel is running.
• The MAC address.
To retrieve your MAC address from a computer where OpenLab CDS is
already installed, open the Control Panel and browse to the
Administration >Licenses section. Use the Copy MAC Address or Save MAC
Address function to obtain the MAC address for license generation.
During this process you will have to enter the MAC address of your license
server. For workstations, this is the local computer. For client/server systems,
this is the server.
If any changes are made to the computer name or domain reference after the
NOTE license is installed, remove the license. A new license will need to be created in
SubscribeNet, downloaded, and installed.
If the network adapter that provides the MAC address used during license
NOTE creation is removed from the machine, your license will no longer be valid. A new
license will need to be generated with a currently available MAC on the license
server.
New Users
1 Go to https://agilent.subscribenet.com/control/agil/AgilRegisterToAccount
to register the product with SubscribeNet.
2 On the registration page, enter the authorization code from the label and
complete the profile information (required fields are marked with an asterisk
*).
The email address you enter will become your login ID.
3 Click Submit. The system will generate and display an account name for you.
SubscribeNet will send a welcome email with your login ID and password.
4 Log in to SubscribeNet using your login ID and password.
Once you log in, you can use the online user manual link for help with any
questions you have.
5 Select Generate or View licenses from the left navigation bar.
6 Follow the prompts to generate your new license. You will be prompted for the
HOST NAME of the computer.
Enter the server hostname. Do not include any DNS suffix (domain.com)
references in the entered machine name.
7 When the system generates the license, view its details, then click Download
License File. Save the license file to your computer and to a backup location
(such as a portable storage device).
Use your login ID and password when you revisit the Agilent SubscribeNet site
to regenerate a license file, add new authorization codes, or further configure
the license for your system.
Offline Licensing
If an internet connection is not available in your laboratory:
You or your local on-site service engineer will collect the necessary information
from you to allow Agilent to create a license account on your behalf. For phone
support in your region, call the sales and service number for your region. See the
Appendix for contact information.
Required Customer Information for Agilent License Support:
The following information must be provided to Agilent in order to enable us to
create a licensing account on your behalf.
1 Collect Account Information:
Your account name will be your company name and Lab name separated by a
comma. Employee information provided here will be used to define the first
administrator of your account for future access to the system as required.
Please prepare the following pieces of information prior to contacting your
local Agilent sales and service center in order to expedite service:
• Company Name
• Lab/Department Name
• First Name
• Last Name
• E-mail address
• Job Title
• Phone #
• Address, City, State/Province, Postal Code, Country
2 Collect Authorization Code(s):
The authorization code is an alpha-numeric code provided on a label which is
enclosed in a lavender envelope. If you have received more than one code you
must provide all codes to ensure that all ordered licenses are granted to your
account.
The license must be added to your system using the Control Panel.
1 Start the Control Panel shortcut on the desktop or go to Start >All
Programs >Agilent Technologies >OpenLab Shared Services >Control Panel.
2 Navigate to Administration >Licenses.
A full restart is required in order for any license to have an immediate effect.
NOTE
Configure Authentication 52
Configure Security Policy 53
Configure users, roles, and privileges 54
Create or import users 54
Groups 55
Roles and Privileges 55
Add users or groups to a role 57
Specific Roles for Individual Instruments or Projects 57
Configure Initial Project 58
Configure Initial Instrument 58
Other settings in the Control Panel 59
This chapter describes the initial configuration steps after installing the software.
All configuration tasks are performed in the Control Panel. For more details, refer
to the Control Panel section in OpenLab Help & Learning.
Configure Authentication
6 Select the check box to use a domain user, and provide user credentials with
the rights to obtain user and group information. Then click Select Account to
open the Search Users dialog and select an administrator account.
7 Confirm your settings. When complete, the Control Panel will restart.
If you need to comply with specific standards (for example, 21 CFR Part 11),
adjust the security policy as required.
With the authentication provider Internal, you can set all parameters in the Control
Panel.
With an external authentication provider (Windows Domain), you can set the
inactivity time or enable single sign-on; all other parameters are defined by the
external system.
1 Launch the Control Panel and navigate to Administration.
2 In the navigation pane, select Security Policy.
3 In the ribbon, click Edit Security Policy.
4 Set the parameters as required, and confirm your changes.
Restart the Control Panel to apply your changes.
To meet 21 CFR Part 11 requirements, set the Password expiration period to 180
NOTE days or less. Do not change the other default values, they comply with 21 CFR
Part 11.
To define what users are allowed to view or do, OpenLab CDS offers predefined
roles and allows you to define your own specific roles.
Roles are equipped with numerous specific privileges. When you set up a
customized role, it is therefore recommended starting from a lower role (that is,
with fewer privileges) and adding specific required privileges, rather than
removing privileges from a higher role.
Each user can be member of multiple groups. You must assign one or more
specific roles to each group. You can also assign roles to single users; however,
for the sake of clarity, it is strongly recommended to assign roles only on the
group level. Every member of a group automatically has all roles of this group.
1 Launch the Control Panel and navigate to Administration.
2 In the navigation pane, select Users, Groups, or Roles.
3 Create new items, or edit the existing ones.
Groups
If you use an external authentication provider, you can either import the names of
groups that exist in the external system, or create new internal groups. There is
no limit on the number of groups that can be mapped or created.
Assign users to groups either in the external system or in the Control Panel. If you
need additional user assignments that are relevant only for OpenLab CDS, create
them in the Control Panel. Otherwise it is sufficient to only import the groups and
assign the required roles to the groups.
If you delete or unmap a group, the users who were members in this group
remain unchanged.
exception is the predefined role Everything, which has all privileges of all role
types. Users or groups may require multiple roles to perform system functions.
For example, a user with the role Chemist may need another role such as
Instrument User with the privilege to run an instrument.
You can create a tree of different locations in the Control Panel, and add
instruments to the relevant locations. For each instrument or instrument group,
you can assign different instrument roles (see also “Specific Roles for Individual
Instruments or Projects” on page 57). For example, a user can have the role
Instrument Administrator for one instrument, and Instrument User for another
instrument.
You can also create a tree of different projects or project groups in the Control
Panel, and assign different Project roles for different projects (see also “Specific
Roles for Individual Instruments or Projects” on page 57). For example, a user
can have the role Project Administrator in one project, so that he can manage the
settings in the Control Panel. In a second project, he may have a role that allows
him to edit the content of a project, but not to change the project settings.
For more information on privileges, see the Appendix.
Table 3 Description of role types
Administrative privileges These privileges are globally assigned to a user or group and cannot be
changed on the instrument/location level. They are the typical
administration privileges such as Backup and restore, Manage security,
Manage printers, etc.
Project privileges Privileges for accessing or modifying different levels of data. You can
assign these privileges globally or on project or project group level.
Software Architecture 61
Components on a Workstation Plus 62
OpenLab Platform Services and Components 63
21 CFR Part 11 Compliance 64
Data Security 64
Data Integrity 65
Audit traceability 65
Customization 66
Customization via custom calculations 66
Customization via report templates 66
Customize application to start external programs 67
Export raw data and results 67
Software Architecture
OpenLab CDS is a data system solution for analytical workflows that controls a
wide variety of instruments including the industry-leading GC and GC/MS-SQ
instruments, along with best-in-class LC and LC/MS-SQ. By combining
chromatography and single-quad mass spectrometry into a single scalable
solution with centralized system administration, you can streamline your
laboratory workflows and maximize productivity. A tailored and simplified user
interface with a new state-of-the-art user experience, along with e-learning tools,
helps you to get up to speed and productive as fast as possible.
The Agilent OpenLab CDS software is provided on read-only USB media that
contains all required executable files and documents. This includes:
• Acquisition
• Data Analysis and Reporting
• Shared Services
• Content Management
• Custom Calculation Editor
• Help and Learning Platform
• User documentation
• Instrument driver software for Agilent LC, GC, LC/MS, GC/MS, or A/D
• Instrument driver software for virtual instruments (Data Player)
• Agilent Parts Finder
• Third party tools
On a Workstation Plus (with Content Management), all components are installed
on a single PC. Results are stored in a database provided by the Content
Management component. Users have no access to the data via the local file
system. The system supports up to four instrument connections.
Workstation
• Test Services
Former QualA. Communicates with the Data Repository.
• CopyTo Server, and CopyTo Client
Manage centralized printing.
To fulfill the FDA rules and guidelines for compliant electronic records and
computerized systems, it is important to understand the basic aspects of secure
data handling.
• Data security: physical protection of data by limiting access to the system and
preventing unauthorized access.
• Data integrity: protecting raw data and metadata and preventing these from
unauthorized modification, and linking raw data and results to reproduce the
original results at any time, for example, in an audit situation, and document
each new result copy.
• Audit traceability: documenting who did what to the results and when, and
tracing the user adding new reanalyzed versions to the original raw data.
Data Security
The Shared Services functionality related to security includes the following (see
“Control Panel” on page 69 for details):
• System Activity Log
• Selection of authentication provider
• Management of users, groups, roles, and privileges
• Security Policy
Data Integrity
OpenLab CDS stores data in a manner that ensures compliance with 21 CFR Part
11. It provides secure data storage with access control and an audit trail. Data
files are versioned to ensure data integrity and traceability. In addition, OpenLab
CDS provides electronic signatures allowing users to sign off on data.
Audit traceability
There are different types of audit trails:
• The sequence audit trail is a record of changes made to the sequence when
acquiring the data.
• The method audit trail provides a detailed list of modifications to a sample
preparation method, an acquisition method, or a processing method.
• The injection audit trail is the record of a single injection that lists all
modifications during the run and in Data Analysis.
• The result set audit trail is a superset of injection audit trails for all injections
that are contained in a sequence/result set.
The specific behavior of an audit trail depends on the project settings in the
Control Panel.
Customization
Control Panel 69
Instrument Management / Lab Status at a Glance 69
License Management 70
System Activity Log 71
Diagnostics 72
Administrative Reports 72
Authentication Provider 73
Security Policy 73
User Management 73
Shared Services Maintenance 74
Important Information about Backup and Restore 75
Content of a Backup 75
Space required 76
Troubleshooting 76
Create a Disaster Recovery Plan 77
Backup Procedures 78
Backup before an Upgrade 78
Anti-virus scanning during backup 78
Use the Backup Utility 79
Backup verification 82
Incremental Backup Support of PostgreSQL Databases 84
Configure Custom Data Directory for PostgreSQL Databases 85
Restore Procedures 87
Troubleshooting the restore procedure 88
Restore on an existing OpenLab System 89
Restore on a clean machine without OpenLab CDS Workstation Plus installed 91
Routine Maintenance 92
This chapter contains information on the Control Panel and Shared Services
Maintenance. In addition, it describes various maintenance procedures.
Control Panel
Using the Control Panel, you can access Shared Services control features such
as security policy, central configuration, or lab status at a glance.
Accessing the functions described below may require specific privileges.
License Management
This service includes the administration of all licenses that are required for your
system.
Before adding a license file, you must first purchase the license and generate the
license file using SubscribeNet. For more information on generating new license
files, see “Obtain a License with SubscribeNet” on page 46.
License Management in the Control Panel provides the following functions:
• You can add license files to the license server.
• You can navigate to the license monitor and view the properties of all licenses
installed on a given license server.
• You can remove license files from the license server. This may be useful if an
invalid license file has been added.
• You can view or change the license server.
• You can view, copy, or save the MAC Address of the license server.
• You can navigate to the Agilent Electronic Software and License Delivery web
page to obtain a license.
The following properties are shown for installed licenses:
• Feature: This indicates the type of license used.
• Version: If a license is versioned, you can see the version number. For licenses
that are not versioned, the version is always shown as 1.0.
• In Use (Available): This indicates the number of licenses that are currently in
use and, in brackets, the total number of licenses. With the OpenLab CDS
Diagnostics
The Diagnostics view allows you to access several reports and tools for
diagnostic purposes:
• Ping the server.
• Create a report, either for the local system or for the server, with information
on the operation system, processors, disk drives, processes, network, and
connections.
• Centrally access and download all the log files, trace files, etc. that are created
by the registered modules.
Administrative Reports
In the Administrative Reports view, you can additionally create and export various
XML or PDF reports related to the system configuration:
Instruments Report
Provides detailed information about configuration and access privileges for all
instruments on the system. On client-server systems, this report includes all
instruments on all Instrument Controllers.
Projects Report
Provides detailed information about configuration and access privileges for all
projects on the system.
System Report
This report provides a consolidated view of the system, which includes all
information about instrument controllers, instruments, projects, roles, users, and
groups.
Authentication Provider
The authentication provider is described under Configure OpenLab CDS. For
details, see “Configure Authentication” on page 52.
Security Policy
The security policy is described under Configure OpenLab CDS. For details, see
“Configure Security Policy” on page 53.
User Management
The user management is described under Configure OpenLab CDS. For details,
see “Configure users, roles, and privileges” on page 54.
It is mandatory that you back up OpenLab CDS Workstation Plus regularly. Use
the Backup Utility to perform immediate or scheduled backups. The Backup
Utility supports periodic full backups and differential backups between the full
backups. These backups are the only way to restore an OpenLab CDS
Workstation Plus if a hardware or software failure occurs.
Agilent recommends using the Backup and Restore utilities whenever possible.
The backup only reduces the amount of data loss if a catastrophic system failure
occurs. Performing backups guarantees that any data that was committed at the
time of the backup can be restored. Data that was queued for upload and not yet
committed or was added or updated in the system after the backup was
performed will not be recoverable by restoring a backup.
It is also mandatory that you test the restore procedures to ensure that the
backups are performed properly and can be used for a restore. To do an effective
restore, you must create a disaster recovery plan. See “Create a Disaster
Recovery Plan” on page 77.
In cases where a restored system will run at the same time as the source
NOTE system, it is imperative that the restored system is on a network isolated from
the source system. See “Data Loss” on page 88.
Content of a Backup
OpenLab CDS Workstation Plus stores files and indexes on your machine file
system. The location of this folder is determined during product installation.
Other data, such as folder information, audit trails, and signatures are stored in a
database.
A full backup captures a complete set of data from OpenLab CDS Workstation
Plus, including uploaded files and its databases. An incremental backup contains
changes that have occurred since the last full backup. The incremental backup
process is faster than the full backup because only the changed elements are
backed up.
Space required
The free space required for the backup procedure depends on different factors,
including the system configuration, backup location, and database backup size.
In the most resource-intensive case, free space should be twice as much space
as is stored on-perm (local or network share) or bigger in the most demanding
case. This is needed to avoid rewriting a previous successful backup with a
backup that finished in the middle for any reason.
Additionally Backup and Restore Utilities use specific databases folders as
temporary backup locations during backup/restore. See “Configure Custom Data
Directory for PostgreSQL Databases” on page 85.
If you plan to use incremental backups, you must configure the OpenLab CDS
and Data Repository PostgreSQL databases first. See “Incremental backup
support of PostgreSQL databases” on page <type correct page number>.
Troubleshooting
The Backup Utility collects logs in the %ProgramData%\Agilent\LogFiles\Backup
folder. During the backup procedure, all steps are checked, and the procedure will
stop on the first failed step. A link with the failed step opens the current backup
log file to help identify the issue. In case of a failed backup, the partial backup is
stored in a Temp folder in the backup location.
Backup Procedures
1 Make sure that the backup location is excluded for both regular/scheduled
scans and real-time protection.
If the backup location cannot be excluded from real-time protection and
real-time protection cannot be turned off, it is possible the final backup tasks
might not finish successfully.
2 If you have an anti-virus running during backup, verify that the backup finished
successfully:
• After the backup completes, check that the backup location contains only
"Current" (or "Current" and "Incremental") sub-folder(s).
• Check that the log file corresponding to the backup time contains an entry
stating "The backup has completed" at the end. Backup logs are placed in
the C:\ProgramData\Agilent\LogFiles\Backup folder.
3 Modify the Retry policy:
By default, the Backup Utility tool tries 3 times to finalize the backup, with a 10
seconds delay inbetween.
To modify the backup finalization settings, change the Delay and Retry
properties in the Backup >BackupFinalizationSettings section of the
configuration.xml file. This file is located in the %ProgramData%\Agilent\
Installation folder. Only a user with System Administrator privileges can
update this file. Acceptable values are more than 0 for Delay, and more than 1
for Retry.
A new value will be applied during a backup; for Backup now at the Processing
Page before the first step, for Backup by schedule when a backup is started.
Reboot the system if the time zone has been changed. Otherwise, the date and
NOTE time on the Status page can show mismatched values.
In the event of a failed backup, the partial backup is saved in a Temp folder in
your backup location.
If a backup failed for some reasons during the final backup tasks execution, the
NOTE backup can still be considered successful if the Temp folder contains backup.xml
file.
In this case, you may rename the Temp folder as follows:
• If a full backup has been performed , rename the Temp folder to Current.
• If an incremental backup has been performed, rename the Temp to
Incremental.
Backup verification
The backup verification step verifies the backed-up data after the completion of
the backup procedure. This step generates two reports. Both reports are located
in the Verification sub folder.
• VerificationReport.xml - This file contains the technical information about the
backed-up entities such as files, their hashes, databases' entities, and so on.
In case of restoration, this report will be used for comparison of the files and
databases' entities.
• VerificationReport.html - This report contains information about backup,
number of verified files, information about failed file verification, and database
entity verification results in a human-readable view.
The verification step checks that main entities (files, database entities) are
backed up properly. The number of files for verification is specified in the
configuration file after backup configuration (10 % by default). Files will be
verified and included in the report after the backup procedure. In case of
restoration, all entities which have been included in the report will be verified. Any
entity (or its version) modified after the backup start time will not be included in
the reports and will not be verified during the restoration procedure.
Files Verification
For the file verification, the following logic is used:
• The Backup Utility first counts all backed up files and randomly takes 10 % of
the amount of the files. The taken percent of the files for the verification is
always rounded up, for example, for 3 files 10% is 0.3, and this value is
rounded to 1. It is useful for a small number of files in Content Management;
the tool guarantees that at least 1 file will be verified.
• Then the utility takes a random version of each file. For example, if a file in
Content Management has three revisions (1.0, 2.0, and 3.0), the utility will
randomly take one of them.
• The Verification excludes deleted files.
• The Verification procedure compares the checksum and size of backed up
files with file information from Content Management. If the checksums are
equal, the verification is passed. Otherwise, the verification is failed.
The amount of files for verification can be configured in the configuration.xml file,
located in the %ProgramData%\Agilent\Installation folder. Only a user with
System Administrator privileges can update this file. Modify the following
properties in the Backup section:
• PercentFilesVerification: the percentage of files verified (10% by default).
Acceptable values are in the range from 1 to 100.
• TotalFilesVerificationLimit: the upper limit files for verification (10 000 by
default). Acceptable values are greater than 0; negative and fractional values
are not acceptable.
. Negative, fractional, and values above 100 are not accepted.
A new value will be applied during a backup; for Backup now at the Processing
Page before the first step, for Backup by schedule when a backup is started.
Database Verification
Verification includes checking of number of database entities for:
• Methods
• Samples with unique names
• Shared Services Activity Log
• Content Management Activity Log
Examples:
• PgIncrementalConfigTool.exe -on
Enable incremental backup, setup default paths.
• PgIncrementalConfigTool.exe -off
Disable incremental backup.
• PgIncrementalConfigTool.exe -on -olcmWalDir D:\wal\
olcm -drWalDir "D:\wal\dr files"
Enable incremental backup and set up specified paths.
The tool configures the PostgreSQL databases and restarts the PostgreSQL
services. On successful completion, it shows the message Configuration
completed successfully. If an error occurs, it shows the message
PgIncrementalConfigTool has failed. The log files: <log file path>.
Restore Procedures
Use the Restore Utility to restore your Workstation Plus from an existing backup
if it becomes inoperable due to a hardware or software failure.
If you are upgrading your machine, perform the following procedures on your
machine before the upgrade.
The restore procedure will restore only committed data captured by the
successful backup procedure. Any data that was created or updated after the
backup was performed are not recovered by restoring a backup. Re-configuration
and restore procedure from AWS S3 backup location are not supported for
Workstation Plus.
The Restore Utility can restore a system from cold and hot backups created with
NOTE the Backup Utility. The Restore Utility can be run on systems with OpenLab CDS
installed or on clean systems (see “Restore on a clean machine without OpenLab
CDS Workstation Plus installed” on page 91).
If you are using non-default paths for configuring PostgreSQL for incremental
NOTE backup in a backed-up system, please follow the instructions under “Incremental
Backup Support of PostgreSQL Databases” on page 84 after the restore.
Data Loss
In cases where a restored system will run at the same time as the source
C AU T I O N system (where the backup was taken), it is imperative that the restored system
is on a network isolated from the source system.
If a test system is created from a backup of the production system, and the
test system and the production system are on the same network, it may cause
the two machines to create a cluster and interact with each other. This can
lead to data corruption and loss.
The restore system must be on a network that is isolated from the
production system.
In addition, it is important to turn clustering off on the restored system using
the following steps:
On the restored machine, open C:\Program Files (x86)\Agilent Technologies\
OpenLAB Data Store\tomcat\shared\classes\alfresco-global.properties. Find
the alfresco.cluster.enabled property, and set it to false
(alfresco.cluster.enabled=false).
Restart the alfrescoTomcat service.
Prerequisites • You must have System Administrator privileges to run and execute the
Restore Utility.
• To successfully access the folder with the backup, the application must be
launched by a user with reading rights in this folder.
1 Stop all OpenLab CDS Workstation Plus operations before performing the
restore process.
2 Make sure that any instruments or other parts of the system are not using the
system during the restore process.
3 From the Windows Start menu, select Agilent Technologies >Restore Utility.
4 On the Backup Location page, choose your backup location.
Select File system as the backup location if the backup is located locally or on
Windows share. Select the backup folder that was used by the Backup Utility.
Restore and Verify is selected by default. For normal recovery, select Restore
only.
Click Next.
5 On the Review page, review the settings and click Apply.
The restore procedure progress is tracked on the Restore page.
6 When the restore procedure is complete, click Done.
If you selected Restore and Verify or Verify only, a verification step is displayed
as the last step. Click the verification status Done link to open the verification
report.
7 When the restore procedure is complete, click Done.
8 Reboot the restored OpenLab CDS Workstation Plus system.
Select Yes to reboot the system immediately. Select No if you want to
postpone the reboot and perform it manually
1 The Agilent OpenLab Shared Services Use the following command instead:
service is already stopped. del /s /f /q %ProgramData%\
Agilent\OLSS\Index\
ActivityLog && net start
SharedServicesHost
1 The Command Prompt has insufficient Make sure the Command Prompt has been
privileges. started as an Administrator.
Verification
Verification is available only for systems on which the OpenLab software has
already been installed.
Verification reports are saved at C:\ProgramData\Agilent\Restore\Verification.
The Restore Utility collects logs in the %ProgramData%\Agilent\LogFiles\Restore
folder.
During the restore procedure, validations on each page prevent possible errors,
such as no access to content and archive locations, or incorrect formats. The
procedure will stop on the first failed step. A link with the failed step opens the
current restore log file to help identify the issues.
Routine Maintenance
License Upgrade 94
Get Upgraded License File 94
Add Upgraded License File to the System 95
Upgrade OpenLab CDS Workstation to Latest Version 96
New Privileges and Roles 98
License Upgrade
If the relevant host name does not appear, you may be managing your
licenses in multiple SubscribeNet accounts. You will need to log into those
accounts to upgrade those licenses.
4 If your license(s) are eligible for an upgrade, you will see the Upgrade All
button. Otherwise you will need to contact your Agilent Sales Representative
to renew your Software Maintenance Agreement (see “Sales and Support
Assistance” on page 113). To proceed with generating your upgrade license,
click the button.
5 On the Upgrade All Licenses for License Host page, review the data, and
confirm by clicking Upgrade All.
This upgrades the license file to the most current version. SubscribeNet will
send you an email with a new license file.
6 Put the new license file on your system (see “Add Upgraded License File to the
System” on page 95.
If you have multiple standalone Workstations, repeat this step for each
individual workstation.
Note that each workstation's MAC address is the file name. This helps identify
the correct license file to import into the workstation's Control Panel.
A full restart is required in order for any license to have an immediate effect.
NOTE
You can upgrade an OpenLab CDS standalone workstation to the latest version
using the OpenLab CDS Installation Wizard. A direct upgrade is supported from
OpenLab CDS rev. 2.4 or higher.
Uninstallation of ADFExport 1.3 or lower after an upgrade may cause the Data
C AU T I O N Analysis application to fail to start.
Rev. 1.3 or lower of ADFExport is not compatible with OpenLab CDS 2.7.
Uninstallation of one of those ADFExport versions after an upgrade (e.g. during
its own upgrade) may remove vital files from OpenLab CDS. This may cause
the Data Analysis application to fail to start. Automated processing and data
analysis during acquisition may fail. A re-installation of OpenLab CDS might
become necessary.
If Rev. 1.3 or lower of ADFExport for OpenLab was installed with your
OpenLab CDS version, uninstall it before upgrading OpenLab CDS to Rev.
2.7.
1 Run the setup.exe file from the installation media as a user with
administrative rights.
2 Select OpenLab CDS.
3 In the OpenLab CDS Installer, select the Installation screen.
4 Select Workstation with CM.
5 In the License Agreement screen, read and confirm Agilent terms and
conditions. Click Next.
6 In the Server Information screen, click Connect. If your previous installation
required user authentication, provide the OpenLab Control Panel login
credentials of an administrator. Click Next.
7 In the Data Repository screen, provide a new password for Data Repository
accounts. The new password will reset an existing password. Click Next.
8 In the System Preparation screen, the upgrade wizard shows the list of
recommended settings for the system. You may clear the check boxes for
items that you do not want to apply on the system. Mandatory settings will be
applied automatically during the upgrade. For an overview of both mandatory
and recommended settings, refer to the chapter System Preparation Tool in
the OpenLab CDS Workstations, Clients, and Instrument Controller
Requirements and Supported Instruments guide
(CDS_v2.7_Requirements_en.pdf).
Click Next to proceed to the Review page. The settings will be applied as part
of the installation.
9 In the Review screen, click Upgrade to start the upgrade.
10 If there are still manual actions required before installation, a warning is
shown.
Options to proceed
• Recommended: Click Open SPT Report to view instructions to complete
these actions. In the report, check the Required Actions section. After
completing the operations, click Resume Installation.
• Cancel Installation: Installation is aborted. Make necessary updates and
restart installation.
• Resume Installation: The dialog is closed, and installation continues with
the installation of the CDS components even if a setting was not applied. If
needed, the settings can be updated after the installation has been
completed.
11 On the Upgrade tab, click Next after all components are installed.
12 In the Configure screen, click Next.
13 On the Finish page, click Run Software Verification.
14 On the Finish page, keep the Reboot check box selected, and click Finish.
15 If you use a GC/MS instrument: Upgrade the GC/MS firmware to the latest
revision. The upgrade is required for the GC/MS software to work properly
with OpenLab CDS 2.7.
For more information on driver upgrades, see “Install or Upgrade Driver
Software” on page 26.
It is recommended that you reconfigure the instrument in the Control Panel.
After the upgrade completes, the Activity Log Index will be rebuilt. The time
NOTE required to rebuild the index depends on the number of Activity Log records. It
and can take up to a few hours. During this interim period, Activity Log searches
in the application provide a user-friendly message about indexing.
On upgrade from a previous version, new privileges and roles may be created. For
example, Starting with Shared Services version 3.6 / OpenLab CDS 2.7, the
privilege View activity log has been added. This privilege is now required to view
activity logs and audit trails (see Appendix for details on roles and permissions).
This privilege is by default assigned to the new role Activity Log Access. During
the upgrade, this new role is automatically assigned to all existing users and
groups.
The View activity log privilege is also automatically added to the System
Administrator default role.
1 Log in as an administrator.
2 In the Windows Settings, open Apps >Apps and features.
3 Select Agilent OpenLab CDS, and confirm uninstallation.
The OpenLab CDS Uninstallation Wizard opens1. In the wizard, click Uninstall,
and follow the wizard.
4 In the Windows Settings under Apps >Apps and features, continue the
uninstallation by removing the following features:
• Agilent Software Verification Tool
• PostgreSQL - OLCM
When uninstalling PostgreSQL, a warning will be shown that the data
directory has not been removed. If you want to remove it, manually delete
the folder that you defined during installation (for example, C:\DSData).
• Instrument drivers
Drivers installed by OpenLab CDS are uninstalled automatically. If you
installed other drivers, uninstall them manually.
5 Reboot.
1
The Uninstallation wizard can also be started from the Installation Wizard used to install the
software.
If you installed OpenLab Help and Learning only, follow this procedure to uninstall
it.
1 From the installation media, right-click the setup.exe file, and run it as
administrator.
2 On the start screen, select OpenLab CDS, and click OK.
3 On the Installation page, select OpenLab Help and Learning Only.
The Agilent OpenLab CDS Help and Learning wizard opens.
4 Click Remove.
The wizard removes OpenLab Help and Learning from your system.
5 After completion of the uninstallation, click Finish to close the wizard.
Troubleshooting Tips
How to recover
If there is not enough space for installation, proceed as follows:
1 Uninstall the OpenLab CDS Application, and delete the content of C:\
ProgramData\Package Cache.
2 Run the installation of OpenLab CDS 2.7 again
The privileges described in the following can be associated with different roles in
the Control Panel. The following roles are available:
• Everything • Chemist
• System Administrator • Activity Log Access
• Instrument Administrator • Archivist
• Project Administrator • Content Management Approver
• Project Content Deletion • Content Management Contributor
• Instrument User • Content Management Reader
• Technician • Content Management PDF Template
Manager
• Content Management Administrator
In the Control Panel under Administration >Roles, you can view or change the
associated privileges, or create your own roles.
Project Privileges
Table 4 Project Management
Name Description
Manage project or project group User can create or edit project properties and can
move the project but cannot view or edit the
project access settings.
Manage project or project group access User can view and edit the project access
settings.
View project or project group User can see a project and project details but
cannot edit.
Note: This privilege is required for all users.
Access content using web client User can view the data via the Content
Management web interface.
Name Description
Edit content of project User can create new versions of documents (e.g.
data, methods, or templates).
Table 5 E-Signature
Name Description
Change method status User can change the status (Generic, Approved,
Obsoleted) of sample prep methods, acquisition
methods and processing methods.
Name Description
Create and modify sample prep View, edit, and save an autosampler sample prep
file
Use generic sample prep methods Use sample prep methods that have the status
Generic.
Name Description
Create and modify acquisition method Create, edit and save an acquisition method file
(*.amx)
Use generic acquisition methods Use acquisition methods that have the status
Generic.
Name Description
Edit integration parameters View and edit the parameters in the Integration
Events section of a method.
Edit chromatogram extraction parameters View and edit the parameters in the
Extraction >Chromatogram section of a method.
Edit spectrum extraction parameters View and edit the parameters in the
Extraction >Spectrum section of a method.
Edit MS library search parameters View and edit the parameters in the MS Library
Search >Properties section of a method.
Edit system suitability parameters View and edit the parameters in the
Compounds >System Suitability section of
method.
Edit custom calculation parameters View and edit the parameters in the
Tools >Custom Calculation section of a method.
Name Description
Edit sample purity parameters View and edit the parameters in the MS Sample
Purity section of a method.
Load older master method With Content Management, load an older version
of a master method.
Edit Post Processing Plugins parameters View and edit the parameters in the Post
Processing Plugins section of a method.
Use generic processing methods Use processing methods that have the status
Generic.
Privilege Description
Unlock/lock report template items Lock and unlock report template items (tables,
chromatograms, groups of items, ...) to control
who is allowed to modify those.
Create report template Create and edit report templates in the Reporting
view.
Name Description
Create and modify sequence template Create, edit and save sequence creation
templates (*.stx).
Table 11 Sequence
Name Description
Edit any users running sequence Edit any user's running sequence (status
Acquiring in the Run Queue).
Create and modify sequence Create, edit and save sequences (*.sqx)
Edit users own running sequences Edit your own running sequences (status
Acquiring in the Run Queue).
Name Description
Change method audit trail settings Edit and save method audit trail settings (project
properties in the Control Panel).
Review audit trail Confirm that you reviewed a changed audit trail.
Add manual audit trail entry Add a manual entry to document your own
actions in the audit trail.
Table 13 Control
Name Description
Abort any running sample Abort any running sequence or single run.
Manual control (in run) Access manual control functions while the
instrument is running.
Manual control (only when instrument idle) Access manual control functions while the
instrument is idle.
Cancel any pending run Cancel pending runs in the run queue submitted
by any user.
Cancel my pending run Cancel own pending runs in the run queue.
Reorder pending runs Reorder pending run queue items in the run
queue. Moving items around in the run queue.
Table 13 Control
Name Description
Modify Instrument configuration in CDS Client Change instrument configuration directly from a
running Acquisition client .
Note: This privilege is not yet used by all
instrument drivers.
Name Description
Integration Optimizer: Display peak results Show the retention time, area, and area % for
each integrated peak in the Integration
Optimizer.
Launch Custom Calculation Editor Start the Custom Calculation Editor from Data
Analysis.
Update master processing method Save changes from a result set method to the
corresponding master processing method in the
Methods folder.
Name Description
Name Description
Table 16 Data
Name Description
Table 17 Lock
Name Description
Name Description
Access Custom Tools section Start external programs that were added to the
application via the customization tool
Table 19 Snapshot
Name Description
Instrument Privileges
Table 20 Instrument Management
Name Description
View instrument or location User can view and access a location in the tree,
but not edit access security, can view properties.
Manage Instrument or location User can create and move locations and edit
properties (name, description, etc).
Manage instrument or location access User can view and edit the location access
settings.
Administrative Privileges
Table 21 System Administration
Name Description
Edit activity log properties Can change the Activity log Settings in the
Control Panel (that is, can turn logging on for the
System Activity Log).
Create administrative reports Can create any of the system admin reports.
Name Description
Name Description
Please check the following web site for your local sales and support contact:
https://www.agilent.com/en/support
Agilent Community
To get answers to your questions, join over 10,000 users in the Agilent
Community. Review curated support materials organized by platform
technology. Ask questions to industry colleagues and collaborators. Get
notifications on new videos, documents, tools, and webinars relevant to your
work.
https://community.agilent.com/
www.agilent.com
Agilent Technologies Inc. 2015-2022
Edition: 04/2022
Document No: D0013820 Rev. A