PST Flight Deck 9.2 - Requirements Guide

Cloud Storage

PST Flight Deck can use Azure storage for the Backup and Cleanup module storage locations. It has been tested with standard, locally redundant blob storage. All access tiers have been used for this sort of storage and it is suggested to select the one that best suits the requirements of the project. For more information on how to create and configure Azure storage for PST Flight Deck, please reference the appropriate article.

Software

The PST Flight Deck server can be installed on several different operating systems.

All server components require the following server-based features to be installed:

·Microsoft .NET Framework 3.5

·Microsoft .NET Framework 4.5

·BITS

·Internet Information Server with ASP.Net enabled It is recommended the required components be installed using PowerShell commands. (See below)

For required versions of Outlook, click here.

SQL Server

PST Flight Deck uses a SQL Server database to track the migration project. The minimum configuration for this server is:

·10 GB Disk Space on a fast disk for the database

·Adequate space to accommodate log growth between maintenance cycles.

The following versions of SQL Server are supported:

Permissions/Security

The PST Flight Deck service account requires local Administrator access to all PST Flight Deck servers, full read/write access to the BITS upload share and the storage location that the share points at, and also active SQL ‘dbcreator’ permissions during the installation process.

For migrations to an Enterprise Vault target, the account used as the PST Flight Deck service account needs to be the Vault Service account used for the applicable Enterprise Vault server(s).

All accounts used during the operation of a PST Flight Deck project require the ability to access applicable servers, and to have full read/write access to the PST Flight Deck SQL database. Any account used during the operation of PST Flight Deck must be configured as an “Expert” in PST Flight Deck to have full control over Console functions.

Accounts running services that provide supplemental functionality, such as the Share Scanner or Central Upload Agent, require permission sufficient to access the resources they are acting against. For some of the more advanced features of the Central Upload Agent, this may include access to local workstation administrative shares. Typically these components run under accounts other than the service account.