Enterprise Vault™ Discovery Accelerator Installation Guide

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

Modifying the Enhanced Auditing setup

To modify the Enhanced Auditing setup

  1. Launch the Veritas Enhanced Auditing installer. To launch the installer, do any of the following steps:

    • Run the MSI file from the command prompt.

    • Right-click on the available MSI file and click Install.

    • Navigate to the Control Panel and double-click the Add or Remove Programs applet. Find and click Veritas Enhanced Auditing in the list of installed programs. Right-click on the installer and click Change.

    The installer opens the Welcome wizard.

    Note:

    Click Cancel if you want to cancel the installation at any stage. After you click Cancel, the application prompts you to confirm the operation. If you interrupt the installation process, the installer prompts you to run the installation again whenever required. Click Yes to complete the operation and click Finish to abort the installation. Click No to continue the installation.

  2. Click Next to proceed to the Settings wizard. On the Modify, repair, or remove installation page, click Modify.
  3. On the Veritas Enhanced Auditing Configuration page, provide the following details to create an Audit Server website and enable it for secured access. Then, click Next.

    • Server Name: Change the DNS Alias name or FQDN for the audit server, if required.

    • Port: Change the Port for the audit server site, if required. Enter a new port that is available to use. You must not use the default IIS port 80.

    • Comma-separated list of IP addresses from where the audit server can be accessed: Enter a comma-separated list of IP addresses of the servers from which the audit server will be accessed. These are the IP addresses for each protocol (IPv4 and IPv6) that are enabled on the Discovery Accelerator server. If you want to keep the previous IP addresses, do not delete them. If you delete the previous IP addresses, the new IP addresses overwrite the previous ones. You can add the new IP addresses by separating every IP address by a comma. You can also provide ranges of IP addresses, for example - 10.1.2.3,10.1.2.11-15.

    • Holding folder Path: Browse to another directory where the audit data is stored temporarily, if required.

      Even though the previously selected holding folder may not be in use, it does not get deleted after the modification.

      Note:

      Ensure that the Access Control List (ACL) of the Holding Folder is not changed. The default users, such as SYSTEM, Built-in administrators, Audit Server Account, and IIS APPPOOL\AuditingServer, must be unchanged.

      Based on these details, the audit server URL format becomes:https://<auditservername>:<portnumber>.

  4. Click Next.

    Note:

    If you try to modify the Elasticsearch URL, the application displays a warning message that the existing server data (auditing-specific) will not be automatically migrated to the new server. Therefore, before you change the Elasticsearch URL, ensure that you need to migrate it manually to the Elasticsearch server you want to use. Otherwise, this data will be lost.

  5. On the Settings wizard, on the Ready to install page, click Install.
  6. On the Veritas Enhanced Auditing Configuration page, ensure that the Elasticsearch installation location is appropriate. Then, click Next.
  7. After the modification is complete, click Finish and restart the server to apply the changes.
  8. To view the modification-specific logs, navigate to the folder where you have installed the Veritas Enhanced Auditing setup and access the Logs folder.