Search Engine: Elastic

Article ID: 129598, created on Oct 11, 2016, last review on Nov 21, 2016

Important: This article is applicable for Odin Automation version 6.0.5 and up to 6.0.x.

Common information

In Exchange 2013, the public folders mechanism was re-engineered to use mailbox infrastructure. Now the legacy (Exchange 2007/2010) public folders and Exchange 2013 public folders can’t exist in your Exchange organization simultaneously. This effectively means that there is no coexistence between versions. Migrating public folders to Exchange Server 2013 or Exchange Online is currently a one-time cutover process.

During migrating the Exchange 2007/2010 subscriptions with public folders to Exchange 2013 in Operation Automation, the public folders remain on the legacy (Exchange 2007/2010) servers.

The procedure described in this KB helps to perform a one-time migration of public folders from the legacy Exchange 2007/2010 servers to Exchange 2013 servers.

The migration procedure consists of several steps:

  1. OA preparation - on this step all the Exchange 2007/2010 subscriptions should be migrated to Exchange 2013 and most of the Exchange OA packages should be removed from the Exchange 2007/2010 nodes. The provisioning of new Exchange 2013 subscriptions with non zero limit on "Public Folders" resource and the creation of new public folders will still be available after this step. The existing public folders will also be accessible for the end users.
  2. Generate public folder-to-mailbox mapping file and turn off public folder provisioning - on this step OA configuration will be analyzed and public folder-to-mailbox mapping file will be generated. New public folder creation and provisioning of new subscriptions with public folders will be blocked. The existing public folders will still be accessible for the end users after this step.
  3. Public folder mailbox creation - on this step a public folder mailbox will be created on the Exchange side. The existing public folders will still be available for the end users on this step.
  4. Public folder migration - on this step public folders will be migrated from the legacy public folders stores to the public folder mailboxes. During public folder migration, public folders will be unavailable to the end users.
  5. OA reconfiguration - on this step OA will be reconfigured. Public folder mailboxes will be registered in OA. Existing public folders will be reassigned to public folders mailboxes.
  6. Turn on public folder provisioning - on this step all the remaining Exchange 2007/2010 packages should be removed from Exchange 2007/2010 nodes. After this step, new public folder creation and provisioning of new subscriptions with public folders will be unblocked in OA. Also, new public folders will be created in Exchange 2013 public folder mailboxes.

Public folder provisioning downtime: step 2-6.

Public folder access downtime: step 5.

Preparation

Before starting public folder migration, the following steps should be performed:

  1. All Exchange 2007/2010 subscriptions must be migrated to Exchange 2013 according to the Hosted Exchange deployment guide or removed.
  2. Turn off Exchange branding on all brands.
  3. The following packages must be removed:
    • Exchange2007POP3/Exchange2010POP3
    • Exchange2007IMAP4/Exchange2010IMAP4
    • Exchange2007Protocols/Exchange2010Protocols
    • Exchange2007Autodiscover/Exchange2010Autodiscover
    • Exchange2007SMTP/Exchange2010Autodiscover
    • Exchange2007SMTPAuh/Exchange2010Autodiscover
    • Exchange2007OAB/Exchange2010OAB
  4. After the removal, some services on nodes will be stopped. Start them manually. On CAS server:

    • "Microsoft Exchange POP3"
    • "Microsoft Exchange IMAP4"
    • "World Wide Web Publishing Service"

    On Hub server:

    • "Microsoft Exchange Transport"
  5. Remove all mailbox stores attached to the remaining Exchange2007Mailstore/Exchange2010Mailstore packages.

After that step, only Exchange2007Mailstore/Exchange2010Mailstore should remain on Exchange 2007/2010 nodes with attched public folder stores which are used for the public folder provisioning for Exchange 2013 subscriptions.

Generate public folder-to-mailbox mapping file and turn off public folder provisioning

To generate the public folder-to-mailbox mapping file and turn off public folder provisioning, execute the pfMigration_GeneratePublicFolderToMailboxMap.py Python script on OA management node. Script will verify the OA configuration, generate the public folder-to-mailbox mapping file and turn off public folder provisioning.

Syntax:

python pfMigration_GeneratePublicFolderToMailboxMap.py --file=<OUT_CSV_FILE> [--mbxsize=<PF_MAILBOX_SIZE>] [--addomain=<AD_DOMAIN_NAME>] [--test]

Full list of script parameters:

file (required) - path of the output file to be generated. If the filename only is specified, then the output file will be generated in the current directory.

mbxsize (optional) - size (in Gigabytes) of any one of the Public folder mailboxes which will be created later. (default value: 100).

addomain (required if several AD domains with Exchange registered in the OA installation, and optional otherwise) - name of the AD domain with Exchange coexistence in which migration will be performed.

First of all, execute the script in test mode with the "--test" flag. The script will perform all operations but public folder provisioning will not be turned off. After executing the script in the test mode, сheck the output of the script and the content of the generated public folder-to-mailbox mapping file. If no errors are found, execute the script without the "--test" flag to generate the public folder-to-mailbox mapping file and turn off public foder provisioning.

Public folder mailboxes creation

Before starting migration of public folders to public folder mailboxes, the public folder mailboxes should be created in Exchange by executing the pfMigration_CreatePFMailboxes.ps1 PowerShell script in Exchange Management Shell on any Exchange 2013 host.

Syntax:

pfMigration_CreatePFMailboxes.ps1 -CSVFile <IN_CSV_FILE> -Database <DATABASE> -AuthoritativeDomain <DEFAULT_DOMAIN> [-EstimatedNumberOfConcurrentUsers <NUMBER_OF_CONCURENT_USERS>] [-PFMailboxSize <PF_MAILBOX_SIZE>]

Full list of script parameters:

CSVFile (required) - path of the input of the public folder-to-mailbox mapping file generated on one of the previous step. If filename only is specified, then the input file will be searched in the current directory.

Database (required) - mailbox database where new public folder mailboxes will be created.

AuthoritativeDomain (required) - any provider domain with the configured Autodiscover. Autodiscover should point to the Exchange 2013 installation, where a new public folder mailbox will be located. This domain will be used to generate email for hierarchy public folder mailboxes.

EstimatedNumberOfConcurrentUsers (optional) - estimated number of simultaneous user connections browsing the public folder hierarchy (default value: 2000).

PFMailboxSize (optional) - size (in Gigabytes) of any one of the Public folder mailboxes which will be created by script (default value: 100).

Public folder migration

To perform the migration of public folders data to the public folder mailboxes on Exchange side, perform steps from the Microsoft TechNet article Use batch migration to migrate public folders to Exchange 2013 from previous versions.

First of all, read the section "What do you need to know before you begin?". To perform the migration, execute the following steps from the "How do you do this?" section:

  1. Step 2: Prepare for the migration.
  2. Step 5: Start the migration request. As the CSVData parameter for the New-MigrationBatch. cmdlet, use the CSV file with public folders to public folder mailboxes map generated on the step "Generate public folder to mailbox map and turn off public folder provisioning". Use the following command to check the migration status from the command line: Get-MigrationBatch.
  3. Step 6: Lock down the public folders on the legacy Exchange server for the final migration (downtime required). Ignore the Note in this step of the MS article.
  4. Step 7: Finalize the public folder migration (downtime required). Use the Complete-MigrationBatch PFMigration command instead of Complete-MigrationBatch PublicFolderMigration stated in the MS article.
  5. Step 8: Test and unlock the public folder migration. As a Public Folder Mailbox Identity, use public folder mailbox with the name "PublicFolderHierarchy01". Skip item 3 from this step.

Finally, perform steps in the section "Remove public folder databases from the legacy Exchange servers".

OA reconfiguration

After the migration of all public folders data to the public folder mailboxes on Exchange side, the public folders should be reconfigured on OA side by executing the pfMigration_UpdateOAConfiguration.py Python script on OA management node. Script will verify the OA configuration, read and verify data from CSV file, register public folder mailboxes in OA and perform update OA subscriptions.

Syntax:

python pfMigration_UpdateOAConfiguration.py --file=<IN_CSV_FILE> [--test]

Full list of script parameters:

file (required) - path to the input of the public folder-to-mailbox mapping file generated on one of the previous step. If filename only is specified, then the input file will be searched in the current directory.

hostid (required) - ID of OA host with Exchange2013Mailstore package installed on which all public folder mailboxes will be registered.

mbxsize (optional) - size (in Gigabytes) of any one of the Public folder mailboxes which will be created later. (default value: 100).

First of all, execute the script in test mode with the "--test" flag. The script will perform all operations but changes will not be applied in OA. After executing, the script in test mode will сheck the script output. If no errors are found, execute the script without the "--test" flag to perform the real OA reconfiguration.

Turn on public folder provisioning

To allow the provisioning of new public folders to public folder mailboxes, perform the following steps:

  1. Remove all public folder stores attached to Exchange2007Mailstore/Exchange2010Mailstore packages on the legacy Exchange 2007/2010 nodes.
  2. Remove the remaining Exchange2007Mailstore/Exchange2010Mailstore packages from the legacy Exchange 2007/2010 nodes.
  3. Turn on the "Ready to provide" parameter for the necessary newly-created public folder mailboxes in PCP.

Email subscription for changes to this article
Save as PDF