Enterprise Vault has several methods of migrating PST data into a users archive. One of them is given the name : Client Driven PST Migration.
Here is a short run through of it :
Client Driven PST Migration is often used in the following situations:
- Remote users who don’t frequently connect to the network.
- Administrators do not have permission to scan all remotemachines.
- Users need to continue to access data in PST files.
- PST migration is going to target a small number of users ina larger EV deployment or a large network.
The process flow for this method of migration is as follows:
· Create the PST Holding Folder
· Review the PST Policies
· Enable selected users for client driven migration
· Outlook Add-in performs a local search for PSTs and informs the Enterprise Vault Server of them
· PSTs are copied in chunks to the PST Holding Folder
· PST Migrator Task migrates each chunk to the mailbox archive, on it’s schedule
· After the last chunk is processed a check is made to see if new items have been added to the PST and those are migrated in a new chunk.
· PST Migrator Task signals that the PST can be post processed (eg removed from the Outlook profile, deleted if selected in the PST Policy)
The Client Driven method of PST Migration requires a PST Migrator Task to exist (it must also be started, and running either manually or in schedule, for the migrations to take place)
It is also worth noting that if a user is enabled for migration, PSTs discovered and migration of the list of PSTs has started, and the user is subsequently disabled for migration, that no new PSTs will be discovered but existing PSTs will still be migrated.