Migrator for Notes to Exchange 4.17 - Scenarios Guide

Distribution of SSDM program and user notifications

If your users (rather than you or another admin) will run the SSDM, you will need to tell them where the program file is, how to prepare their desktops for the program runs, and how to run the program.

IMPORTANT: Verify that all users have read-only access to the share containing notesdtapp.exe (the SSDM program file) and the AddressTranslation.bin file. The path is specified in the Common application directory field, on the Shared Directories Configuration screen in the MNE console. SSDM requires access to the address translation file generated by the Directory Export Wizard to convert addresses in messages, address books, and calendar content.

IMPORTANT: Any antivirus software on an end-user SSDM workstation must be configured to not scan the Quest program files directory or %temp% directory. Or a user can turn off any antivirus software prior to running the SSDM application and restart it after SSDM runs. You may want to provide instructions for how to turn off (and back on) antivirus and desktop-search applications. If an antivirus scan misinterprets an Migrator for Notes to Exchange temporary file as a threat, it will try to "clean" the file, which generates an error when the program call fails.

Typically an administrator will send an email to migrating users with a link to the SSDM program so each user can click the link in the email to launch the program. The email can also provide other pertinent information (see preceding notes), to minimize help-desk calls.

You can also include a copy of the Self-Service Desktop Migrator User Guide in PDF format, which explains how to operate the per-desktop program from the end-user point of view. The User Guide is included with your “clean” software. You can either copy the PDF file to a public-access folder and link to it from the same email that introduces the SSDM to your users, or add it to the email as an attachment.

If you want to run the SSDM with App-V

The SSDM must be sequenced in with the Outlook virtual application package. The SSDM cannot be sequenced separately nor can it access a local Outlook installation directly. The Notes client must be installed locally or also sequenced in with the Outlook package.

Also, you must edit the OSD file for NotesDtApp.exe. Find:

... and change the parameter value from windows to console.

Configuring the SSDM

The SSDM can be configured to behave differently in different environments to suit different needs and preferences. The following topics explain how to configure the SSDM to suit your needs. These program customizations are accomplished by manipulating certain parameters in the notesdtapp.ini file as described:

Other SSDM customization features let you enforce or eliminate certain choices to match your migration strategy. For example, if you intend to migrate users’ server mail and address books in batches and use the SSDM to migrate only user archives, you can customize the SSDM to migrate only archives and to not offer the option to migrate server mail or address books. These “silent mode” features are described in Silent mode options in per-desktop migrations.

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 information about Active Mail, see Migrating Notes “Active Mail” in chapter 3 of the Migrator for Notes to Exchange Pre-Migration Planning Guide.

The MNE Data Migration Wizard provides options to enable/disable and configure Active Mail processing. In the SSDM you can enable and configure these features using 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 the following parameters in the notesdtapp.ini file:

NOTE: The text file must be UTF-8 encoded and must contain a placeholder, called $ActiveMailAttachment$, that the SSDM replaces with the Active Mail NSF attachment when the message is migrated. Since the content of this file becomes part of an RTF body, characters such as "\", "{", and "}" must be escaped with a leading "\" (so they become, respectively, "\\", "\{", and "\}").