Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.16.1 - Release Notes

Resolved issues

Resolved an issue in which, during group migration, MNE could not correctly synchronize membership when MNE encountered Domino group members that had a blank SMTP address. Blank SMTP addresses can occur if Domino groups have members/senders that were added as contacts instead of as mail-enabled user members. Now MNE evaluates the primary SMTP address and only attempts to remove members when the SMTP address is valid.


Resolved an issue where MNE, during group provisioning, would log an error and exit the provisioning process if there was more than one group with the same display name. In on-premises Exchange and Office 365, it is possible to have duplicate group names. Now MNE uses the group SMTP address which is unique.


Resolved an issue in which resource reservations that were created by an Exchange organizer through the Coexistence Manager for Notes (CMN) mail connector were not migrated correctly if the exception list contained Subject. If a recurring meeting has an meeting instance that does not follow the defined recurrence rule, an exception attachment is added. In this case, the migrated subject line incorrectly contained [[CMN]] and [[\CMN]],


Resolved an issue where an HTML email with an inline image (such as a company logo) was migrated and the Outlook email showed an attachment icon but the email had no actual attached files.


Resolved an issue where a customer migrated an iNotes message from a Notes draft folder (reserved view) to an Exchange draft folder. However, the migrated message did not contain the mail recipients (the email addresses in the TO, CC, and BCC fields).


Resolved an issue where the SSDM crashed on exit when run on a workstation that did not have Microsoft .NET Framework 4.0 runtime installed.


Resolved an issue where a customer could not migrate a resource (meeting room) with a long name (left side over 20 characters) to Office 365, using the Microsoft Azure Active Directory Synchronization (DirSync) tool. When attempting to migrate the room, the customer got an error "unable to find object". In addition to limiting the sAMAccountName to a maximum of 20 characters, MNE was incorrectly truncating the mailNickName (Alias) and the userPrincipalName (UPN) to 20 characters as well.


Resolved an issue in which a customer found that two duplicate copies of Group To Do task requests were migrated to the Sent Items folder in Exchange. This issue affected Group To Do tasks that were created with the Notes client and which were set for Repeat (recurrences). The issue did not affect Group To Do tasks created with the iNotes client or created with the Notes client for a single task instance (no repeating).


Resolved an issue in which a data migration task that executed using a template that was configured with the Manage mail routing task set to route new mail to Exchange did not update the forwarding address or retain “Append Domino domain to forwarding address” on the person document in the Notes directory.


Resolved an issue so that the Notes Directory Export is now able to update the primary addresses which had conflicts in a previous Directory Export and for which the conflicts were resolved on the Domino server.


Resolved an issue in which, when migrating a large amount of mail, MNE could not correctly display the migration volume (number of emails and size). Now, when the number of migrated emails is very large (one million or more), MNE displays a rounded value such as 1.2M for the migration volume (number of emails) value. You can hover your cursor over the field to see the exact value.


Resolved an issue where, if you migrated a mail message to Exchange from an external sender, the name is displayed as the sender but there is no SMTP address. If you clicked on Reply in Outlook, you could not respond to migrated emails from external senders. This issue did not occur if you replied in OWA.


Resolved an issue so that migrations that use the Mne MapiHttp library will support the migration of Journal Entry messages.


Resolved an issue in which the user status data did not display if the SQL server version was older than SQL Server 2012.


Resolved an issue where MNE failed to migrate to PST if the “Resolve attendees for archive mail” option is selected for an Office 365 target.


Resolved an issue in which the control of "Append Domino domain to forwarding address" was not available when you selected Use current Domino internet address option on the Specify Notes to Exchange Mail Forwarding page in the Data Migration Wizard.


Resolved an issue where the file and the line number was missing from the log entry when the information should be included. For example, the log did not show the file and the line number for a message that was filtered out or skipped in a migration.


Resolved an issue in which a calendar item that was created as an appointment that repeated with a single instance was missing the parent document and deemed corrupted by the MNE tool and MNE skipped migrating the calendar item.


Resolved an issue in which a message is migrated without body due to missing RTF temporary files. Now MNE stops migrating a message if it cannot find the exported RTF files, which allows MNE a chance to remigrate the message.


Resolved an issue when migrating with the MNE MAPI/HTTP library, migrated contacts were displayed multiple times in the Outlook Address Book search dialog with the same Email Address and Display Name.


Resolved an issue in which, after upgrading MNE from 4.15.x to 4.16.0, a customer attempted to migrate the Notes archive to Exchange Online archive. The archive migration created duplicates in Outlook when the archive migration was repeated. The issue was found for migration to both Exchange Online hybrid and native environments.


Resolved an issue in which, when customer was migrating user data for a user collection in a non-English environment, the Data Migration Wizard continuously displayed the Check for Outlook Folders prompt in the Select Destination Exchange Server page. Even when the customer clicked the Do not prompt me again check box, the prompt was displayed for each user in the collection. The prompt was displayed even if the parameter [General] DeclineFolderCheck=0 was set to disable the folder check.


Resolved an issue in which a WMF format image in Domino was extracted and converted to Bitmap format in Exchange by MNE. The file size increased an excessive amount (1.5M to 60M), which resulted in Outlook being unable to display the image.


Resolved an issue to handle the Microsoft deprecation of Basic Authentication for Exchange Online connections using remote PowerShell (RPS) on October 13, 2020. Modern Authentication is now the default authentication mechanism for Exchange Online remote PowerShell calls by Migrator for Notes to Exchange applications. See the Microsoft announcement at this Microsoft link.


Resolved an issue in which MNE failed to migrate folder permissions or delegate access for a mail user when the migration used the MNE MAPI/HTTP library.


Resolved an issue in which the customer experienced permission errors during group provisioning to Office 365 while keeping groups in sync with corresponding Notes groups. Now the BypassSecurityGroupManagerCheck parameter is added to the PowerShell command when setting group properties. It also reports an error if the PowerShell command fails.


Resolved an issue in which the customer wanted user folders to be migrated under the default Inbox in Outlook and edited the INI settings to include:


Though the folders were migrated to this location, MNE also created an empty folder at the same level as the inbox called Inbox1.


Resolved an issue in which, when the Keep groups in sync with corresponding Notes' groups check box was selected in the wizard and MNE was unable to contact the GC (Global Catalog) server and verify the group members, MNE deleted the group members from Active Directory.


Resolved an issue in which the sequence numbers of rescheduled, recurring meeting/appointment series and instances were not migrated to the Exchange target as the MAPI property PidLidAppointmentSequence. Some customers had a third party tool which needed to read this property to process the migrated meeting/appointment.


Resolved an issue in which Export Notes Directory tasks and other scheduled tasks would fail to run when MNE was installed using a non-default folder name.


Resolved an issue in which, if you wanted to change the logging levels to verbose for debugging purposes, you had to manually modify the individual configuration files for each MNE component. Now you can set the logging level for all MNE components in the MNE Administrator Console using the Shared Directories | Log Level settings.


Resolved an issue to meet the new Microsoft LDAP binding security requirements by changing the default value to 65 (the combination of ADS_SECURE_AUTHENTICATION and ADS_USE_SIGNING) for the [ActiveDirectory] OpenFlags and [ActiveDirectory2] OpenFlags parameters. Microsoft recommends administrators harden the configurations for LDAP channel binding and LDAP signing on Active Directory domain controllers. For more information and a list of valid options, see this Microsoft article.


Resolved an issue in which the data migration would be interrupted by the following error, 'System.OutOfMemoryException', when the customer was migrating a non-standard MIME message using the MNE MAPI/HTTP library for the migration.


Resolved an issue in which, in the Admin console under View Summaries, the customer would export the User and Resource Details Summary report to TSV (tab separated value) format. When the .TSV file was opened, the last three columns were empty.


Resolved an issue in which, when a customer was running a migration job, the following error occurred: "The primary key is duplicated to the table T_NMEDataStoreMigrationWorkItemRuns when migration is canceled." Viewing the log files, it was determined that the migration was canceled and the existing migration results were successfully inserted to the T_NMEDataStoreMigrationWorkItemRuns table, but MNE attempted to store the same results again which caused the error.


Resolved an issue in which a migrated meeting proposal request (such as Propose New Time) did not contain the new Proposal Time and the meeting originator could not respond to the proposal.


Resolved an issue in which MNE appeared to overwrite the first PST file when migrating a large archive. The issue occurred when the PstRootDir contained a valid path separator such as / or \ which caused an issue when MNE was looking for the next PST file into which to migrate. The fix removes the extra path separators if they are specified.


The PSRetryWait parameter was not honored by some PowerShell commands which resulted in provisioning errors. Though MNE was configured to perform multiple retry attempts to issue some PowerShell cmdlets and to wait 60 seconds between retries (PSRetryWait=60), the multiple retries were attempted within one minute.


Resolved an issue in which MNE failed to migrate a base64 encoded MIME message that had a specific message body size (e.g. 8212 bytes).


Resolved an issue in which the SSDM (64-bit version) stopped with the error "[4651-33-126-00000FF6]Unable to migrate recurring appointments/tasks" when scanning recurring appointments.


Resolved an issue in which the Topic field in Notes was incorrectly migrated to the Subject field in Exchange for some special Databases. A new parameter named [Exchange] MigrateTopicAsCategory is added to allow you to correct the issue.

By default the parameter is set to 0, meaning that MNE will not change current logic. When you set the parameter to 1, MNE migrates Topic as Category, and will not override Subject with Topic.


Resolved an issue in which a WMF format image with a transparent background in Domino was extracted and converted to Bitmap format in Exchange by MNE. The conversion had a slight distortion in the image over the transparent background.


Resolved an issue in which the GIF image file size expanded more than 6 times and OWA could not display the image after migration. This issue was introduced in version 4.16.0 Update 5, when resolved issue 190565 improved the GIF image quality but caused the file size to grow excessively. Now MNE will reduce the GIF image file size. You might see minor quality loss for some GIF images which have a transparent background or that have been resized in Domino.


Known issues

Most of the known issues and limitations of any migration process are due to feature inconsistencies between the source and target environments. Features that are available in the Notes environment cannot be migrated to a target environment that does not offer the same or comparable features. Other limitations are due to feature incompatibilities where similar features are available in both the source and target environments, but their implementations are so different that migration is impractical. In any case, most administrators regard these limitations as trivial or incidental to an overall migration project.

Quest distinguishes between known issues (listed here), which are believed to be temporary and likely to be resolved in a future release, and known limitations, which are believed to be inherent to the process and environmental architectures, and are likely permanent. Appendix A of the MNE Pre-Migration Planning Guide provides a list of known limitations of the migration process as facilitated by the current version of Migrator for Notes to Exchange.

The following is a list of known issues, including those attributed to third-party products, known to exist at the time of this release.

Draft calendar items are migrated to Exchange, but after migration they are not fully functional.


MNE truncates a Notes user name if the Domino name exceeds the maximum name length in Exchange, but any subsequent run of the Directory Export Wizard generates a duplicate object record since the wizard does not recognize the truncated name compared to the Notes original name.


When the Data Migration Wizard removes forwarding from an Office 365 user, and there is no local AD, the wizard successfully completes its run but generates three errors, two of which are failed attempts to locate the user in AD.


When a recurrence pattern for a series of meetings is supported in Notes but not supported in Outlook, and when the organizer OR the attendee, but not both, has been migrated, some updates/cancellations/responses for single occurrences will not work.


A migrated recurring meeting may not correctly show the accept/decline status of a Notes user to whom a meeting invitee delegated the invitation if the invitation was delegated and the delegatee accepted or declined the invitation prior to migration.


Exchange does not allow other applications (including Notes Migrator for Exchange) to set the owner property of items migrated to resource mailboxes.


When migrating only iNotes contacts, the Notes Mail Files screen does not appear so you cannot choose to migrate via the server or the file system. The program runs via file system if that is what you chose for your last migration unless you go into the Task Parameters or INI file and change it.


The MNE Migration Worker process can crash when configured to share a single MAPI profile across all worker processes. This issue only occurs when the MAPI/HTTP protocol is enabled. The default configuration settings are set to avoid this issue but you can encounter the issue if the following combination of INI settings are used:


The SSDM might crash when installed on a non-English operating system with Outlook 2016 and if the following parameter is set:

To resolve the issue, set [Exchange] RewriteRTF=7.


When migrating offline, the HTMLdoclinks program parameter in the [General] section of the Data Migration Wizard task parameters must be set to 0 (zero). The HTMLdoclinks=0 setting tells the wizard to migrate Notes doclinks as Notes-style doclinks which can be opened in Exchange only if a Notes client is installed on the client workstation. By default, (HTMLdoclnks=1) Notes doclinks migrate to Exchange as HTML-style links, which can be opened in a web browser if the user is able to use iNotes, but the default setting causes errors in an offline migration.


Outlook archiving is not applied to migrated messages within the age range set for auto-archiving, because Outlook determines message age by Last Modified time, which it updates to the migration date/time upon migration. Since all migrated messages become zero days old as soon as they are migrated, and Outlook does not allow the Data Migration Wizard to reset the property to the true pre-migration date/time, the Outlook archiving feature skips the messages until they have "re-aged" to the archive age (typically 30 days) following migration. At this time all of the migrated messages will be archived.


When saving message reference attachments from OneDrive using Outlook 2016/2019, an error message is displayed.

Though earlier versions of Outlook client do not support reference attachments, MNE provides parameter settings [Exchange] SupportOversizedAttachmentsInLegacyOutlook=1 to migrate oversized attachments to OneDrive and adds a link to the uploaded attachments as an HTM attachment in the message.

However, for newer versions of the Outlook client (2016/2019), when MNE tries to save the migrated message reference attachment, the following error is displayed “Outlook cannot save the file. file name or directory name is not valid.” The Outlook Web Client (OWA) does not exhibit this problem and allows the user to save reference attachments.

Instead of clicking Save, the user can click Open and save the attachment from OneDrive.


System requirements

Before installing MNE, make sure your environment meets (or will meet) these minimum hardware and software requirements.

Domino servers

Supported Domino source environments (all ranges inclusive):

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating