Chat now with support
Tchattez avec un ingénieur du support

Migrator for Notes to Exchange 4.16 - Scenarios Guide

About the Migrator for Notes to Exchange documentation Scenarios overview Migration to a proprietary Exchange
Migration to a proprietary Exchange target Pre-migration preparations Batch migration process Post-migration activities
Migration to Microsoft Office 365
Pre-migration preparations Batch migration process Post-migration activities
SSDM (per-desktop) migration

Enabling/disabling and configuring Notes "Active Mail" processing

Active Mail processing is an optional feature that can detect and convert Notes rich-content features whereby messages carry "live" or "active" functional content. For more information about Active Mail, see Migrating Notes “Active Mail” in chapter 3 of Migrator for Notes to Exchange’s Pre-Migration Planning Guide.

Migrator for Notes to Exchange’s Data Migration Wizard offers the options to enable/disable and configure Active Mail processing, but in the SSDM these features are enabled and configured only by program parameters in the notesdtapp.ini file. Active Mail processing is disabled by default (if the parameters are omitted from notesdtapp.ini).

To enable and configure Active Mail processing in SSDM, set these parameters in notesdtapp.ini:

[Notes] MigrateActiveMail=<#>
Boolean; default = 0
Determines whether Migrator for Notes to Exchange's Active Mail features are enabled (1) or disabled (0).
[Notes] ActiveMailTemplatePath=<string>
String; default = <Migrator for Notes to Exchange installation directory>\ActiveMail.ntf
Specifies the full path (including filename) of the Migrator for Notes to Exchange Active Mail template file. This file provides the information necessary for Migrator for Notes to Exchange to properly process the Notes OND attachment and produce the Active Mail attachment file. Migrator for Notes to Exchange installs a default ActiveMail.ntf to the Migrator for Notes to Exchange installation directory, and that path is the default string for this parameter, but you can specify a different path
[Notes] ActiveMailNotificationMessagePath=<string>
String; default = <Migrator for Notes to Exchange installation directory>\ActiveMailNotificationMessage.txt
Specifies the full path (including filename) of the Migrator for Notes to Exchange Active Mail notification message text file. The SSDM inserts the contents of this file at the top of the body of any migrated message containing Active Mail. Migrator for Notes to Exchange installs a default file, ActiveMailNotificationMessage.txt, to the Migrator for Notes to Exchange installation directory, and that path is the default string for this parameter, but you can specify a different path.
NOTE: The text file must be UTF-8 encoded and must contain a placeholder, called $ActiveMailAttachment$, that the SSDM will replace with the Active Mail NSF attachment when the message is migrated. Since the contents of this file become part of an RTF body, characters like "\", "{", and "}" must be escaped with a leading "\" (so they become, respectively, "\\", "\{", and "\}").
[Notes] ActiveMailAttachmentName=<string>
String; default = ActiveMail.nsf
Specifies the filename you want MNE to assign to Active Mail attachment files, as it will appear in the Outlook message.
[Notes] ActiveMailTypes=<#>
Integer; default = 31
Specifies which type(s) of Active Mail will be processed. The value here is the sum of the associated values of these individual types:
For example, to tell the SSDM to process encrypted mail (1), stored forms (2), and dropdown sections (32), the ActiveMailTypes value would be 35 (1 + 2 + 32). The default value 31 tells the SSDM to process every type except dropdown sections.

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. Migrator for Notes to Exchange lets you specify a migration destination (within Exchange or Office 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: users' server-mail mailboxes, or users' 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 these three parameters in the [General] section of notesdtapp.ini:

Each parameter determines the destination of a particular data type (archives, PABs, or server mail), to be sent to the user's 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 will preserve the earlier PST files and automatically append a digit to the designated filename to differentiate it from previously migrated PSTs (filename.pst, filename_1.pst, filename_2.pst, etc.).

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

Note that this feature is enabled only when all migrated items are directed to PSTs by:

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

Option to track unmigrated messages

The SSDM can be configured to generate a folder of messages that are not migrated to the target. These items will be referenced as doclinks in a new folder in the user's Notes mailbox. The feature is enabled/disabled and configured by two program parameters in the [Notes] section of notesdtapp.ini:

The WriteFailedMessageListToThisMbxFolder parameter specifies a name for the folder to be added to the user's 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:

This 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's mailbox.

The feature is enabled 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).

Documents connexes