Migrator for Notes to Exchange 4.17 - Scenarios Guide

Configure data destinations for different data types

In the SSDM, the destination within Exchange of migrated data is not selectable in the GUI, but is controlled by three parameters in the [General] section of the notesdtapp.ini file. MNE lets you specify a migration destination within Exchange or Microsoft 365 for each of the three primary data types to be migrated: archives, address books, and server-based data. Each type can be migrated to: user server-mail mailboxes, to user pst files, or to personal-archive (server-based) mailboxes.

The migration destination is not selectable in any screen of the SSDM (as it is in the Data Migration Wizard for batch migrations), but is controlled by three parameters in the [General] section of the notesdtapp.ini file:

Each parameter determines the destination of a particular data type (archives, PABs, or server mail), to be sent to the user server mail or to a pst file.

Option to migrate encrypted messages to PSTs

The SSDM can optionally direct encrypted messages to a separate PST file, no matter how many source.nsf files are selected for the migration. The feature is enabled/disabled by a notesdtapp.ini parameter that also specifies the full filename and extension for the target PST file:

In any subsequent SSDM runs, the program preserves the earlier PST files and automatically appends a digit to the designated filename to differentiate it from previously migrated PST files (filename.pst, filename_1.pst, filename_2.pst, etc.).

The default is [null], which disables the feature so that encrypted messages are sent to the same PST files as all other (unencrypted) migrated items.

This feature is enabled only when all migrated items are directed to PST files by:

If any of the item types are directed to a non-PST destination, the EncryptedPstFileSuffix parameter is ignored.

Option to track unmigrated messages

You can configure the SSDM to generate a folder of messages that are not migrated to the target. These items are referenced as doclinks in a new folder in the user Notes mailbox. You enable/disable and configure the feature using two parameters in the [Notes] section of the notesdtapp.ini file:

The WriteFailedMessageListToThisMbxFolder parameter specifies a name for the folder to be added to the user mailbox to contain the unmigrated messages. WriteFailedMessageListClass specifies one or more types of message failures for the feature to capture. Valid keyword values are: Errored, Skipped and Filtered.

To specify more than one type, separate multiple keywords by the pipe ("|") character, as in this example:

The example tells the SSDM to create copies of any Errored, Skipped and/or Filtered messages and save them in a new folder named FailedMessages in the user mailbox.

You enable this feature by entering any value for the WriteFailedMessageListToThisMbxFolder parameter. (If that parameter is omitted or its value is left empty, the feature is disabled and the WriteFailedMessageListClass parameter is ignored.) The feature is disabled by default (WriteFailedMessageListToThisMbxFolder is omitted or its value is [null]), and by default WriteFailedMessageListClass=Errored (only).

Option to show (or hide) Error Log Report button

The SSDM is configured by default to offer an Error Log Report button that lets the user view the program log file for more information about any errors that may have occurred during the program run. (The button does not appear if no errors have occurred.) From the Error Log Report, a user may also save the log file or print a copy.

This feature is enabled by default, but may be disabled (so the button does not appear in any case) by a boolean parameter in the notesdtapp.ini configuration file:

Disabling the button may be useful in some environments where accessing a large log file might cause a user desktop to hang.