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
Preparation for PST scripted migration
Policy Manager only uses a limited number of settings in Exchange PST Migration policies. Enterprise Vault archives items from the PST files according to the following settings in your Enterprise Vault installation:
Enterprise Vault archives only the classes of items that are defined as eligible for archiving on thetab in Exchange PST Migration properties.
The migration obeys the registry settings that are set for the Storage service.
If you have configured customized shortcuts on thetab of the Exchange PST Migration policy, then the PST Migrator uses these settings. Otherwise the shortcut content settings that are configured in the Exchange Mailbox policy are used.
Items can be assigned a specific retention category during PST migration.
Some Enterprise Vault features, such as the retention folders and classification features, can override the specified retention category. For more information on retention, see the Administrator's Guide.
The PST files must not be in use at the time of migration, so make sure that users do not have them open. You may find that it is better to move the PST files.
The best procedure may be to gather all the PST files into the same place and then to migrate them from there. This makes it easier to generate the initialization file, assign permissions, and to manage files. Note though, that you may have some file name conflicts if there are PST files with the same name. Also, if any PST files are likely to be unmarked ensure that you know the owners because there may be no identifying information in the PST.
The Vault Service account must have Full Control access to the PST file.
The Storage service for the destination vault store must be running.
PST files that are password-protected cannot be processed. You must remove such protection before migrating their contents.
Alternatively, you may allow Enterprise Vault to override PST passwords during PST migration. To override passwords, enablein the tab of the properties.
If you intend to use the automatic PST compaction feature at the end of migrations, you may need some spare disk capacity for the compaction to take place. You can need as much as the size of the largest PST file, plus approximately 5% of its size. You may choose to ignore compaction if you plan to delete the PST files after migration.
Policy Manager migration checks the mailbox storage limit when a mailbox has either Prohibit Send or Prohibit Send & Receive mailbox limits set. If both these limits are set, Policy Manager does not move any item to the mailbox that exceeds the lower limit. If only one of the limits is set, then Policy Manager obeys that limit.
Note that, even if the storage limit prevents items from being moved to the mailbox, the items are still archived in the appropriate archive. In this case you can increase the mailbox quota and then migrate the PST file again to move the items to the mailbox.