Please enter search query.
 
              Search <book_title>...
            
 
          Enterprise Vault™ Upgrade Instructions
                Last Published: 
				
                2018-05-21
              
              
                Product(s): 
				
                 Enterprise Vault (12.3)
              
              
            - 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
 
Enterprise Vault 12.3 requires uniform SQL collation
Enterprise Vault 12.3 requires that SQL has a uniform collation across the Master and all the Enterprise Vault databases. An inconsistent collation prevents you from upgrading, so you must ensure there is a uniform collation before you upgrade. For information about how to fix an inconsistent collation, see the following technical note: