Chat now with support
Chat mit Support

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

Other features

The following sections describe additional features that may be used to perform tasks in Migrator for Notes to Exchange:

•
How do I schedule tasks?
•
How do I troubleshoot service startup permissions?
•
How do I send pre- or post-migration notification emails to end users?
•
How do I perform an offline migration?
•
How do I migrate resources?
•
How do I migrate mail-in databases?
•
How do I save and restore all Migrator for Notes to Exchange-defined collections from TSV files?

How do I schedule tasks?

Scheduled tasks are run using the Migrator for Notes to Exchange (MNE) Task Scheduler (qsched.exe). The Task Scheduler runs as a Windows service and is installed when you install Migrator for Notes to Exchange. The Task Scheduler is configured by default to autostart (upon every workstation reboot) and run under the credentials of the administrator account that runs the MNE installer.

The Task Scheduler polls the MNE database at regular intervals for any scheduled tasks and runs those tasks at the designated times.

See Admin Guide chapter 13 for information about the Task Scheduler (qsched.exe).

How do I troubleshoot service startup permissions?

If the MNE Task Scheduler experiences logon failures when trying to start the service, the following information will help you resolve them.

When a service does not start because of a logon failure, you might find error messages in the system event log when you restart the server:

Source: Service Control Manager
Event ID: 7000
Description:
The %service% service failed to start due to the following error:
The service did not start due to a logon failure.
No Data will be available.Source: Service Control Manager
Event ID: 7013
Description:
Logon attempt with current password failed with the following error:
Logon failure: unknown user name or bad password.
No Data will be available.

When you attempt to manually start the service, you might see the following error message, even though the user account is a valid user:

Microsoft Management Console
Could not start the %service% service on Local Computer
Error 1069: The service did not start due to a logon Failure.

This behavior can occur for any of these reasons:

•
The password has changed on the account that the service is configured to use to log on.
•
The password data in the registry is damaged.
•
The right to “log on as a service” is revoked for the specified user account.

To resolve these issues, you can configure the service to use the built-in system account, change the password for the specified user account to match the current password for that user, or restore the user's right to “log on as a service”.

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:

in the Domain controller domain

If the user is in an Active Directory domain:

1
Start the Active Directory Users and Computers Microsoft Management Console (MMC) snap-in.
2
Right-click the Organizational Unit (OU) in which the user right to log on as a service was granted. By default, this is in the Domain Controller OU.
3
Right-click the container and then click Properties.
4
On the Group Policy tab, click Default Domain Controllers Policy and click Edit.
This starts Group Policy Manager.
5
Expand the Computer Configuration object by clicking the plus sign (+) next to the policy object.
6
Under the Computer Configuration object, expand Windows Settings, and then expand Security Settings.
7
Expand Local Policies, and click User Rights Assignment.
8
In the right pane, right-click Log on as a service, and click Security.
9
Add the user to the policy, and click OK.
10
Quit Group Policy Manager, close Group Policy properties, and close the Active Directory Users and Computers MMC snap-in.
On a member server

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

1
Start the Local Security Settings MMC snap-in.
2
Expand Local Policies and click User Rights Assignment.
3
In the right pane, right-click Log on as a service and click Security.
4
Add the user to the policy and click OK.
5
Close the Local Security Settings MMC snap-in.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen