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
How to configure the PST Locator task
The PST Locator 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.
. On this page you configure how the task is to search for domains, computers, and PST files.
Select whether the task is to use NetBIOS or Active Directory to find the domains and computers on which PST files reside.
You can configure the task to search computers for PST files using a registry or hard disk search. A registry search uses remote registry calls to search the Outlook profile for PST files. If a PST file is found in a profile, the Exchange mailbox in the profile is noted. If an Exchange mailbox is found, the task tries to determine the archive and the site that is associated with the primary mailbox referenced in the profile.
A hard disk search scans all the local hard disks on the designated computer for files with an extension of
.pst. It does not search the PST holding folder or the temporary migration folder on any computer running a PST Migrator task. On all computers, the Recycle Bin is not searched.
As there can be very large numbers of PST files on computer hard disks, it is advisable to perform registry searches initially.
On computers running Windows 7, you must enable the RemoteRegistry service to allow the PST Locator task to look for PST files using registry searches.
With the default settings, the task does not automatically search any computers for PST files; you need to select the computers to search. If you select the setting, the task automatically starts searching every computer it finds. As this process can take a very long time on a large network, use this setting with caution.
. Here you can specify the paths that you want the PST Locator to look in or ignore when looking for PST files.
. Domains that the task finds are listed on this page. Only the domains that are selected on this page are searched for computers and PST files.
. It is advisable to schedule the PST Locator task to run during normal office hours, so that it finds the maximum possible number of computers and PST files when users' computers are switched on and connected to the internal network. If the site schedule is set to run tasks during non-office hours, you may want to override the site settings by specifying the schedule for this task.
. The account under which the PST Locator task runs must have appropriate access to the computers that it is to search for PST files. Depending on the type of search that is configured for the task, the account must either be able to scan remotely the registry on each computer or have access to the drives on each computer.
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 thepage of the task properties to specify the account.