Enterprise Vault™ Upgrade Instructions
- About this guide
- Before you begin
- Points to note when upgrading
- Installing Outlook on the Enterprise Vault server
- Improved consistency when applying a retention period to items
- Additional points to note when upgrading from Enterprise Vault 11.0 or 11.0.1
- Steps to upgrade your system
- Enterprise Vault server preparation
- Backing up the system
- 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
- Upgrading the FSA Agent
- Upgrading Enterprise Vault Office Mail App
- Upgrading OWA Extensions
- Upgrading SharePoint Server components
- Upgrading SMTP archiving
- Checking the SMTP journaling type configuration
- Upgrading your Enterprise Vault sites to use Enterprise Vault Search
- Setting up provisioning groups for Enterprise Vault Search
- Configuring user browsers for Enterprise Vault Search
- Setting up Enterprise Vault Search Mobile edition
- Carrying out preinstallation tasks for 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:
- 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