How to Export .pst directly from Exchange 2003 database

Hi,
 
I need to migrate several user mailboxes from EXCH 2003/SBS2003 into EXCH 2010/SBS2011. Client Outlook will also change from Outlook 2003 to 2010 version.
I know I can go to each user OUTLOOK 2003, create a PST, copy it to an external USB drive, copy it to the new workstation and import PST into Outlook 2010.
However some users have close to 10GB of data and last time when I tried to create a PST file from his OUTLOOK 2003, it took literally hours to complete.

The reason for the long time was partially because the data has to travel from the server to the workstation via Ethernet cable. So I figure if I can somehow create a PST file directly from Exchange 2003 server and save it to the folder on SBS2011 folder, it would be a lot quicker. After creating PST for each mailbox, I can just copy all PST files to external USB all at once and move them to the new server/SBS2011 and import them directly into Exchange 2010.

Can you help?
sgleeAsked:
Who is Participating?
 
Cliff GaliherConnect With a Mentor Commented:
Unfortunately the server tool for exporting mail in 2003 (called exmerge if you are curious) has a 2GB file limit. Given one of your issues is you have 10GB+ mailboxes, that makes exmerge unsuitable.

You really have two choices:

1) Install SBS 2011 in migration mode. This preserves AD and allows the two exchange servers to communicate directly. Moving mailboxes in this scenario is trivial.

Offline migration methods, like a swing migration kit keep the same basic premise as above, but offer other improvements. If you chose to "build fresh" because of concerns around migrating, a swing kit lets you get the best parts of a migration and avoid the pitfalls. Highly recommended.

2) Or use outlook to export, with all of those drawbacks. If you have a gigabit switch and you have hardware that supports gigabit, you could plug a laptop and the server into the switch (even a small 4 port switch would be suitable) just for the export process. At gigabit speeds, you'll often see that the disks become the bottleneck instead of the network, so you could avoid SOME of the downtime issues.

So... sadly.... no great answers. Only a matter of which compromises you can live with.
0
 
sgleeAuthor Commented:
What is swing migration kit?

I think I will simply log into SBS2003 with each user account using REMOTE DESKTOP and configure OUTLOOK for each user and create & save a PST directly on SBS2003 Server folder.
At least I will avoid Ethernet cable travel time.
0
 
Cliff GaliherConnect With a Mentor Commented:
Installing outlook on SBS 2003 breaks Exchange. Don't do that.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
sgleeAuthor Commented:
I am glad that I heard from you before attempting to do so.
I am just curious how setting up Outlook on SBS2003 will harm Exchange ...
0
 
Cliff GaliherConnect With a Mentor Commented:
Exchange has a set of DLLs for MAPI. Outlook has a different set of DLLs for MAPI. They are not interchangeable. So installing outlook breaks exchange because not all MAPI calls exchange expects works.
0
 
sgleeAuthor Commented:
Thanks fro the information.
The network already has Gigabit network including Cat 5e cable and Gigabit switch.
Even so, dumping 9GB of data took HOURS.
0
 
sgleeAuthor Commented:
But this software costs $500 to $1,000.
For several mailboxes,  I will just go thru inconveniences.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.