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
- Configuring Intelligent Review API Authentication and Authorization
- 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 a dedicated server for Intelligent Review processing (optional deployment configuration)
- 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.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 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
- Error messages when the Intelligent Review (IR) API authentication and authorization fails
- Appendix C. Installing and configuring the Enhanced Auditing feature
- Overview
- Prerequisites for the Enhanced Auditing feature
- Installing the Enhanced Auditing feature
- Post installation steps
- Upgrading the Enhanced Auditing setup
- Modifying the Enhanced Auditing setup
- Repairing the Enhanced Auditing setup
- Uninstalling the Enhanced Auditing setup
- Managing access from Veritas Surveillance
Security requirements for temporary folders
Note:
The following article on the Veritas Support website provides comprehensive information on the security requirements:
On both Compliance Accelerator server and client computers, Compliance Accelerator makes occasional use of various folders for temporary storage. To protect against unauthorized access to these folders, which can contain sensitive data, Compliance Accelerator checks access to them on startup and periodically thereafter. If the security check fails on the Compliance Accelerator server, the Enterprise Vault Accelerator Manager service stops and an error event is recorded in the Veritas Enterprise Vault event log. If the security check fails on a Compliance Accelerator client computer, the user must choose to rerun the check or close the client.
On client computers, Compliance Accelerator checks the security of the temporary folder that belongs to the user who is running the client.
In both cases, Compliance Accelerator considers the following to be authorized users:
Members of the Built-in groups Administrators, Backup Operators, Domain Administrators, and System Operators
The user to whom the temporary folder belongs
The Local System account