New top-level public folders added
After migration starts, new top-level public folders that are added need to be synchronized.
New top level public folders can be detected and added to migration automatically by MAgE using DetectNewTopLevelFolders parameter for Set-MMExProjectOptions cmdlet. Both of the following conditions should be satisfied:
- IPM_SUBTREE should be configured as public folder synchronization root folder. New top-level public folders will be detected on source (and target, respectively) only IPM_SUBTREE is processed by the MAgE
- DetectNewTopLevelFolders parameter should be set to True for current project.
For details refer to Configuring Migration Using PowerShell.
|
|
NOTE: If for some reason it is not acceptable to use DetectNewTopLevelFolders, but certain source top level folder with subfolders needs to be migrated, use procedure described below. Here are some examples of cases where this approach should be used: target organization contains top-level folders that are not supposed to be synced back to source, or only particular source top level folders should be migrated. |
Take the following steps to synchronize the new top-level public folder manually:
- Call Stop-MMExAgent -Type PublicFolder -AgentHost <agent host name>
- Prepare updated CSV file using Export-MMExPublicFolderMapping cmdlet, you can also create new CSV file (only new folder can be included) manually.
- Call Import-MMExPublicFolderMappingcmdlet using updated CSV file.
- Call Stop-MMExAgent -Type PublicFolder -AgentHost <agent host name> to stop MAgE before synchronization start.
- Call Initialize-MMExPublicFolderMigration cmdlet using updated CSV file.
- Call Start-MMExAgent -Type PublicFolder -AgentHost <agent host name> to start synchronization.
You can see these added public folders in the statistics with Get-MMExPublicFolderStatistics.
Synchronizing public folders containing more than 10000 elements from Exchange 2010
This section is applicable in case Microsoft Exchange 2010 as source.
In case source public folder contains more than 10000 elements it can take a while to gather necessary information related to content. It may cause MAgE cannot read necessary information or fails to transfer the content of such folders. In case the Progress value for a public folder returned by Get-MMExPublicFolderStatistics does not grow, and this public folder contains more than 10000 elements, you can take the following actions:
- Reduce the number of elements in a folder by dividing into several public folders
-OR-
- In Public Folder Management console open the public folder properties to clear Maintain per-user read and unread information for this folder option until the migration is complete.
Technical Reference
Cmdlet Reference
This is a collection of Windows PowerShell cmdlets to perform public folder synchronization for supported configurations:
Starting public folder migration in simple mode with minimal customization
Configuring public folder synchronization in advanced mode
- Set-MMExGroupMatching (Microsoft Office 365 only)
- Export-MMExPublicFolderMapping
- Import-MMExPublicFolderMapping
- Initialize-MMExPublicFolderMigration
- Sync-MMExMailPublicFolder
Managing public folder synchronization (granular synchronization)
- Restart-MMExPublicFolderMigration
- Suspend-MMExPublicFolderMigration
- Resume-MMExPublic FolderMigration
- Remove-MMExPublicFolderMigration
- Restart-MMExPublicFolderMigration
Monitoring public folder synchronization
Managing Migration Agent for Exchange (MAgE)
- Install-MMExAgent
- Get-MMExAgent
- Start-MMExAgent
- Stop-MMExAgent
- Repair-MMExAgent
- Restart-MMExAgent
- Uninstall-MMExAgent
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).