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
Checking the permissions of the SMTP Archiving task account
Adjustments have been made to the permissions that are required to run the SMTP Archiving task. The advice in this section only applies if your configuration fulfils the following criteria:
The SMTP Archiving task runs under an account other that the Vault Service account
Your environment contains Enterprise Vault storage servers that do not host an SMTP Archiving task
After you have upgraded Enterprise Vault, check the members of the local Administrators group on any Enterprise Vault storage servers that do not host an SMTP Archiving task. If the group includes the SMTP Archiving task account, then we recommend that you remove it from the group if there is no other reason for the account having this permission. Obviously you should not remove the account from the group if, for example, another Enterprise Vault task on that server is configured to run under the account.