Export users mailbox from exchange 2010

Exporting Mailboxes with Exchange Server 2010 SP1

Exchange Server 2010 Service Pack 1 introduced a new method for exporting mailboxes called Mailbox Export Requests. This new method replaces the previous Export-Mailbox command.
Before we look at how to create a new mailbox export request in Exchange 2010 SP1 there are a few things that you should understand.
Firstly, no accounts are granted the rights to export mailboxes by default. You need to explicitly grant these rights, even to accounts that are organization administrators.
Secondly, the mailbox export request is processed by the Client Access server role. Because multiple Client Access servers can exist in a site the request could be processed by any one of them. To ensure that the path to the export PST file is valid for any Client Access server it has to be a UNC path to network share, not a local path.
Granting User Rights for Mailbox Exports in Exchange 2010 SP1
The first step is to grant the right to export mailboxes to an account in your organization. In the Exchange Management Shell run the following command.
New-ManagementRoleAssignment –Role “Mailbox Import Export” –User Administrator
If you’re logged with that user already simply restart your Exchange Management Shell session to be granted access to the new cmdlets.
Creating a Network Share for Mailbox Exports in Exchange 2010 SP1
Next we need to create the network share that will be used as the file path for the exported PST files. All that is required here is a network share that the Exchange Trusted Subsystem group has read/write permission to.
Exporting a Mailbox with an Exchange Server SP1 Mailbox Export Request
With everything configured properly we can now use New-MailboxExportRequest to start the mailbox export. The only two required parameters for the command are the file path to the export PST file, and the name of the mailbox to export.
[PS] C:\>New-MailboxExportRequest -Mailbox “adrian.chatto1” -FilePath \\dserver\pst\davelister.pst
To view the status of the request uses the Get-MailboxExportRequest cmdlet.
[PS] C:\>Get-MailboxExportRequest
Name Mailbox Status
—- ——- ——
MailboxExport KPS/Company/Users/Head of… InProgress
You can also see more detail about the mailbox export request with Get-MailboxExportRequest.
An easy way to see the progress of all mailbox export requests is to pipe Get-MailboxExportRequest into the Get-MailboxExportRequestStatistics cmdlet.
[PS] C:\>Get-MailboxExportRequest | Get-MailboxExportRequestStatistics
Name Status SourceAlias PercentComplete
—- —— ———– —————
MailboxExport InProgress Adrian.chatto1 20
Exporting an Archive Mailbox with Exchange Server SP1 Mailbox Export Request
You can also export a user’s Personal Archive using mailbox export requests simply by adding the -IsArchive parameter to the command.
[PS] C:\>New-MailboxExportRequest -Mailbox davelister -FilePath \\dubbur-fs01\pst\davelister.pst -IsArchive


OWA not working for Mailbox (MB) in remote location – Its all about the proxy!

One site, MB and CAS server all in one site. OWA worked with no issues.

Moved mailbox to another Site and OWA broke.

I had to change the settings on the remote location (MB Locations) for OWA:

Server configuration – > Client Access -> go to the server in question (the MB server) -> OWA (Default Web Site) -> Authentication -> change to “Integrated Windows Authentication” and on general tab, set external URL to nothing.


Getting “Crawling” or “Failed” for Content Index State for databases in DAG over WAN links?

In PowerShell run this “Get-MailboxDatabaseCopyStatus | fl name, contentindexstate”

If a DB has failed or Crawling next to ContentIndexState do this:


1. Restart the MSExchange Search service

2. Update-MailboxDatabaseCopy -Identity DB4\MB3 -CatalogOnly

3. Run “Get-MailboxDatabaseCopyStatus | fl name, contentindexstate” again to confirm