立即与支持人员聊天
与支持团队交流

Binary Tree Migrator for Notes 20.11 - Requirements

Section 3. Supporting Source and Target Platforms

Domino

  • Domino versions 11, 10, 9.0.1, and 8.5, 8, 7, 6.5 are supported

  • The Notes ID used to sign the Migrator for Notes database requires Domino server security rights to run agents. This can be updated on the Domino Server document Security tab.

Microsoft Exchange

  • Microsoft Exchange versions O365, 2019, 2016, 2013, 2010 are supported

  • MAPI must be enabled on the target mailbox.

  • Outlook desktop integration must be allowed for migration accounts and target mailboxes.

  • If migrating to Exchange 2010, Exchange 2013 or higher, or Office 365, the privilege level required to migrate user mailboxes is Full Access.

  • If migrating to Exchange 2013, you must ensure that the migration workstation(s) being used have Outlook 2013 (32-bit).

  • MAPI over HTTP should be enabled on the Exchange server for migrations. RPC is no longer supported by the migration engine.

  • The migration engine utilizes MAPI over HTTP and performs an Autodiscover lookup to identify the target mailbox on Exchange (or Office 365). For this to function properly, all DNS configuration must be completed following Microsoft’s best practices for Autodiscover with a CNAME record added for the Autodiscover domain(s).

  • Exchange should be updated to the current patch levels, at the time of this product release. 

 


Be sure that enough disk space is available on the destination Exchange servers.

 


If migrating to Exchange 2010 and the mailbox has an online archive attached, Migrator for Notes Autodiscover will fail. To migrate in this scenario, an older version of Migrator for Notes, 4.5, that does not utilize Autodiscover should be used. If there is no data in the online archive it can be removed, and the migration can proceed with the latest version of Migrator for Notes.

Office 365 Migration Requirements

The following software is required on the Migration Control Center to allow the operator to use PowerShell related agents in the Notes Migrator.nsf database:

  • Microsoft Online Services Sign-In Assistant for IT Professionals RTW

  • Azure Active Directory Module for Windows PowerShell (64-bit version)

  • Windows Management Framework 4.0 or 5.0 (PowerShell 4.0 or 5.0)

With the change to support MAPI over HTTP, the migration engine performs an Autodiscover lookup to identify the target mailbox and create the mail profile. For this to function properly, all DNS must be completed following Microsoft’s best practices for the O365 tenant. Below is a link to a Microsoft support document for how to create the DNS entries for O365. For the Autodiscover action performed by the Migration engine, a CNAME record for Autodiscover needs to be created for all primary SMTP domains pointing to the O365 Autodiscover A record.

https://support.office.com/en-us/article/Create-DNS-records-for-Office-365-using-Windows-based-DNS-9eec911d-5773-422c-9593-40e1147ffbde

* For Office 365 migrations the Migrator for Notes system is supported for building a staging farm in Microsoft Azure. For information on the use of the Azure platform at the operating system level please refer to Microsoft documentation.

Domino

  • Domino versions 11, 10, 9.0.1, and 8.5, 8, 7, 6.5 are supported

  • The Notes ID used to sign the Migrator for Notes database requires Domino server security rights to run agents. This can be updated on the Domino Server document Security tab.

Microsoft Exchange

  • Microsoft Exchange versions O365, 2019, 2016, 2013, 2010 are supported

  • MAPI must be enabled on the target mailbox.

  • Outlook desktop integration must be allowed for migration accounts and target mailboxes.

  • If migrating to Exchange 2010, Exchange 2013 or higher, or Office 365, the privilege level required to migrate user mailboxes is Full Access.

  • If migrating to Exchange 2013, you must ensure that the migration workstation(s) being used have Outlook 2013 (32-bit).

  • MAPI over HTTP should be enabled on the Exchange server for migrations. RPC is no longer supported by the migration engine.

  • The migration engine utilizes MAPI over HTTP and performs an Autodiscover lookup to identify the target mailbox on Exchange (or Office 365). For this to function properly, all DNS configuration must be completed following Microsoft’s best practices for Autodiscover with a CNAME record added for the Autodiscover domain(s).

  • Exchange should be updated to the current patch levels, at the time of this product release. 

 


Be sure that enough disk space is available on the destination Exchange servers.

 


If migrating to Exchange 2010 and the mailbox has an online archive attached, Migrator for Notes Autodiscover will fail. To migrate in this scenario, an older version of Migrator for Notes, 4.5, that does not utilize Autodiscover should be used. If there is no data in the online archive it can be removed, and the migration can proceed with the latest version of Migrator for Notes.

Office 365 Migration Requirements

The following software is required on the Migration Control Center to allow the operator to use PowerShell related agents in the Notes Migrator.nsf database:

  • Microsoft Online Services Sign-In Assistant for IT Professionals RTW

  • Azure Active Directory Module for Windows PowerShell (64-bit version)

  • Windows Management Framework 4.0 or 5.0 (PowerShell 4.0 or 5.0)

With the change to support MAPI over HTTP, the migration engine performs an Autodiscover lookup to identify the target mailbox and create the mail profile. For this to function properly, all DNS must be completed following Microsoft’s best practices for the O365 tenant. Below is a link to a Microsoft support document for how to create the DNS entries for O365. For the Autodiscover action performed by the Migration engine, a CNAME record for Autodiscover needs to be created for all primary SMTP domains pointing to the O365 Autodiscover A record.

https://support.office.com/en-us/article/Create-DNS-records-for-Office-365-using-Windows-based-DNS-9eec911d-5773-422c-9593-40e1147ffbde

* For Office 365 migrations the Migrator for Notes system is supported for building a staging farm in Microsoft Azure. For information on the use of the Azure platform at the operating system level please refer to Microsoft documentation.

Microsoft Exchange

Domino

  • Domino versions 11, 10, 9.0.1, and 8.5, 8, 7, 6.5 are supported

  • The Notes ID used to sign the Migrator for Notes database requires Domino server security rights to run agents. This can be updated on the Domino Server document Security tab.

  • Microsoft Exchange versions O365, 2019, 2016, 2013, 2010 are supported

  • MAPI must be enabled on the target mailbox.

  • Outlook desktop integration must be allowed for migration accounts and target mailboxes.

  • If migrating to Exchange 2010, Exchange 2013 or higher, or Office 365, the privilege level required to migrate user mailboxes is Full Access.

  • If migrating to Exchange 2013, you must ensure that the migration workstation(s) being used have Outlook 2013 (32-bit).

  • MAPI over HTTP should be enabled on the Exchange server for migrations. RPC is no longer supported by the migration engine.

  • The migration engine utilizes MAPI over HTTP and performs an Autodiscover lookup to identify the target mailbox on Exchange (or Office 365). For this to function properly, all DNS configuration must be completed following Microsoft’s best practices for Autodiscover with a CNAME record added for the Autodiscover domain(s).

  • Exchange should be updated to the current patch levels, at the time of this product release. 

 


Be sure that enough disk space is available on the destination Exchange servers.

 


If migrating to Exchange 2010 and the mailbox has an online archive attached, Migrator for Notes Autodiscover will fail. To migrate in this scenario, an older version of Migrator for Notes, 4.5, that does not utilize Autodiscover should be used. If there is no data in the online archive it can be removed, and the migration can proceed with the latest version of Migrator for Notes.

Office 365 Migration Requirements

The following software is required on the Migration Control Center to allow the operator to use PowerShell related agents in the Notes Migrator.nsf database:

  • Microsoft Online Services Sign-In Assistant for IT Professionals RTW

  • Azure Active Directory Module for Windows PowerShell (64-bit version)

  • Windows Management Framework 4.0 or 5.0 (PowerShell 4.0 or 5.0)

With the change to support MAPI over HTTP, the migration engine performs an Autodiscover lookup to identify the target mailbox and create the mail profile. For this to function properly, all DNS must be completed following Microsoft’s best practices for the O365 tenant. Below is a link to a Microsoft support document for how to create the DNS entries for O365. For the Autodiscover action performed by the Migration engine, a CNAME record for Autodiscover needs to be created for all primary SMTP domains pointing to the O365 Autodiscover A record.

https://support.office.com/en-us/article/Create-DNS-records-for-Office-365-using-Windows-based-DNS-9eec911d-5773-422c-9593-40e1147ffbde

* For Office 365 migrations the Migrator for Notes system is supported for building a staging farm in Microsoft Azure. For information on the use of the Azure platform at the operating system level please refer to Microsoft documentation.

Office 365 Migration Requirements

Domino

  • Domino versions 11, 10, 9.0.1, and 8.5, 8, 7, 6.5 are supported

  • The Notes ID used to sign the Migrator for Notes database requires Domino server security rights to run agents. This can be updated on the Domino Server document Security tab.

Microsoft Exchange

  • Microsoft Exchange versions O365, 2019, 2016, 2013, 2010 are supported

  • MAPI must be enabled on the target mailbox.

  • Outlook desktop integration must be allowed for migration accounts and target mailboxes.

  • If migrating to Exchange 2010, Exchange 2013 or higher, or Office 365, the privilege level required to migrate user mailboxes is Full Access.

  • If migrating to Exchange 2013, you must ensure that the migration workstation(s) being used have Outlook 2013 (32-bit).

  • MAPI over HTTP should be enabled on the Exchange server for migrations. RPC is no longer supported by the migration engine.

  • The migration engine utilizes MAPI over HTTP and performs an Autodiscover lookup to identify the target mailbox on Exchange (or Office 365). For this to function properly, all DNS configuration must be completed following Microsoft’s best practices for Autodiscover with a CNAME record added for the Autodiscover domain(s).

  • Exchange should be updated to the current patch levels, at the time of this product release. 

 


Be sure that enough disk space is available on the destination Exchange servers.

 


If migrating to Exchange 2010 and the mailbox has an online archive attached, Migrator for Notes Autodiscover will fail. To migrate in this scenario, an older version of Migrator for Notes, 4.5, that does not utilize Autodiscover should be used. If there is no data in the online archive it can be removed, and the migration can proceed with the latest version of Migrator for Notes.

The following software is required on the Migration Control Center to allow the operator to use PowerShell related agents in the Notes Migrator.nsf database:

  • Microsoft Online Services Sign-In Assistant for IT Professionals RTW

  • Azure Active Directory Module for Windows PowerShell (64-bit version)

  • Windows Management Framework 4.0 or 5.0 (PowerShell 4.0 or 5.0)

With the change to support MAPI over HTTP, the migration engine performs an Autodiscover lookup to identify the target mailbox and create the mail profile. For this to function properly, all DNS must be completed following Microsoft’s best practices for the O365 tenant. Below is a link to a Microsoft support document for how to create the DNS entries for O365. For the Autodiscover action performed by the Migration engine, a CNAME record for Autodiscover needs to be created for all primary SMTP domains pointing to the O365 Autodiscover A record.

https://support.office.com/en-us/article/Create-DNS-records-for-Office-365-using-Windows-based-DNS-9eec911d-5773-422c-9593-40e1147ffbde

* For Office 365 migrations the Migrator for Notes system is supported for building a staging farm in Microsoft Azure. For information on the use of the Azure platform at the operating system level please refer to Microsoft documentation.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级