|Subject:||Difficulties importing Outlook 2003 PST files into Exchange using EXMERGE|
|Posted by:||Joseph Keegan (jkeeg…@ctny.net)|
|Date:||Mon, 04 Jun 2007|
When someone using OUTLOOK 2003 creates a PST to store their email in
(usually an ISP account, with Outlook NOT connected to an Exchange
server), the default way that the application (Outlook 2003) creates
the PST file is with ENCRYPTION. This allows a password to be put
onto the PST to protect it, among other seldom-used features. The one
large DETRIMENT to this, however, is that IMPORTING this format of
file into Exchange server using EXMERGE is impossible, because EXMERGE
does not understand the encryption.
RESOLUTION: 3 possible.
1. From the Outlook client, export the mail to a pst file (file -->
export), and when prompted for the type of PST file, make sure to
select NO ENCRYPTION. This will create a new PST file that has the
exact contents of the original one, however, this one will be
IMPORTABLE into Exchange using Exmerge. Copy the new file to the
Exchange server, run Exmerge, and import.
2. Create a new PST file within the user's Outlook profile. Make
sure that the PST file created does NOT have encryption. Copy the
root of the mailbox to the new file. Close Outlook, copy the new file
to the Exchange server, run Exmerge, and import.
3. Export the mail to a pst file (file --> export), connect the user
to their new empty Exchange mailbox, and import the pst file into the
mailbox using Outlook (file --> import).
Note: ** Yes, #2 is basically the same as #1, but I've seen scenarios
where #1 did not work and #2 did.
** #3 should be used when you're not having any luck with #1
or #2, and need to get the task DONE already, and quickly.
The results are the same, so use #1, #2, and #3 interchangably. I
personally like to use #1 exclusively, unless I run into errors,
because it allows you to gather ALL of the PSTs and import them all at
the SAME TIME. Being that the most likely reason to use these methods
or utilities is while moving people that never had an Exchange server
ONTO an Exchange server (Usually because they finally decided to grow
up and buy an Exchange server), #1 is the most efficient method as it
imports everything in one fell SWOOP.