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

Verify .Net version and CAS permissions

The SSDM requires Microsoft .Net Framework version 2.0 be installed on each end user's workstation. If end users will run the SSDM application from a network share (rather than from each user's own local copy), then each user's 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.

For the SSDM to authenticate with Office 365 using Modern Authentication, .Net 4.5 or later must be installed. If .Net 4.5 or later is not installed, the SSDM falls back to migrating without Modern Authentication.

If, for example, SSDM resides in a folder \\server1\shared\SSDM\, the necessary permissions can be granted by an administrator executing this command on the client machine:

For more information about CasPool.exe, see this article in Microsoft online technical library, and see also the Microsoft KB article: How to determine which versions and service pack levels of the Microsoft .Net Framework are installed.

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 Migrator for Notes to Exchange’s Notes Migration Manager. 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: Remember that any antivirus software on an end user’s SSDM workstation must be configured to not scan the Quest program files directory or %temp% directory. Or a user may simply turn off any antivirus app prior to running the SSDM application, and then restore it after SSDM runs. You may want to provide instructions for how to turn off (and back on) your users’ 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 will generate 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 simply 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 may also include a copy of Quest’s Self-Service Desktop Migrator User Guide (in PDF format), which explains how to operate the per-desktop program from the end user’s point of view. The SSDM User Guide accompanies your Migrator for Notes to Exchange software. You may 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 simply 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 install 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 topics below 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 in full detail in the subtopics below:

Other SSDM customization features let you enforce or eliminate certain choices in accordance with a particular migration strategy. For example, if you intend to migrate users’ server mail and address books in batches, and then use the Desktop Migrator 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 more detail below in Silent mode options in per-desktop migrations.

Documents connexes