Installing & Using the Microsoft PST Capture Tool–Part 1…

by Andy Grogan on February 13, 2012 · 13 comments

in Exchange 2010 (Compliance), Exchange 2010 (General), Exchange 2010 (Mailbox), Mailbox Databases

The PST Capture Tool was released on the 30th Jan 2012 (see: http://blogs.technet.com/b/exchange/archive/2012/01/30/pst-time-to-walk-the-plank.aspx for more information) after a fairly long and highly anticipated wait by the Exchange Community.

In essence the PST Capture tool has two main tiers of operation:

  1. PST Capture Central Service The PST Capture Central Service maintains the knowledge of the PST files found within your organisation and processes the data as it’s moved to your internal (on-premises) Exchange servers or Exchange Online Accounts.
  2. PST Capture Agent Discovery of PST files on remote machines is performed by the PST Capture agent that is installed locally on computers within your organisation. The agent Service will also send the relevant PST files to the Central Service Server when requested for Import operations.

There is technically a 3rd tier to the PST Capture Tool which is known as the PST Capture Console – which it the primary management interface that is used by administrators to locate the relevant PST’s on machines and manage the process of PST imports into mailboxes.

Before you crack on and install the tool there are a few Pre-Requisites that you should be aware of before you begin (these are taken from: http://technet.microsoft.com/en-us/library/hh781033.aspx):

  • If you intend to import the captured PSTs to an on-premises Exchange server, your organization must be running Exchange 2010

NOTE: The tool can be used with Exchange 2007, but it is important to point out that it has NOT been tested with 2007 – therefore if you run into problems then you are unlikely to be supported by Microsoft.

  • If you intend to import the captured PSTs to Exchange Online, your organization must have an Office 365 or BPOS subscription.
  • Microsoft .NET Framework 3.5 or 3.5 Service Pack 1 (SP1).
  • 64-bit version of Microsoft Outlook 2010 (required only on the host computer where you install the PST Capture Console).
  • A Central Service account. Depending on how you plan to use PST Capture, you must grant specific rights to the service account (these are detailed below).
  • The server which you choose to install the Central Service must be Windows 2008 x64 or R2.

Quick Tip (from painful experience)

You should ensure that you have all of your domain controllers online and working, especially if you have a configuration that has child domains. Failure to do so could result in the PST Capture Service terminating.

Installation

Download the Tool from the following location: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=28767, ensure that your chosen server which will host the Central Service meets the prerequisites mentioned above.

When downloaded double click on the “PSTCapture.msi” file which will launch the installation wizard (click on the “Next” button) – see below;

pstCaptureTool001

On the EULA screen, tick the “I accept the terms in the license Agreement” and then click on the “Next” button – see below:

pstCaptureTool002

On the “Destination Folder” screen – choose the location where you want the tool installed – personally I would leave it at the default location and then click on the “Next” button – see below:

pstCaptureTool003

You will then be asked to provide the details of the Central Service Account. You will need to ensure that the account that you provide has the following permissions (borrowed from: http://technet.microsoft.com/en-us/library/hh781036.aspx )

Scenario

Permissions required

Installing PST Capture

  • Local administrator privileges on the computer where you want to install the PST Capture Console or PST Capture agent.

Searching for PSTs

  • You must be logged on with local administrator privileges on the computer where you run the PST Capture Console.

Importing PSTs to mailboxes in your Exchange Online (Office 365) organization

  • You must be logged on with local administrator privileges on the computer where you run the PST Capture Console.
  • The user account you specify on the Online Connection Settings tab of the PST Capture settings must be assigned the Organization Management role.

Importing PSTs to mailboxes in your Exchange Online (BPOS) organization

  • You must be logged on with local administrator privileges on the computer where you run the PST Capture Console.
  • The user account you specify on the Online Connection Settings tab of the PST Capture settings must be an Exchange Online administrator account.

Importing PSTs to mailboxes in your on-premises organization

  • You must be logged on with local administrator privileges on the computer where you run the PST Capture Console.
  • The user account that the PST Capture Central Service uses must be mailbox-enabled.
  • The user account that the PST Capture Central Service uses must be assigned the Public Folder Management role in your Exchange organization.

Importing PSTs to archive mailboxes in your on-premises organization

  • You must be logged on with local administrator privileges on the computer where you run the PST Capture Console.
  • The user account that the PST Capture Central Service uses must be mailbox-enabled.
  • The user account that the PST Capture Central Service uses must be assigned the Organization Management role in your Exchange organization.

When you are happy with your choice – click on the “Next” button – see below:

pstCaptureTool004

You will then be presented with the Review of your installation choices – review them and if you are happy click on the “Install” button – see below

pstCaptureTool005

The installation process will then complete – when done click on the “Finish” button – see below:

pstCaptureTool007

In the next part:

I will cover the following:

  • The installation of the PST Capture Agent including automated deployment.
  • Using the PST Capture Tool

{ 11 comments… read them below or add one }

Leave a Comment

*

{ 2 trackbacks }

Previous post:

Next post: