Enterprise Vault™ Installing and Configuring
- About this guide
- Section I. Enterprise Vault requirements
- Enterprise Vault hardware requirements
- Hardware requirements for Enterprise Vault server
- Hardware requirements for SQL Server
- Network requirements for Enterprise Vault
- About the storage requirements for Enterprise Vault
- Storage for vault stores
- Storage for Enterprise Vault indexes
- Storage for Enterprise Vault index snapshot location
- Storage requirements for SQL databases
- Storage requirements for the Enterprise Vault cache folder
- Local storage requirements for temporary files
- TEMP folder security requirements
- Granting additional users and groups access to the TEMP folder
- Enterprise Vault required software and settings
- About the Enterprise Vault required software and settings
- About valid computer names for Enterprise Vault servers
- About the Enterprise Vault Deployment Scanner
- Basic software requirements for Enterprise Vault
- Best practice settings for Enterprise Vault servers
- Message queue cleanup interval: MessageCleanupInterval
- Message queue message storage limit: MachineQuota
- Disable opportunistic locking: OplocksDisabled
- Disable loopback check: DisableLoopbackCheck
- Disable strict name checking: DisableStrictNameChecking
- Maximum Outlook attachments and recipients: AttachmentMax and RecipientMax
- TCP/IP maximum ports and TCP timed wait delay
- Preinstallation tasks for Enterprise Vault server
- Creating the Vault Service account
- Creating a SQL login account
- About assigning permissions and roles in SQL databases
- Assigning the required SQL Server roles and permissions to an Active Directory group
- Locking down Enterprise Vault SQL databases
- Creating Enterprise Vault DNS aliases
- Turning off or reconfiguring Windows Firewall
- Securing data locations
- About User Account Control (UAC)
- Additional requirements for Operations Manager
- Additional requirements for classification
- Additional requirements for Enterprise Vault Reporting
- Additional requirements for Exchange Server archiving
- About Exchange Server archiving
- Preinstallation tasks for Exchange server archiving
- Installing Outlook on the Enterprise Vault server
- Creating the Enterprise Vault system mailbox
- Removing the restriction on NSPI connections to a Windows Server domain controller
- Creating a user profile on the Enterprise Vault server
- Creating a mailbox for the Vault Service account
- Configuring the Exchange throttling policy on the Vault Service account
- Granting the Vault Service account Send As permission on the system mailboxes
- Assigning Exchange Server permissions to the Vault Service account
- Enterprise Vault client access with Exchange Server archiving
- Additional requirements for Domino Server archiving
- Domino Server archiving requirements for all Enterprise Vault servers
- Requirements for Domino mailbox archiving
- Required software for Enterprise Vault Domino Gateway
- Required software for target Domino mail servers
- Requirements for Enterprise Vault extensions for Notes clients
- Preinstallation tasks for Domino mailbox archiving
- Register the Enterprise Vault Domino Gateway
- Configuring the Internet port on the Enterprise Vault Domino Gateway
- Configuring server security for the Enterprise Vault Domino Gateway
- Configuring Single Sign-On on the Enterprise Vault Domino Gateway
- Configuring Time-based One-Time Password on the Enterprise Vault Domino Gateway
- Clustering Enterprise Vault Domino Gateway servers
- Configuring an alias URL for web connections to the Enterprise Vault Domino Gateway server
- About the user ID for Domino mailbox archiving
- Configuring the server document for each target Domino mail server
- Install and configure Enterprise Vault Domino Gateway
- 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
- Default security for the Enterprise Vault Web Access components
- Customizing the port or protocol for the Enterprise Vault Web Access components
- Customizing authentication for the Enterprise Vault Web Access components
- Customizing security for the Web Access components on client computers
- Encrypting session cookies
- Running the Enterprise Vault Getting Started wizard
- What the Enterprise Vault Getting Started wizard does
- Preparing to run the Enterprise Vault Getting Started wizard
- 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
- About policy definition with the Enterprise Vault Getting Started wizard
- About Exchange target configuration with the Enterprise Vault Getting Started wizard
- About Domino target configuration with the Enterprise Vault Getting Started wizard
- About file target configuration with the Enterprise Vault Getting Started wizard
- Planning for 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 setting up storage for Enterprise Vault archives
- About Enterprise Vault single instance storage
- About sharing levels and sharing boundaries
- How Enterprise Vault single instance storage works
- About the fingerprint database
- Deletion of SIS parts
- Requirements for Enterprise Vault single instance storage
- About Centera device-level sharing
- About sharing partitions on storage devices that support the Enterprise Vault storage streamer API
- Developing a suitable sharing regime for Enterprise Vault single instance storage
- Creating vault store groups
- About creating vault stores
- About Enterprise Vault safety copies
- Choosing when to remove Enterprise Vault safety copies
- Checking that the partition has been backed up before Enterprise Vault removes safety copies
- Using the archive attribute to determine whether a partition has been backed up
- Using the trigger file mechanism to determine whether a partition has been backed up
- Creating a vault store
- About Enterprise Vault safety copies
- Creating vault store partitions
- Configuring sharing for a vault store group
- Configuring index locations
- Setting up Index Server groups
- About Index Server groups
- Do I need to create Index Server groups?
- Do you have more than one Enterprise Vault server?
- Do you use or plan to use journal archiving or File System Archiving?
- Do you use or plan to use Compliance Accelerator or Discovery Accelerator?
- Is the server loading evenly distributed across existing Enterprise Vault servers?
- Are there more than approximately 5,000 mailbox archives per Enterprise Vault server?
- Creating an Index Server group
- Adding an Index Server to an Index Server group
- Removing an Index Server from an Index Server group
- Assigning a vault store to an Index Server group
- Unassigning a vault store from an Index Server group
- Assigning a vault store to a different indexer
- Reviewing the default settings for the site
- Setting up Enterprise Vault Search
- About Enterprise Vault Search
- Defining search policies for Enterprise Vault Search
- Allowing privileged Enterprise Vault Search users to restore items to other users' mailboxes
- Setting up provisioning groups for Enterprise Vault Search
- Creating and configuring Client Access Provisioning tasks for Enterprise Vault Search
- Configuring user browsers for Enterprise Vault Search
- Configuring Enterprise Vault Search for use in Forefront TMG and similar environments
- 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
- Before you run 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
- About installing and configuring SFW HA-VVR with Enterprise Vault
- Overview of the steps for installing and configuring SFW HA-VVR
- Setting up the VCS cluster on the primary site
- Setting up the VCS cluster on the secondary site
- Adding the VVR components for replication
- Adding the GCO components for wide-area recovery
- Troubleshooting clustering with VCS
- Section VI. Clustering Enterprise Vault with Windows Server Failover Clustering
- Introducing clustering with Windows Server Failover Clustering
- About clustering Enterprise Vault with Windows Server Failover Clustering
- Supported Windows Server Failover Clustering configurations
- Required software and restrictions on clustering Enterprise Vault with Windows Server Failover Clustering
- Typical Enterprise Vault configuration in a Windows Server failover cluster
- 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
- About configuring Enterprise Vault in a Windows Server failover cluster
- Setting up a new Enterprise Vault installation with Windows Server Failover Clustering support
- Configuring a new Enterprise Vault server with Windows Server Failover Clustering support
- Configuring a failover node in a Windows Server failover cluster
- Troubleshooting configuration of the Enterprise Vault Monitoring database
- 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
- About this chapter
- Enterprise Vault event messages and the failover cluster log
- Resource ownership and dependencies when configuring Enterprise Vault in a failover clustered environment
- Registry replication on failover clustered nodes
- Viewing the clustered message queues for an Enterprise Vault cluster server
- Starting and stopping Enterprise Vault services in a Windows Server Failover Clustering environment
- Potential failover issue in a Windows Server cluster
- 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.