サポートと今すぐチャット
サポートとのチャット

Migrator for Notes to Exchange 4.15.2 - 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 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

Configuration for migration to Office 365 without Migrator for Notes to Exchange's Admin Account Pool features

Configuration for migration to Office 365 without Migrator for Notes to Exchange’s Admin Account Pool features

When migrating to Office 365 (with or without MSOL AD synchronization), but without using Migrator for Notes to Exchange's Admin Account Pool features, the Migrator for Notes to Exchange Task Scheduler service requires access to an Office 365 admin mailbox via a MAPI profile with cached credentials. However, the Migrator for Notes to Exchange Task Scheduler service cannot interact with foreground processes, such as a credentials prompt, so it requires a mechanism to provide the credentials and dismiss the prompt.

Create a local Windows user account, or a domain user (see Note below) with rights to access migration resources and login as Windows services. Create a new mail profile for this user and configure the profile with cached credentials to the Office 365 admin mailbox. Then login to the Office 365 admin mailbox at least one time and save the credentials.

Configure the Migrator for Notes to Exchange Scheduler service to run as the Windows user. The service will use the cached Office 365 admin credentials stored with the Windows account, which will remain secure behind the identity of the Windows user.

 
* 
NOTE: If Migrator for Notes to Exchange's SQL server is configured to use SQL server authentication, the Migrator for Notes to Exchange Task Scheduler will automatically discover the SQL server and credentials using Migrator for Notes to Exchange configuration. But if the SQL server uses Windows authentication, the user that will run the Migrator for Notes to Exchange Task Scheduler must be granted access to the migration database. If the SQL server uses Windows authentication only and is not hosted on the migration server, you may have to make the shadow user a domain user so he/she can be granted permission to connect to the SQL server.
To create a user to run the Migrator for Notes to Exchange Task Scheduler:
1
On the migration server, create a new user:
a
Start lusrmgr.msc or go to Control Panel | Administrative Tools | Computer Management, and select the Local Users and Groups snap-in.
b
Create a new local user, for example O365admin.
Recommended: Make the password permanent or valid for the duration of the migration project. For more information, see the Microsoft TechNet article: Create a Local User Account.
2
Make O365admin a member of the local Administrators group (required for Notes server file share access and remote login).
For more information, see the Microsoft TechNet article: Add a Member to a Local Group.
3
Grant O365admin permission to run as service on migration server.
For more information, see the Microsoft TechNet article: Add the Log On as a Service Right to an Account.
To configure the Office 365 admin mail profile:
1
Log into the migration server as O365admin.
2
Open Control Panel | Mail (32bit).
3
Remove any existing mail profiles.
4
Create a new profile.
5
Add Office 365 administrator email account to the new profile.
6
Configure the email account. While configuring the account:
a
Click More Settings….
b
On the Security tab: Verify the checkbox Always prompt for logon credentials is unchecked.
c
Check the radio button Prompt for profile to be used.
7
Use Outlook or MFCMAPI to login to the O365 admin mailbox.
8
Very Important: When prompted to enter credentials, check the Remember password checkbox.
9
Log out from the O365admin session.
To configure the Migrator for Notes to Exchange Task Scheduler service:

Log into the migration server as Administrator to configure the Migrator for Notes to Exchange Task Scheduler service to run as O365admin. In addition, the service must be configured to start in the "Autostart (Delayed Start)" mode.

1
Start services.msc or go to Control Panel | All Control Panel Items | Administrative Tools | Services.
2
Find the Migrator for Notes to Exchange Task Scheduler service, right-click on it, and select Properties. The name of the Migrator for Notes to Exchange Task Scheduler service is “Quest Migrator for Notes to Exchange Task Scheduler”.
3
In the Startup Type field, select "Autostart (Delayed Start)".
4
On the Log On tab, select This Account and enter credentials for the O365admin Windows user.
5
Click OK.
6
Restart the service.

Configuration for migration to Office 365 using Migrator for Notes to Exchange's Admin Account Pool features

Configuration for migration to Office 365 using Migrator for Notes to Exchange’s Admin Account Pool features

Migrator for Notes to Exchange's qsched.exe task-scheduling utility is compatible with Migrator for Notes to Exchange's Admin Account Pool for migrations to Office 365, but only with an additional step added to the process. For other migration scenarios (to an on-premises Exchange, or to Office 365 without the Admin Account Pool) the qsched.exe utility regularly checks Migrator for Notes to Exchange's SQL database to see whether any tasks have been scheduled to run since the last check, and then executes any such tasks it finds. But Office 365 access restrictions require an intermediate scheduling mechanism to accommodate the Admin Account Pool.

When migrating to Office 365 with Migrator for Notes to Exchange's Admin Account Pool, use Windows' Task Scheduler to run Migrator for Notes to Exchange's qsched.exe for each Migrator for Notes to Exchange task you want to run:

1
Add a Windows scheduled task to run Migrator for Notes to Exchange's qsched.exe (in the Migrator for Notes to Exchange installation directory) at the task's scheduled execution time, and to "Run only when user is logged on."
2
At the time the task is scheduled to run:
•
Make sure the Migrator for Notes to Exchange task scheduler service is disabled.
•
Make sure the task's associated user is logged on (per step 1 above).

Log files

The Migrator for Notes to Exchange Task Scheduler logs to a file named SchedulerService.wlog in the Migrator for Notes to Exchange installation directory.

The location of the SchedulerService.wlog can be changed by completing the following steps:

1
Stop the Migrator for Notes to Exchange Task Scheduler service.
2
Open the SchedulerService.exe.config file in the Migrator for Notes to Exchange installation directory.
3
Find the following line: <file value=".\SchedulerService.wlog" />
4
Replace the value in double quotes with a full path to the desired location.
5
Save the file.
6
Start the Scheduler Service.

SSDM Scheduling Administration utility

•
About SSDM Scheduling Administration
•
Before you can use the SSDM Scheduling Administration utility
•
Scheduling SSDM runs and limiting concurrent runs
•
Monitoring SSDM usage status
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択