Please enter search query.
Search <book_title>...
Enterprise Vault™ PST Migration
Last Published:
2022-09-04
Product(s):
Enterprise Vault (14.3)
- About this guide
- Introduction to PST migration
- PST file ownership
- PST migration: scripted
- PST migration: wizard-assisted
- About the PST Migrator wizard
- Outline of the wizard-assisted PST migration process
- Preparation for the wizard-assisted PST migration process
- Migration tips for the wizard-assisted PST migration process
- How the wizard-assisted PST migration process affects users
- Starting the wizard-assisted PST migration process
- PST migration: Locate and Migrate
- About Locate and Migrate
- Setting up PST Locate and Migrate
- Migrating PST files using PST Locate and Migrate
- Excluding network shares from PST migration using the PstLocatorTask.exe.config file
- Troubleshooting PST migration
- PST migration: client-driven migration
- About client-driven PST migration
- Preparation for client-driven PST migration
- Editing the PST migration messages for client-driven PST migration
- Configuring the PST holding folder for PST client-driven migration
- Creating a PST Migrator task for PST client-driven migration
- Enabling mailboxes for PST client-driven migration
- Permissions required for migrating PST files stored on network drives
Output from PST migration
When you run Policy Manager with an initialization file containing a [PSTdefaults] section, Policy Manager automatically writes a new initialization file that contains details of any problems that it found.
The new initialization file has the following features:
There is a [PSTcheckpoint] section at the top of the file, summarizing the results of the run.
If you had been using process mode then the following apply:
All [PST] sections for files that were processed successfully are commented out.
There is a JobStatus entry in each [PST] section, indicating for that file, either success or the type of error that occurred.