Enterprise Vault™ PST Migration
- About this guide
- Introduction to PST migration
- PST file ownership
- PST migration: scripted
- Output from PST migration
- PST migration: wizard-assisted
- PST migration: Locate and Migrate
- Setting up PST Locate and Migrate
- Configuring the holding folder for PST Locate and Migrate
- Creating and configuring the PST Locator, PST Collector, and PST Migrator tasks
- Migrating PST files using PST Locate and Migrate
- Running the PST Locator task to find domains and computers
- Running the PST Locator task to find PST files
- PowerShell cmdlets for PST migration
- PST migration: client-driven migration
- About client-driven PST migration
- Enabling mailboxes for PST client-driven migration
Migration tips for the wizard-assisted PST migration process
Migrate a few PST files and then, when you are familiar with the process, increase the numbers.
Migration is much easier if you have PST files in just a few locations, rather than in many.
Sort out the permissions on the PST files before running PST Migrator, otherwise they will just fail.
There is a Windows server command-line utility, CACLS, which you can use to grant the Vault Service account Full Control access to the PST files.
You can run more than one instance of PST Migrator. There is no point in running more instances than you have processors. For example, if you have two processors, then do not run more than two instances of PST Migrator. If the computer is also archiving at the same time, then reduce the number of PST Migrator instances.
When Enterprise Vault archives items, it also converts the contents to HTML and indexes them. There is a default conversion timeout of 10 minutes for this process. Enterprise Vault makes three attempts to convert an item, so can take up to 30 minutes before failing an item and moving on to the next one.
If there are very large, or very complex, items in a PST file, it can take a long time to migrate them all. If you do not need the content of the items to be indexed, then you can improve performance by lowering the conversion timeout to just a few minutes.
This change to the conversion timeout also affects normal archiving, so remember to return it to the original value when you have migrated the PST files.
To change the conversion timeout, perform the following steps in the order listed:
On the Storage service computer, set the following string registry value to the timeout, in minutes, that you want to use:
HKEY_LOCAL_MACHINE \Software \Wow6432Node \KVS \Enterprise Vault \ConversionTimeout
Restart the Storage service.
If you have PST files in the same location that you want to go to different vault stores, the quickest way to do this is as follows:
Run PST Migrator and select the first archive store that you want to use.
Select all the PST files, including those that should go to other vault stores.
Select automatic correlation. PST Migrator will open the vault store and match PST files to archives within that vault store. All other PST files will not be matched.
Click theheading on the screen to sort by destination archive. This puts at the top of the list all the PSTs that could not be matched to archives.
Drag-select all the PSTs that could not be matched to archives and then click.
On the PST Migrator screen that asks, select .
At the end of the migration, PST Migrator hides the PST files that were migrated. The next time you run PST Migrator, these PST files will not appear in the list of PST files available for migration. The files appear hidden only if you have set your desktop so that it does not show hidden files.
Repeat the process, running PST Migrator again, this time choosing a different vault store.
When you have worked through all the vault stores, you may have some PST files left that failed to migrate. Run PST Migrator again and manually select the correct archive for each PST
If you run PST Migrator on a computer that is not running the Storage service for the vault store, then you cannot choose PSTs on a local disk. However, you can choose PSTs from a mapped network drive or a shared network folder.