Import-mailbox problem
I am trying to import .pst files into exchange 2007 sp1. The import includes all the default folders from the .pst, but does not include any of the custom folders. Is this a limitation in the Import-Mailbox cmdlet, or am I doing something wrong?
December 7th, 2007 7:58pm

Nope the Import-Mailbox with only the -PSTFolderPath parameter normally imports all folders in the respective PST file. So you run the following cmdlet? Code BlockImport-Mailbox -Identity <alias> -PSTFolderPath: <path to PST>
Free Windows Admin Tool Kit Click here and download it now
December 7th, 2007 10:57pm

That is what I have been running, but it is only importing e-mail from Inbox, SentItems, Drafts, etc. It is not importing any e-mail from folders that were created by the user.
December 7th, 2007 11:41pm

just a thought, but I presume you have opened the PST in Outlook & actually made sure additional folders exist other than the defaults? I used the same command above to import 250+ mailboxes from PST with no problems what so ever.
Free Windows Admin Tool Kit Click here and download it now
December 9th, 2007 7:42pm

Yeah I've used it quite extensively too, and never seen an issue similar to this. Last problem I had was in the SP1 beta 2 days and it was related to something completely else.
December 9th, 2007 10:38pm

No, I agree with Donkey, I initially had a problem whereby I could not import the mailboxes coming from non-exchange psts, the import-mailbox command completed successfully very quickly and in fact did not import any messages. I resolved this by exporting a blank mailbox to the pst, then re-running the import, this worked but still with the same problem as donkey, only the default "special folders" are imported by default it appears. So is there an "allfolders" option to include in the command? Recently upgraded the server to SP1 and was hoping to import 150 psts from previous non exchange mail system and go live asap.
Free Windows Admin Tool Kit Click here and download it now
December 12th, 2007 2:13am

I haveexactly the same probblem!
December 12th, 2007 12:43pm

Same problem.... is there any workaround ? Iam also trying to find some solution for this issue... trying to importusing powershell,a PST generated using outlook 2003which is connected toa non exchange mail system
Free Windows Admin Tool Kit Click here and download it now
December 13th, 2007 9:09pm

A"me too" here. Using a 2003 PST, import-mailbox fails. If I export\merge an empty PST from Exch 2007 on top of the 2003 PST, import works, but only grabs inbox & sent items, none of the other folders that exist in the PST. One more thing -- the 2003 PST opens fine in Outlook 2007 without issue and with all folders showing.
December 20th, 2007 6:10pm

I just got of the phone with Microsoft PSS and they stated that this functionality DOESN'T work with the import-mailbox cmdlet. This will probably be solved in SP2 for Exchange 2007. Instead, they forwarded me a link on how to use exmerge against exchange 2007...
Free Windows Admin Tool Kit Click here and download it now
December 27th, 2007 5:41pm

Well Done BoerLowie, what's the link?
December 28th, 2007 12:34pm

Here you go: http://www.exchangeinbox.com/article.aspx?i=88 The only BIG downside is that ExMerge can't handle Unicode PST's (which is the default PST format in Outlook 2003 and higher), while the import-mailbox cmdlet can do this. So it's a workaround, but in our situation it wasn't a real solution since we have tons of 2003 PST's. Therefor, i had to buy a thirdparty tools to convert the PST's to ANSI format (pr 2003 format), and then import it with ExMerge. Not ideal, but since the import-mailbox cmdlet is useless for these imports, we had no other option...
Free Windows Admin Tool Kit Click here and download it now
January 1st, 2008 9:49pm

I reproduced and documented this problem on ExchangeInbox.com. Even better I found a dirty solution for importing the custom folders. Full details here: http://www.exchangeinbox.com/article.aspx?i=108 Please add a comment to the article if you find anything new!
April 17th, 2008 12:09pm

Haven't tested it yet myself however apparently this problem is now solved in Update Rollup 2 for Exchange Server 2007 Service Pack 1: http://support.microsoft.com/?kbid=948016
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2008 12:43pm

To import PST files using exMerge tool, firstconvert unicode pst files to ansi pst file with PSTUPGRADE software from http://www.pstupgrade.com. Once pst files gets converted to Ansi format you can import them with exMerge tool.
June 28th, 2008 2:36pm

Yeap, this problem is now solved in Update Rollup 2 for Exchange Server 2007 Service Pack 1. I tested it and it worked fine.
Free Windows Admin Tool Kit Click here and download it now
July 25th, 2008 6:56pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics