Video Screencast Help

PST Migration

Created: 26 Oct 2012 • Updated: 01 Apr 2013 | 2 comments
This issue has been solved. See solution.

Hi,

I will be needing to import a large number of PST files for about 80 users into our vault. Is it easier to use PST migration components or use manual import PST process.

Do I need an additional licenses for using PST Migration under EV? I do see PST Migration options under policies.

Any advice...!!

Comments 2 CommentsJump to latest comment

JesusWept3's picture

depending on the license you may find you can't import PST files, but thats really easy to test.

The easiest option for importing the PST files is most likely through EVPM if you have the PST files already in a centralized location and know which PST file belongs to who

Take a look at rob wilcox's article regarding migrating PSTs via EVPM
http://thingsilearnedtoday.net/2010/10/19/scripted-pst-migration/

SOLUTION
RahulG's picture

If majority of the PSt file exist on the client machine a tipical stratergy would be as follows 

1. Enable user for archiving and make sure you enable PST marking in the desktop policy .

2. Once archiving of the mailbox backlog is complete you can enable client driven migration in batches.

3. Use server driven migration if there are PSt files on the servers.

4. Then use the PST migration wizard to archvie the remaining PST fies.

If the majority of the pst files on the file server , you can simply skip the client driven migration and use server driven migration .

I guess the license is based on the data i.e Per Gb I am not sure .