Chat now with support
Chat mit Support

Migrator for Notes to Exchange 4.16.3 - Release Notes

MNE admin migration servers

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

Workstation hardware

Required for all Exchange target types, including Microsoft 365

Also required for Microsoft 365 target

NOTE: The Microsoft Graph SDK v1.0 PowerShell module replaces the deprecated Azure AD PowerShell module that Microsoft will not support.
NOTE: Version 2.0.5 and earlier is known as the Exchange Online PowerShell V2 module (abbreviated as the EXO V2 module). Version 3.0.0 and later is known as the Exchange Online PowerShell V3 module (abbreviated as the EXO V3 module).

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.

For Microsoft 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 7.  

Supported operating systems

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 Microsoft 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 Microsoft 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

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”.

Server hosting the SSDM scheduling utility web service

ASP.net version 4.8 must be installed. If the SSDM Scheduling Web Service is running, you must change the .NET Framework version of the Application Pool used by the SSDM Scheduling Web Service to .NET 4.8.

Upgrade and compatibility

There is no need to uninstall a previous version before installing a new version. The upgrade installation and setup are fully automated, and will preserve any data already migrated by an earlier version, so you may simply resume the migration process from wherever you left off with the previous version.

IMPORTANT: The upgrade process will back up your existing pabreplicator.nsf, attrs.tsv, msgtypes.tsv, NMEPSErrorFile.xml, wte_template.htm, ybm_template.htm and ynma_template.html files and copy them to the target installation folder.

The following locally saved configuration files are overwritten as part of the upgrade to release 4.16.3. Make a backup copy of these files before performing the upgrade.

The upgrade procedure contains a step for restoring the files.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen