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
Undertaking the PST migration process using Policy Manager
In outline, you perform scripted migrations with Policy Manager as follows.
To undertake the migration process using Policy Manager
- Decide whether to use markers within PST files to determine their ownership. By default, PST files are marked. You can turn off PST file marking in Exchange Desktop policies using the setting, Mark PST files, in the list of advanced Outlook settings.
- Write the Policy Manager initialization file to specify which PST files you want to migrate to Enterprise Vault. In the file, specify that Policy Manager is to run in report mode. Remember to save the initialization file in Unicode format.
- Run Policy Manager in report mode with the initialization file.
Policy Manager does the following:
Checks that all the PST files listed are accessible.
Creates a new initialization file that shows any problems with the listed PST files, such as files that could not be accessed or are password-protected.
The new initialization file has the same name as the original, with a number added to make it unique. For example, if the original script was called
PSTMigration.inithen the new script would be called
Creates a log file with the same name as the original initialization file and a file type of
.log. For example, if the original script was called
PSTMigration.inithen the log would be called
- You can fix problems that are listed in the new initialization file, or you can leave them for later.
- Run Policy Manager with the new initialization file. Policy Manager migrates the file contents and writes a log file with the same name as the initialization file and a file type of
If any PST files fail the migration process, Policy Manager automatically writes a new script that you can run to process just those failed files.
If necessary, fix any problems and then run the new script to migrate the contents of just those PST files that were not processed before.