Overview of the scripting mechanism

You can perform scripted migrations of the contents of PST files to Enterprise Vault using Policy Manager. For detailed information on Policy Manager, see the Utilities manual.

The scripting mechanism enables you to configure how each PST file is processed.

For example, for each PST file you can do the following:

You write the Policy Manager initialization file, in which you list each of the files whose contents you want to migrate to Enterprise Vault. You can set up default settings that apply to all PST files and you can override the default settings for individual PST files.

It is possible for you to make Enterprise Vault clients save details of the owner's default archive in each PST file (PST marking). Policy Manager can then use this information to determine the correct archive and mailbox to use for each PST file. If you prefer to not to use this mechanism, or to override it for some PST files, then for individual PST files you can override these values.

When you migrate PSTs using Policy Manager you can use report mode to check all the PST files listed in your initialization file. This mode generates a new copy of the initialization file, with lines that identify any problems. Entries for PST files that cannot be processed are marked so that PST migrator ignores these files.

You can then do either of the following:

Note the following:

More Information

About the PST Migrator wizard