Arctera Enterprise Vault™ eDiscovery Installation Guide
- Introducing eDiscovery
- Preparing to install eDiscovery
- Configuration options for eDiscovery
- Supported versions of Enterprise Vault in eDiscovery environments
- Prerequisites for Arctera eDiscovery
- 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 eDiscovery environment
- Disabling the Windows Search Service on the eDiscovery server
- Ensuring that the Windows Server service is running on the eDiscovery 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 eDiscovery
- Installing the eDiscovery server software
- Allowing Enterprise Vault to communicate with eDiscovery through the Windows firewall
- Creating the configuration database and customer databases
- Setting up a Insight eDiscovery Custodian Manager website
- Uploading the eDiscovery report templates
- Configuring eDiscovery for use in a SQL Server Always On environment
- Installing eDiscovery in a clustered environment
- Maximizing security in your eDiscovery databases
- Installing the eDiscovery client
- Installing the eDiscovery server software
- Appendix A. Ports that eDiscovery uses
- Appendix B. Troubleshooting
- Error messages appear in the event log when upgrading to eDiscovery 15.2
- Enterprise Vault eDiscovery Manager service not created
- Enterprise Vault eDiscovery 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 eDiscovery customer databases when Symantec Endpoint Protection is running
- Permissions error when uninstalling the eDiscovery client from a UAC-enabled computer
- Uninstalling the eDiscovery client from a shared location may prevent other users from starting the client
- 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 eDiscovery
Configuring Outlook to enable the processing of items with many attachments or many recipients
You must install a supported version of Outlook on the eDiscovery server so that application users can export Exchange Server items in PST format and download the original versions of the items.
By default, Outlook does not allow any items that have more than 2048 attachments or 2048 recipients to be opened. To avoid problems when application users try to export or download any items that have a larger number of attachments or recipients, set the registry values AttachmentMax and RecipientMax on the eDiscovery server.
To configure Outlook to enable the processing of items with many attachments or many recipients
- On the eDiscovery server, start the Registry Editor.
- Where version is 16.0 for Outlook 2016, 19.0 for Outlook 2019, and 22.0 for Outlook 2022.
Do one of the following:
If you do not use policies, locate and then click the following registry subkey:
HKEY_CURRENT_USER\Software\Microsoft\Office\version\Outlook\Options\Mail
If you use policies, locate and then click the following registry subkey:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\version\Outlook\Options\Mail
- On the Edit menu, point to New, and then click DWORD Value.
- Type AttachmentMax, and then press Enter.
- Right-click AttachmentMax, and then click Modify.
- In the Value data box, type the required value, and then click OK.
The recommended value is FFFFFFFF in hexadecimal.
- Repeat steps 3 through 6 to add the RecipientMax registry entry.
- Exit the Registry Editor.
More Information