Enterprise Vault™ Upgrade Instructions
- About this guide
- Before you begin
- Points to note when upgrading
- Installing Outlook on the Enterprise Vault server
- Improved consistency when applying a retention period to items
- Additional points to note when upgrading from Enterprise Vault 11.0 or 11.0.1
- Steps to upgrade your system
- Enterprise Vault server preparation
- Backing up the system
- 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
- Upgrading the FSA Agent
- Upgrading Enterprise Vault Office Mail App
- Upgrading OWA Extensions
- Upgrading SharePoint Server components
- Upgrading SMTP archiving
- Checking the SMTP journaling type configuration
- Upgrading your Enterprise Vault sites to use 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
- Carrying out preinstallation tasks for 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
Outlook version on Enterprise Vault server
Outlook 2013 SP1
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:
Disabling MAPI over HTTP causes Enterprise Vault to revert to an Outlook Anywhere connection to Exchange.
Exchange Server 2013/2016 with Outlook Anywhere enabled
Exchange Server 2010 with RPC over HTTP enabled
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.