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 Outlook on the Enterprise Vault server
To support Exchange Server archiving, you must install Outlook on the Enterprise Vault server. Enterprise Vault currently supports the following versions of Outlook for this purpose:
Outlook 2013 SP1, 32-bit version.
Outlook 2016, 32-bit version. You need build version 16.0.4534.1001 or later.
In each case, Enterprise Vault supports the Windows Installer (MSI) version of 32-bit Outlook, which is available with the volume license. It does not support the Click-to-Run and 64-bit versions. For the latest information on supported versions of Outlook, see the Compatibility Charts.
Outlook must be the default email client on the Enterprise Vault server. When the Enterprise Vault Admin service starts, it checks that Outlook is configured as the default client and, if it is not, configures it as such.
Install a version of Outlook to suit the transport protocol that you have enabled in Exchange: MAPI over HTTP or Outlook Anywhere (formerly "RPC over HTTP").
Table: Exchange transport protocols and required version of Outlook
Exchange version | Outlook version on Enterprise Vault server | |
|---|---|---|
Outlook 2013 SP1 | Outlook 2016 | |
Exchange Server 2013/2016 with MAPI over HTTP enabled | MAPI over HTTP connections from Enterprise Vault client computers to Exchange are supported, but not those from the Enterprise Vault server itself. Disable MAPI over HTTP on the server by following the instructions here: https://www.veritas.com/docs/100040583 Disabling MAPI over HTTP causes Enterprise Vault to revert to an Outlook Anywhere connection to Exchange. | Supported |
Exchange Server 2013/2016 with Outlook Anywhere enabled | Supported | Not supported |
Exchange Server 2010 with RPC over HTTP enabled | Supported | Not supported |
By installing Outlook 2013 SP1 on the Enterprise Vault server, you also provide support for archiving from Exchange public folders. Outlook 2016 is not currently supported for this purpose.