Veritas Enterprise Vault™ Compliance Accelerator Installation Guide

Last Published:
Product(s): Enterprise Vault (12.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
    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.  
      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 AlwaysOn environment
        1.  
          Using SQL Server Reporting Services in an AlwaysOn 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 12.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.  
      Home page of Compliance Accelerator website not found
    6.  
      Cannot create or upgrade Compliance Accelerator customer databases when Symantec Endpoint Protection is running
    7.  
      Permissions error when uninstalling the Compliance Accelerator client from a UAC-enabled computer
    8.  
      Uninstalling the Compliance Accelerator client from a shared location may prevent other users from starting the client

Home page of Compliance Accelerator website not found

If you receive the message "Page Cannot Be Displayed" when you browse to the home page of the Accelerator Manager website, start IIS Manager and then check the following:

  • The virtual directories have been created.

  • The websites are running.

  • The virtual directories are configured to use ASP.NET 2.0 rather than an earlier version.

If the installation program failed to create a virtual directory as part of the installation process, you can create it manually.

To create the virtual directory manually

  1. Open IIS Manager on the server that is hosting the website.
  2. Right-click the container for your default website and then click New > Virtual Directory.
  3. When the Virtual Directory Creation Wizard appears, click Next.
  4. For the virtual directory alias, type one of the following, and then click Next.

    EVBAAdmin

    Used by the Accelerator Manager website.

    EVBACompliance

    Used by the Compliance Accelerator reporting functionality.

  5. For the website home directory, enter the path to the appropriate subfolder of the Compliance Accelerator program folder (AcceleratorAdminWeb or ComplianceWebMin), and then click Next.
  6. When you are prompted to set the access permissions for the virtual directory, click Next without changing the default permissions.
  7. Click Finish to close the wizard and create the virtual directory.

To configure the settings for the virtual directory

  1. Open IIS Manager on the server that is hosting the website.
  2. Right-click the EVBAAdmin or EVBACompliance virtual directory, and then click Properties.

  3. On the Virtual Directory tab, do the following:

    • Make sure that Read, Log visits, and Index this resource are all checked.

    • Remove the entry in the Application name box.

    • Make sure that the application pool is set to EVAcceleratorAppPool.

  4. On the Documents tab, remove all the entries in the Enable default content page box, and then add Login.aspx.
  5. On the Directory Security tab, click Edit under Authentication and access control.
  6. In the Authentication Methods dialog box, uncheck Enable anonymous access and check Integrated Windows authentication. (You can select Basic authentication, but it is less secure.)
  7. Click OK to save the changes you have made to the Authentication Methods dialog box.
  8. Click OK to close the properties dialog box.
  9. Check that the website is running.