Hi Edo,

Here's my 10p worth of wisdom;

A.  I understood that the EVPM script (like the one you have posted) uses the PST migration policy that is set in the Vault Admin Console by default.  Somone please correct me if i'm wrong here, as this will make the following answers null and void ;( 

B.  There's the Message Class tab on the PST migration policy.  Just include the ones that you have available (set at the directory level).  This is of course dependent on the above

C.  You could take a look in the utilities guide for version 8, there might be something in there? http://seer.entsupport.symantec.com/docs/336838.htm

D.  Looks good to me.

Thanks,
BZ

Hi Bz,

Thanks for your first comment on my "Problem", well the EVPM util does not use the Policy Defined in the Admin Console.. (Well not as long as a PST file is not marked)

I used the Utility Guide to add the most essential part in the scripts for PST import. The more you have to define, the more complex the script for large scale import is going to be.

So most of my questions still stand,

- Is there a way to use the PST migration policy defined in the Admin Console, while PST files are not marked.
- the utilities guide does not specify if all items in a pst file (Message Classes) are processed, if I use the shortcut mailbox option, it will place items It does not archive in the   Exchange Mailbox. But no specific Message Classes can be defined in the script.

I Hope some one has a experience with a complete PST import script for unmarked PST files. That is the big issue. Everything would work fine (using the policy) if I was able to mark the PST files before importing. To bad I don't have that change.

Regards,
Edo

Edo,

BZ is correct.  The PST Policy status of  "Default" usually 'Default PST Policy' will be used by evpm where relevent.  Any settings you specify in the script will override the policy.  Message classes, etc are pulled from the default policy.

To enable all message classes just edit the default policy and enable them.

note:In my experience it was NOT possible to import non-expired calendar items via script.  I had a case logged with Symantec:

Heres the response:

ISSUE: EVPM import of recurring expired & non-expired calendar items from PST
 
ROOT CAUSE ANALYSIS: Recurring appointments can only be imported using the PST Import utility.
 
TROUBLESHOOTING STEPS:
1.  Is trying to do PST imports using EVPM, but it is not importing non-expired calendar items
2.  Verified message classes are added; items are being migrated from Lotus Notes
3.  Added HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault\Admin\PSTMArcNonExpiredCalendarItems = 1, nogo
4.  Explained that recurring appointments being imported with EVPM doesn't always work
 
With non-marked PSTs you specify the archive\vault name in the script. 

-Joe