Client-driven migration

It is possible to configure the Enterprise Vault Outlook Add-In so that it migrates PST files automatically to a central PST holding folder. The PST Migrator task then processes the PST files and archives the contents.

You need to configure a PST Migrator task on every Enterprise Vault server that hosts a Storage service and manages the archives to which you intend to migrate PST files. When migrating a PST file, the migration process runs on the Enterprise Vault server that manages the destination archive.

Client-driven PST migration can be useful in the following cases:

You do not have permission to access PST files on the user's computer.
Users need continual access to their PST files.
The user's computer is available on the network only occasionally. For example, a user with a laptop computer who visits the office on one day each week.

In summary, the client-driven migration process is as follows:

You enable mailboxes for client-driven PST migration.
An explanatory mail message is immediately sent to the newly-enabled mailboxes.
The next time a user starts Outlook, the computer is scanned for PST files.
Starting with PST files in the users' profile, each PST file is sent as a series of approximately 10 MB chunks to the PST holding folder.
The PST Migrator task migrates the chunks to the user's archives.
When a PST file has been successfully migrated, checks are made to make sure that no more items have been added to it. Provided that there are no more items, the PST file is removed from the user's profile.