Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.16 - Administration Guide

About the Migrator for Notes to Exchange documentation Notes Migration Manager NABS Discovery Wizard Internet Domains Discovery Wizard Directory Export Wizard Collection Wizard Groups Provisioning Wizard Notes Data Locator Wizard Provisioning Wizard Send PAB Replicator Wizard Data Migration Wizard SSDM Statistics Collection Wizard The Log Viewer Using the Qsched.exe task-scheduling utility SSDM Scheduling Administration utility Office 365 Admin Account Pool utility PowerShell cmdlets for Migrator for Notes to Exchange Appendix A: How do I ...?
Post-installation configuration Pre-migration preparations Batch-migration process Other features

How to configure user rights

If the right to log on as a service is revoked for the specified user account, restore the right by performing the following steps:

If the user is in an Active Directory domain:

4
On the Group Policy tab, click Default Domain Controllers Policy, and then click Edit. This starts Group Policy Manager.
6
Expand Local Policies, and then click User Rights Assignment.
7
In the right pane, right-click Log on as a service, and then click Security.

If the user is a member of a stand-alone member server:

2
Expand Local Policies, and then click User Rights Assignment.
3
In the right pane, right-click Log on as a service, and then click Security.

How to configure service logon information

To configure the password for the specified user account to match the current password for that user, use the following steps:

1
Click Start, point to Settings, click Control Panel, and then double-click Administrative Tools.
2
Double-click Services.
4
On the Log On tab, change the password, and then click Apply.
5
On the General tab, click Start to restart the service.

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:

1
Click Start, point to Settings, click Control Panel, and then double-click Administrative Tools.
2
Double-click Services.
4
On the Log On tab, click Local System Account, and then click Apply.
5
On the General tab, click Start to restart the service.

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.
3
On the Edit menu, click Modify.
4
In the Value Data box, type localsystem, and then click OK.

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.

1
Perform all of the Pre-Migration Preparations described in chapter 2 or 3 of the Migrator for Notes to Exchange Scenarios Guide.
3
On the Select Notes Administrative Operations screen, select the Send migration notfication messages checkbox.
4
On the Configure mail-merge messages to migrating users screen, Define the personalized (mail-merge) notification emails (if any) you want the wizard to send to the users in this collection, and click Next.
Related Documents