Chatta subito con l'assistenza
Chat con il supporto

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

Post-installation configuration

After installing MNE, there are additional configuration steps required to use the Migrator for Notes to Exchange Task Scheduler utility. Open the Windows Service Manager and complete the following steps:

Log files

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

You can change the location of the SchedulerService.wlog by completing the following steps.

2
Open the SchedulerService.exe.config file in the Migrator for Notes to Exchange installation directory.

SSDM Scheduling Administration utility

About SSDM Scheduling Administration

The SSDM Scheduling Administration utility lets you control when users can run the SSDM (Self-Service Desktop Migrator) to more evenly distribute the demand on network and server resources. Each user collection is assigned a specific date and time period when its member users are permitted to migrate. When a user runs the SSDM, the program identifies the user by his or her login credentials and checks the schedule to see whether the user is early, late, or “in the window” for his or her migration.

The SSDM Scheduling Administration utility also lets you set per-collection limits on the number of concurrent migration runs to prevent processing bottlenecks that can occur if too many users run the SSDM at the same time. If a user’s SSDM run exceeds the limit, the user has the option of “parking” the run in a waiting queue so that his or her migration would run in the next available slot.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione