Chat now with support
Chat mit Support

Migrator for Notes to Exchange 4.16.3 - Release Notes

Quest® Migrator for Notes to Exchange 4.16.3

Quest® Migrator for Notes to Exchange 4.16.3

These release notes provide information about the Quest® Migrator for Notes to Exchange (MNE) 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 such as Microsoft 365.

MNE 4.16.3 is a minor release, with enhanced features and functionality.


What's New

NOTE: One-click registration for Azure App registration is not supported in 4.16.3. To configure the migration of oversized attachments to OneDrive, you must register the MNE as an Azure app on Azure portal. For more information, see the instructions in the MNE Administration Guide on pages 21-22.

The following parameters are removed or added to Migrator for Notes to Exchange in this release.

The following new parameters are reserved for use by Quest PSO (Professional Services) and Quest Support for specific migration projects only:

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.

The MNE prerequisite checker does not recognize the supported HCL Domino server version 12 and the Notes client version 12 as a supported version.


MNE does not support migrating Notes Sametime Chat messages.


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


When migrating a contact’s birthday property or anniversary property, MNE creates a recurrent appointment in the personal calendar for the contact’s birthday or anniversary. However, MNE does not create a link between the contact object and the newly created appointment. If you update the birthday or anniversary in the target, the appointment created by MNE is not updated automatically, and Outlook will create a new recurrent appointment in the personal calendar.


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.


Knowledge Base
Benachrichtigungen und Warnmeldungen
Technische Dokumentationen
RSS Feed
Unterstützung bei der Lizenzierung
Technische Support
Alle anzeigen
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen