Enterprise Vault™ Discovery Accelerator Installation Guide
- Introducing Discovery Accelerator
- Preparing to install Discovery Accelerator
- Configuration options for Discovery Accelerator
- Supported versions of Enterprise Vault in Discovery Accelerator environments
- Prerequisites for Discovery Accelerator
- Configuring Outlook to enable the processing of items with many attachments or many recipients
- Setting the Windows and ASP.NET Temp folder permissions
- Security requirements for temporary folders
- Disabling networking facilities that can disrupt a Discovery Accelerator environment
- Disabling the Windows Search Service on the Discovery Accelerator server
- Ensuring that the Windows Server service is running on the Discovery Accelerator server
- Configuring the SQL Server Agent service
- Assigning SQL Server roles to the Vault Service account
- Installing and configuring the SQL full-text search indexing service
- Verifying that Enterprise Vault expands distribution lists
- Installing Discovery Accelerator
- Installing the Discovery Accelerator server software
- Allowing Enterprise Vault to communicate with Discovery Accelerator through the Windows firewall
- Creating the configuration database and customer databases
- Setting up a Custodian Manager website
- Uploading the Discovery Accelerator report templates
- Configuring Discovery Accelerator for use in a SQL Server AlwaysOn environment
- Installing Discovery Accelerator in a clustered environment
- Maximizing security in your Discovery Accelerator databases
- Installing the Discovery Accelerator client software
- Installing the Discovery Accelerator server software
- Appendix A. Ports that Discovery Accelerator uses
- Appendix B. Troubleshooting
- Error messages appear in the event log when upgrading to Discovery Accelerator 12.5
- Enterprise Vault Accelerator Manager service not created
- Enterprise Vault Accelerator Manager service does not start
- "Access is denied" message is displayed when you try to create a customer database on a UAC-enabled computer
- Cannot create or upgrade Discovery Accelerator customer databases when Symantec Endpoint Protection is running
- Permissions error when uninstalling the Discovery Accelerator client from a UAC-enabled computer
- Uninstalling the Discovery Accelerator client from a shared location may prevent other users from starting the client
Using the MSI installer package to install the Discovery Accelerator client
Typically, you distribute the Discovery Accelerator client software by directing users to a central location from which they can run the MSI installer package. By default, the installer package for the Discovery Accelerator client software performs a per-user installation of the software. This type of installation does not permit other users of the computer to run the application. However, if you have administration privileges on the computer and want to permit all users to run the application, you can perform a per-machine installation.
To install the Discovery Accelerator client software
- Ensure that the configuration file
AcceleratorClient.Exe.Configfile is in the installation folder for the Discovery Accelerator client software. - Do one of the following:
To perform a per-user installation, start the Discovery Accelerator installer package (
Veritas Enterprise Vault Discovery Accelerator Client.msi).To perform a per-machine installation, open a Command Prompt window and then type the following:
msiexec /I "path_to/Veritas Enterprise Vault Discovery Accelerator Client.msi" TARGETDIR="install_path" ALLUSERS=1
Where:
path_to
Specifies the path to the
.msifile.install_path
Specifies the path to the folder in which to install the client software.
For example, you might type the following:
msiexec /I "D:\Veritas Enterprise Vault Discovery Accelerator Client.msi" TARGETDIR="C:\Program Files (x86)\" ALLUSERS=1
Caution:
If User Account Control (UAC) is enabled on your computer, you must open the Command Prompt window with administrator privileges.
- Follow the on-screen instructions.
- After you have installed the client software, set the access permissions on the installation folder to prevent unauthorized users from tampering with it - for example, by placing malicious files in the folder. Only authorized users should have Modify and Write permissions on this folder.