PST Flight Deck 9.2.2 - Requirements Guide

For Ingestion into Enterprise Vault

If the intended target system of a PST migration is Enterprise Vault, additional requirements are needed to accomplish the ingestion.

The current Enterprise Vault Service Account is required for installation and to run the services responsible for any Enterprise Vault related function.

The API associated with version of Enterprise Vault being ingested to is also required. This is typically included in the Enterprise Vault installation media (e.g. “X:\Symantec Enterprise Vault\API Runtime\” where “X:\” is the drive letter of the Enterprise Vault installation media). Frequently, customers choose to install the Enterprise Vault Admin Console instead of the API. this is an acceptable and supported configuration.

For migrations requiring Enterprise Vault shortcut creation, the account running the shortcut module will require “Application Impersonation” rights in the target Exchange environment.

Adding/changing the credentials for Office 365 ingest account

To add or change credentials for Office 365 ingest account, you must use OAuth in order to authenticate with Microsoft Office 365.  The main steps of this approach can be found here.

For Shortcut Rehydration

PST Flight Deck includes the ability to restore Enterprise Vault shortcuts found within PST files in the upload area prior to the ingestion into a desired target.

The current Enterprise Vault Service Account associated with the shortcuts being restored is required to run the service responsible for any Enterprise Vault related function, including shortcut rehydration. The Enterprise Vault server associated with the shortcuts must be running and able to successfully retrieve the items associated with the shortcuts via API calls to the source server.

The API for the version of Enterprise Vault being retrieved from is also required. This is typically included in the Enterprise Vault installation media (e.g. “X:\Symantec Enterprise Vault\API Runtime\” where “X:\” is the drive letter of the Enterprise Vault installation media). Frequently, customers choose to install the Enterprise Vault Admin Console instead of the API. This is an acceptable and supported configuration.

For Repair