Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.16 - Pre-Migration Planning Guide

About the Migrator for Notes to Exchange documentation Introduction Critical considerations Other strategic planning issues Appendix A: Known limitations of the migration process

End-user desktops (if running the SSDM)

Any antivirus software must be configured to not scan the Migrator for Notes to Exchange program files directory or %temp% directory, or may be simply turned off, but may be restored after the program runs. If an antivirus scan misinterprets an Migrator for Notes to Exchange temporary file as a threat, it will try to "clean" the file, and the SSDM program call would then fail.

Server hosting the SSDM Scheduling Utility Web Service

ASP.net version 4.5 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.5.

Other required directories

Common application directory

The Migrator for Notes to Exchange applications and wizards need a directory that is accessible (read and write) to the admin accounts that will run the admin components and access source and target data and accounts, and that is shared (read only) to all users who will run the SSDM.

Shared log directory

The admin components need a shared log directory that is accessible (read and write) to the admin applications and wizards.

Shared desktop log directory

Optionally, a shared log directory for the log files generated by the Self-Service Desktop Migrator is required with write access for all users who will run the SSDM.

Authentication

In order to migrate Notes data to Exchange, MNE must log on to the target mailbox and provide authentication credentials to Exchange. MNE supports multiple authentication mechanisms.

MNE selects the appropriate authentication mechanism automatically using information from the Exchange Autodiscover service. If MNE detects that Modern Authentication is enabled on the migration target, it uses Modern Authentication as the preferred mechanism. If Modern Authentication is not supported, MNE reverts to legacy mechanisms such as Windows Integrated or Basic authentication.

Additional authentication details for the MNE Migration server are provided below for each of the migration components included with MNE:

Related Documents