The Pst capture tool for Exchange has – finally -been released (see the following link for more information)

http://blogs.technet.com/b/exchange/archive/2012/01/30/pst-time-to-walk-the-plank.aspx

It consists of two components that will be deployed separately: The ‘server’ component that will retrieve the scan lists and from where you will ‘manage’ the operations, and the client agent that will actually scan the computer to find the psts.

While the server installation is documented, the client agent, although pretty simple to install, is not and there is no built-in Push of the client from the Console.

There are two agent versions : one for 32bits, one for 64bits platform.

You can change the port being used by the agent when it communicates with the server host (by default it is port 6674). If you do so, do not forget to apply the change also when you install the server component. (to change the port, add the SERVICEPORT property to your command line)

On the other hand, you Need to define the Dns name of the Server component that the agent will communicate with. This is done via the CENTRALSERVICEHOST property.

Those Properties are available via Msi Transforms or by adding them to the command line.

The command would look like this:

32bits platform client:

Msiexec /i PSTCaptureAgent_x86.msi CENTRALSERVICEHOST=myhost.mydomain.com /!qb-

64bits platform client:

Msiexec /i PSTCaptureAgent.msi CENTRALSERVICEHOST=myhost.mydomain.com

Since there is no builtin detection of the platform by a separate setup that would install the correct client, you will need to deploy it via different collections or via a task sequence that would verify the type of Operating System for you.

Note that the 32bits version installs on 64bits OS, but the 64bits version should be installed on 64bits OS for better performance and would fail on 32bits OS.

In order to do this easilly, you create a task sequence with two ‘Install Application’ steps.

On the conditions tab, you verify that the following key exists:

HKEY_LOCAL_MACHINE\SOFTWARE\wow6432Node

If you are running a 64bits OS, this key will be present, otherwise not.

 

Finally one little remark that might save you some time: for the Host server, you should use a dedicated 64bits server (not an existing Exchange 2010 server) where you install the console and Outlook 2010 64bits.

Advertisements