There may be a business need for Enterprise Vault (EV) Compliance Accelerator (CA) or Discovery Accelerator (DA) Reviewers to be restricted to a specific CA or DA Customer when multiple CA or DA Customers exist in the environment. This Article describes how to accomplish this need.
Note: These steps do not apply to Veritas Advanced Supervision (VAS), which is web-based thin client available in CA version 14.0.0 and higher. They are also not applicable to the DA web-based thin client used for viewing Enhanced Auditing information starting from DA Version 14.5.0.
There are 2 files that need to be edited. These are the Accelerator.exe.config and StartupPreferences.xml files. The following uses DA as an example, but the same also applies to CA.
1. AcceleratorClient.exe.config
This file controls the initial startup of the Client the first time the Client is launched on a user's workstation. The file can be found in one of two locations, depending on how the CA or DA Client was installed:
- Per-User: C:\Users\
- Per-Machine: The folder as specified during the Client's installation.
The following entries under in this file will need to be edited (default settings listed below):
- Edit the name of the Accelerator Server. Replace localhost with the NetBIOS name or the Fully Qualified Domain Name (FQDN) name or IPV4 IP address of the CA or DA server:
- Edit the CustomerID of the CA or DA Customer to which to connect. This can be found by looking at the Connected to line at the bottom of the CA or DA Client when connected to the required CA or DA Customer, or by looking in the tblCustomer table in the Configuration database (SELECT * FROM tblCustomer;):
- Edit the CustomerName of the Customer to which to connect. This can be found by looking at the Connected to line at the bottom of the Client when connected to the required CA or DA Customer, or by looking in the tblCustomer table in the Configuration database (SELECT * FROM tblCustomer;):
- Edit to False to have the CA or DA Client automatically connect to the CA or DA Customer listed in the above settings:
- Edit to True to have the CA or DA Client not list any CA or DA Customers except the CA or DA Customer listed in the above settings:
- Edit to True to have the CA or DA Client not list any CA or DA Servers except the CA or DA Server listed in the above settings:
- Edit to True to remove the ability to change a CA or DA Server and/or CA or DA Customer by clicking on the CA or DA Customer name at the bottom of the CA or DA Client (Click here to connect to another instance) after editing the above settings:
2. StartupPreferences.xml
After the CA or DA Client has logged on for the first time, the StartupPreferences.xml file will be created per user under C:\Users\
- Edit to the required Accelerator Server name:
- Edit to False to prevent the CA or DA Client from prompting for an Accelerator Server and CA or DA Customer:
- Edit the CustomerName of the CA or DA Customer to which to connect. This can be found by looking at the Connected to line at the bottom of the CA or DA Client when connected to the required CA or DA Customer, or by looking in the tblCustomer table in the CA or DA Configuration database (SELECT * FROM tblCustomer;):
- Edit the CustomerID of the CA or DA Customer to which to connect. This can be found by looking at the Connected to line at the bottom of the CA or DA Client when connected to the required CA or DA Customer, or by looking in the tblCustomer table in the CA or DA Configuration database (SELECT * FROM tblCustomer;):
The below example is for an environment using a DA installation with multiple DA Customers to which the DA Admin wants to restrict certain users to a particular DA Customer having the following information:
The AcceleratorClient.exe.config file entries need to be set as follows:
The StartupPreferences.xml file entries need to be set as follows: