Exchange online import pst

экспорт почтового ящика в PST файл

Многие наверное сталкивались с необходимостью экспорта почтового ящика пользователя в файл архива почтового ящика т.е. PST файл. В ранних версиях можно было использовать утилиту Exmerge, на сегодняшний день все действия можно производить, а некоторых случаях только из - Exchange Management Shell.

Так как в организации может быть несколько серверов клиентского доступа и нет возможности определить какой из них будет обрабатывать запрос, то импортируемый PST файл должен был расшарен и доступен по UNC пути.

Аккаунт, выполняющий импорт также должен иметь необходимые на это права, так как по умолчанию такие права нет ни у одного аккаунта, даже у администратора организации.

Предоставлению пользователю права на импорт PST в Exchange 2010 SP1

-ContentFilter

Specifies what conditions the contents of a mailbox have to match to be exported into the PST file. The conditions are provided in the form of standard PowerShell logical clauses with several item properties available for filtering (wildcards are supported). Example of a script that exports items received prior to 2013-01-01 with subjects beginning with fwd:

-ExcludeFolders and -IncludeFolders

Just what it sounds like. You can choose from all Exchange mailbox folders. There are also two interesting features available:

  • If the Show Mailbox Size checkbox is selected, it can take much longer to load the list of mailboxes.
  • In larger organizations you can use MAPI to Get Mailboxes from the GAL instead of Remote PowerShell.  Checking this option results in a small performance improvement.
  • If you have a license key for over 1000 users, you can skip Getting All Mailboxes via Remote PowerShell.  You will then have to search for the mailboxes or use a CSV file on the next screen.

The next screen has several options which are described below:

Source Export Options for PST from Exchange Online

It will use the destkey that I have retrieved from Office 365 Import window. And will leave all the logs in your local drive c:PSTuploadUploadlog.log

AzCopy /Source:C:UsersMohammedDesktopupload /Dest:https://d49d7ae0e38a4d8e9c93565.blob.core.windows.net/ingestiondata/SERVER01/PSTshareR1/

/Destkey:KA9Z00rEYa1JlqGE4wO222MnsN5ywT0elOgLeNht/fSMIJPe2134hEChuuDJ5mfdknq8ts0+cez6uUvFzcQd6g== /S /V:C:PSTUploadUploadlog.log

To make sure that files are uploaded. I will open Azure Storage Explorer 6 (Preview) and click Add Account on top

On add storage account window I will use the blob name that I have got from the URL earlier and storage secure key in the storage account key below and click on save.

Once I click that I will get a list of directories .. The default directory which is used by Office 365 is the “Ingestiondata” folder .. There our files will be uploaded.

Exporting to PST using Exchange Management Shell

In order to Export to a PST there are only two required parameters: Mailbox and a PST location. If we want just to export the entire content, we can run the cmdlet shown below and the result will be a request being queued as shown in Figure 09.

New-MailboxExportRequest <Mailbox> -FilePath <EXUtil-Shared-Folder-on-Exchange>

Note:
The Mailbox can be an alias, SMTP or Display name.

Image
Figure 09

With Exchange Management Shell, we have several parameters to help us out to perform granular PST exports. A good example is to generate a PST of a couple of mailboxes in the same PST file. This can be easily achieved using Exchange Management Shell. Basically, we just need to run 3 Exports using the same file and we can also create a folder for each source mailbox using the –TargetRootFolder as shown in Figure 10.

  • Office 365 Dedicated or Office 365 Government Community Cloud (GCC) customers.
  • Mailboxes hosted in the Brazil, China, Japan or Australia datacenters.
  • Cross-premises archive mailboxes (where the primary mailbox is on-premises and the archive mailbox is hosted in Exchange Online).

We are committed to enabling these scenarios as soon as we can. Note that currently support for Office 365 Government Community Cloud (GCC) customers is limited to using the public Azure infrastructure with our additional encryption.

2.       The item number for each mailboxes has the limitation

•         Cutover Migration (recommend if we have the management of On-Premise Exchange Server, and the mailbox number is below 1,000)

               Overview:  Need to enable On premise Exchange Server’s ROH, prepare a .CSV file, Exchange 2003 or Later version

               Benefit: Cutover Migration can migrate all information (include emails/ Calendar / Task / etc…) from On-premise to Office 365

•         Staged Migration (recommend if we have the management of On-Premise Exchange Server, and the mailbox number is over 1,000)

              Overview: Need to enable On premise Exchange Server’s ROH; prepare a .CSV file; Exchange 2003 or Later version; installed DircSync Tool (which you can download it from Office 365 Website)

Does anyone know if taking Outlook off-line during the import will help with the import speed?  My thinking is that if it is importing directly to the mail server, it will take much longer, as it has to update across the Internet (10 of them simultaneously).  If I configure Outlook and then take it off-line, will the import run quicker because it is writing locally only?  When the import is complete, I would put Outlook back on-line and it would sync behind the scenes.

Чтобы использовать функцию импорта для пользователей, которые больше не состоят в организации, выполните указанные ниже действия.

  1. В Office 365 создайте пользователя с активной лицензией.

  2. Убедитесь в наличии целевого почтового ящика (основного и/или архивного).

  3. Переведите пользователя в режим хранения.

  4. Импортируйте PST-файлы с помощью службы импорта.

  5. После завершения импорта преобразуйте пользователя в неактивного (путем удаления объекта пользователя из списка активных пользователей Office 365).

В Office 365 создайте пользователя с активной лицензией.

Убедитесь в наличии целевого почтового ящика (основного и/или архивного).

Переведите пользователя в режим хранения.

Импортируйте PST-файлы с помощью службы импорта.

После завершения импорта преобразуйте пользователя в неактивного (путем удаления объекта пользователя из списка активных пользователей Office 365).

Этот процесс аналогичен управлению неактивными почтовыми ящиками.

Наверх