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
- 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
- Upgrading the FSA Agent
- Upgrading Enterprise Vault Office Mail App
- 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
- 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 Auditing tab of the of the Enterprise Vault server.
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 theIn 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.