Quest® Migrator for Notes to Exchange 4.16.3
Release Notes
December 2024
These release notes provide information about the Quest® Migrator for Notes to Exchange(MNE) release.
Topics:
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.
The following is a list of what’s new in Migrator for Notes to Exchange 4.16.3.
-
Support for HCL Domino 12 is added.
-
Support for Exchange Online Management 2.0.5 is added.
-
MNE now uses the Microsoft Graph SDK v1.0 PowerShell module, instead of the deprecated Azure AD Graph module, to connect to and execute administration tasks in Microsoft 365.
|
|
NOTE: References to Office 365 are changed to Microsoft 365 to reflect the changes in the Migrator for Notes to Exchange user interface. (Microsoft has rebranded the Microsoft Office cloud-based apps to Microsoft 365.)
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. |
|
|
IMPORTANT: Due to Microsoft API updates, use of Migrator for Notes to Exchange 4.16.3 with Exchange Online requires updating to the latest maintenance release. Visit the Quest Support portal to obtain the latest 4.16.3 update. |
Parameter changes
The following parameters are removed or added to Migrator for Notes to Exchange in this release.
Added
The following new parameters are reserved for use by Quest PSO (Professional Services) and Quest Support for specific migration projects only:
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.
Table 1: General known issues
| The MNE prerequisite checker does not recognize the supported HCL Domino server version 12 and the Notes client version 12 as a supported version. |
406869 |
| MNE does not support migrating Notes Sametime Chat messages. |
320952 |
| Draft calendar items are migrated to Exchange, but after migration they are not fully functional. |
100000 |
| 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. |
100071 |
| 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. |
100088 |
| 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. |
227308 |
| 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. |
242781 |
| Exchange does not allow other applications (including Notes Migrator for Exchange) to set the owner property of items migrated to resource mailboxes. |
57381 |
| 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. |
57447 |
|
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:
[Exchange]
AutodiscoverDisableMapiHttp=0
MapiUseSharedProfile=1 |
727841 |
| 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. |
243658 |
Table 2: SSDM known issues
|
The SSDM might crash when installed on a non-English operating system with Outlook 2016 and if the following parameter is set:
[Notes] RewriteDocLinks=1.
To resolve the issue, set [Exchange] RewriteRTF=7. |
709742 |
Table 3: Offline Migration known issues
| 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. |
30886 |
Table 4: Offline Outlook known issues
| 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. |
58004 |
|
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.
Workaround
Instead of clicking Save, the user can click Open and save the attachment from OneDrive. |
184487 |
|
|
IMPORTANT: The requirements listed here document the basic hardware and software requirements for Migrator for Notes to Exchange (MNE). MNE also requires certain configuration considerations and account permissions. Be sure to see these additional requirements in the MNE Pre-Migration Planning Guide, in chapter 1 under Configuration requirements and account permissions. |
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):
-
Notes/Domino 12.0.0-12.0.2
-
Notes/Domino 11.0.0 and 11.0.1
-
Notes/Domino 10.0.0 and 10.0.1
-
Notes/Domino 9.0.0 and 9.0.1
-
Notes/Domino 8.5.0-8.5.3, and 8.0.0-8.0.2
-
Notes/Domino 7.0.0-7.0.4
-
Notes/Domino 6.x
Microsoft Exchange servers
|
|
NOTE: Migrator for Notes to Exchange supports Cumulative Update (CU) releases for all supported versions of Exchange. If you encounter an incompatibility with a newly released CU, contact Quest Support for a resolution. |
Supported Exchange target environments:
-
Exchange 2019: RTM
-
Exchange 2016: RTM
-
Exchange 2013: RTM and SP1
-
Exchange 2010: RTM, SP1, SP2 and SP3
-
Microsoft 365:
SQL server
MNE requires access to a Microsoft SQL Server. The following versions are supported:
-
SQL Server 2008
-
SQL Server 2008 Express Edition
-
SQL Server 2008 R2
-
SQL Server 2008 R2 Express Edition
-
SQL Server 2012
-
SQL Server 2012 Express Edition
-
SQL Server 2014
-
SQL Server 2014 Express Edition
-
SQL Server 2016
-
SQL Server 2016 Express Edition
-
SQL Server 2017
-
SQL Server 2017 Express Edition
-
SQL Server 2019
-
SQL Server 2019 Express Edition
Note the following:
-
SQL must be installed either on the administrator’s migration server or on a separate server, with a minimum of 20 GB free disk space.
-
You can use an existing (installed) MS SQL Server, or install a new instance of SQL Server using one of the supported versions.
-
Quest recommends a full-featured (non-Express) edition of SQL Server for best performance of the MNE Directory Export Wizard, particularly for sites with a large number of groups or domains.
MNE admin migration servers
Table 5: Supported operating systems for migrations
| Windows Server 2019 |
64-bit |
• |
• |
| Windows Server 2016 |
64-bit |
• |
• |
| Windows 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 |
• |
• |
Table 6: Other Requirements
| 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:
-
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 Microsoft 365 |
-
.Net Framework 4.8
-
Microsoft OLE DB Driver for SQL Server 18.2 (or later) or Microsoft SQL 2012 Native Client.
-
Microsoft Command Line Utilities for SQL Server (a free download from the link provided in the MNE Autorun).
NOTE: This component is required only if SQL Server is not installed locally (i.e. the MNE Server is connecting to a remote SQL instance).
-
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). If PowerShell 3.0 does not come with your OS, you can download Windows Management Framework 3.0 at this Microsoft link.
-
Notes must be installed in single-user mode and configured. The Notes client version must be one of 6.0.0-12.0.2 (all ranges inclusive), and should match or be higher than the Domino server version.
-
The 32-bit edition (only) of Outlook 2019, 2016, 2013 or 2010. The Outlook client must also conform to the Microsoft 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.
-
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 Microsoft 365 target |
|
To install Exchange Online Remote PowerShell V3.1 Module
-
Install or update the Microsoft PowerShellGet module. For details, see Installing PowerShellGet.
-
Close and re-open the window.
Now you can use the Install-Module cmdlet to install the EXO V2 module from the PowerShell Gallery. Typically, you want the latest public version of the module.
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).
-
To install the latest EXO V2 version supported by MNE in this release, run the following command:
Install-Module -Name ExchangeOnlineManagement -RequiredVersion 2.0.5
Windows Remote Management (WinRM) on your computer must allow basic authentication (enabled by default).
-
To verify that basic authentication is enabled for WinRM, run the following command in a Command Prompt:
winrm get winrm/config/client/auth
-
If you don't see the value Basic = true, run the following command to enable basic authentication for WinRM:
winrm set winrm/config/client/auth @{Basic="true"}
Important: Avoiding permission conflicts
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.
Best Practices for Microsoft 365 Multi-Geo tenants
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: End-user Desktop Requirements
| Supported operating systems |
-
Windows 10, Windows 8.1, or Windows 8, 32-bit or 64-bit edition.
-
Windows Server 2019: 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. |
| 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 |
-
12.0.0 or 12.0.2 (inclusive)
-
11.0.0 or 11.0.1 (inclusive)
-
10.0.0 or 10.0.1 (inclusive)
-
9.0.0 or 9.0.1 (inclusive)
-
8.5.0–8.5.3 (inclusive)
-
8.0.0–8.0.2 (inclusive)
-
6.0.0–7.0.4 (inclusive) |
| 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: If you are upgrading from 4.14.1 or earlier, 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. |
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.16.. Make a backup 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.
