S
stjulian
Outlook 2003, standalone mode, no Exchange.
When I had to upgrade a machine from Outlook 2000 to 2003, where the .pst
was in the older format (and almost the 2Gb limit), I created a new version
..pst to deliver the mail into, and imported from the the old file into the
new file. All of the mail accounts are set to download the messages and
leave a copy on the server. I have this problem in a few situations.
But, Outlook didn't recognize that the mail messages it was downloading are
already downloaded and downloaded hundreds of copies into the new message
store. The result is an annoyed employee.
Is there a way to prevent this in the future, to make sure that messages
left on the server are not re-downloaded, especially when I must upgrade the
..pst to the new version to allow for a larger message store?
Is there a best practices on upgrades of this nature?
Also, is there a way to de-dupe these downloaded messages so I can clean up
this mess?
Julian
When I had to upgrade a machine from Outlook 2000 to 2003, where the .pst
was in the older format (and almost the 2Gb limit), I created a new version
..pst to deliver the mail into, and imported from the the old file into the
new file. All of the mail accounts are set to download the messages and
leave a copy on the server. I have this problem in a few situations.
But, Outlook didn't recognize that the mail messages it was downloading are
already downloaded and downloaded hundreds of copies into the new message
store. The result is an annoyed employee.
Is there a way to prevent this in the future, to make sure that messages
left on the server are not re-downloaded, especially when I must upgrade the
..pst to the new version to allow for a larger message store?
Is there a best practices on upgrades of this nature?
Also, is there a way to de-dupe these downloaded messages so I can clean up
this mess?
Julian