As users complete, an Operator may choose to move their migration priority to a disabled value. This permits control over future discoveries for the user. Backup files are frequently kept for a determined period of time after a user has completed the migration. This location, and all other modules storage locations will need to have content removed when appropriate. When a user or the migration completes, it is recommended that those users have the DisablePST registry key set on their workstations to reduce the re-introduction of PST files after a users source files have been removed.
During a migration, both users and files are progressing through a workflow. Each stage of the process has specific results indicating what has happened to the file. Stages are used to describe the phases of this process so that an individual can tell the status of a user or a file at a glance.
The user workflow stage is complex and are calculated by the server on an hourly schedule. The displayed status may not correctly reflect the current status of the user. This is normally not an issue as the status of a user does not change that fast. Below is a list of stages used to describe the status of a user:
|
Stage |
Description |
|---|---|
|
0 |
No actions have been taken against the user or the user has a disable Migration Priority set |
|
1 |
User is enabled for migration |
|
2 |
All of an enabled users files have had expired discovery conditions met or have had actions taken against them |
|
3 |
User has started uploading PST files to the server |
|
4 |
All files in scope are in a completed status |
|
5 |
All of a users PST files have fully completed the workflow |
File stages are current, up to the minute, for a specific file. The following are the stages of file processing:
|
Stage |
Description |
|---|---|
|
0 |
File has been discovered but no actions against that file have been taken yet |
|
1 |
Owning user is enabled for migration and is eligible for actions to be taken against the file |
|
2 |
An action has been taken against the file |
|
3 |
File has been queued by the agent for centralization |
|
4 |
File has been centralised to the desired location and is ready to be processed by the modules |
|
5 |
Modules have begun to process the file |
|
6 |
The file is ingested into the target |
|
7 |
All workflow operations have completed for this file |
The primary goal of a PST Flight Deck is to move PST files from a dispersed location and ingest them into a centralized location. Files are considered Complete when the need to ingest the file has been satisfied. This is most commonly due to complementing a successful ingestion of a file, however can also be achieved by a file being in a status that does not get ingested (Deleting, Not a PST File ..). Files or users can be considered Complete but still have modules in the workflow that have not competed.
Issues do happen! When they do it is important to be able to identify that a problem did occur, the nature of the problem, and what actions need to be taken to remediate the problem. While investigating, it is encouraged to note the steps of your investigation through the PST Flight Deck comment system. This will enable you to easily see when an issue with a file is recurring and the approach being taken will need to be reviewed.
There are many difficulties that can happen in PST migration projects. Being able to identify when a problem is happening at the client vs. the server or which module a failure took place in can expedite the ability to identify the problem and promptly resolve it.
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center
