Hello everyone,
I've been running into hurdle after hurdle trying to migrate an organization of 25 Users into our hosted Exchange Environment.
First, the export, I used exmerge to export the mailboxes from 2003 to a PST file.
(really wish I could restore a BackupExec backup from 2003 to 2010.)
Because of the 2GB file limit for Exmerge I ended up exporting the mailboxes in 6month chunks.
I found this would keep the PSTs under 2gb for even the heaviest mail users.
This was the first pain in the A. Is there a version of Exmerge (or another utility) that will export a PST in unicode? (supporting the 20GB max file size)
Ok now the import,
I started off scripting the the imports using >New-MailboxImportRequest
I ran this and it put everything into Queue.
After 3 days I had a mix of completed, failed, in process, and queued jobs.
I tried re-running some of the failed jobs with -verbose, but this just gives me a detailed output until the import request is queued, then it runs (and fails) without much explaination. (maybe I'm missing a log location to check here)
So, Then I started logging in as each user and importing each of the 12 PSTs for each user by hand (yes getting slow and unmanagable at this point, thank god I'm working on 25users and not 250.)
Then on some of the Imports they still fail. with an error (your mailbox is out of space error)
I found this happened at 2.3gb for each user that failed. (hosting package is set for 5GB mailboxes)
Now I'm running SCANPST.exe against all of the mailboxes with import problems.
most have errors (why would this be when ex-merge said successful!!!)
Usually 2 runs of repairs with SCANPST get the PST to a point where it is clean.
I'm hoping once this is done the PSTs will import, or even maybe be able to be imported with the New-MailboxImportRequest commandlet.
there must be an easier way!
Thanks for any help!
-Ryan
-Ryan Biddle-