Search <book_title>...

Enterprise Vault™ PST Migration

Last Published: 2019-10-21

Product(s): Enterprise Vault (12.5)

Migrating PST files in hosted environments

For each mail item that Enterprise Vault archives, it creates an XML document that contains the item's sender information and recipient information. This document is archived with the item, and Enterprise Vault subsequently uses the XML data during indexing.

Enterprise Vault builds the XML data it requires from the sender information and recipient information in each item as it is archived. However, if any of the information is not present in the item, Enterprise Vault attempts to establish a connection to the relevant Exchange server's domain controller to gather the information. This process requires that at least one Exchange server is targeted in your site.

If you migrate PST files in environments where no suitable Exchange server is available to provide the information that Enterprise Vault requires, migration performance can be degraded. For example, this situation can arise in the following circumstances:

You migrate legacy data from the PST files that were created in an old Exchange environment, whose Exchange servers no longer exist.
You migrate data from PST files in a hosted environment that has no Exchange server.

In cases like these, you should set a registry value to bypass the lookup of addresses during archiving.

To bypass Active Directory address lookups

On every Enterprise Vault Storage service computer, create a new DWORD registry value that is called BypassAddressLookups under the following registry key:
```
HKEY_LOCAL_MACHINE
 \SOFTWARE
  \Wow6432Node
   \KVS
    \Enterprise Vault
     \Storage
```
Set BypassAddressLookups to 1.
Restart the Storage service.

This setting allows PST migrations to use only the sender information and recipient information that it finds in each mail item that it archives. Enterprise Vault does not attempt to establish an Active Directory connection to resolve addresses.