Migrator for Notes to Exchange 4.17

Table 5. Supported operating systems for migrations.
Operating systems supported for migration to...		Exchange version	Microsoft 365
Windows Server 2022		Exchange 2019	•
Windows Server 2019		Exchange 2019	•
Windows Server 2016		Exchange 2016	•
Windows 11		•	•
Windows 10	32-bit	•
Windows 10	64-bit	•	•

Table 6. Other Requirements

Requirement

Description

Workstation

•

Must be a separate machine from the Exchange server, but a member of the same domain as AD and Exchange.

•

Minimum hardware requirements:

•

Intel Xeon quad core 1.8 Ghz (x64) or AMD equivalent

•

8GB memory

•

512GB disk space (or more, depending on log retention requirements)

•

1 Gbps NIC, and 1 Gbps or faster network connections among all migration servers and the Exchange and Domino servers.

Required for all Exchange target types, including Microsoft 365

•

.Net Framework 4.8

•

Microsoft OLE DB Driver for SQL Server 18.2 (or later) or Microsoft SQL 2012 Native Client.

•

Microsoft Command Line Utilities for SQL Server (a free download from the link provided in the MNE Autorun).

NOTE: This component is required only if SQL Server is not installed locally (i.e. the MNE Server is connecting to a remote SQL instance).

•

Windows PowerShell 3.0, which is part of Windows Management Framework 3.0 (included with any MNE-supported OS).

•

Notes must be installed in single-user mode and configured. The Notes client version must be one of 9.0.1-12.0.2 (all ranges inclusive), and should match or be higher than the Domino server version.

NOTE: MNE supports only 32-bit Notes clients. Notes 14 does not have a 32-bit version. A future update of MNE will add support for Notes 14 64-bit client. Until then, Quest recommends using 32-bit Notes 12.0.2 with Domino 14.0.

•

The 32-bit edition (only) of Outlook 2024, 2021, 2019 or 2016. The Outlook client must also conform to the Microsoft version requirements for the applicable Exchange target version. See the Exchange Server supportability matrix for more details.

•

The MAPI DLLs required to perform a migration must be those that are part of Outlook, not the downloadable Exchange "server" MAPI.

•

Update for Universal C Runtime in Windows. See the Microsoft knowledge base article KB2999226.

Also required for Microsoft 365 target

•

ExchangeOnlineManagement v3.2

•

Microsoft.graph 2.22.0

•

Configuration of an Azure Application ID (App ID) in the destination tenant.

•

The App ID must be entered into the MNE configuration. (See the Administration Guide for instructions.)

To install compatible Exchange Online and Microsoft Graph PowerShell modules

Open PowerShell as Administrator and run the following commands:

To install Microsoft Graph

install-module -name Microsoft.Graph -requiredversion 2.22

To Install Exchange Online Management 3

install-module -name ExchangeOnlineManagement -requiredversion 3.2

Important: Avoiding permission conflicts

If you are migrating to an on-premises Exchange server, it is important to ensure that the Exchange administrator account used by MNE to perform the migration does not belong to the Domain Admins or the Enterprise Admins security group, or to the Organization Management role group.

Since these groups are denied Receive As rights on all mailbox databases, adding the Exchange account to any of these groups will result in conflicting permissions. These conflicting permissions have always had the potential to cause issues, but due to changes in how MNE connects to the target mailboxes, it is more likely that the conflicting permissions will prevent the new version of MNE from connecting to the mailboxes that are the migration targets.