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
- Requirements for RPC over HTTP
- 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
- 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
- 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
- Adding 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
Troubleshooting default SSL configuration issues
If the Enterprise Vault configuration wizard cannot create a self-signed certificate, or configure certificate and HTTPS bindings in IIS, then configuration reports an error in the Enterprise Vault event log. For example:
Failed to create HTTPS binding in IIS. Reason: Could not create self-signed certificate "Enterprise Vault" in IIS on this server. ...
The Enterprise Vault configuration wizard invokes the utility, HTTPSBindingAndCertificateProvider.exe
, to create the certificate and HTTPS binding, and enable SSL on the Enterprise Vault virtual directories. If an error is reported in the event log, you can take the following action:
Look for exceptions in the log file that is created by
HTTPSBindingAndCertificateProvider.exe
. The path for the log file is<%Temp%> \EVHTTPSBindingConfiguration.log
If the errors are transient, you can rerun the utility manually, as described in the following procedure.
To run HTTPSBindingAndCertificateProvider.exe manually
- Open a command prompt window, and navigate to the Enterprise Vault installation folder. This is typically
C:\Program Files (x86)\Enterprise Vault
. - Enter the following command line:
HTTPSBindingAndCertificateProvider createcertificateandbinding EVServerAlias enableSSLFlag SSLport
where
EVServerAlias is the fully qualified DNS alias that you configured for the Enterprise Vault server; that is, the fully qualified vault site alias.
enableSSLFlag is a numeric flag to enable or disable SSL on the Enterprise Vault virtual directories. Enter 1 to enable SSL, or 0 (zero) to disable SSL.
SSLport This parameter is optional. By default, port 443 is used for SSL bindings. Use this parameter to specify a different port.
Below is an example command line:
HTTPSBindingAndCertificateProvider createcertificateandbinding test.domain.com 1
This example command does the following in IIS:
Creates a self-signed certificate for the Enterprise Vault server that has the DNS alias, test.domain.com. The certificate is called "Enterprise Vault", and is stored in the Personal Certificate Store in IIS.
On the Default Web Site, creates an HTTPS binding on port 443, if this binding does not already exist.
Enables SSL on all of the Enterprise Vault virtual directories.
- When the command, HTTPSBindingAndCertificateProvider, has completed successfully, change the web access application port and protocol in the Enterprise Vault Administration Console.
To do this, open site properties in the Enterprise Vault Administration Console, and click the General tab.
- Select Use HTTPS on SSL Port:. If you are not using HTTPS port 443, change the SSL port number to the one you specified in the HTTPSBindingAndCertificateProvider command line.
- Click OK to close the properties window. The changes will take affect during the next archiving run.