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
- Automatic migration of NetApp C-Mode connection settings
- Enterprise Vault auditing configuration
- Amazon Simple Storage Service (S3) partition
- Classification using Microsoft File Classification Infrastructure on Windows Server 2016 and 2019
- Data Classification Services does not support all the types of retention categories available in Enterprise Vault 14.1
- eDiscovery Platform compatibility with Enterprise Vault
- 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 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 'Journal Reports settings' 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
- Granting the Administrators group and system account full access to the SMTP holding folder
- 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
Enterprise Vault auditing configuration
In Enterprise Vault 12.3 and earlier releases, you could configure auditing settings only at the server-level. Enterprise Vault 12.4 onwards, you can configure auditing at the site-level. The option in the Enterprise Vault servers container in the Administration Console lets you enable and configure auditing for all the available Enterprise Vault servers in the site. Note that the option to enable auditing is no longer available from the Auditing tab of the of the Enterprise Vault server.
In Enterprise Vault 12.3 and earlier, the auditing configuration was stored as registry settings under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\KVS\Enterprise Vault\Admin\Auditing on each server. During the upgrade to Enterprise Vault 12.4 or later, these settings are migrated from each server's registry to the Enterprise Vault Directory database. After the successful migration of the settings, these registry keys are no longer available.
Note that auditing category settings are stored at the server-level whereas connection pool size settings are available at the site-level only. You can no longer configure separate connection pool sizes at the server-level. If you previously configured different connection pool sizes for each server, then the upgrade process stores the minimum configured value as the default connection pool size at the site-level, which applies to all the servers in the site. For example, if the Indexing service connection pool size for EVServer1 was 6, and the Indexing service connection pool size for EVServer2 was 3, then the upgrade process chooses 3 as the default Indexing service connection pool size. Additionally, if you had turned on connection information logging for any of the servers, then the option is enabled for all the servers in the site.