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 the wizard-assisted PST migration process
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 choose to copy PST files so that users can continue using the original files while you migrate the contents of the copies.
The Vault Service account must have Full Control access to the PST file. If you plan to perform PST migration using a different account, then both the account and 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 Migrator's automatic correlation rejects any PST file that has more than one user account with write permission, leaving you to do the correlation manually. You may find it easier to set the permissions appropriately before running PST Migrator.
PST Migrator does not migrate the PST files that are password-protected. You must remove such protection before running PST Migrator.
Alternatively, you may allow Enterprise Vault to override PST passwords during PST migration. To override passwords, enablein the tab of the properties.
Items can be assigned a specific retention category during PST migration.
If PST files are scattered in different locations on users' disks, you may find it easier to move them all to a central location before you run PST Migrator.
If you have PST files that must be migrated to different vault stores, the quickest way to sort them is to use the automatic correlation within PST Migrator and remove those that do not correlate.
If you intend to use the automatic PST compaction feature at the end of migrations, you may need some spare disk capacity to provide room 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.
PST Migrator 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, PST Migrator does not migrate the items that exceed the lower limit. If only one of the limits is set, then PST Migrator obeys that limit.
If a PST file fails migration because the mailbox is full, you can modify the appropriate mailbox storage limit and then migrate the PST file again.