Arctera Enterprise Vault™ eDiscovery Installation Guide

Last Published:
Product(s): Enterprise Vault (15.2)
  1. Introducing eDiscovery
    1.  
      About eDiscovery desktop application
    2.  
      About eDiscovery web application
    3.  
      Feature comparison: Arctera eDiscovery desktop application Vs Arctera eDiscovery web application
    4.  
      Key features of eDiscovery
    5. Product documentation
      1.  
        White papers on the Arctera Support website
      2.  
        eDiscovery training modules
  2. Preparing to install eDiscovery
    1. Configuration options for eDiscovery
      1.  
        eDiscovery configuration for large installations
      2.  
        eDiscovery configuration for smaller installations
    2.  
      Supported versions of Enterprise Vault in eDiscovery environments
    3. Prerequisites for Arctera eDiscovery
      1.  
        Prerequisites for the SQL Server computer
      2.  
        Prerequisites for the Arctera eDiscovery server computer
      3.  
        Prerequisites for the Enterprise Vault server computer
    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 eDiscovery environment
    8.  
      Disabling the Windows Search Service on the eDiscovery server
    9.  
      Ensuring that the Windows Server service is running on the eDiscovery 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 eDiscovery
    1. Installing the eDiscovery server software
      1.  
        Allowing Enterprise Vault to communicate with eDiscovery through the Windows firewall
      2. Creating the configuration database and customer databases
        1.  
          Configuring analytics database locations
      3. Setting up a Insight eDiscovery Custodian Manager website
        1.  
          Assigning the required Active Directory permissions to the Insight eDiscovery Custodian Manager synchronization account
      4.  
        Uploading the eDiscovery report templates
      5. Configuring eDiscovery for use in a SQL Server Always On environment
        1.  
          Using SQL Server Reporting Services in an Always On environment
      6. Installing eDiscovery in a clustered environment
        1.  
          Configuring eDiscovery for use in a Network Load Balancing cluster
      7.  
        Maximizing security in your eDiscovery databases
  4. Appendix A. Ports that eDiscovery uses
    1.  
      Default ports for eDiscovery
    2.  
      Changing the ports that eDiscovery uses
  5. Appendix B. Troubleshooting
    1.  
      Error messages appear in the event log when upgrading to eDiscovery 15.2
    2.  
      Enterprise Vault eDiscovery Manager service not created
    3.  
      Enterprise Vault eDiscovery 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 eDiscovery customer databases when Symantec Endpoint Protection is running
    6.  
      Permissions error when uninstalling the eDiscovery client from a UAC-enabled computer
    7.  
      Uninstalling the eDiscovery client from a shared location may prevent other users from starting the client
  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 eDiscovery

Using SQL Server Reporting Services in an Always On environment

Microsoft does not fully support the use of SQL Server Reporting Services in an Always On environment and, consequently, neither does eDiscovery. As the following article explains, however, it is possible to configure Reporting Services to work with an Always On availability group:

https://msdn.microsoft.com/hh882437.aspx

In summary, you must do the following to make the eDiscovery reports work in an Always On environment:

  • Install SQL Server Reporting Services on all the replicas in the availability group.

  • On all the secondary replicas, assign the same reporting server credentials to the Vault Service account as you assigned to this account on the primary replica:

    • The System Administrator role

    • The Content Manager role on the Home folder

    Use the Report Manager tool that comes with SQL Server to assign the credentials.

    See Uploading the eDiscovery report templates.

  • On the primary replica, use the Encryption Keys page of Reporting Services Configuration Manager to back up the encryption keys for the report server databases to a file.

  • Add the report server databases, ReportServer and ReportServerTempDB, to the availability group.

  • When you upload the eDiscovery report templates through the eDiscovery Manager website, take care to specify the correct URL for the reporting server. Rather than specify the name or address of a standalone SQL reporting server, you must specify the virtual network name of the appropriate availability group listener. For example, you might specify the reporting server URL as follows:

    http://availability_group_listener/ReportServer

  • After failover occurs, do the following:

    • Use the Reporting Services Configuration Manager to point the report server service on the new primary replica to the failed-over databases, ReportServer and ReportServerTempDB.

      Take care to specify the report server database credentials for the same domain user as you previously specified on the old primary replica.

    • On the Encryption Keys page of Reporting Services Configuration Manager, restore the encryption keys from the backup file that you previously created on the old primary replica.