This document help you perform public folders synchronization by enhanced Migration Agent for Exchange (MAgE) combined with extended MMEx PowerShell module instead of legacy agents in migration scenarios from Microsoft Exchange 2010/2013/2016/2019 to Microsoft Office 365
To synchronize public folders you can use enhanced Migration Agent for Exchange (MAgE) combined with enhanced MMEx PowerShell module instead of legacy agents in migration scenarios from Microsoft Exchange 2010/2013/2016/2019 to Microsoft Office 365
Enhanced MMEx PowerShell module complements Quest Migration Manager by synchronizing the mail-enabled state and public folders directory properties.
IMPORTANT: To ensure permission synchronization you should set object matching for migrated by Quest Migration Manager for Active Directory (Microsoft Office 365) mail-enabled universal security distribution groups using Set-MMExGroupMatching cmdlet.
Public folder synchronization process is collection-based. All public folders are included in one public folder collection Public Folder Collection (AgentHostName). Public folder collection properties are used as synchronization process properties.
You can specify the direction that will be applied to all public folders:
Consider the following specifics on how conflicts will be resolved for migrated public folders after migration:
The following hierarchy changes can be handled automatically using folder ID:
Migration Agent for Exchange at the beginning of the session detects a change of the full path of the source or the target public folder.
In case of change, Agent changes data in the project database to restart synchronization in next session and the following record is reported The folder path is changed. The folder will be processed in the next session.
In the next session, the new path will be reported in the Migration Agent log and in the statistics (GetMMExPublicFolderStatistics cmdlet). Synchronization will be restarted using new data.
Migration Agent for Exchange at the beginning of the session detects a change of the name of the source or the target public folder. If the target public folder renamed after the migration has been started, the Get-MMExPublicFolderStatistics returns the System.Exception: Not Found error in Last error field.
In the next session, the new name will be reported in the MigrationAgent log and in the statistics (GetMMExPublicFolderStatistics cmdlet). Synchronization will be restarted using new data.
Refer to specific case workarounds for instructions on how to handle the rest of hierarchy changes.
Before you begin migration to Microsoft Office 365, you need to provision user accounts in it. For that, use the Migration Manager for Active Directory (Office 365) console for migration to Office 365
This document introduces a toolkit of Windows PowerShell cmdlets to support public folder synchronization for supported configurations.
This document is intended for the following migration scenarios supported by MAgE:
|To Exchange 2013||To Exchange 2016||Exchange 2019||To Office 365|
|From Exchange 2010|
|From Exchange 2013|
|From Exchange 2016|
|From Exchange 2019|