Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.16 - Release Notes

Quest® Migrator for Notes to Exchange 4.16.0

Quest® Migrator for Notes to Exchange 4.16.0

These release notes provide information about the Quest® Migrator for Notes to Exchange release.

About Migrator for Notes to Exchange

Migrator for Notes to Exchange (MNE) is a set of coordinated software applications designed to facilitate a variety of migration strategies for organizations moving from a Domino server, with Notes clients, to a Microsoft Exchange environment with Outlook clients. MNE can migrate either to a proprietary Exchange environment, or to a hosted Exchange service like Microsoft’s Office 365.

MNE 4.16.0 is a minor release, with enhanced features and functionality. See the Enhancements and Resolved issues sections that follow.

New Features

Previously, Migrator for Notes to Exchange (MNE) used Outlook MAPI to write migrated data to the target server mailbox or PST file. Though Outlook MAPI works well for PST file creation, it has limitations related to authentication when targeting a server mailbox.

With the introduction of Modern Authentication in Office 365, it was impossible to implement a solution that allowed MNE to authenticate using Modern Authentication with Outlook MAPI. As a result, MNE has discarded Outlook MAPI when migrating to a server mailbox target. Instead, MNE provides its own API library that uses the same communication protocol that Outlook MAPI uses to talk to the Exchange server (MAPI over HTTP protocol). This library is called the MNE MAPI/HTTP library.

The MNE MAPI/HTTP library was introduced in version 4.15.2 with support for Modern Authentication but functionality was limited to migrations with the SSDM. The 4.15.2 version library supplemented the other protocols (such as Exchange Web Services and the newer REST API) that handled most migrations in the SSDM using Modern Authentication.

In version 4.16, the MNE MAPI/HTTP library is extended to provide the functionality to perform a full migration, eliminating the need to use other protocols. This ensures a robust migration, allowing data to be handled by a single protocol. The MNE MAPI/HTTP library is used for all migrations to server mailboxes to both on-premises Exchange and Office 365.

The MNE MAPI/HTTP library has the following advantages over the Outlook MAPI library:

NOTE the following:

As part of support for Domino 10 and Domino 10.0.1, Migrator for Notes to Exchange (MNE) provides the following features:

Messages can be scheduled to be delivered at a specific time and date: Domino 10 allows scheduling email for future delivery. After migration, since any deferred unsent mail is still in the Domino queue, MNE will create a XXX-DeferredEmails.tsv in the MNE (or SSDM) log folder. The file will contain information about any unsent deferred emails that are timestamped for delivery after a specified date. The specified date is configured in an INI file. For information about configuring the date, see the [General] DeferredMailDate parameter in the Program Parameters Reference Guide.
Meeting attendees can invite others: Domino 10 supports a new feature for meetings, "Allow attendees to invite others”. The feature has three options: "Allow", "Allow and auto-approve", and "Don't allow". Outlook provides a similar feature by forwarding a meeting request to other users. However, the Outlook feature has only two options: "Allow forwarding" and "Do not allow forwarding". The following mapping is used when MNE migrates a meeting from Domino 10 to Exchange or Office 365.
Delegate calendar but not contacts: MNE supports the feature where you can delegate your calendar to someone but keep your contacts private when the new Domino 10 feature "Calendar and To Do" is selected.

This release introduces differential templates. In the Provisioning Wizard and in the Data Migration Wizard, when Save as template is selected, you can choose to create a Full Template or a Differential template.

A full template is a snapshot of the INI configuration file that was used to run a task when the template was created. This INI file includes all of the settings from the Global Default settings plus any additions or modifications that were made by the wizard used to run the task. A full template does not pick up new Global Default settings after it is created.

Instead of saving all of the INI settings in the template, a differential template only contains the INI settings that are different than those in the Global Default INI file. A differential template can pick up new Global Default settings.

After a software upgrade to 4.16.0, the navigation drawer contains the Upgrade Templates option. Click to upgrade all the full templates in the database to differential templates.

For information about authentication, including support for modern authentication, see “Authentication” in the Pre-Migration Planning Guide.

The MNE Exchange Admin account no longer requires the ApplicationImpersonation role.

In previous releases, when migrating to Office 365, there was a requirement that the Exchange Admin account be assigned the ApplicationImpersonation role. The role group that was created for the Admin Account Pool accounts was also configured with the ApplicationImpersonation role.

URL sections and associated parameters

The following configuration file settings were used to provide URLs for the different Office 365 Azure clouds. They are no longer required and have been removed.

The following parameters were configured using the URL’s in the sections above. These parameters have been removed from the product:

[Exchange] O365AuthenticationUrl: The correct URL is now automatically retrieve using the Autodiscover service.
[Exchange] O365EwsUrl: The correct URL is now automatically retrieve using the Autodiscover service.
[Exchange] OutlookServicesUrl: Not required since MNE no longer uses the REST API for migrating data.

Previously deprecated and removed in this release

The New-GlobalDefaultSettings cmdlet was deprecated in release 4.15.1. The cmdlet has now been removed from MNE in this release.

Other parameters removed

[Exchange] MapiErrorsToRetry: No longer relevant since migrations to mailboxes are no longer done using Outlook MAPI.
[Exchange] MigrateWellKnownFolderAclOnly: MNE now always migrates ACL’s for all folders to both on-premises and online mailboxes.
[Exchange] O365Tenant: The Office 365 tenant is now determined automatically using Autodiscover.
[PowerShell] PropagationDelay: Replaced by the new parameter [Exchange] O365MaxMailboxConnectionWaitTime.
[Exchange] EnableModernAuthentication: This SSDM parameter is replaced by the new [Exchange] DisableModernAuthentication parameter that applies to both the migration server and the SSDM. In the 4.15.2 release, Modern Authentication was supported only in the SSDM and was disabled by default. In 4.16.0 Modern Authentication is supported by both the SSDM and the migration server, and is enabled by default.


Table 1. Enhancements

MNE now supports migrating from Domino server 10 using Notes client 10.


MNE now uses Differential templates.


The Migration Prioritization screen has been added to the Data Migration Wizard. You can use this screen to prioritize users in the migration queue. For a description of the screen, see the MNE Administration Guide.


Added the Note ID of the relevant note to the following error:

ERROR: [4727-33-5-00000000]The update message has an inconsistent number of dates in the date attributes. The message cannot be migrated.


MNE offers a new parameter, [Notes] RootFolderAclMode that can be used to control how permissions are migrated to the root folder.

MNE utilizes a new component for writing migrated data to Exchange with the MAPI over HTTP protocol. This new component replaces the MAPI library provided by Microsoft Outlook.

For more information, see “Migrating folder ACLs and delegation (send on behalf of) rights” in the MNE Pre-Migration Planning Guide.


MNE now supports running the console as a domain user.

The user account used to run the MNE console must belong to the Local Administrators group. You can add the user account to Domain Admins group as the Domain Admins group belongs to the Local Administrators group by default.


MNE now supports SQL Server 2017.


The new parameter [General]DisableDebugPool allows you to disable the debug pool.

Set [General]DisableDebugPool=1 to tell the program to not write out the previous 128 DEBUG log lines before a WARNING or ERROR log when LogLevel is less than or equal to 2.


Numbers have been added to log errors that previously did not have numbers.


MNE now supports Windows Server 2019.


Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents