Veritas Enterprise Vault™ PST Migration
- 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
Troubleshooting PST migration
You can use the task report files to assist in troubleshooting PST migration failures. Each time a task runs, it creates a report and places it in the Reports folder, which is a subfolder of the Enterprise Vault program folder (for example C:\Program Files (x86)\Enterprise Vault\Reports). The report file name takes the following form:
PSTLocTask_server_datetime.txt
PSTColTask_server_datetime.txt
PSTMigTask_server_datetime.txt
If file sharing is not enabled on a user's computer, the PST Locator task is unable to search the registry or files on that computer. Note that Windows does not automatically enable file sharing. If the PST Locator task cannot search the registry or files, this results in errors such as the following in the report file:
** 18/07/2005 14:34:21 Hard disk search failure on DEMO : Failed to read registry to get list of drives : The network path was not found. ** ** 18/07/2005 14:34:21 Registry search failure on DEMO : The network path was not found. **
These errors are also reported if the Windows firewall is on. If the firewall is on, then you need to create an exception in Windows firewall for "File and Printer sharing", TCP port 139 and 445.