Enterprise Vault™ Installing and Configuring
- About this guide
- Section I. Enterprise Vault requirements
- Enterprise Vault hardware requirements
- Hardware requirements for Enterprise Vault server
- About the storage requirements for Enterprise Vault
- Storage for vault stores
- Storage requirements for SQL databases
- Enterprise Vault required software and settings
- Basic software requirements for Enterprise Vault
- Best practice settings for Enterprise Vault servers
- Preinstallation tasks for Enterprise Vault server
- About assigning permissions and roles in SQL databases
- Additional requirements for Operations Manager
- Additional requirements for classification
- Additional requirements for Enterprise Vault Reporting
- Additional requirements for Exchange Server archiving
- Preinstallation tasks for Exchange server archiving
- Assigning Exchange Server permissions to the Vault Service account
- Enterprise Vault client access with Exchange Server archiving
- Additional requirements for Domino Server archiving
- Requirements for Domino mailbox archiving
- Register the Enterprise Vault Domino Gateway
- About the user ID for Domino mailbox archiving
- Requirements for Domino journaling archiving
- Additional requirements for File System Archiving (FSA)
- Additional requirements for SharePoint Server archiving
- Additional requirements for Skype for Business Archiving
- Additional requirements for SMTP Archiving
- Additional requirements for Enterprise Vault Search
- Additional requirements for a standalone Enterprise Vault Administration Console
- Additional requirements for the Archive Discovery Search Service
- Additional requirements for Single Sign-On
- Enterprise Vault hardware requirements
- Section II. Installing Enterprise Vault
- Section III. Configuring Enterprise Vault
- About configuring Enterprise Vault
- Running the Enterprise Vault configuration wizard
- Securing Enterprise Vault Web Access components
- Customizing security for the Web Access components on client computers
- Running the Enterprise Vault Getting Started wizard
- About the express and custom modes of the Enterprise Vault Getting Started wizard
- About indexing configuration with the Enterprise Vault Getting Started wizard
- About storage configuration with the Enterprise Vault Getting Started wizard
- Configuring Enterprise Vault Operations Manager
- Configuring the Archive Discovery Search Service
- Section IV. Initial Enterprise Vault setup
- Initial Enterprise Vault setup
- Setting up storage
- About Enterprise Vault single instance storage
- About creating vault stores
- About Enterprise Vault safety copies
- About Enterprise Vault safety copies
- Creating vault store partitions
- Configuring index locations
- Setting up Index Server groups
- Do I need to create Index Server groups?
- Reviewing the default settings for the site
- Setting up Enterprise Vault Search
- Setting up provisioning groups for Enterprise Vault Search
- Configuring user browsers for Enterprise Vault Search
- Setting up Enterprise Vault Search Mobile edition
- Managing metadata stores
- Section V. Clustering Enterprise Vault with VCS
- Introducing clustering with VCS
- Installing and configuring Storage Foundation HA for Windows
- Configuring the VCS service group for Enterprise Vault
- Running the Enterprise Vault Configuration wizard
- Setting up Enterprise Vault in an active/passive VCS configuration
- About setting up Enterprise Vault in a VCS N+1 configuration
- Implementing an SFW HA-VVR disaster recovery solution with Enterprise Vault
- Troubleshooting clustering with VCS
- Section VI. Clustering Enterprise Vault with Windows Server Failover Clustering
- Introducing clustering with Windows Server Failover Clustering
- Control of Enterprise Vault services in a Windows Server failover cluster
- Preparing to cluster with Windows Server Failover Clustering
- Configuring Enterprise Vault in a Windows Server failover cluster
- Setting up a new Enterprise Vault installation with Windows Server Failover Clustering support
- Examples of Enterprise Vault installations in various Windows Server Failover Clustering modes
- Converting an existing Enterprise Vault installation to a Windows Server failover cluster
- Modifying an existing Enterprise Vault cluster
- Troubleshooting clustering with Windows Server Failover Clustering
- Introducing clustering with Windows Server Failover Clustering
- Appendix A. Automatically preparing an Enterprise Vault server
Default security for the Enterprise Vault Web Access components
The Enterprise Vault Web Access components are configured in the Default Web Site in IIS. By default in a new installation of Enterprise Vault 12.3 or later, Enterprise Vault configures HTTPS on port 443, and enables SSL on each Enterprise Vault virtual directory. If the Default Web Site does not have a valid certificate, the configuration wizard creates and installs a self-signed certificate. Configuration assigns this certificate to the HTTPS binding.
If the Default Web Site already has an HTTPS binding on port 443 using a valid certificate, then the Enterprise Vault configuration wizard just enables SSL on the Enterprise Vault virtual directories.
We strongly recommend that you replace the self-signed certificate as soon as possible with a certificate obtained from a trusted authority. The self-signed certificate is not trusted beyond the Enterprise Vault server. This may prevent some functionality in the Enterprise Vault Outlook Add-In, Enterprise Vault Search, and the Veritas Information Classifier from working, if the clients connect from a remote computer.
If you have upgraded Enterprise Vault from a version that is earlier than 12.3, then the existing configuration of the Default Web Site and Enterprise Vault virtual directories remains unchanged. However, to ensure the security of web connections to Enterprise Vault, we recommend that you manually configure and enable SSL on the Enterprise Vault virtual directories.
You can change the port or protocol that is used to access the Enterprise Vault Web Access components.
See Customizing the port or protocol for the Enterprise Vault Web Access components.
Warning:
If you use HTTP, communication between Enterprise Vault clients and the Enterprise Vault Web Access components is unencrypted, and therefore vulnerable to interception on the network.
Both Basic authentication and Integrated Windows authentication are configured automatically.
The authentication that is automatically set up affects users when they log in, as follows:
A user logging in with a browser that supports Integrated Windows Authentication, such as Internet Explorer, must supply domain name and username separately:
Username: username
Password: password
Domain: domain
This domain can never be defaulted.
An Internet Explorer user with suitably-customized browser settings does not need to supply logon details manually because the logon is automatic; Internet Explorer automatically uses the details of the account to which the user is currently logged on.
A user logging in to the Web Access components with a browser that does not support Integrated Windows Authentication must supply both domain name and username in response to a single username prompt:
Username: domain\username
Password: password
It is possible for you to set up a default domain.
Note:
Enterprise Vault recommends configuring Windows account lockout policies to prevent threats, such as Brute force password attacks, where an attacker can attempt to log on with user accounts using every possible combination of password characters. When the Windows account lockout is configured, Windows locks the user account after a certain number of failed logon attempts for a specified duration.
For details on how to configure Windows account lockout, please refer to your Microsoft Windows documentation.