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
Migrating existing targets to provisioning groups
SMTP targets that you added in a previous release of Enterprise Vault will continue to work in Enterprise Vault 12.3. In the Administration Console, existing targets are located under > > .
To take advantage of the easier maintenance provided by the SMTP provisioning feature in Enterprise Vault 12.3 and later, you may decide to migrate some or all of your existing targets to SMTP provisioning groups. Before you migrate targets to provisioning groups, read the "Planning your configuration" topic and "Provisioning users for SMTP Group or SMTP Mailbox Journaling" chapter in the Setting up SMTP Archiving guide.
Points to note when you configure the provisioning groups for the target users:
In Enterprise Vault 12.3, you can assign multiple archives to a single SMTP Group Journaling provisioning group.
Only Internet Mail archives are supported in SMTP Mailbox Journaling provisioning groups. If your existing SMTP Mailbox Journaling targets use Exchange Mailbox archives for SMTP messages, these archives are no longer used under provisioning. Instead, provisioning creates new Internet Mail archives for each of these users. If a user already has an Internet Mail archive, then Enterprise Vault links that archive to the SMTP target.
To migrate existing targets to provisioning groups
- Create the required SMTP Group or Mailbox Journaling provisioning groups, and add the target users. Add Active Directory target users by selecting one of the menu options other than Email address.
Use the Email address option to add to the provisioning group the target SMTP address of a user who is not associated with an Active Directory account. For example, you can use this option to add to the group users who are external to your organization.
- Check that the target users are in the correct provisioning groups.
- Check that the provisioning groups are in the required order.
Enterprise Vault processes the groups from the top of the list down. If a user appears in more than one provisioning group, they are only provisioned in the first group in which they appear.
- We strongly recommend that you stop the SMTP Archiving task until the provisioning run below has finished. This ensures that messages that arrive during the period when the original targets are deleted and the users are provisioned are not lost.
- When you have checked that a user in the manual targets is included in a provisioning group, you can delete the manual target. Enterprise Vault does not provision the target user as a member of the group until you delete the existing target under Manual targets.
- Run the SMTP provisioning task, and then check the provisioning task reports.