IT_Fanatic
asked on
Download exchange mailboxes
We have a customer who’s exchange on premises server has been decommissioned and have been on office 365 for 6 years.
I need to get emailed from several users on the old server. How do I go about this? The server is online all
I did was just Disable All exchange services when we went live on 365.
I need to get emailed from several users on the old server. How do I go about this? The server is online all
I did was just Disable All exchange services when we went live on 365.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Exchange 2010 standard. It's on a VM. I rather a third party tool if it's easier. If not the normal Microsoft way is fine for me.
the powershell command if you going to do the MS way is
make sure you have full permissions to the share where you dump it otherwise the command fails
the share can be on the local server
New-MailboxExportRequest -Mailbox ITFanatic -FilePath "\\SERVER01\PSTFileShare\ITFanatic.pst"
make sure you have full permissions to the share where you dump it otherwise the command fails
the share can be on the local server
Hi,
I would consider exporting *all* the mailboxes to PSTs while you are at it, then you can archive those PSTs in case you ever need to do the same again.
To do that from PowerShell (I would recommend against using any third-party tools on an Exchange Server ever):
The 'Sleep 180' is a three minute pause between each export - I have had problems in the past running them without a gap.
Change the location (\\BackupServer\PSTs\) to whatever suits, but make sure you have plenty of space there (I normally go for at least twice the size of the total mailboxes as reported by Exchange).
You can go without the '-BadItemLimit 50' and '-AcceptLargeDataLoss' but you'll probably have errors - I usually go with them, and if I want to be really sure, I run it twice to have two separate backups to archive.
All the usual caveats about requiring sufficient permissions at all points in the process of course.
Depending on the volume of data / emails, it might take a long time, but usually I don't care, I just set it off and let it run over a weekend or whatever.
Hope that helps,
Alan.
I would consider exporting *all* the mailboxes to PSTs while you are at it, then you can archive those PSTs in case you ever need to do the same again.
To do that from PowerShell (I would recommend against using any third-party tools on an Exchange Server ever):
ForEach ($MailBox in (Get-Mailbox)) { New-MailboxExportRequest -Mailbox $MailBox -FilePath "\\Backupserver\PSTs\$($MailBox.Alias).pst" -BadItemLimit 50 -AcceptLargeDataLoss ;while ((Get-MailboxExportRequest -mailbox $MailBox | ? {$_.Status -eq “Queued” -or $_.Status -eq “InProgress”})) { Sleep 180 } }
The 'Sleep 180' is a three minute pause between each export - I have had problems in the past running them without a gap.
Change the location (\\BackupServer\PSTs\) to whatever suits, but make sure you have plenty of space there (I normally go for at least twice the size of the total mailboxes as reported by Exchange).
You can go without the '-BadItemLimit 50' and '-AcceptLargeDataLoss' but you'll probably have errors - I usually go with them, and if I want to be really sure, I run it twice to have two separate backups to archive.
All the usual caveats about requiring sufficient permissions at all points in the process of course.
Depending on the volume of data / emails, it might take a long time, but usually I don't care, I just set it off and let it run over a weekend or whatever.
Hope that helps,
Alan.
ASKER
Which services do I need to turn on since I have them all disabled?
I would pull the network cable from the machine, re-enable all the services you disabled, reboot, run the above command, then disable the services again, reboot again, and plug in the network cable while it restarts.
Alan.
Alan.
Is it a VM? if so and you have access to the console you could disconnect the network , connect to the console and start at least the information store (may need other services)