PST Flight Deck is a scalable enterprise capable solution designed to address the issue of decades of unmanaged PST file creation, utilization, and proliferation throughout an organization. The objective of this solution is to identify and migrate the content of Personal Storage Table (PST) files into a target environment in order to permit the content to be subject to regulatory, retention, and organizational requirements. Upon ingestion, it can also be used to eliminate PST files identified throughout the organization.
PST files were initially introduced to help Administrators manage data on Exchange 4.0 mail servers. Their availability was expanded to support the use by Outlook to archive or store mail items locally. Expensive and limited mailbox store data on early versions of Exchange made PST files popular with organizations. PST files permitted the expanded use of a mail system without dramatically increasing the perceived cost, downtime, or expense of an Exchange environment. Mailbox quotas began to shrink to ensure the stability and availability of mail servers and PST files were now the target of the exponential growth in data use to facilitate the increased use of email systems within an organization.
PST files are a problem within most organizations today. When introduced to users, there were few guidelines as to how or when to use them. Some users began to route all their Exchange mail directly to their local storage, removing the administration and defensible deletion of mail content. Other users took this as an opportunity to save and store everything; began abusing the intent of the system by using it more as a file server than a mail server. Departments began using the storage containers for projects or departmental data on network shares where they were unsupported and more prone to corruption. The data stored within the files frequently fell outside of organizational compliance, retention, and discovery requirements. Data began being lost to poor management practices from the users of these files, corruption, or hardware changes. This PST file life-cycle continued for over a decade in several organizations, resulting in an enormous body of data completely unmanaged, decentralized, and with limited accessibility to those needing it most.
As time progressed, Exchange was able to restructure its storage to accommodate less expensive disks and more redundancy. The server could now accommodate the level of storage being used at a reasonable price without the same concerns of older server versions. While in the wild, PST files had become a problem. A big problem. The longer the use of PST files was permitted, the harder the problem was to resolve. Until the recent versions of Outlook, users were still permitted to store all Exchange mailbox data directly to a PST file on their system and remove all their messages from the centrally managed Exchange servers.
Manual attempts to eliminate PST files by IT departments proved to require a high level of messaging expertise, be very costly, and have an ever-expanding project duration. When things went well, a migration project was time consuming, labour intensive, and was challenging to track the progress of. The limited visibility made it challenging to accurately communicate the expected experience to the users impacted and groups intended to support them. Help desks became flooded with frustrated users wanting access to their critical data and was unable to provide any insight or accurate time-lines as to when their data would become available to them again. Engineers had to request personal passwords, be challenged with old PST file formats, duplicate items within PST files, files that were erroneous duplicated, files that were made as a backup, and file corruption of the PST files. When things went poorly, the effort frequently just failed after much expense and little progress.
PST Flight Deck is a feature-rich, enterprise grade solution designed to reduce the time and level of effort required migrate PST files to a desired target. PST Flight Deck is designed to minimize many of the issues that plague PST migration projects. PST Flight Deck is able to discover, associate, centralize, process, ingest, and eliminate PST files automatically.
With PST Flight Deck, modules are run prior to the ingestion that are designed to prepare a PST file for quick delivery to the target system. These “pre-flight checks” are initially configured, then executed on every PST file that runs through PST Flight Deck. This process reduces the effort of an overall PST file migration by automating many of the tasks that would be performed reactively by skilled professionals, whom likely have several other responsibilities.
PST Flight Deck is built on a modular framework that permits a nearly infinite number of solution design options. The architectural components of PST Flight Deck can be summarized as those that are required for a functional environment and those that provide expanded and supplemental functionality to the solution.
In its most basic configuration, PST Flight Deck requires at least one server, a SQL database, and Migration Agents deployed. The actual requirements for a given project are dependent on the scope and limitations of the project. For a properly scaled environment, please consult a qualified PST Flight Deck architect to review your environment and it’s needs as it pertains to a PST Flight Deck deployment.
Below is a diagram showing a high-level architecture of the required components for PST Flight Deck and how they interact in a production environment.
The Core server is responsible for several aspects required for a functional PST Flight Deck system. In a typical configuration, the Core server hosts the PST Flight Deck Core service, the Internet Information Services (IIS) instance hosting PST Flight Deck files, the Background Intelligent Transfer Service (BITS) upload directory, and any number of modules.
The Core service is responsible for communication with the PST Flight Deck system database and execution of scheduled operations. All deployed agents also check-in and update the system through the Core server. Essentially, the Core service acts as the conductor of the entire solution.
A typical deployment of PST Flight Deck begins with the installation of a Core server. In most environments, more than one PST Flight Deck server is used, however for non-production installs it is possible to install all the components on a single server. Supplemental components may also be installed on the Core server, either from the Core installer itself or independent installers.
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|
|Park||Moves ownerless files to an alternate storage location until ownership is defined|
|Backup||Copies a PST file to a designated location until operator deletion|
|Repair||Executes a repair on a PST file|
|Extraction||Filters and extracts PST files to disk to enable streamlined processing and delivery to the target|
|Deduplication||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|
|CleanUp||Removes processed content from the BITS upload directory|
|Source File Remover||Queues request for Agents to delete the original file in its original location|
|PowerShell||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.|
PST Flight Deck leverages a component installed on end-user Windows workstations called the Migration Agent. This agent is critical for discovering PST files, providing meta-data to help determine PST file ownership, managing the user interaction with the migration process, and uploading PST files to a centralized location throughout a migration project. The Migration Agent has a lightweight footprint and is supported on many client operating systems. The Windows version of the Migration Agent has 64 and 32-bit versions. The version of agent that will be installed will coincide with the architecture of Outlook that is installed.
PST Flight Deck has several features that are not required for a basic configuration but provide an enhanced, more robust, or more customizable experience. The features that are required for any given deployment will vary wildly and it is encouraged to discuss your needs with a qualified PST Flight Deck Architect to determine which components are appropriate for you.
PST Flight Deck permits the flexibility to support any size of organization. Smaller organizations may be well suited in utilizing a single configuration for all its users. A larger enterprise often has several conditions which make a “one configuration fits all” approach impractical. PST Flight Deck is able to support the smallest branch offices while managing multiple large campuses within a single environment. To begin to support an enterprise’s level of complexity, PST Flight Deck permits the customization of configuration settings within its environment via profile and location designation.
Profiles are the initial building block of the ability for a PST Flight Deck to have the level of customizable configuration needed to support today’s enterprise. Profiles are used to permit an alternate configuration for users assigned to them. Examples where profiles may be of use are:
Profiles enable the assignment of unique File Scanner, Agent, Language, and Location configurations.
Locations permit work to be assigned into geographically appropriate groupings without the overhead of deployment and management of independent migration environments. This enables an organization to centralize and process PST files in data centres close to the users and their data. Enabling the ability to support multiple locations can reduce overall environmental network consumption and the time for project completion.
PST Flight Deck permits the ability to scale out an environment to offload the burden on any given system in the environment. For small and mid-sized projects with no special requirements, a standard deployment may be sufficient. For larger environments or projects with tight time requirements, processing modules may be distributed over several machines to scale the system to match the environment’s needs or reduce bottlenecks in the workflow. These computers with module components of PST Flight Deck installed are referred to as “nodes”.
When considering the scalability of your PST Flight Deck environment there are many factors to consider. Please consult a qualified PST Flight Deck Architect prior to scaling out an environment.
Part of the flexibility of PST Flight Deck is the modular approach that is taken within its architecture. The functions required to perform a migration can be run over multiple nodes. This permits many of the same modules to be run in parallel or assigned to specific locations.
Module Nodes are servers with PST Flight Deck modules installed on them. They encompass all PST Flight Deck servers containing modules and not included in another node type. Module nodes can be used to scale processing of any module workload to permit rapid processing of items uploaded.
Most Module Nodes do not have any special considerations outside of resource availability and the ability to communicate to the Core. Extraction and repair nodes have high disk requirements and are typically located on the machine with the highspeed disks used for the BITS upload directory.
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 Microsoft’s 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 Deck’s Content Scanner is used to scan PST files marked as “Ownerless,” or those files located on specific fileservers. 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 user’s 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 workstation’s Migration Agent.
In a traditional migration situation without a CUA, remotely stored PST files would be queued for BITS transfer using a user’s 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.
If an environment has a CUA installed, configured, and running with sufficient permissions, it can be used to facilitate Forced Migration requests. A Forced Migration utilizes the CUA to connect to a user’s local machine and copy the eligible PST file over the administrative share on their local system. This enables a user to have their files uploaded without having to go through BITS or even a Migration Agent. This feature is useful for Migration Agents struggling to complete an upload or as a means to migrate users who are rarely connected to the domain.
The PST Flight Deck Application Streaming Wrapper (ASW) is designed for environments that utilize virtual application streaming to provide Outlook to users. Due to the way application streaming is performed, a typical agent approach cannot be used.
The ASW works as a wrapper for Outlook on an application streaming solution. Upon launch, it checks to see if a user is enabled for migration. If they are enabled, it quickly closes open connections to PST files associated with the user’s Outlook profile during that streaming session. Once that has completed, it launches Outlook and maintains the standard user experience without any of the PST files connected. There is no interaction required from users streaming Outlook but their experience will be impacted as PST files will no longer be attached to their streamed Outlook instance. The ASW is frequently used in conjunction with a Share Scanner and Central Upload Agent to enable discovered files to be uploaded from shared resources without the use of a traditional Migration Agent.
A PST Flight Deck environment can be globally distributed and centrally managed by a single Core server. Administration and operation of the environment can be performed remotely. The PST Flight Deck Management Console is available to those needing the ability to manage a PST Flight Deck migration without the need to edit the settings of the migration solution. The ability to install a console on an Operator’s workstation enables them to perform their duties without the need to grant remote access to the server hosting. The core services and Administration Console.
PST Flight Deck has a choice of user interfaces to interact with the product. To some extent the interface utilized depends on the role being performed. PST Flight Deck is scalable not just in processing power, but also in its ability to adapt to any size of team associated with the migration project.
PST Flight Deck consoles are applications that run from the server or an Administrator, Architect, or Operator’s workstation. They permit the most control over a PST Flight Deck environment. There are two consoles available: The PST Flight Deck Administrator Console and the PST Flight Deck Management Console.
The PST Flight Deck Administrator Console (Admin Console) provides the most access to configure a PST Flight Deck environment. It is typically available on the Core server and is installed as an available feature by the Core installer. Access to the Admin Console is required during the initial install, setup, pilot, and ramp-up of your project, but is not typically required for the duration of your project. Alternatively, a project can be entirely managed from the Admin Console if desired.
The PST Flight Deck Management Console (Management Console) is intended to provide operators a client to use on their local workstations. The Management Console provides the options necessary to perform the daily operations of a PST Flight Deck migration without requiring access to a PST Flight Deck server. The primary difference between the two consoles is the Management Console does not have the option for the “Settings” menu as the Admin Console does.
With the exception of the above, both interfaces are the same. The remainder of this section will refer to both as the Console.
In general, navigation within the Console is similar no matter where you are in the Console. The core of a Console has a Ribbon Panel, Navigation panel, and the body of the console, where the selected data is displayed.
The top of the Console contains several features and is seen below:
|1||File Options||Provides the ability to display general information, launch a help file, or exit the Console|
|2||Info||Provides information related to the product, version, and license|
|3||Ribbon||Provides options related to the visible or selected items within the interface. Changes depending on location and selection within the Console|
The left side of the Console is used for navigation. The following is an example of the options available within the navigation pane of the console:
|1||Navigation Control||Collapses the navigation panel|
|2||Navigation sub-menus||Options that are exposed based on the navigation menu selected|
|3||Navigation sizing||Slider to permit you to resize the navigation pane|
|4||Navigation menus||Parent navigation options that expose contextual options for a given area|
The navigation pane has menus at the bottom that act as parent containers for related options within. Selecting one of these menus will expose relevant sub-menus in the navigation pane above. The menus available are Manage, Reports, and Settings.
The Consoles have a powerful interface that permits the filtering of live data to return data you are seeking. Many areas of PST Flight Deck return a lot of data that can be too much to be useful without the ability to refine the results. The information below discusses several approaches to managing the data being returned within the grid of several options within the Console.
Additional data columns can be added to many of the grids in PST Flight Deck.
To access the additional columns of data:
A list of available data columns will be shown. You can drag and drop from the list of columns on to the appropriate part of the user-list.
The column headings can be clicked to change the sort order, a subsequent click on the same column heading will change the direction of the sort. Most columns support “drag and drop” functionality to change their position relative to the other data columns. This can make the data more presentable and readable. A data column can be removed if required by right-clicking on the column and choosing the “Remove this Column” option.
It is possible to access the data filtering features in most of the Console’s grids in these ways:
Simply click on the desired operator and it will be entered.
After a filter has been applied, an option to “Edit Filter” is presented in the lower right corner of a console. This can be selected to access the advanced editor for the currently applied filter, which will permit you to perform very complex queries to return specific data within a Console.
The list of users can be grouped by one or more columns as follows:
Filtering can be used to reduce the overall list, but sometimes it is necessary to search for data within a given column. You can search for particular data within a grid by right-clicking on a column heading and selecting the option “Show Find Panel.” Previously used searches can be selected from the dropdown list.
If you identify a filter that is useful for your migration it is possible to save it for later use. To store the customized grid click on “Save” in the “Layout” ribbon. Each saved layout can be given a unique name. Previously saved layouts can be retrieved by clicking on “Load” in the “Layout” ribbon bar. The current data list can be reset to the defaults by clicking on “Reset” in the “Layout” ribbon bar. Saved layouts can be retrieved and executed by selecting “Load” on the PST Flight Deck “Layout” ribbon and selecting the name assigned to the saved layout. You can also select “Overwrite” to save over a pre-existing layout or “Delete” to remove the saved layout.
The “Manage” menu is the most commonly accessed area during a migration. Most of the functionality required for an Operator to manage the PST Flight Deck migration can be found in this section. Options are grouped into sub-menus and are described below:
|Progress||Provides high-level statistics and trends about the current status of a migration|
|Operations||Provides information of interest in the daily operation of a system including performance trends and current backlog information|
|Resources||Provides information about CPU, memory and disk performance|
|Users||Provides information and options to manage the end-users in the environment|
|Files||Provides information and options to manage the files discovered in the environment|
|Events||A filterable list of events produced within the PST Flight Deck environment during a migration|
|Owners||Permits ownership review and management during a migration|
|Schedule groups||Permits the scheduling of enabled batches|
Some key combinations have been included to assist in the navigation of the Manage section of the console. The areas affected are frequently navigated between during a migration project. Use of these hotkeys can enable quicker daily navigation.
|ALT + U||Navigates to the last view of the Manage > User section|
|ALT + F||Navigates to the last view of the Manage > File section|
|ALT + O||Navigates to the last view of the Manage > Owners section|
Additionally, there are shortcut keys associated with specific popup dialog boxes.
This view provides an overview of the project as a whole. The following are its features:
|User||Table showing statistics related to uses and their status within the migration|
|Project Statistics||Graphs showing the status and trends of files and users over the past days, weeks, or months|
|File||Table showing statistics related to discovered files and their status within the migration|
A section designed to enable an Operator to quickly be able to tell the current health of a migration in a graphical display. The following are its features:
|Alerts||Drillable badges displaying the number of actions needed or unacknowledged events|
|Last 24 hour BITS activity||Shows hourly activity reported for files being centralized from the Agents to PST Flight Deck for the past 24 hours|
|Module Backlog||Drillable bar graph showing the size or count of data backlogged per PST Flight Deck module|
|Last 24 hour Ingest activity||Shows hourly ingest rates over the past 24 hours|
|BITS size last 14 days||Line graph showing daily rates of centralized data over the past two weeks|
|Ingest activity last 14 days||Line graph showing daily rates of ingestion over the past two weeks|
This section permits centralized observation of resource consumption of servers running Modules within a specified location. The focus of this is to provide a point in time review of resource consumption and not a comprehensive performance monitor for the PST Flight Deck environment. Displayed is graphical output for CPU, RAM, and disk usage.
This section of the Console is where most actions against users are taken. Assignment of user types, profiles, and priorities are all performed within this section. This sub-menu is where a lot of the migration monitoring and management takes place.
The grid returned under the “Users” sub-menu is comprised of two portions. Initially presented is a display of user information and general statistics about all the users in an AD environment. Each user who has discovered files can be expanded by clicking the plus sign (+) at the left of its row. The resultant sub-table has the same characteristics as the “Files” section and will be described in detail in a succeeding section of this guide. The ribbon and right-click options change depending on which section your selection is located.
The home ribbon when “Users” is selected has options impacting the selected user (with one exception). These options and a description of their functionality are as follows:
|Refresh||Refresh||Refreshes data in the grid|
|Enable Users||Manage Users||Permits the ability to set migration and email priority assignments to enable users for email communication or migration|
|Actions||Manage Users||Contains a dropdown list of several available actions. The contents of the list are also available when right-clicking a selection in the grid|
|Reset User||Manage Users||Removes all database entries for files associated with the selected user or group of users|
|Assign Profile||Manage Users||Permits profile assignments to users for specialized settings|
|Request Client Log File||Manage Users||Queues a request delivered at the next agent polling period for a selected user to return the PST Flight Deck Migration Agent client logs to the server for review|
|Import Attributes||Manage Users||Allows importing of a specifically formatted text file, or XLSX, to assign values to fields for specific users|
|Edit Attributes||Manage Users||Allows manual assignment of “User Custom Field” values|
|User Log||Manage Users||Provides information regarding events, errors, and actions taken against the selected user through the duration of the project|
|Progress||Information||Provides Active Directory information about the selected user and the status of all PST files for that user by number, volume, and current progress|
|Inactive Users||Information||Provides the ability to identify users who have historically returned discovery results but have been inactive for a specified number of days|
|Add||Comments||Enabled Operator to create a new comment on a user or file depending on the selection|
|Show||Comments||Shows all comments associated with the selection|
|Close All Comments||Comments||Closes all comments associated with the selection|
The “Action” menu has several options for selection. As with the home ribbon under the “Users” sub-menu, these options are related to the presently selected object in the grid, and changes depending on if that selection is one or many files or users. These options are also available when right-clicking on selection within the grid. The following is a list and description of the options available under the “Action” menu when a user is the selected object:
|Clear Postponement||During an interactive migration, permits a reset of a user’s request to postpone the migration of their files|
|Mark files for Migration||Operators option to migrate a user’s files|
|Mark files for Deletion||Operators option to delete a user’s files|
|Change User Type||Operators option to specify a non-default user type for an account|
|Manage User’s Files||Shows a filtered redirection to the owner management portion of the console showing the selected users files|
|Set Unauthorized for Migration||Marks a user not authorised for migration, even though they may be enabled|
|Watch/Stop processing||Flags or un-flags a user for watching|
|Show user’s workstations||Shows workstations that a given user has logged into|
The type of user designated by the “Change User Type” option can dictate the way the features of the product affect a given user. Below is a list of available types and their description:
|User Account||Default type assigned to all users|
|Service Account||Type to identify service accounts that may be discovering data erroneously|
|Admin Account||Type to identify accounts with elevated permissions that may be discovering data erroneously|
|Group Mailbox Account||Type to identify mailboxes belonging to a department or other group|
|Operator||Designated type for all PST Flight Deck Operators|
|Leaver||Designation for an account belonging to someone who has left the organization|
|Helpdesk||Designation for member of the help desk team|
|Not in AD||Designation for local accounts logged into workstations with a Migration Agent installed|
|Mac OS user||Designation for users running a version of Apple’s workstation operating system|
|Cloud||Designation for a user that is in Office 365 with an email address different from the one in Active Directory|
The “Files” section of the console is also very commonly accessed while managing a migration. Like the “Users” section, it provides a lot of functionality to determine status and granular details of a migration. Actions can be executed on specific files when appropriate. The options available in the “Files” sub-menu’s home ribbon are as follows:
|Refresh||Refresh||Refreshes the data in the grid|
|Actions||Manage PSTs||Contains a dropdown list of several available actions available to take about the selection in the grid|
|Reprocess Module||Manage PSTs||Opens a window to allow for removing and reprocessing modules for the selected file|
|Reset Upload||Manage PSTs||Removes upload status and queues eligible files to be uploaded|
|Import File Attributes||Manage PSTs||Allows importing of a specifically formatted text file, or XLSX, to assign values to fields for specific files|
|Migration Statistics||Information||Shows statistics for the ingestion of a PST file|
|Progress||Information||Shows the details for all modules run against a selected file|
|Show Discovery||Information||Shows information on instances of discovery for a selected file|
|Show Events||Information||Shows all events logged that are related to a file|
|User log||Information||Provides information regarding events, errors, and actions taken against the user associated with the selected file through the duration of the project|
|Add||Comments||Enables creation of a new comment on the selected file|
|Show||Comments||Shows all comments associated with the selection|
|Close All Comments||Comments||Closes all comments associated with the selection|
|Continue/Delete||Operations||Change status of selected file or files to ‘Deleting’ and removes applicable failed module|
|Repair||Operations||Changes status of selected file or files to ‘File corrupt’ and removes applicable failed module|
|Continue/Unblock||Operations||Removed ‘Ingestion blocked’ or “Partial extraction’ status on selected files|
|Reingest||Operations||Queues a file or its contents to be copied from the configured ‘re-ingestion’ location to the configured ‘upload location’ and sets the file to be reprocessed|
|Continue/Migration||Operations||Changes status of the selected file or files to ‘Migrating’ and removes applicable failed module|
|Skip Module||Operations||Forces the current module to be skipped and permits a file to move on to the next phase of the workflow|
The “Action” menu has several options for selection. These options are also available when right-clicking on a file within the grid. The following is a list and description of the options available:
|Show User||Changes console navigation to the Users section filtered by the user associated with the selection|
|Change Owner||Launches a window to specify the owner of selected file or files|
|Change Status||Launches a window to change the migration status of selected file or files|
|Request Client Log File||Queues a request to be delivered at the next agent polling period of a specific user to return the PST Flight Deck client lots to the server for review|
|Reset Agent||Queues a request delivered at the next agent polling period for the agent to be exited and launched again|
|Disconnect File||Removes the selected file from the users PST profile resulting in the file being disconnected from Outlook when next launched|
|Scan Content||Flags a file for the Content Scanner to review|
|Show Workstation Files||Change console navigation to a filtered ‘owners’ section showing all files located on the same machine as the selections original location|
|Collect Orphaned||Permits users to receive a request to secure and transfer a PST file for centralization|
|Report Module Stats||Redirects view to Reports > PostProcess Stats with filter for the selected PSTFileEntryID|
|Remove File Entry||Removes record of the selected file from the database|
|Re-Ingest||Re-ingest a file|
|Watch/Stop Watching||Flags or un-flags a file for watching|
The Watched items section shows all files and users that have been flagged for watching. This provides a consolidate view of key items. The home ribbon for this sub-menu and each action menu changes depending what is selected, a user or a file. The ribbons and action menu options are the same as their respective
The Events section shows all unacknowledged events that have occurred on the system since deployed. The default view of the Events grid shows the Type, Source, Event details, a count of the occurrences of the events, the level of severity of the event, and the last logged time for the event. The home ribbon for this sub-menu has the following options:
|Refresh||Refreshes the data appearing in the grid with the latest information from the system database|
|Acknowledge||Marks the selected event as acknowledged resulting in its removal from the view upon refresh|
|Search||Permits searching events using values in specified fields|
|Add||Enables creation of a new comment on a selected event|
|Show||Show all comments associated with the selection|
|Close All Comments||Closes all comments for the selected event(s)|
Managing owners is a critical part of a successful migration. The Owners section shows the results of our owner identification efforts; including owner conflicts, warning levels, all ownership related metadata, the probability that ownership has been identified, who a presently is the owner of a file, and who PST Flight Deck thinks should be the owner.
In some migrations, a lot of effort is required in the Owners section to ensure the data discovered is going where it is expected to go. Upon discovery, ownership management can begin and drastically reduce the level of effort required towards the middle and end of a migration. Owner management can also be delayed until later in the migration. If file ownership is not addressed early in the project, the files could be blocked from ingestion due to not meeting the minimum ownership probability threshold.
The options on the home ribbon for the Owners sub-menu are as follows:
|Refresh||Refreshes the data|
|Recalculate Ownership||Calculates ownership probability and conflict warning of the selection|
|Accept Suggest User||Assigns ownership of the selection to the user suggested|
|Clear Operator Override||Removes Operator assigned ownership of the selection|
|Set Owner||Produces window to assign ownership of the selection from a list of users|
|Import Owners||Option to import specifically formatted CSV file to make ownership decisions|
|Unblock||Enables file where ingestion has been blocked, to proceed|
|Mark for Deletion||Change status of selection to ‘Deleting’ status|
|Add||Enables creation of a new comment on a selected file|
|Show||Shows all comments associated with the selection|
|Close All Comments||Close all comments for the selected files(s)|
|Details||Shows key pieces of information for a specific file|
Schedule groups allows an operator to schedule batches to be enable at a certain time/date, with a specific migration priority. Settings are available that can limit the number of people and/or volume for a given batch.
At the specified date/time, the users in a given batch are set to the specified migration priority as long the following conditions are met:
Office 365 mailbox information is obtained from the Office 365 user synchronization task. The options on the home ribbon for the Schedule groups su