Enterprise Vault™ Upgrade Instructions
- About this guide
- Before you begin
- Points to note when upgrading
- Order of upgrade in an environment with Compliance Accelerator or Discovery Accelerator
- Silently installing Enterprise Vault from the command line
- Installing Outlook on the Enterprise Vault server
- Securing Enterprise Vault web applications
- Weak protocols and ciphers are blocked
- Improved consistency when applying a retention period to items
- Classification using Microsoft File Classification Infrastructure on Windows Server 2016
- Data Classification Services does not support all the types of retention categories available in Enterprise Vault 12.3
- eDiscovery Platform compatibility with Enterprise Vault
- Additional points to note when upgrading from Enterprise Vault 11.0 or 11.0.1
- Steps to upgrade your system
- Enterprise Vault server preparation
- Single server: upgrading the Enterprise Vault server software
- Multiple servers: upgrading the Enterprise Vault server software
- Veritas Cluster Server: upgrading the Enterprise Vault server software
- Windows Server Failover Clustering: upgrading the Enterprise Vault server software
- Upgrading standalone Administration Consoles
- Upgrading Enterprise Vault Reporting
- Upgrading MOM and SCOM
- Upgrading Exchange Server forms
- Upgrading Domino mailbox archiving
- About upgrading Domino mailbox archiving
- Domino client version required to run EVInstall.nsf
- Preparing for the upgrade of Domino mailbox archiving
- Upgrading Domino mailbox archiving
- Granting the Domino archiving user access to mail files
- Identifying internal mail recipients
- Run the Domino provisioning task
- Upgrading the FSA Agent
- Compatible versions of the FSA Agent and Enterprise Vault server
- About upgrading the FSA Agent
- Upgrading FSA Agent services that are clustered for high availability
- Upgrading the FSA Agent on a target Windows file server from the Administration Console
- Upgrading the FSA Agent on an FSA Reporting proxy server from the Administration Console
- Upgrading the FSA Agent manually
- Upgrading Enterprise Vault Office Mail App
- Upgrading OWA Extensions
- Upgrading SharePoint Server components
- Upgrading SMTP archiving
- Required and optional tasks when upgrading SMTP Archiving
- Checking the SMTP journaling type configuration
- Checking the permissions of the SMTP Archiving task account
- Checking the 'Journal report processing' advanced SMTP policy setting
- Checking the 'Selective Journal Archiving' site setting
- About upgrading legacy SMTP archiving components
- Migrating existing targets to provisioning groups
- Reconfiguring targets that are configured for target address rewriting to use multiple archives
- Upgrading your Enterprise Vault sites to use Enterprise Vault Search
- About Enterprise Vault Search
- Server requirements for 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
- Upgrading Enterprise Vault API applications
Installing Enterprise Vault Search Mobile edition
Whether you want to install the required components for Enterprise Vault Search Mobile edition on the Enterprise Vault server or on a proxy server, follow the steps below.
To install Enterprise Vault Search Mobile edition
- On the server where you want to install Enterprise Vault Search Mobile edition, log in as the Vault Service account.
- Load the Enterprise Vault installation media.
Do one of the following:
If an AutoPlay dialog box appears, click Run Setup.exe.
If AutoPlay is not enabled, use Windows Explorer to open the root folder of the installation media and then double-click the file
Setup.exe.
- In the left pane of the Veritas Enterprise Vault Install Launcher, click Enterprise Vault.
- Click Server Installation.
- Choose the required installation option.
To install Enterprise Vault Search Mobile edition on a proxy server, choose Installation on an additional server.
- Follow the instructions in the Enterprise Vault installation wizard.
When the wizard prompts you to select the features that you want to install, do one of the following:
For installation on a proxy server, clear all the options except for Search Access Components.
When you click Next, the wizard requests the Vault Site alias. This alias is the DNS alias for the Enterprise Vault site.
For installation on an Enterprise Vault server, choose all the required components.
If you choose to install the Enterprise Vault services, or you have previously installed them on this server, then you cannot clear the Search Access Components option. The components will be automatically installed.
- Follow the on-screen instructions to complete the remaining steps in the installation wizard.
- Ensure the Enterprise Vault Search web application is configured for HTTPS to secure transmitted data.
On the Enterprise Vault server and on the proxy server, the Enterprise Vault Search web application is configured in the Default Web Site in IIS. In a new Enterprise Vault installation of 12.3 or later, Enterprise Vault automatically configures HTTPS on port 443 as default. If SSL is not already configured on the Default Web Site, Enterprise Vault configuration creates and installs a self-signed certificate, and adds an HTTPS binding on port 443 using the certificate. On an Enterprise Vault server, the configuration wizard then enables SSL on all of the Enterprise Vault virtual directories. On a proxy server, the configuration wizard enables SSL on the virtual directory,
EnterpriseVault\Search.We recommend that you replace the self-signed certificate as soon as possible with one obtained from a trusted authority.
If you have already installed a certificate and configured a valid HTTPS binding on port 443, then Enterprise Vault configuration uses the existing binding.
If you are upgrading from a version of Enterprise Vault that is earlier than 12.3, then Enterprise Vault does not change the existing IIS configuration on the Enterprise Vault server or proxy server. If HTTPS is not already configured for Enterprise Vault virtual directories, then you need to do this manually on the Enterprise Vault server and on the proxy server.