Oddly enough, we just started a mail archive project this week. In the coming week, I'll be implementing a set of scripts that does what you want - sort of.
We are deploying a GPO that prevents users from accessing PST files. Once that's in place, code will be placed in the login script to run on the user's PC. This script will terminate outlook, identify the location of all PST files, rename each PST file so the user and outlook can't find it, then identify the path of the PST (in its newly named form) to a central process. That process will then move the file to a central location. The login process happens in 3-4 seconds, while the background file copy can take quite a while, depending on size. The advantage of this is that many of our users have their PSTs in a central file server where their home profile structure is mapped to. The move will happen server to server.
The backend process will return the file to its original name and log it into the archiving system for processing.
I should be able to post some code in a week or so.
Glenn
_________________________
Actually I
am a Rocket Scientist!
