Chatee ahora con Soporte
Chat con el soporte

Migrator for Notes to Exchange 4.16.1 - 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 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, select Settings, click Control Panel and double-click Administrative Tools.
2
Double-click Services.
3
Right-click the appropriate service and click Properties.
4
On the Log On tab, change the password and click Apply.
5
On the General tab, click Start to restart the service.
6
Quit the Services tool.

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, select Settings, click Control Panel, and then double-click Administrative Tools.
2
Double-click Services.
3
Right-click the appropriate service, and then click Properties.
4
On the Log On tab, click Local System Account, and then click Apply.
 
* 
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 check box clear.
5
On the General tab, click Start to restart the service.
6
Exit the Services tool.

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 can display this error message:

The RPC Server is unavailable

This message can occur due to a logon failure with the Remote Procedure Call (RPC) service or some other dependent 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:

1
Start Registry Editor (Regedit.exe).
 
* 
CAUTION: These steps tell you to modify the registry. Serious problems might occur if you modify the registry incorrectly. Ensure that you follow these steps carefully. Quest strongly recommends that you back up the registry before you modify it so you can restore the registry if a problem occurs.
2
Locate the ObjectName value in this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceName
3
On the Edit menu, click Modify.
4
In the Value Data box, type localsystem and click OK.
5
Exit the Registry Editor.
6
Attempt to restart the service. You may need to restart the computer for some services to restart properly.

If you cannot start Registry Editor, you can modify the service account information by performing a parallel installation. See the Microsoft 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 you can use this feature to send personalized emails to users before or after they are migrated. For example, you can use 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 you can run the Data Migration Wizard to only send the messages—but not mailbox-enable users or perform any other migration or administrative functions.

To send a notification email to end users without migrating data:
1
Perform the Pre-Migration Preparations described in chapter 2 or 3 of the Migrator for Notes to Exchange Scenarios Guide.
2
Prepare a suitable mail-merge template file, as described in this Appendix. See How do I create or edit a template for personalized user-notification emails?
3
On the Select Notes Administrative Operations screen, select the Send migration notification messages check box. This option allows you to send mail merge messages when a data migration is not in progress.
The Configure mail-merge messages to migrating users screen is displayed.
4
On the Configure mail-merge messages to migrating users screen, define the personalized (mail-merge) notification emails you want the wizard to send to the users in this collection and click Next.

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 useful:

•
if problematic bandwidth makes direct connection impractical (e.g., if the source and target servers are far apart—geographically and/or from a network perspective).
•
if the Domino environment is managed by a third party that does not allow admin access.
•
in a disaster scenario, where the Domino server is destroyed but backup NSF files survive.

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

•
Notes source data is saved to replica or otherwise-disconnected NSFs and the MNE Data Migration Wizard migrates from the NSF files directly to Exchange.
•
The MNE Data Migration Wizard migrates Notes source data to PST files (rather than directly to an online Exchange target), and the PST files are imported into the Exchange target by some other application. The Quest Migration Manager for PSTs would be a good choice.

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.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación