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
Improved consistency when applying a retention period to items
Changes to the Vault Administration Console provide improved consistency and clarity in the way that Enterprise Vault applies a retention period to items. Some of these changes include changes to default behavior.
Table: Changes to Administration Console elements
Administration Console element | Changes made |
|---|---|
Exchange Mailbox Policy dialog box > Existing Items tab (In Enterprise Vault 11.0, this tab was called Moved Items) | This tab has been removed. The settings on the tab related to how retention was assigned to items whose shortcuts were moved from one mailbox folder to another. The settings also applied to existing shortcut items in the mailbox folder. On the Archive Settings tab of the Site Properties dialog box, the Update the category for existing items setting also controlled how retention was assigned to such items. The various setting names and their combined effect caused confusion. In this release, the item movement behavior has been standardized across Enterprise Vault. That is:
|
Site Properties dialog box > Archive Settings tab | The Allow user actions to update categories setting on this tab determines whether, when users perform actions that could potentially update the retention categories of their archived items, Enterprise Vault allows the updates to take place. For example, users may move archived items between folders to which you have applied different retention categories, or change the retention categories of items in Enterprise Vault Search, if permitted. Both actions can cause the retention categories of the items to change. The following options now let you control when Enterprise Vault updates the retention category of such items:
|
Classification Policy Properties dialog box > Settings tab | This tab now provides an option, , with which you can block unwanted changes to the retention categories that the Enterprise Vault classification feature has assigned to archived items. For example, users can potentially update the retention categories by moving the items from one folder to another. You can choose to block retention category updates in all instances or, if you use the Enterprise Vault records management feature, you can allow them in instances where this also causes the record types of the items to change. |
Retention Category Properties dialog box > Details tab (In Enterprise Vault 12.1 and earlier, this tab was called General) | The following options are available on this tab:
Consider the following situation:
In previous releases, Enterprise Vault did not update the category in this situation. This behavior has now changed. Enterprise Vault updates the item category, subject to site and classification policy settings for allowing user actions to update categories on items. In this example, updating the category means that the hold on automatic deletion on expiry is removed. Similarly, a user action may cause a change of retention category from one that specifies a hold on user deletion to one that does not. This can lead to the removal of the hold on user deletion. |
Search Policy Properties dialog box > Features tab | This tab now contains an option, Allow Retention Category to be changed, with which you can allow Enterprise Vault Search users to change the retention categories of the items in their archives. By default, this option is turned off. This setting is subject to the site and classification policy settings that are described above. |
For an overview of retention in Enterprise Vault 12.3, see the technical note Managing Retention.