Domain controllers of the following Microsoft Windows Server versions can be used for Active Directory migration, synchronization and processing.
All AD Functional Levels supported by Microsoft for a Microsoft Windows Server operating system listed below are supported for migration from/to Domain controllers running on that same Operating System. For example, Windows Server 2016 functional levels are supported on Windows Server 2022, Windows Server 2019, and Windows Server 2016. For full details see Microsoft’s documentation of Active Directory Domain Services Functional Levels in Windows Server on Microsoft Learn.
|
Note: Windows Server 2003 functional levels are supported only on Windows Server 2016. That is, Microsoft does not support Windows Server 2003 functional levels on Windows Server 2019 or Windows Server 2022. |
Requirement | Details |
---|---|
Platform |
One of the following:
|
Operating System |
One of the following:
|
|
IMPORTANT: Attributes selected as DSA matching service attributes (adminDisplayName and extensionAttribute15 by default) must be indexed in the Active Directory schema. Indexing is configured in the Active Directory Schema MMC snap-in, by the Index this attribute in the Active Directory option in the attribute properties. |
On-premises Exchange migration involves moving mailboxes (including calendars and free/busy status information) and public folders. The following table shows the supported paths for on-premises migration. For details about the specifics of mailbox, calendar and public folder synchronization, including handling of different Exchange versions, see the Mailbox Migration Process and Calendar Synchronization Process topics in the Migration Manager for Exchange User Guide.
Source Exchange Organization → Target Exchange Organization ↓ |
Microsoft Exchange 2003 Service Pack 2 or later | Microsoft Exchange 2007 Service Pack 2 or later | Microsoft Exchange 2010 Service Pack 2 Rollup 6 or later | Microsoft Exchange 2013 Cumulative Update 10 (CU10) or later | Microsoft Exchange 2016 | Microsoft Exchange 2019 |
---|---|---|---|---|---|---|
Microsoft Exchange 2003 Service Pack 2 or later | Yes | Yes | Yes | No | No | No |
Microsoft Exchange 2007 Service Pack 2 or later | Yes | Yes | Yes | No | No | No |
Microsoft Exchange 2010 Service Pack 2 Rollup 6 or later | Yes | Yes | Yes | Yes |
Yes |
No |
Microsoft Exchange 2013 Cumulative Update 10 (CU10) or later | Yes | Yes | Yes | Yes |
Yes |
No |
Microsoft Exchange 2016 | Yes | Yes | Yes | Yes | Yes | No |
Microsoft Exchange 2019 | No | No | Yes |
Yes |
Yes |
Yes |
|
NOTE:
|
Mailbox, calendar and public folder synchronization to Microsoft Office 365 can be performed from the following Exchange versions:
|
NOTE: Migration Manager also supports certain migration scenarios that involve hybrid deployments as migration destination. For detailed information, refer to the Hybrid Migration Scenarios section of Migrating to Microsoft Office 365 document. |
|
NOTE: Migration to Office 365 China tenants (operated by 21Vianet) and Office 365 Germany tenants (operated by T-Systems) is not supported. |
Migration Manager for AD supports the following Microsoft Exchange Server versions for Active Directory migration, synchronization and processing (by Active Directory Processing Wizard and by Exchange Processing Wizard):
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center