I have huge headache. We are thinking of upgrading our Exchange server to MS Exchange 2000 Server. I have printed out around 4 thick folders with various TechNet/KB docs (btw, I've compiled it all to a 20mb PDF. If anyone wants it, leave your e-mail address, and i'll send u an URL to DL from).

Now to the headache. I've found out that even a simple thing as "forklifting" users between servers can be a read pain, and you almost always end up having some trouble with synchronization, clientupdates to servers etc etc. I'm afraid i'll only end up with alot of warnings and errors if I choose this way...

So I thought (and was also actually recommended) that the absolutely easiest and "clean" way to do this was to:

1. Export the user's mail, contact list, and calendar to a *.pst on their own machines.
2. Generate a PRF to implement the new Exchange server in the client's Outlook (perhaps even the generation of a new mailbox for the user if a backup *.pst is found could be automated?).
3. Import the *.pst to their new account.

No servermigration problems, no sync problems, and *much* less work, I believe? and as a bonus, you get a *clean* server installation.

Anyone around here with experience? I've seen some good *.PRF examples. But is it possible to fully automate a full *.pst backup of all client Outlook data (and perhaps also generate new mailbox's)?