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
- Classification using Microsoft File Classification Infrastructure on Windows Server 2016
- Data Classification Services does not support all the types of retention categories available in Enterprise Vault 12.3
- eDiscovery Platform compatibility with Enterprise Vault
- 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
- 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 OWA Extensions
- 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 '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
- 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
About upgrading the FSA Agent
We recommend that you upgrade the FSA Agent on the Windows computers on which it is installed. Support is provided for backward compatibility, but new features may not be available until the FSA Agent version is aligned with the Enterprise Vault server version.
Note the following:
Do not install the FSA Agent on Enterprise Vault servers. Enterprise Vault servers do not require the FSA Agent.
As part of the upgrade process, you are prompted for a compulsory restart of the file server.
Enterprise Vault 12.3 does not support File Blocking. If you are upgrading from Enterprise Vault 12.1 or earlier, the upgrade process removes the Enterprise Vault File Blocking service from the file server.
FSA Agent installation requires an up-to-date root certificate on the target computer. Certificate updates usually happen automatically over the Internet. If the certificate is out-of-date, for example because the computer has no Internet connection, the FSA Agent installation fails with a "Signature verification failed" error in the FSA Agent installation log. For more details and for instructions on how to update the root certificate, see the following technical note on the Veritas Support website:
https://www.veritas.com/docs/100023437
You can upgrade the FSA Agent from an Enterprise Vault Administration Console, or by installing the files manually on the file server.
To install or upgrade the FSA Agent you must use an account that is a member of the local Administrators group on the file server.
If you upgrade the FSA Agent from the Administration Console then if the file server's firewall is enabled it must be suitably configured. Otherwise the Administration Console wizard fails with the message "Error: The RPC server is unavailable". See the following technical note on the Veritas Support website:
https://www.veritas.com/docs/100022335
Table: Upgrading the FSA Agent describes the options for upgrading the FSA Agent.
Table: Upgrading the FSA Agent
To do this | See this section |
|---|---|
Upgrade FSA Agent services that are clustered for high availability. | See Upgrading FSA Agent services that are clustered for high availability. |
Upgrade the FSA Agent on target Windows file servers from the Administration Console. | See Upgrading the FSA Agent on a target Windows file server from the Administration Console. |
Upgrade the FSA Agent on FSA Reporting proxy servers from the Administration Console. | See Upgrading the FSA Agent on an FSA Reporting proxy server from the Administration Console. |
Upgrade the FSA Agent manually. |