Importing PST into Migrated Mailbox

HELLO ALL,
When migrating from lotus to exchange, if the message that are encryted, they are skipped, but the rest of the messages are moved to the new mailbox. If one
makes a PST using some third party software and import the pst into the mailbox, would the messages come into the folder structure present in the mailbox. For instance if Folder A contained encrypted messages at lotus domino,
but when migrated, it became empty at exchange. So, if we import the PST into mailbox, would the Folder A be showing us the messages that were present at lotus?
thanks in advance.

Hi,
If that is encrypted, then message will need to have certificate to be opened, I think.
Xiu Zhang
TechNet Community Support

Similar Messages

Exchange 2013 - Folders missing when importing PST to archive mailbox

Hello,
I'm having an issue when importing PST files to an Exchange 2013 archive mailbox using the command "New-MailboxImportRequest
test -FilePath '\\server\e$\ArchiveExport\test.pst' -IsArchive -BadItemLimit 5 -ErrorAction Stop"
The import is running without an error and shows the status complete. The size of the archive mailbox is exactly the same like the size
of the PST file!
But when I check the users archive mailbox some folders are missing. It seems that this happens only to default folders like "Inbox"
or "Sent Items". Other folders are visible.
The mailbox import log shows the following:
16.01.15 16:31:56 [server] Merging folder '/Top of Personal Folders/Inbox [Inbox]' into '/Inbox [Inbox]'.
16.01.15 16:31:56 [server] Copying 3 items, 4.789 KB (4,904 bytes). Skipping 0 items, 0 B (0 bytes).
If I start the import process again the log says the following:
16.01.15 16:46:54 [server] Merging folder '/Top of Personal Folders/Inbox [Inbox]' into '/Inbox [Inbox]'.16.01.15
16:46:54 [server] Copying 0 items, 0 B (0 bytes). Skipping 3 items, 4.789 KB (4,904 bytes).
So it seems that the mails are really there but just not visible.
I did some tests:
When I import the PST file directly to the users mailbox (without parameter -IsArchive) I can see all content of the PST file.
When I add the parameter -TargetRootFolder "Testfolder" the whole PST content shows up correctly under that folder.
Can anyone explain this?
Regards

Hi PhilippMair,
Thank you for your question.
If all subfolders were merged, we could use OWA to check if the missing folders is appeared. If we could see missing folders by OWA, I suggest we recreate outlook profile and reset outlook view.
In order to troubleshooting, I suggest we collect the import log to analysis if the subfolder of Inbox or Sent Item is exported.
In my test lab, inbox has three subfolders, there are 123,456,789; when I import PST file, I will see the following log:
1/20/2015 7:32:31 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox' into '/Top of Information Store/Inbox'.
1/20/2015 7:32:31 AM [EXCH2-CU1] Copying 18 items, 302.3 KB (309,594 bytes). Skipping 0 items, 0 B (0 bytes).
1/20/2015 7:32:32 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/123' into '/Top of Information Store/Inbox/123'.
1/20/2015 7:32:32 AM [EXCH2-CU1] Copying 5 items, 62.21 KB (63,699 bytes). Skipping 0 items, 0 B (0 bytes).
1/20/2015 7:32:33 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/456' into '/Top of Information Store/Inbox/456'.
1/20/2015 7:32:33 AM [EXCH2-CU1] Copying 1 items, 6.908 KB (7,074 bytes). Skipping 0 items, 0 B (0 bytes).
1/20/2015 7:32:33 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/789' into '/Top of Information Store/Inbox/789'.
1/20/2015 7:32:33 AM [EXCH2-CU1] Copying 1 items, 21.31 KB (21,820 bytes). Skipping 0 items, 0 B (0 bytes).
We could check if there are any subfolder which would not be merged and copied. If your import log has any abnormal, I suggest you send log file to
[email protected] for our troubleshooting.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Winmail.dat attachments after importing PST into online archive

Hi, we enabled the online archive feature on one of our Office365 exchange account. Later, we used the PST capture tool to import a PST file into the archive. Now after importing, the user came back saying he sees winmail.dat files as attachments. Prior
to uploading the PST to the online archive the attachments were visible normally. The PST file belongs to the same user. Its an old PST file attached to his mailbox since a long time. We then subscribed to the online archive plan for his account and used the
PST capture tool for importing the emails. To isolate the cause of the issue we tried dragging an email with an attachment from themailbox to the online archive from within Outlook. The moved email appeared correctly with attachment in his archive. We have
not tried importing the whole PST from within outlook, as the size of the PST is too large (32 GB). Could someone please help resolve the issue.
Thanks in advance.

I recommend that you post this in the Office 365 Exchange Online Forum:
http://community.office365.com/en-us/forums/158.aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

How can I import contacts into a mailbox and overwrite the previous ones?

Hey guys, so I am new to powershell. I understand some of the basics and am still trying to teach myself as much as I can.
So I have been asked to automatically push our company's contacts to everyone's mailbox (around 60-70 contacts to 60-70 mailboxes) We use Office 365.
They also want the contacts to sync to mobile phones, so I cannot used a shared contact list. It seems only the MAIN contact list can sync to a phone.
So far I have used this:
import-contactlist -csv -csvdata ([system.io.file]::readallbytes("PATH TO CSV FILE")) -identity USER
This works just fine, but if there are any changes to the CSV and I run it again, it just doubles all the contacts instead of overwriting. Is there anyway I can overwrite the contacts?
I have also tried this:
Search-Mailbox -identity USER -SearchQuery kind:contacts -deletecontent
This does delete the contacts I have created in the first place, but if there are any OTHER contacts that users have created, it would delete those as well.
I feel like im headed in the right direction.. can anyone help?

Okay I think I figured it out. After I import the contacts with: import-contactlist -csv -csvdata ([system.io.file]::readallbytes("PATH TO CSV")) -identity USER
I can run this to find and delete each added contact:
$tcontacts = get-content PATH TO CSV WITH ONLY NAMES
$zcontacts = get-content PATH TO CSV WITH NAMES OF MAILBOXES YOU WANT TO REMOVE CONTACTS FROM
$ccontacts = "null"
$scontacts = "null"
$xcontacts = "null"
foreach ($ccontacts in $tcontacts) {foreach ($scontacts in $zcontacts) {$xcontacts = $scontacts; Search-Mailbox -identity $xcontacts -SearchQuery kind:'contacts', $ccontacts -deletecontent -force}}
I use xcontacts = scontacts because of pointer issues (i think?) but anyway, using
$scontacts for the -identity doesnt work.
This is a pretty rough script, and you guys could probably find a shorter one, but it works! Thanks

Import multiple PST files for a single user into archive mailbox is failing

Most of our users that have PST files have between 2 and 10 separate PST files named by either subject or year.
I am trying to find a way to automate using New-MailboxImportRequest to import ALL of the psts found within a user's shared folder.
I found a script that others says should work, but it doesn't work for me.
One of the problems is that that the commands are spread over several lines. I have tried entering it line by line but it still errors out.
First, how can I run a multi-line command?
Second, can anyone see an error in the script below?
I do change the server name, share name and mailbox alias to the actual values before running.
I am trying the script below and it fails:
$filepath=”\\server\usersfileshare”
$items=get-childitem -path $filepath -filter *.pst
foreach($item in $items)
{$location=$filepath+”\”+$item.Name
New-MailboxImportRequest -mailbox mailboxalias -isarchive -filepath $location}
The error says:
Unexpected token 'items' in expression or statement.
At line:1 char:51
+ $filepath="\\servername\usersfileshare" $items <<<< =get-childitem -path $filepath -filter *.pst foreach ($item i
n $items) {$location=$filepath+"\"+$item.Name New-MailboxImportRequest -mailbox mailboxalias -isarchive -filepath $location
+ CategoryInfo : ParserError: (items:String) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : UnexpectedToken

You can have check this
thread which has been discussed earlier with similar concern.
Here is another helpful
Blog reference. Please check this.
Moreover, you can have also check this
automated option which would be very helpful in terms of importing PST files into live exchange mailboxes.

Powershell command to migrate Exchange 2007 mailbox databases with a legacy name, & import them into a new 2007 instance, with a new name.

Hi All. I am currently at the later stage of provisioning a new CCR Exchange 2007 migration (to
virtualise old Exchange 2007 hardware) for 5,000 users & have a quick question.
I have created around 15 newly named storage groups, & have named 1 new DB per group, with the same name (let's say New-DB-1), residing within them. The problem I have, is the old legacy DB's have different names (let's say Old-DB-1) & I need
to import them into the new storage groups, to match the new names. So far I can import/export between old & new OK if both old & new DB names\folders etc. names marry up perfectly, but are unable to if there not the same. Does anyone have any thoughts
on how best to tackle this, as this is one of the final hurdles stopping the migration? Many Thanks, John

Hi All
Many Thanks for the feedback.
The terminology 'migrate' was used based around the fact I will be decommissioning the old 2007 physical environment. This is after moving all DB's over to the new newly created Virtual environment that will host all roles.
The solution I ended up using yesterday, was the following:
1) Dismounted the relevant named DB (NEWDB) in the new environment.
2) I then ticked the 'This database can be overwritten by a restore option' box.
3) Copied over the old named DB (OLDDB) to the same location, & overwrote using the new name (NEWDB).
4) Re-mounted the (NEWDB).
5) Ran the following 2 PowerShell commands:
Get-mailbox –database OLDDB | move-mailbox –targetdatabase NEWDB -configurationonly:$true
Get-MailboxDatabase NEWDB | ResetSearchIndex.ps1 -force
6) Checked to make sure the clients were working ok, in the now the new (NEWDB) environment.
Rich: Many thanks for your PS script, which I will test with future DB moves & provide feedback
J
John.

Import PST of mailbox has been queued indefinitely

Hi,
I have issues importing PST files to user mailboxes, the queue never starts, I have tried removing tasks, re-adding tasks, tried different PST files, tried different folder locations for the PST files, tried multiple mail boxes and even restarted the replication
service all to no avail.
I have also waited a long time for them to finish but there is little progress, I can see that one of the users has a few folders and a couple of emails in there archive folders now but there is no report of a percent completed.
Does anyone have any suggestions for me please? In past this has worked on this server, note when it did work I only imported PST files to current user mailbox not archive folders.
Kind Regards
Anthony

Hi,
According to your description, you want import PST file into archive.
If I misunderstand your meaning, please feel free to let me know.
If yes, we can try the above suggestion: add the parameter IsArchive in the command New-MailboxImportRequest.
http://technet.microsoft.com/en-us/library/ff607310(v=exchg.150).aspx
Additionally, to narrow down the cause, we can check the event log and find if there is any error.
Thanks,
Angela Shi
TechNet Community Support

Importing PST file using Import-Mailbox Command Crashes Powershell

I am attempting to import a .pst file into a mailbox via the Import-Mailbox powershell command. The command starts and imports the deleted items and creates the folder structure in the Inbox then crashes powershell. I am running Outlook 2007 SP2 on a Windows 2003 Std SP2 server w/Exchange 2007 SP1 Update Rollup 8 management tools. I have tried everything i can think of. This happens on multiple machines with similar packages installed. No anti-virus software is installed. It happens on both pst files i am testing with and no errors are logged in the event logs either on the exchange mailbox server or the server i am using to do the import.

Have you tried to do this from the actual Exchange 2007 server? I assume you are trying to import the pst to an Exchagne 2007 email account to Exchange 2007 correct?
Have you tried to perform the import on a Windows XP machine using the 32bit EMC/EMS rather then using Windows 2003 server?
I honestly recall in the back of my head a problem with Exchange 2007 and Outlook CDOs or something like that. I could be wrong but I remember something from a year ago.....
Seriously though, try it from a Windows XP machine running the Exchange Managerment Tools and see what happens rather then a W2K3 Server.
SF - MCITP:EMA, MCTS
Yea I double check the link i posted as well I never tried from a 2003 server either, I've always done it from an XP machine, but again we know its works because you got it to work with a newly export PST, so I think its more to do with the PST file itself, hopefully you dont have a bunch of them, if so let the users re-import them =)

Exported and later Imported .pst files retain the permissions from the original Mailbox.

After migrating from Exchange 2003 to 2010 something strange happens when exporting folders to a .pst file and importing them in another mailbox.
The acces right that are applied, are those from the original mailbox.
I have been searching on the internet about this strange behaviour, but it seems our organization is the only one where is applies.
Does anybody have any ideas what can be the cause?

Hi,
For example, userA was granted permissions to the Inbox folder of userB's mailbox. You exported userB's Inbox folder to PST file and then imported to userC's mailbox. After that, userA had permissions for Inbox folder in userC's mailbox as well. This is
what you had encountered, is it right?
Generally, permissions aren't preserved when you export folders to PST file, only the content itself is exported. I recommend you remove this mailbox folder permission using the Remove-MailboxFolderPermission command to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Export and Import PST corrupting mailbox folder structure

Hi,
I have an old Exchange 2003 mailserver which I am replacing with Exchange 2013 server. I am doing a fresh install in a new domain and will import the old mailboxes (5) via PST's.
I have exported the mail from Exchange 2003 using exmerge to PST files, then imported using the new EAC import PST process. When completed I see that the folders inside the mailbox have corrupt names.
Any ideas?
Cheers
Craig

Hello Craig,
Did you see this issue before you import the pst file (which export with Exmerge)?
If not, I suggest you follow this way to have a try:
Use Outlook to export pst files from Exchange 2003 mailboxes.
Import the pst file to Exchange 2013 mailboxes.
After that, check whether this issue will occur or not.
Thanks,
Evan Liu
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
Evan Liu
TechNet Community Support

How to import PST file into Entourage 2004 ?

Hello all,
I wonder if somebody can help. I just recently threw my Windows PC out and replaced it by an iMac - I just love it !
One thing still challenges me though. I got all the old contacts and emails in a PST file format, Outlook 2003.
Can anybody tell me how I convert/import them into Entourage 2004 ?
Thanks very much for your help in advance
Lenochka

The best way is through an exchange server. If you don't have access to one, then there are two more options from the site mentioned above (http://www.entourage.mvps.org/cross_platform/#pst):
"Other options to convert your Outlook mail into the MBOX format.
Use Mozilla Mail. See Dave Riches tutorial here
Use Paul Berkowitz's Export-Import Scripts download here"

Dear Team, Can we secure "sent msg" that the receiver cannot edit while forwarding/replying? Is possible to import .PST file(S) into thunderbird?

Dear Team,
Can we secure “sent msg” that the receiver cannot edit while forwarding/replying?
Is possible to import .PST file(S) into thunderbird? If yes, any size limit?
Can we convert thunderbird data file in .PST?

I don't think you can prevent email body text from being copied and edited.
You'd probably need to created a protected Word or PDF document, and send it as an attachment.
This is still some sort of guessing because it's still not clear to me what exactly your scenario is.
Whatever text you send in an email, regardless of whether in the body or as an attachment, the recipient will always be able to use that and distribute it further, e.g. by making a screenshot. And images can be 'photoshoped' as well.
If you want the recipient to be able to detect whether a message or an attachment has been altered on transit, you'd need to sign it.

PST Capture error when trying to import .PST files

I am currently migrating mailboxes from Exchange 2010 to Exchange 2013 on prem. I have installed PST Capture 2.0 and 64-bit Outlook 2013 on a Windows 2008 R2 machine and have installed the PST Capture 2.0 agent on a workstation that has some .pst files
on it. PST Capture finds all the .pst files on the workstation, but when I use PST Capture to try to import PST files into a mailbox on Exchange 2013, I get the error "Import error: Error opening mailbox [email protected]".
I created a userID with a mailbox to run PST Capture. Based on the instructions at
https://technet.microsoft.com/en-us/library/hh781035%28v=exchg.141%29.aspx I have made that user a member of the groups that are assigned the Public Folder Management role, the Mailbox Import Export role and the Organizational Management role. The
user is also a local admin on the machine running the PST Capture console. While the error sounds like a permissions issue, these are the only permissions I could find documented for PST Capture. I am starting PST Capture with "Run as administrator"
Any ideas why this isn't working? Are there any other permissions that the PST Capture user needs? Is there anything else I need to do?
Thank you very much for your help.

Generally PST capture tool allows you to search for PST files & import these PST files
to the mailboxes but as your account is not getting connected, so you need to check settings of your PST Capture tool :
https://technet.microsoft.com/en-us/library/hh781032(v=exchg.141).aspx
If this solution does not work out for you, then I would advise you to use any professional
tool for exchange migration like CodeTwo , Stellar. From my personal experience, I would recommend you to go for Stellar Mailbox Extractor for Exchange Server as it migrated my mailboxes to another Exchange Server in quick time.

Import PST files for multiple users at the same time?

While importing PST files into archive mailboxes, the Exchange 2010 mailbox server went to 100% CPU and memory usage and I could not stop the imports because the EMS stopped responding. We had to restart the whole server to get back to normal.
Not sure if importing PSTs was the cause of it it was a coincidence. We have done imports the same way before without this issue.
How many PST imports can be done at the same time and how do we queue up multiple users and have the mailbox imports have unique names for each user? I noticed they are always called MailboxImport and MailboxImport1 and then it starts over as MailboxImport
again for additional users. So, if more than one user's PSTs are being imported at the same time, we will have multiple identically named imports running.
We would like multiple users' PST imports to queue up and start automatically when the previous users' imports complete.

Please try like this. Rename folder name same as alias. i.e. \\server\share\<alias>. below are examples.
"\\server\share\jsmith"
"\\server\share\tjones"
"\\server\share\rsmith"
"\\server\share\bspears"
"\\server\share\mmouse"
And run below command to take PST from the corresponding
foreach ($i in (Get-Mailbox)) { New-MailboxImportRequest -Mailbox $i -FilePath "\\Server\share\$($i.Alias)\$($i.Alias).pst" -baditemlimit 50 -acceptlargedataloss ;while ((Get-MailboxImportRequest -mailbox $i | ? {$_.Status -eq "Queued" -or $_.Status -eq "InProgress"})) { sleep 180 } }
If a folder missing with the alias you will see an error similar to this.I think this will work for you. You just keep only the required PST folders to import in the "\\Server\share" folder.
"Unable to open PST file '\\server\share\mmouse\mmouse.pst'.
Error details: Could
not find a part of the path '\\server\share\mmouse\mmouse.pst'.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MailboxImportRequest], RemotePermanentException
+ FullyQualifiedErrorId : 27802833,Microsoft.Exchange.Management.RecipientTasks.NewMailboxImportRequest"
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Best way to migrate Mailboxes with all permissions Exchange 2010 to Exchange 2010--cross forest

Hi,
Due to some Exchange and Active Directory issues (with remnants of old Ex 2003 server), we are going to migrate Exchange 2010 Mailboxes and public folders to a new Exchange 2010 Sp3 server, which is created in a new AD forest.
I would really appreciate if someone can direct us to the best way to migrate mailboxes and PFs with their permissions, to new Ex 2010 SP3 server. We have around 30 mailboxes, and 300 GB of mailboxes data, and 200 GB of PFdata.
Thanks in anticipation.
Regards, David Johnson

Hello,
Firstly, you need to creat forest trust between two forests.
If you want to move AD user account and mailboxes, please use ADMT and PrepareMoveRequest script.
If you want to migrate public folder, please export data to PST file and then import pst file to new server.
Additional article for your reference.
http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
Cara Chen
TechNet Community Support

Importing PST into Migrated Mailbox

Similar Messages

Maybe you are looking for