Migrator for Notes to Exchange 4.15.2 - Administration Guide

How to configure the service to start up with the built-in system account

If the service still does not work with the specified user account, you can configure the service to start up with the built-in system account using the following steps:

NOTE: You typically do not need to configure a service to interact with the desktop, so you can leave the Allow service to interact with desktop checkbox unselected.

When you attempt to open the properties of a service using the Services tool in Control Panel, the computer may stop responding (hang) and/or may display this error message:

This message can occur due to a logon failure with the Remote Procedure Call (RPC) service or some other dependency service. Some services cannot start until after dependency services have started (for example, the Workstation service).

If you cannot start the Services tool, follow these steps to configure the service to use the built-in system account:

CAUTION: These steps tell you to modify the registry. Serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. Quest strongly recommends that you back up the registry before you modify it, so you will be able to restore the registry if a problem occurs.

If you cannot start Registry Editor, you can modify the service account information by performing a parallel installation. See Microsoft’s Knowledge Base for information about parallel installations.

Although most system services are configured to use the system account credentials for logon by default, you can configure them to use a specific user account instead. When a user's password is changed, the password information field is not automatically changed for services.

You can start a service with the local system account or by specifying a specific user account and password. If you choose to specify a user account and password, it is important that the account name and password remain constant. For example, this account should not be required to change password or be renamed. If these two events (or other similar events) occur, you should also update the logon credentials for the service.

How do I send pre- or post-migration notification emails to end users?

The Data Migration Wizard contains a feature originally developed to facilitate notification emails to users at the time of migration, but this feature can also be used to send personalized emails to users before or after they are migrated. For example, you can use such notifications to announce an upcoming migration, explain the implications to end users, and tell them what they can expect and what will be expected of them. To send pre- or post-migration emails like this you can run the Data Migration Wizard to only send the messages—but not mailbox-enable users, or any other migration or administrative functions.

How do I perform an offline migration?

Migrator for Notes to Exchange supports offline migration—a strategy in which Notes source data that was previously extracted from Notes is migrated directly to the Exchange target. An offline strategy can be valuable:

An offline migration can be accomplished by either of these two approaches:

See the Offline migration topic in chapter 1 of the Migrator for Notes to Exchange Scenarios Guide for more information, including requirements and guidelines, for offline migrations.

How do I migrate resources?

Exchange 2010 and later permit the differentiation of resources into three types: Room, Equipment and Online Meeting. The Directory Export Wizard copies the resource type designations from Domino into the object records in the SQL database, and the Provisioning Wizard then provisions the objects into Active Directory with the type designations intact. When the Data Migration Wizard later mailbox-enables those objects, the mailboxes are created with the correct resource type.

In a typical scenario, AD security objects have already been created for all users and resources, and a dirsync creates mail-enabled AD contacts that correspond to existing security objects. The Provisioning Wizard then merges the contact information (including resource types) into the existing security objects, and deletes the contacts, leaving a single mail-enabled security object in AD per user or resource. After that merge process has created mail-enabled security objects, the Data Migration Wizard can mailbox-enable the objects.

Note: If a resource appears in a collection, but no corresponding security object or contact yet resides in AD, the Provisioning Wizard can be configured to overlook the missing entities. This feature is enabled or disabled by a checkbox on the wizard’s Choose the Container for User Objects screen:

Mark the checkbox if you want the wizard to create a new mail-enabled object in AD when none is found by the wizard to correspond with a user (resource) in the collection. Leave the checkbox unmarked to disable that feature. Any such new objects will be created in the container specified by the User Container text box (on the wizard’s Choose the Container for User Objects screen).

NOTE: Use this Create new objects... feature only if no corresponding contact or user object already exists in AD. If an AD user object exists without a corresponding contact, the wizard will simply mail-enable the existing object.