Enterprise Vault™ Compliance Accelerator Installation Guide
- Introducing Compliance Accelerator
- Preparing to install Compliance Accelerator
- Configuration options for Compliance Accelerator
- Supported versions of Enterprise Vault in Compliance Accelerator environments
- Prerequisites for Compliance 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 Compliance Accelerator environment
- Disabling the Windows Search Service on the Compliance Accelerator server
- Ensuring that the Windows Server service is running on the Compliance 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 Compliance Accelerator
- Installing the Compliance Accelerator server software
- Allowing Enterprise Vault to communicate with Compliance Accelerator through the Windows firewall
- Creating the configuration database and customer databases
- Uploading the Compliance Accelerator report templates
- Configuring Compliance Accelerator for use in a SQL Server Always On environment
- Installing Compliance Accelerator in a clustered environment
- Maximizing security in your Compliance Accelerator databases
- Installing the Compliance Accelerator client software
- Uninstalling Compliance Accelerator
- Installing the Compliance Accelerator server software
- Appendix A. Ports that Compliance Accelerator uses
- Appendix B. Troubleshooting
- Error messages appear in the event log when upgrading to Compliance Accelerator 14.1
- 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 Compliance Accelerator customer databases when Symantec Endpoint Protection is running
- Permissions error when uninstalling the Compliance Accelerator client from a UAC-enabled computer
- Uninstalling the Compliance Accelerator client from a shared location may prevent other users from starting the client
Changing the ports that Compliance Accelerator uses
You can set Compliance Accelerator to use different ports if another application requires the default ones.
To change the port used for communications with SQL Server, if you do not use SQL Always On
- On the Compliance Accelerator server, open the Accelerator Manager website.
- In the left pane, right-click the server name and then click Properties.
- In the Name field, specify the required SQL Server computer as server_name,port_number.
- Click OK to save the change that you have made.
For each customer database, do the following:
In the left pane, right-click the name of the database and then click Properties.
In the SQL Server field, specify the required SQL Server computer as server_name,port_number.
Click OK to save the change that you have made.
To change the port used for communications with SQL Server, if you do use SQL Always On
- If the Enterprise Vault Accelerator Manager service is running on the Compliance Accelerator server, stop it.
- Open the Accelerator Manager website and wait for the following page to appear (this may take several minutes):
- In the SQL Server field, enter the required details and then click Update Configuration. For example, in the figure above, this field specifies an availability group listener (SQL-L), which is followed by a comma and then the port number 5053.
- Start the Enterprise Vault Accelerator Manager service.
To change the port used for communications between the Compliance Accelerator server and the Compliance Accelerator websites
- On the Compliance Accelerator server, locate the copies of the
Web.configfile in theAcceleratorAdminWebandComplianceWebMinsubfolders of the Compliance Accelerator installation folder. (TheComplianceWebMinsubfolder is only present if you have chosen to install the Compliance Accelerator website.) - Open each file in a text editor such as Windows Notepad.
- Find the following line, and change the port number to a suitable alternative.
<add key="RemotePort" value="8085"/>
- Save and close the files.
- Restart the Enterprise Vault Accelerator Manager service.
To change the port used for communications between the Compliance Accelerator server and the Compliance Accelerator clients
- On each Compliance Accelerator client computer, locate the
AcceleratorClient.Exe.Configfile in the installation folder.This folder is typically
%HOMEPATH%\Local Settings\Application Data\Enterprise Vault Compliance Accelerator\Client. - Open the file in a text editor such as Windows Notepad.
- Find the following line, and change the port number to a suitable alternative.
<add key="AcceleratorServerPort" value="8086" />
- Save and close the file.
- If you need to change port 8086 to another port and you want to use Open Data (OData) web service to create reports, make sure that you update the OData configuration to use the same port. To update the port number, do the following:
On each Compliance Accelerator server computer, locate the
AcceleratorService.Exe.ConfigandAcceleratorManager.Exe.Configfiles in the installation folder.Open each file in a text editor such as Windows Notepad.
Find the following lines, and change the port number to match the setting in the AcceleratorClient.Exe.Config file.
<add key="Windows Client Remoting Channel Configuration" value="8086" /> <add key="Windows Client Remoting Channel Configuration IPv6" value="8086" />
Save and close the file.
To change the port used for communications with the SQL reporting server
- On the Compliance Accelerator server, open the Accelerator Manager website.
- Click Reporting Server at the bottom of the page.
The Uploading Reporting Server Templates page appears.
- In the Reporting Server URL field, type the URL with which to access the SQL reporting server in the following form:
http://server_name,port_number/virtual_directory