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
- Automatic migration of NetApp C-Mode connection settings
- Enterprise Vault auditing configuration
- 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.4
- 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 'Journal Reports settings' 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
Identifying internal mail recipients
You can specify that Enterprise Vault must perform a local address lookup for specific Notes domains. The local lookup enables Enterprise Vault to identify the Notes user name for messages that are addressed to alternate email addresses. The local lookup results can aid searching in the web applications and in Compliance Accelerator and Discovery Accelerator.
In order to specify the domains that require local address lookup, you must make some changes to the registry on the Enterprise Vault servers that run the journaling and archiving tasks.
To specify local lookup domains
- On an Enterprise Vault server that runs a Domino archiving or journaling task, create a new registry key named NotesDomains in the following location:
HKEY_LOCAL_MACHINE \SOFTWARE \Wow6432Node \KVS \Enterprise Vault \Agents - Under the new NotesDomains key, create a subkey for each Notes domain. For example, if you have Notes domains 'MyNotesDomain1' and 'MyNotesDomain2' you create subkeys 'MyNotesDomain1' and 'MyNotesDomain2'.
- Under each of the Notes domain subkeys, create a new String value named InternalSMTPDomains.
- Assign to each InternalSMTPDomains value a string that lists the domains for which you want to use local lookup. Use semi-colons (;) to separate domains. For example:
exampledomain1.com;exampledomain2.com
- Under each of the Notes domain subkeys, create a new DWORD value called EnableLocalPartLookup.
- Give EnableLocalPartLookup one of the following values:
0 to disable local part lookup
1 to enable local part lookup
- Repeat all these steps for other Enterprise Vault servers that run Domino archiving or journaling tasks.
Table: Effects of NotesDomains registry key shows how the NotesDomains registry key controls how Enterprise Vault identifies internal mail recipients.
Table: Effects of NotesDomains registry key
Registry key or value | Effect on Enterprise Vault behavior |
|---|---|
NotesDomains key is missing | Full address lookup and a warning in the event log. |
NotesDomains key is present but has no key for the current Notes domain | Original address is recorded. No lookup. |
NotesDomains key is present and has a key for the current Notes domain |
|