Migrator for Notes to Exchange 4.15.2 - Administration Guide

•

Statistics last gathered: Reports the date and time that per-desktop statistics were last gathered.

•

Self-Service Desktop Migration statistics directory (UNC Path): The full path for the directory that contains the central log file for the Self-Service Desktop Migrator, or use the Browse button to locate and specify the path. This is the same as the Directory for central log and status files that you entered in the Log Directory Configuration screen.

•

Gather statistics: Launches the Self-Service Desktop Migration Statistics Collection Wizard, as described above.

•

Next scheduled run for collection: Displays the next scheduled run (if any) of this task, as configured by a previous run of the wizard or as amended on the Manage Scheduled Operations screen.

•

Operation type: Use this drop-down list box to specify a task that you want to add to the Tasks table below. Tasks in the Tasks table can be scheduled, edited, or run immediately, as explained below.

•

Collections labeled as: A drop-down list box that lets you filter the contents of the Collection name list box (below), to show only collections associated with the particular label specified here. Labels are a device for classifying and sorting collections (see the note under User Collections: Manage Users).

•

Collection name: Use this drop-down list box to specify the collection to which you want to apply the designated task.

•

Reschedule: Specify (or re-specify) the date(s) and time(s) that you want the selected task to run. The task will run for all objects in the collection, even if some objects in the collection were processed in an earlier run of the task.

•

Run now: Run the selected task immediately. The task will run for all objects in the collection, even if some objects in the collection were processed in an earlier run of the task.

•

User and resource details: An invaluable information resource for migration planning, this summary lists all resources and user mailboxes eligible for migration, and also reports the number of items and size of the data store in Notes, and identifying information such as department, location and server. You can use this information to define collections of resources and mailboxes to be migrated together. Typically, collections contain users in the same department and location. The use of the data store size estimates permits you to create collections of appropriate sizes so they can be completed in your intended timeframe.

•

Distribution list details: This summary lets you see the groups (distribution lists) defined in the Notes environment, which Migrator for Notes to Exchange can migrate to Exchange. Information in this summary such as owner, group type, Notes and Internet Address can help you collect similar groups together and have Migrator for Notes to Exchange provision them in the same Organizational Unit within Active Directory. Many admins prefer this approach to placing an extremely large number of groups all into the same OU container.

•

Internet domains: Sometimes, usually in large Notes installations, an additional Internet domain has been configured on some servers. In cases such as mergers or acquisitions, the Notes infrastructure may support some domains that are unknown to the staff performing the migration. This summary documents what domains are currently configured on the Notes servers, and identifies whether each domain is considered primary or secondary by Notes, so you can properly configure Internet domains for the Exchange system.

•

Notes domains: Large Notes installations sometimes contain multiple Notes domains, some of which may be unknown to migration admins—for example, in the case of a merger or acquisition. Admins at such sites should carefully review this summary to make sure it includes all Notes domains. The Data Migration Wizard will be able to migrate only the servers and domains listed in this summary. For any additional domains not listed, use the NAB Discovery Wizard to add an appropriate Name and Address Book to the Migrator for Notes to Exchange configuration.

•

Datastore design classes: Lotus Notes permits the use of different design classes to support different types of data. Some examples include STDR6Mail for mail, and STDR6PersonalAddressBook for personal address books. Notes also supports the creation of custom design classes, either by creating a new one or making modifications to an existing design class. When migrating data, Migrator for Notes to Exchange uses these design classes to determine the types of data and how they should be mapped to Exchange. All default design classes are automatically mapped. This report shows you all the different design classes in use in the data scanned by Migrator for Notes to Exchange. For each class, the summary indicates if it is already mapped or not, and identifies a specific example of a data store using each design class. If your enterprise has customized data classes, you should look at the unmapped data classes to determine if they contain standard data, such as messages and calendar data, and if they should be mapped for migration. If expected design classes are missing from this summary, you can add them to the database in the User Collection: Manage Design Classes screen of Notes Migration Manager.

•

User migration status per collection: This summary reports, for each user or resource in the collection, the amount of data migrated and how many errors were encountered. Use this summary to identify mailboxes and resoures that require cleanup, re-migration, or other additional attention. You can also use the data to calculate throughput and estimate the throughput of subsequent migrations. Adjusting the size of different collections based upon these numbers lets you optimize migration resources.

•

Distribution list provisioning: This summary shows which distribution lists have and have not been provisioned, and also documents any changes to previously migrated lists, so you can use Notes as the authoritative source for a list and periodically re-migrate the list.

•

Datastore status: This summary reports the migration status of specific user mailboxes or resource reservation databases. You can report on NSF files specific to a server, or select specific user mailboxes or resource reservation databases and determine if and when they were migrated, error counts, and how much data was migrated. Checkboxes let you filter results for runs with errors, and group migration runs by user and datastore.

•

Export to TSV: Export the displayed data to a TSV-format (tab-separated-values) data file.

•

Refresh Data: Regenerate the display, to include any new data from tasks currently running or recently concluded.

•

OK: Close the pop-up window.

•

Operation type: Use this drop-down list box to specify a task whose runs you want to add to the Task runs table below. You can further filter the displayed list by collection, as noted below.

•

Collections labeled as: A drop-down list box that lets you filter the contents of the Collection name list box (below), to show only collections associated with the particular label specified here. Labels are a device for classifying and sorting collections. For more information, see the note under User Collections: Manage Users.

•

Collection name: Use this drop-down list box to specify the collection to which the task was applied.

•

View log file: Launches the Log Viewer for the selected task run.