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
- 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
- Upgrading Enterprise Vault API applications
Upgrading any applications that use the Enterprise Vault API Runtime
You may have installed a third-party application that uses the Enterprise Vault API to archive proprietary data or filter the data that Enterprise Vault stores. After upgrading Enterprise Vault, you may need to perform the following additional tasks to upgrade these applications:
If the application uses the Enterprise Vault API Runtime, you need to update the API Runtime on each computer that hosts the application.
For a .NET application that uses a specific version of the Enterprise Vault API Runtime, you need to update the binding redirections in the application's configuration file.
For instructions on how to update the binding redirections, see the document
ReadMeFirst_en.htm
. The document is located with the API Runtime kit in theAPI Runtime
folder on the Enterprise Vault media.