Enterprise Vault™ Compliance Accelerator Installation Guide

Last Published:
Product(s): Enterprise Vault (14.4)
  1. Introducing Compliance Accelerator
    1.  
      Key features of Compliance Accelerator
    2.  
      About the Compliance Accelerator components
    3. Product documentation
      1.  
        White papers on the Veritas Support website
  2. Preparing to install Compliance Accelerator
    1. Configuration options for Compliance Accelerator
      1.  
        Compliance Accelerator configuration for large installations
      2.  
        Compliance Accelerator configuration for smaller installations
    2.  
      Supported versions of Enterprise Vault in Compliance Accelerator environments
    3. Prerequisites for Compliance Accelerator
      1.  
        Prerequisites for the SQL Server computer
      2.  
        Prerequisites for the Compliance Accelerator server computer
      3.  
        Prerequisites for the Enterprise Vault server computer
      4.  
        Prerequisites for Compliance Accelerator client computers
      5. Prerequisites for Veritas Advanced Supervision
        1.  
          Additional requirements for Veritas Advanced Supervision
        2.  
          Set Kerberos Trusted Delegation
    4.  
      Configuring Outlook to enable the processing of items with many attachments or many recipients
    5.  
      Setting the Windows and ASP.NET Temp folder permissions
    6. Security requirements for temporary folders
      1.  
        Granting additional users and groups access to the temporary folders
    7.  
      Disabling networking facilities that can disrupt a Compliance Accelerator environment
    8.  
      Disabling the Windows Search Service on the Compliance Accelerator server
    9.  
      Ensuring that the Windows Server service is running on the Compliance Accelerator server
    10.  
      Configuring the SQL Server Agent service
    11.  
      Assigning SQL Server roles to the Vault Service account
    12.  
      Installing and configuring the SQL full-text search indexing service
    13.  
      Verifying that Enterprise Vault expands distribution lists
    14. Configuring Intelligent Review API Authentication and Authorization
      1.  
        Setting Kerberos trusted delegation between Compliance Accelerator Servers and Compliance Accelerator Database Servers
      2.  
        Setting Kerberos trusted delegation between Compliance Accelerator Servers and Compliance Accelerator Database Servers on IP address
  3. Installing Compliance Accelerator
    1. Installing the Compliance Accelerator server software
      1.  
        Allowing Enterprise Vault to communicate with Compliance Accelerator through the Windows firewall
      2.  
        Creating the configuration database and customer databases
      3.  
        Uploading the Compliance Accelerator report templates
      4.  
        Configuring a dedicated server for Intelligent Review processing (optional deployment configuration)
      5. Configuring Compliance Accelerator for use in a SQL Server Always On environment
        1.  
          Using SQL Server Reporting Services in an Always On environment
      6. Installing Compliance Accelerator in a clustered environment
        1.  
          Configuring Compliance Accelerator for use in a Network Load Balancing cluster
      7.  
        Maximizing security in your Compliance Accelerator databases
    2. Installing the Compliance Accelerator client software
      1.  
        Modifying the configuration file for the Compliance Accelerator client
      2.  
        Using the MSI installer package to install the Compliance Accelerator client
    3.  
      Uninstalling Compliance Accelerator
  4. Appendix A. Ports that Compliance Accelerator uses
    1.  
      Default ports for Compliance Accelerator
    2.  
      Changing the ports that Compliance Accelerator uses
  5. Appendix B. Troubleshooting
    1.  
      Error messages appear in the event log when upgrading to Compliance Accelerator 14.4
    2.  
      Enterprise Vault Accelerator Manager service not created
    3.  
      Enterprise Vault Accelerator Manager service does not start
    4.  
      "Access is denied" message is displayed when you try to create a customer database on a UAC-enabled computer
    5.  
      Cannot create or upgrade Compliance Accelerator customer databases when Symantec Endpoint Protection is running
    6.  
      Permissions error when uninstalling the Compliance Accelerator client from a UAC-enabled computer
    7.  
      Uninstalling the Compliance Accelerator client from a shared location may prevent other users from starting the client
    8.  
      Error messages when the Intelligent Review (IR) API authentication and authorization fails
  6. Appendix C. Installing and configuring the Enhanced Auditing feature
    1.  
      Overview
    2.  
      Prerequisites for the Enhanced Auditing feature
    3.  
      Installing the Enhanced Auditing feature
    4.  
      Post installation steps
    5.  
      Upgrading the Enhanced Auditing setup
    6.  
      Modifying the Enhanced Auditing setup
    7.  
      Repairing the Enhanced Auditing setup
    8.  
      Uninstalling the Enhanced Auditing setup
    9.  
      Managing access from Veritas Advanced Supervision

Changing the ports that Compliance Accelerator uses

You can set Compliance Accelerator to use different ports if another application requires the default ones.

To change the port used for communications with SQL Server, if you do not use SQL Always On

  1. On the Compliance Accelerator server, open the Accelerator Manager website.
  2. In the left pane, right-click the server name and then click Properties.
  3. In the Name field, specify the required SQL Server computer as server_name,port_number.
  4. Click OK to save the change that you have made.

  5. For each customer database, do the following:

    • In the left pane, right-click the name of the database and then click Properties.

    • In the SQL Server field, specify the required SQL Server computer as server_name,port_number.

    • Click OK to save the change that you have made.

To change the port used for communications with SQL Server, if you do use SQL Always On

  1. If the Enterprise Vault Accelerator Manager service is running on the Compliance Accelerator server, stop it.
  2. Open the Accelerator Manager website and wait for the following page to appear (this may take several minutes):
    SQL Always On port change dialog box in Accelerator Manager website
  3. In the SQL Server field, enter the required details and then click Update Configuration. For example, in the figure above, this field specifies an availability group listener (SQL-L), which is followed by a comma and then the port number 5053.
  4. Start the Enterprise Vault Accelerator Manager service.

To change the port used for communications between the Compliance Accelerator server and the Compliance Accelerator websites

  1. On the Compliance Accelerator server, locate the copies of the Web.config file in the AcceleratorAdminWeb and ComplianceWebMin subfolders of the Compliance Accelerator installation folder. (The ComplianceWebMin subfolder is only present if you have chosen to install the Compliance Accelerator website.)
  2. Open each file in a text editor such as Windows Notepad.
  3. Find the following line, and change the port number to a suitable alternative.
    <add key="RemotePort" value="8085"/>
  4. Save and close the files.
  5. Restart the Enterprise Vault Accelerator Manager service.

To change the port used for communications between the Compliance Accelerator server and the Compliance Accelerator clients

  1. On each Compliance Accelerator client computer, locate the AcceleratorClient.Exe.Config file in the installation folder.

    This folder is typically %HOMEPATH%\Local Settings\Application Data\Enterprise Vault Compliance Accelerator\Client.

  2. Open the file in a text editor such as Windows Notepad.
  3. Find the following line, and change the port number to a suitable alternative.
    <add key="AcceleratorServerPort" value="8086" />
  4. Save and close the file.
  5. If you need to change port 8086 to another port and you want to use Open Data (OData) web service to create reports, make sure that you update the OData configuration to use the same port. To update the port number, do the following:

    • On each Compliance Accelerator server computer, locate the AcceleratorService.Exe.Config and AcceleratorManager.Exe.Config files in the installation folder.

    • Open each file in a text editor such as Windows Notepad.

    • Find the following lines, and change the port number to match the setting in the AcceleratorClient.Exe.Config file.

      <add key="Windows Client Remoting Channel Configuration" value="8086" />
<add key="Windows Client Remoting Channel Configuration IPv6" value="8086" />

    • Save and close the file.

To change the port used for communications with the SQL reporting server

  1. On the Compliance Accelerator server, open the Accelerator Manager website.
  2. Click Reporting Server at the bottom of the page.

    The Uploading Reporting Server Templates page appears.

  3. In the Reporting Server URL field, type the URL with which to access the SQL reporting server in the following form:

    http://server_name,port_number/virtual_directory