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 defined as eligible for archiving on the tab in Exchange PST Migration properties.
The migration obeys registry settings that are set for the Storage service.
If you have configured customized shortcuts on the tab of the Exchange PST Migration policy, then the PST Migrator uses these settings. Otherwise the shortcut content settings configured in the Exchange Mailbox policy are used.
Items can be assigned a specific retention category during PST migration. You may want such items to retain this retention category if they are moved later to a folder with a different retention category. To prevent Enterprise Vault from changing the retention category, ensure that the policy option, is not selected. This option is on the tab of the Exchange mailbox policy properties.
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 will make it easier to generate the initialization file, assign permissions, and to manage files. Note though, that you will have some filename conflicts if there are PST files with the same name. Also, if any PST files are likely to be unmarked you must be sure you know the owners because there will 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.
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 could need as much as the size of the largest PST file, plus approximately 5% of its size. There is no point in compacting the PST files if you are going to delete them.
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 would exceed 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 could increase the mailbox quota and then migrate the PST file again to move the items to the mailbox.