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

Migrator for Notes to Exchange 4.16.2 - Release Notes

Microsoft Exchange servers

 
* 
NOTE: Migrator for Notes to Exchange supports Cumulative Update (CU) releases for all supported versions of Exchange. If you encounter an incompatibility with a newly released CU, contact Quest Support for a resolution.

Supported Exchange target environments:

•
Exchange 2019: RTM
•
Exchange 2016: RTM
•
Exchange 2013: RTM and SP1
•
Exchange 2010: RTM, SP1, SP2 and SP3
•
Microsoft Office 365:
•
All Office 365 license plans that include an Exchange mailbox and permit connecting to that mailbox with Outlook and the Exchange Web Service (EWS).
•
Office 365 environments:
•
Office 365 Global
•
Office 365 Germany
•
Office 365 operated by 21Vianet

SQL server

MNE requires access to a Microsoft SQL Server. The following versions are supported:

•
SQL Server 2008
•
SQL Server 2008 Express Edition
•
SQL Server 2008 R2
•
SQL Server 2008 R2 Express Edition
•
SQL Server 2012
•
SQL Server 2012 Express Edition
•
SQL Server 2014
•
SQL Server 2014 Express Edition
•
SQL Server 2016
•
SQL Server 2016 Express Edition
•
SQL Server 2017
•
SQL Server 2017 Express Edition
•
SQL Server 2019
•
SQL Server 2019 Express Edition

Note the following:

•
SQL must be installed either on the administrator’s migration server or on a separate server, with a minimum of 20 GB free disk space.
•
You can use an existing (installed) MS SQL Server, or install a new instance of SQL Server using one of the supported versions.
•
Quest recommends a full-featured (non-Express) edition of SQL Server for best performance of the MNE Directory Export Wizard, particularly for sites with a large number of groups or domains.

MNE admin migration servers

 
Table 7. Supported operating systems for migrations.
Operating systems supported for migration to...
 
Exchange 2019/2016/2013/2010
Office 365

Windows Server 2019

64-bit

•

•

Windows Server 2016

64-bit

•

•

Windows Server 2012 or 2012 R2

64-bit

•

•

Windows 10

32-bit

•

 

64-bit

•

•

Windows 8

32-bit

•

 

64-bit

•

•

Windows Server 2008 SP2

32-bit

•

 

64-bit

•

 

Windows Server 2008 R2

64-bit

•

•

Windows 7

32-bit

•

 

64-bit

•

•

 
Table 8. Other Requirements
Requirement
Description

Workstation hardware
•
Must be a separate machine from the Exchange server, but a member of the same domain as AD and Exchange.
•
Minimum hardware requirements:
•
2 GHz dual-core processor, 4GB memory, 20GB free disk space.
•
Recommended for improved performance, especially for high-volume migrations:
•
2 GHz quad-core processor, 8GB memory.
•
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 Office 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 except pre-SP1 editions of Windows Server 2008 R2 and Windows 7). If PowerShell 3.0 does not come with your OS, you can download Windows Management Framework 3.0 at this Microsoft link.
•
Notes must be installed in single-user mode and configured. The Notes client version must be one of 6.0.0-11.0.1 (all ranges inclusive), and should match or be higher than the Domino server version.
•
The 32-bit edition (only) of Outlook 2019, 2016, 2013 or 2010. The Outlook client must also conform to the Microsoft version requirements for the applicable Exchange target version. Outlook 2010 is not supported by Office 365 or Exchange 2019. 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 Office 365 target
•
To use modern authentication when connecting to Office 365 using remote PowerShell, the Microsoft Exchange Online Remote PowerShell module must be installed. For more information, see To install Exchange Online Remote PowerShell V2 Module.
•
Microsoft's Azure Active Directory PowerShell for Graph - General Availability version (available at this Microsoft link).
NOTE: Azure AD Module for Windows PowerShell x64 edition (PowerShell V1) has been deprecated. MNE will remove support for this module in a future release.
•
For systems running Windows 2008 R2, TLS 1.2 must be enabled as the default secure protocol. See this Microsoft support page.
To install Exchange Online Remote PowerShell V2 Module
1
Install or update the Microsoft PowerShellGet module. For details, see Installing PowerShellGet.
2
Close and re-open the window.
Now you can use the Install-Module cmdlet to install the EXO V2 module from the PowerShell Gallery. Typically, you want the latest public version of the module, but you can install a preview version if one is available.
3
To install the latest public version of the module, run the following command:
Install-Module -Name ExchangeOnlineManagement
- OR -
To install a preview version of the module, replace <PreviewVersion> with the necessary value, and run the following command:
Install-Module -Name ExchangeOnlineManagement -RequiredVersion <PreviewVersion> -AllowPrerelease
Windows Remote Management (WinRM) on your computer must allow basic authentication (enabled by default).
4
To verify that basic authentication is enabled for WinRM, run the following command in a Command Prompt:
winrm get winrm/config/client/auth
5
If you don't see the value Basic = true, run the following command to enable basic authentication for WinRM:
winrm set winrm/config/client/auth @{Basic="true"}
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.

Best Practices for Office 365 Multi-Geo tenants

For Office 365 Multi-Geo tenants, the Administrator accounts used for migration must be in the same geographical region as the target mailboxes to avoid permission access issues due to GDPR compliance requirements. (220431)

End-user desktops (if running the SSDM)

An SSDM end-user workstation can be a virtual machine, but a dedicated physical machine will likely yield better migration performance.

 
Table 9.  
Requirement
Description

Supported operating systems
•
Windows 10, Windows 8.1, Windows 8 or Windows 7: 32-bit or 64-bit edition.
•
Windows Server 2019: 64-bit edition.
•
Windows Server 2016: 64-bit edition.
•
Windows Server 2012 or 2012 R2: 32-bit or 64-bit edition.
•
Windows Server 2008 SP2 or 2008 R2: 32-bit or 64-bit edition.
•
Windows Vista (Business, Enterprise or Ultimate): 32-bit or 64-bit edition.

Required Outlook client

Outlook 2019, 2016, 2013, or 2010: 32-bit or 64-bit edition.

The Outlook client must also conform to Microsoft's version requirements for the applicable Exchange target version. Outlook 2010 is not supported by Office 365 or Exchange 2019. See the Exchange Server supportability matrix for more details.

On each end-user SSDM desktop

Microsoft .Net Framework version 2.0 or later must be installed.

If end users will run the SSDM application from a network share (rather than from each user's own local copy):
Each workstation must also have either .Net 3.5 SP1 (or later) installed, or a Code Access Security (CAS) policy granting full trust to SSDM in the network share. (See “Before Running the SSDM” in chapter 4 of the MNE Scenarios Guide for instructions to set the required CAS policy.)

For the SSDM to authenticate with Office 365 using Modern Authentication, .Net 4.8 or later must be installed. If .Net 4.8 or later is not installed, the SSDM falls back to migrating without Modern Authentication.

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

Required Notes client
•
11.0.0 or 11.0.1 (inclusive)
•
10.0.0 or 10.0.1 (inclusive)
•
9.0.0 or 9.0.1 (inclusive)
•
8.5.0–8.5.3 (inclusive)
•
8.0.0–8.0.2 (inclusive)
•
6.0.0–7.0.4 (inclusive)

SmartCloud Notes support

MNE provides partial support for migrations from SmartCloud Notes via the SSDM, for Notes client versions 8.5.3 or newer. This feature also requires that you configure your local Notes client for SmartCloud Notes, as described in the MNE Pre-Migration Planning Guide, in chapter 1 under “Configuration requirements and account permissions”.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级