Get Live Help
Ingestion Nodes are Module Nodes that include an Ingestion module. They are typically deployed to support geographically distributed resource allocation within PST Flight Deck. Multiple ingestion nodes may also be leveraged to expedite the timeline to project completion when appropriate.
An Azure Node is a special node used in migrations to cloud based targets. Azure nodes can be used in a migration by itself or in support of geographically centric resource allocation for a multi-site organization. Azure Nodes are nodes deployed to Microsofts Azure service to act as the intended centralization target, processing, and ingestion nodes for a configured location. Azure Nodes can be used to minimize the footprint required to scale an environment out or to enable small businesses to leverage PST Flight Deck by reducing the initial hardware requirements of the solution.
One of the largest challenges in PST migration projects is accurately determining ownership of a PST file. Most PST files have ownership identified within the Discovery process for PST Flight Deck. PST files identified by a Share Scanner, or by a user as not belonging to them, require some special analysis. PST Flight Decks Content Scanner is used to scan PST files marked as Ownerless, or those files located on specific file servers. It can provide more information to help determine ownership association based on the contents of the file. Files processed by the Content Scanner can have the most common sender and most common recipient recorded and taken into consideration when determining PST file ownership. This attribute is also evaluated against a users proxy addresses to ensure account migration history is taken into consideration when evaluating ownership.
The Central Upload Agent (CUA) is a component frequently utilized in a PST Flight Deck environment. The primary role of the CUA is to upload files stored on centralized repositories more rapidly without having to use a workstations Migration Agent.
In a traditional migration situation without a CUA, remotely stored PST files would be queued for BITS transfer using a users Migration Agent to facilitate the upload request.
When a CUA is deployed, and the environment is appropriately configured, files on remote file servers are uploaded by a nearby CUA rather than connecting back through the workstation.