Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.15.2 - Release Notes

MNE admin migration servers

 
Operating systems supported for migration to...
 
Exchange
2016/2013/2010
Office 365

Windows Server 2016

64-bit

•

•

Windows Server 2012 or 2012 R2

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

•

•

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.0 (Office 365 targets require .Net Framework 4.5)
•
Microsoft SQL 2012 Native Client.
•
Microsoft SQL Server 2012 Command Line Utilities (a free download from the link provided in the MNE Autorun).
•
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.
•
Lotus Notes must be installed in single-user mode and configured. The Notes client version must be one of 9.0.0–9.0.1, 8.5.0–8.5.3 or 8.0.0–8.0.2 or 6.0.0–7.0.4 (all ranges inclusive), and should match or be higher than the Domino server version.
•
Default mail client must be a 32-bit edition (only) of Outlook. If migrating to an on-premises Exchange server, Outlook versions 2016, 2013 or 2010 are supported. If migrating to Office 365, Outlook versions 2016 and 2013 are supported. The Outlook client must also conform to Microsoft’s version requirements for the applicable Exchange target version (see Exchange 2016 or Exchange 2013 or Office 365). Additional version requirements are listed under Required for the MAPI over HTTP protocol section below.
NOTE: The minimum version for Outlook 2016 is 16.0.8420.1000. Only the Click-to-Run version is supported.
•
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
•
.Net Framework 4.5
•
Microsoft’s MSOL Sign-in Assistant x64 edition (available at this Microsoft link).
•
Microsoft's Azure Active Directory PowerShell for Graph - General Availability version (available at this Microsoft link).
NOTE: For Chinese and German Office 365 tenants, the minimum PowerShell module version is 1.1.166.0.
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.
•
When migrating with Outlook 2016, the following registry values must be set. If not set, MNE automatically sets it before starting the migration:
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity]
“EnableADAL”=dword:00000000
•
As of October 31, 2017, MAPI over HTTP is the only MAPI protocol supported by Office 365. Therefore, the requirements for the MAPI over HTTP protocol listed below are also requirements for migrating to Office 365.
•
For systems running Windows 2008 R2, TLS 1.2 must be enabled as the default secure protocol. See this Microsoft support page.

Required for the MAPI over HTTP protocol

MAPI over HTTP is the latest protocol developed by Microsoft for transmitting mail data between mail client applications and Exchange servers. The MAPI over HTTP protocol is supported by the following Exchange targets:

•
Exchange 2013 SP1
•
Exchange 2016
•
Office 365
NOTE: The minimum version for Outlook 2016 is 16.0.8420.1000. Only the Click-to-Run version is supported.
•
Migrations using the MAPI over HTTP protocol are supported by Migrator for Notes to Exchange when the following prerequisites are met.
•
Outlook 2013 version 15.0.4815.1000 or later
This version number represents the File Version of the Outlook.exe executable, not the version number that is reported in the Outlook About dialog.
•
When migrating with Outlook 2013, the following registry value must be set. If not set, MNE automatically sets it before starting the migration:
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Cached Mode]
"AllowAutoDiscoverForNonOutlook"=dword:00000001
•
If a registry value has previously been added to disable the MAPI over HTTP protocol, this registry value must be removed or modified. If this value exists, and it is not set to 0, MNE automatically sets it before starting the migration:
[HKEY_CURRENT_USER\Software\Microsoft\Exchange]
“MapiHttpDisabled”=dword:00000000

End-user desktops (if running the SSDM)

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

 
Requirement
Description

Supported operating systems
•
Windows 10, Windows 8.1, Windows 8 or Windows 7: 32-bit or 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 2016, 2013, or 2010: 32-bit or 64-bit edition.

If migrating to Exchange 2016 or Exchange 2013 or Office 365, the required Outlook client must conform to Microsoft's requirements for Exchange 2016 or Exchange 2013 or Office 365, respectively.

On each end user’s 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.)

If migrating with Modern Authentication enabled, .Net 4.5 or later must be installed. If .Net 4.5 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 Lotus Notes client
•
9.0.0 or 9.0.1
•
8.5.0–8.5.3 (inclusive)
•
8.0.0–8.0.2 (inclusive)
•
6.0.0–7.0.4 (inclusive)

Lotus Live support

MNE provides partial support for migrations from Lotus Live, via the SSDM, for Lotus Notes client versions 8.5.3 or newer. This feature also requires that you configure your local Notes client for Lotus Live, 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.0 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.0.

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: If upgrading from 4.14.1 or earlier, before upgrading to 4.15.1, you must back up the SSDM Scheduling Administration utility configuration files. See the section below for information on backing up the files.
* 
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.
* 
IMPORTANT: The enhancement 674823 contains a breaking change to the [TimeZoneInfo] Program Parameter. If your installation currently contains configuration data in the [TimeZoneInfo] section, this configuration data must be updated. See the [TimeZoneInfo] section in the NME Program Parameters Reference for details.
Backing up the SSDM Scheduling Administration utility configuration files

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

C:\Program Files (x86)\Dell\Migrator for Notes to Exchange\SSDM Scheduling Web Service\Bin\SchedulingGlobals.config
C:\Program Files (x86)\Dell\Migrator for Notes to Exchange\SSDM Scheduling Administration\AdminConfigPaths.xml

The upgrade procedure contains a step for restoring the files.

 

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating