Migrator for Notes to Exchange 4.15.2 - Scenarios Guide

SSDM (per-desktop) migration

Why and when to use the SSDM

Batch migrations and per-desktop migrations are performed using different migration engines, both included with Migrator for Notes to Exchange. This chapter describes administrator planning for and deployment of Migrator for Notes to Exchange’s per-desktop Self-Service Desktop Migrator (SSDM). For batch migration (multiple users at a time, performed by an administrator), see the Batch Migration sections of the preceding two chapters, for migration to a proprietary Exchange target and migration to Microsoft’s Office 365.

The SSDM is used by an end user, or by an administrator on behalf of an end user, to extract a single user’s Notes data and migrate it to Exchange. Depending on your circumstances and preferences, you may choose to migrate some or all of your users one at a time, from each user’s desktop, using the SSDM. For example, some administrators prefer the per-desktop tool to migrate user archives when the archives reside on users’ individual workstations, where that option seems easier than prepping exported user data in the SQL database with per-user values for the locations of all the local archives.

Migrator for Notes to Exchange’s SSDM provides a distributed migration option, which runs in memory on the user’s workstation. SSDM runs from a share, offers an optional Silent Mode to minimize end user interaction, and does not install anything locally. These features can eliminate the need for desktop visits by the admin during or after the migration, although an admin can run the SSDM at user desktops if he/she chooses, perhaps selectively for only some users. The per-desktop migration option can be used for a portion of the migration (e.g., for local archives) or to migrate all of a user’s data: the Exchange mailbox, PST files, or both.

Before running the SSDM

Verify all of the Pre-Migration Preparations are complete before the first desktop migration is performed (see the Pre-Migration Preparations sections of the preceding two chapters, for migration to a proprietary Exchange target or to Microsoft’s Office 365). These pre-migration tasks are performed just once prior to the first run of either the SSDM or Data Migration Wizard (not repeated for each run of a migration application).

If you are migrating with coexistence: An update of the exported directory data in the SQL database may be necessary if any users have joined or left the organization since the last run of the Directory Export Wizard. For the recommended procedure to update the directories and update Quest data tables, see the topic How Do I Synchronize Directory Data and Update the SQL Server Database? in Appendix A of the Migrator for Notes to Exchange Administration Guide.

Consider also:

SSDM customization options

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 under Configuring the SSDM below.

Some 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.