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
Customizing the port or protocol for the Enterprise Vault Web Access components
You can change the port or protocol that is used to access the Enterprise Vault Web Access components. If you change the protocol, you will need to make changes to the configuration of the Default Web Site in IIS.
If you change the port after items have been archived, existing shortcuts will no longer work. Shortcuts in Outlook and Notes can be updated with the new protocol or port information using Synchronize mailboxes in the Enterprise Vault Administration Console, but customized shortcuts, FSA shortcuts and SharePoint shortcuts cannot be updated.
Before you change the Web Access port or protocol in Enterprise Vault, you must first make the required changes to the Default Web Site in IIS for each server in the Enterprise Vault site. Bear in mind that changing the protocol or port for the Default Web Site will affect all virtual directories in the website, including the FSAReporting virtual directory.
See “To create a certificate request, and implement SSL in IIS”.
When you have made the necessary changes in IIS, change the Web Access port or protocol settings on the
tab of the Site properties in the Administration Console.If the Enterprise Vault site uses FSA Reporting, you must then perform some additional steps. Otherwise the status of FSA Reporting is shown as Off in the Administration Console. Perform the following steps on each Enterprise Vault server and on each file server in the Site.
See “Additional steps for FSA Reporting after you change the port or protocol”.
To create a certificate request, and implement SSL in IIS
- Create and submit an SSL certificate request to a trusted certificate authority. Your certificate must include both the short names and fully qualified domain names of the Vault Site alias (that is, the DNS alias for the Enterprise Vault site). For example, EVServer1 and EVServer1.domain.com.
You can use any suitable tool to request the certificate. For example, you can use OpenSSL, which is installed in the Enterprise Vault installation folder. How to create a certificate request using Microsoft Management Console (MMC) is described in the document, https://www.veritas.com/docs/100038186.
- On the Enterprise Vault server, perform the following steps in IIS Manager:
Use the Server Certificates feature to install the new certificate.
In the site bindings for the Default Web Site, add a binding for the HTTPS protocol and link it to the new certificate.
In the SSL Settings pane for each Enterprise Vault virtual directory, select Require SSL.
These tasks are also described in the document, https://www.veritas.com/docs/100038186.
Additional steps for FSA Reporting after you change the port or protocol
- Log on as the FSA Reporting user. The FSA Reporting user is the Windows user account that you specified for FSA Reporting to use when you ran the FSA Reporting Configuration wizard.
- Open Internet Explorer and select Tools > Internet Options.
- If you chose to use an SSL port, click the Advanced tab and under Security make sure that Check for server certificate revocation is not selected.
- Click the Security tab and select the Local intranet zone. Then click Custom Level to display the Security Settings. Under User Authentication, make sure that Prompt for user name and password is not selected.
- Repeat steps 1 to 4 on each Enterprise Vault server and on each file server in the Site.