Enterprise Vault™ Compliance Accelerator Installation Guide

Last Published:
Product(s): Enterprise Vault (14.1)
  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
    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
  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 Compliance Accelerator for use in a SQL Server Always On environment
        1.  
          Using SQL Server Reporting Services in an Always On environment
      5. Installing Compliance Accelerator in a clustered environment
        1.  
          Configuring Compliance Accelerator for use in a Network Load Balancing cluster
      6.  
        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.1
    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