지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Scheduling and limiting concurrent runs

To schedule user SSDM runs and set limits on concurrent runs
1
From your Windows Start menu: Select All Programs | Quest | Migrator for Notes to Exchange | SSDM Scheduling Administration.
The SSDM Scheduling Administration Utility appears, with four tabs: Collection Settings, Global Settings, Custom Notifications, and Monitor. The utility opens to the Collection Settings panel.
2
On the File menu, select the Configuration option to open the Configuration dialog box.
3
In the Configuration dialog box, set or change the following value:
•
Web Service Location: The URL of the web service.
Click Save to register the value, clear the dialog and return to the Collection Settings panel.
4
Click the Global Settings tab to show the Global Settings panel. The settings in this panel apply to all SSDM migration runs, regardless of user collection.
5
In the Global Settings panel:
a
Select or clear the following check boxes as appropriate:
•
Enable SSDM Scheduling: Determines whether the SSDM Scheduling features, as defined on the Collection Settings panel, will be used at all. If this check box is cleared, the SSDM will run with no scheduling restrictions and no limits on number of concurrent users.
•
Schedule Reminder: In the event a user tries to use the SSDM prior to his/her scheduled migration window, this check box determines whether the SSDM will schedule a task to restart for the user when it is permitted to run.
 
* 
IMPORTANT: Since a non-privileged user cannot create a reminder task (by Windows policy) and would not be alerted if the task could not be scheduled, an administrator should not allow this scheduled-reminder option for users that lack that privilege.
•
Email Migration Team: Determines whether the SSDM will be enabled to notify the migration administrator in the event the program cannot run due to scheduling restrictions. The Auto Send Email field determines whether the notification is generated, or if an option posed to the SSDM user. If Email Migration Team is cleared, the program does not automatically send an email or offer the option to users.
 
* 
IMPORTANT: If this feature is disabled, the Report This Issue button will not appear to the user, so the message defined in the Custom Notifications panel should not mention the button.
•
Auto Send Email (valid only if Email Migration Team is selected): Determines whether the SSDM notifies the migration administrator in the event the program cannot run due to scheduling restrictions. If this box is selected and the SSDM is unable to run, the program generates notification emails to the migration administrator defined in the Migration Team Email Information fields. If this box is cleared and the SSDM is unable to run, the error screen presented to the user includes a button that lets the user choose whether to send a notification to the migration team.
b
Set values for the update and timeout fields:
•
Update progress after ____ minutes: Defines the interval at which the program will update the system’s migration statistics while the SSDM is running.
•
Session timeout after ____ minutes: The number of minutes of program inactivity after which the SSDM would timeout.
c
Specify your choices for the User Connection Settings, to (optionally) limit SSDM connection-retry attempts. Choose either:
•
Allow unlimited retry attempts within date/time window.
— OR —
•
Limit retry attempts within date/time window.
If you choose to Limit retry attempts, you must also specify values for the number of SSDM retry migration attempts, and the interval (in number of minutes) between retries (SSDM retry migration request after).
d
Set values for the Migration Team Email Information. These fields define the recipients and contents of the notification email the program can send if a user cannot run the SSDM due to scheduling restrictions or concurrency limits:
•
Email Addresses: Defines the recipients of the notification email. To add an address to the list, type an email address in the text box and click the Add button. To remove an address from the list, select the address and click Delete Selected.
•
Subject: The Subject line of the notification email.
•
Message: The body of the notification email.
e
When all the Global Settings field values are set as you want them, click Save to save the settings.
6
Click Custom Notifications to show that panel, and make any changes you care to make to the messages that will be presented to users in these different circumstances:
•
Not Scheduled Notification: The message that will be presented to the user if his/her User ID is not a part of any user collection that is scheduled for migration.
•
Before Migration Window Notification: The message that is presented if you try to run the SSDM before the earliest date and time set for your collection’s migration window.
 
* 
IMPORTANT: The default text entries for the “Before” and “After” conditions noted here and below make no mention of the Schedule Reminder button—an option that may or may not be offered depending on your setting for Schedule Reminder in the Global Settings panel (step 5a). If the Schedule Reminder option is enabled, you should add brief explanations of the button to the messages here.
•
After Migration Window Notification: The message that is shown if the user tries to run the SSDM after the latest date and time set for his/her collection’s migration window.
•
Before Migration Time Window Notification: The message that is shown if the user tries to run the SSDM within the migration window date range, but before the permitted time-of-day range. Also see the IMPORTANT note above.
•
After Migration Time Window Notification: The message that is shown if the user tries to run the SSDM within the migration window date range, but after the permitted time-of-day range. Also see the IMPORTANT note above.
•
Too Many Connections Notification: The message that is shown if the number of other users running the SSDM at the same time has reached the concurrency limit set for the collection.
When all the Custom Notifications field values are set as you want them, click Save to save the settings.
7
Click the Collection Settings tab to show that panel, and:
a
Select a collection from the list of Collections on the left. The fields in the right half of the screen will set the schedule “window” and concurrent usage limit for all users in the selected collection.
 
* 
NOTE: To define a new collection while in this Collection Settings panel, click the Add/Edit Collection button (below the Collections list, on the left) to launch the Collection Wizard.
b
Set the Migration Time Window values for the selected collection in the right half of the panel: the From (beginning) and To (ending) dates and times.
c
Optional: If you want to allow SSDM runs only within a certain time period (per day), recurring daily throughout the From—To period defined in the preceding step:
•
Select the check box for Only allow migrations between, and enter the beginning and ending times of the daily range in the accompanying "________ and ________" time fields.
d
Set the Number of concurrent users allowed value for this collection in the right half of the screen. Any integer greater than zero will limit concurrent runs of the SSDM to the specified value. A zero (0) sets the limit to “unlimited” (any number of concurrent users will be allowed).
e
When the values in the right half of the screen define the migration window and concurrency limit you want for the selected collection, click the Save button.
f
Repeat steps 7a through 7e as often as you like to define the migration windows and concurrency limits for other collections. Remember to click the Save button after setting values for each collection, or the settings will be lost when you select a different collection or Exit the SSDM Scheduling Administration Utility.
8
When all three tabs’ field values are set as you want them, click Exit to close the SSDM Scheduling Administration Utility.
9
Add the following parameters to the notesdtapp.ini file:
[SSDMThrottle]
UseThrottle=1
WebServiceUrl=<UrlToWebsite>
For example:
http://xyzcorp.com/ssdmschedulingwebservice/SSDMSchedulingWebService.asmx

Monitoring SSDM usage status

The SSDM Scheduling Administration Utility includes a Monitor panel that lets you monitor the current status of SSDM usage, by numbers of users:

•
Processing: Number of users currently running the SSDM.
•
Waiting: Number of users waiting for an opening to start running the SSDM.
•
Timed Out Waiting: Number of users whose SSDM was waiting for so long that it timed out.
•
Cancelled Waiting: Number of users who were waiting for an opening to start processing, but clicked Cancel on the SSDM to stop waiting.

To monitor SSDM usage status: Click the Monitor tab in the SSDM Scheduling Administration Utility. To leave the Monitor panel: Click a different tab in the Utility, or click Exit to close the SSDM Scheduling Administration Utility altogether.

Office 365 Admin Account Pool utility

•
About the Admin Account Pool utility
•
Necessary preparations for the Admin Account Pooling utility
•
Managing the Admin Account Pool

About the Admin Account Pool utility

Microsoft currently imposes various throttles in Office 365 to ensure service availability and performance for all tenants. Some of these throttles take effect when any account (including a migration administrator account) initiates more than two concurrent connections. Each migration thread counts as a connection, so throttling can have a dramatic impact on migration performance to Office 365.

Migration solutions commonly achieve optimal throughput with eight to 12 threads for migration to local targets, and potentially more threads for higher-end hardware. To achieve similar results to Office 365, separate migration administrator accounts must be used to bypass the throttling limitations.

 
* 
NOTE: When running Migrator for Notes to Exchange in a federated Office 365 environment, the Account Pool Utility cannot use a federated domain.

Since Microsoft’s throttling is applied per administrator account, Migrator for Notes to Exchange runs multiple administrator accounts simultaneously on separate machines, each set to migrate with only one thread at a time. The net throughput becomes a function of the sum of all these multiple accounts’ processing threads—one per administrator account.

Migrator for Notes to Exchange includes an Admin Account Pool utility that helps you manage a pool of Office 365 administrator accounts for this purpose. The utility is designed to help you coordinate and "choreograph" these administrator accounts.

 
* 
NOTE: To maximize the performance of concurrent migration threads, ensure the size of the pool is greater than or equal to the total number of threads across all migration servers.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택