Chat now with support
Chat with Support

PST Flight Deck 9.2 - Deployment Guide

Overview

The CUA is usually installed on a low resource server or workstation located near user file servers, project shares, or other centralized locations where PST files are typically stored. Once a CUA is configured, file servers can be designated as “Central Servers” that the CUA will use to copy files from their original location to the PST Flight Deck server’s upload location and resume a typical workflow. With sufficient rights, the CUA can also be used for a “Forced Migration”. This will expedite uploading a user’s PST files and bypass the Migration Agent.

The CUA may be used for either Transparent or Disconnect modes of migration.

Installation

The CUA needs sufficient permissions to access, copy, and remove PST files from their original location. On file shares, the account will need read/write share and file system access. If you intend to use the CUA to perform “Forced Migrations” the account used to run the CUA will need sufficient rights to access the administrative share on locations where PST files are located. To ensure stability and supportability, ensure the system requirements are met prior to installing the CUA.

To install the Central Upload Agent:

1.Log onto the machine where the CUA will be installed as an account with sufficient rights to perform the installation.

2.Execute the CUA MSI installer: CentralUploadAgent.msi

3.Follow installer prompts to provide the following information:

b.Review and accept the License Agreement

c.Provide credentials with sufficient rights to access and remove PST files from their discovered locations

d.Select Check and Next when available

e.Provide the desired installation path of the CUA

f.Provide the Core PST Flight Deck server name or alias and method of communication to the server

g.Specify the UNC path of the BITS upload location

h.Select Install to begin the installation

i.Monitor the installation and select Finish once completed

Content Scanner

One of the largest challenges of a PST migration project is identifying the proper owner for each of the PST files that have been found on a shared file server. PST Flight Deck Content Scanner is used to scan PST files marked as “Ownerless” or those files located on specific fileservers, and associate ownership based on the contents of the file. This component is specifically useful when scanning project or departmental shares where PST files identified may not have clear owners associated with them.

Installation

The Content Scanner can be installed on the Core server as described above or on another machine using the installer available. All requirements, including proper account access rights, of the Content Scanner should be met prior to installation. For instructions on how to install the Content Scanner on the Core server, please refer to the installation section above.

To install the Content Scanner on a server other than the Core server:

1.Log into the machine where you will be installing the Content Scanner as an account with sufficient rights to perform the installation.

2.Execute the Content Scanner MSI installer: ContentScanner.msi

3.Complete installer prompts providing the following information:

b.Review and accept the License Agreement

c.Supply and validate the account that will be used to run the Content Scanner module

d.Provide Core PST Flight Deck server name or alias and method of communication to the server

e.Select Install to begin the installation

f.Monitor the installation and select Finish once completed

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating