Chat now with support
Chat with Support

Quadrotech PST Flight Deck 9.1.3 - Administration Guide


In PST Flight Deck, a module refers to one of the components of the solution that run against successfully uploaded user data to a defined and centralized location. It is possible to categorize the PST Flight Deck modules in three categories: pre-ingestion, ingestion, and post-ingestion modules. Although workflow order is configurable, the following categorization is based on a default installation with no modification in the workflow’s order.


Pre-ingestion modules are those that are configured to run prior to the ingestion module. Sometimes referred to as the “pre-flight checks,” pre-ingestion modules are designed to prepare and safeguard PST data for ingestion into a desired target. The following table discusses the pre-ingestion modules available for enablement.



Local Upload

Checks if the PST file is present in the BITS upload location


Moves ownerless files to an alternate storage location until ownership is defined


Copies a PST file to a designated location until operator deletion


Executes a repair on a PST file


Filters and extracts PST files to disk to enable streamlined processing and delivery to the target


Reviews the PST file content to identify duplicated messages and removes them


In most configurations, Extraction and Repair modules should be local to the Uploads directory frequently configured on the Core server.


Ingestion modules are typically chosen at the point of installation. These are the modules responsible for the PST Flight Deck actions taken to ingest a PST file’s contents into the desired target. As the first item ingesting successfully completes, the migrated content should be immediately available in the target system. Once a PST file has been successfully ingested or ingestion of the file is not required, PST Flight Deck considers the file as “completed.”


Rate of ingestion is frequently a point of bottleneck in a migration and can be monitored in the Management Console, Admin Console, or via the PST Flight Deck Portal. Tuning an ingestion for performance requires the PST Flight Deck Admin Console and an account with sufficient rights. The net ingestion rate may be constrained by limitations of the environment and increasing its work capabilities may result in a decrease of performance. In general, ingestion tuning is performed while closely monitoring the entire environment and until a suitable rate has been achieved or a resource is excessively constrained. If resource constraint occurs, the last known good configuration should be evaluated for resource constraint and selected as the “best tuned” configuration at that point in time.


PST Flight Deck still has some wrapping up to do after the ingestion has completed for a file. Post-ingestion modules are those modules that are responsible for the tasks necessary to clean up after a file has been migrated. The following table discusses the post-ingestion modules available for enablement.



Legacy Viewer

Provides a web-based view into the original PST file contents and structure


Removes processed content from the BITS upload directory

Source File Remover

Queues request for Agents to delete the original file in its original location


Permits the execution of PowerShell scripts as part of the workflow of a PST file. PowerShell scripts can also be used in the pre-ingestion workflow.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating