|
|
The PST Migrator task properties include the following pages:
. Properties on this page let you configure how often the task should retry a failed operation, and the number of report files to keep.
. This page contains the following configuration settings:
The location on a local drive of the temporary files folder that the PST Migrator task uses during the migration process. You specify the location of this folder when you create the PST Migrator task.
If you have configured building blocks, you must create a temporary files folder with the same folder path on all the Enterprise Vault servers in your building blocks environment. If the PST Migrator task fails over to a different server, it continues to use the same local path for the temporary files folder.
The maximum number of PST files to migrate concurrently. Depending on your system configuration and workload, you may find that changing this number improves performance.
. It is advisable to schedule the PST Migrator task to run during normal office hours, so that it can access as many computers and PST files as possible (when users' computers are switched on and connected to the internal network). Access to the computers and original PST files is required for post migration operations, such as unlocking the PST files, creating shortcuts or deleting the PST files. As the site schedule is typically set to run tasks during non-office hours, you probably do not want to run this task according to the site schedule.
. The account under which the PST Migrator task runs must have appropriate access to the PST holding folder, temporary files folder, and computers and PST files to be migrated. Access to the computers and original PST files is required for post migration operations. To ensure that the task has adequate access to all the computers in the domain you can run the task under an account that is a member of the domain administrators ' group. Use the settings on the page of the task properties to specify the account.