Migrator for Notes to Exchange 4.17 - Administration Guide

Operations screen when migrating to a local, proprietary Exchange, or a "hosted Exchange"

When migrating to on-premises Exchange or to “hosted Exchange” (other than Microsoft 365), the Operations screen lists the following options:

NOTE: By default, the wizard preserves ACL information as it migrates Notes source data to Exchange. To disable this feature, you can set ACLs=0 in the [General] section of Task Parameters or Global Defaults.

NOTE: If the Notes Data Locator Wizard finds a PAB or Archive twice (once by the server and again by the file system), the Data Migration Wizard tries to migrate it twice. But the file-system attempt will fail and generate an error because the prior successful server access locked the file, rendering it inaccessible. The Data Locator Wizard cannot be configured to search using both methods at once, but you can run the wizard more than once, selecting different search methods in subsequent runs.

Operations screen when migrating to Microsoft 365 with Microsoft AD synchronization

When migrating to Microsoft 365 and using the Microsoft AD synchronization tool, the Operations screen offers the following options:

IMPORTANT: The Prepare local AD accounts feature is a necessary administrative step that must precede running the MS AD synchronization, and must precede running this wizard for any other function. After running MS AD synchronization, you must run the Data Migration Wizard again and Set Microsoft 365 resource capacity (below) to complete mailbox-enabling in Microsoft 365.

NOTE: When you select Prepare local AD accounts, all other options are disabled (grayed out). When you select any other option, the Prepare Local AD accounts option is disabled.

NOTE: By default, the wizard preserves ACL information as it migrates Notes source data to Exchange. To disable this feature, you can set ACLs=0 in the [General] section of Task Parameters or Global Defaults.

NOTE: If the Notes Data Locator Wizard finds a PAB or Archive twice (once by the server and again by the file system), the Data Migration Wizard tries to migrate it twice. But the file-system attempt will fail and generate an error because the prior successful server access locked the file, leaving it inaccessible. The Data Locator Wizard cannot be configured to search using both methods at once, but you could run the wizard more than once, selecting different search methods in subsequent runs.

Operations screen when migrating to Microsoft 365 without Microsoft AD synchronization

When migrating to Microsoft 365 without Microsoft AD synchronization, the Operations screen offers the following options:

NOTE: By default, the wizard preserves ACL information as it migrates Notes source data to Exchange. To disable this feature, you can set ACLs=0 in the [General] section of Task Parameters or Global Defaults.

NOTE: If the Notes Data Locator Wizard finds a PAB or Archive twice (once by the server and again by the file system), the Data Migration Wizard will try to migrate it twice. But the file-system attempt will fail and generate an error because the prior successful server access locked the file, rendering it inaccessible. The Data Locator Wizard cannot be configured to search using both methods at once, but you could run the wizard more than once, selecting different search methods in subsequent runs.

Select Microsoft 365 Administrative Operations

This screen appears if you selected the Microsoft 365 administrative functions check box on the Operations screen. It lets you select the following options.

NOTE: The Data Migration Wizard can license Microsoft 365 users when the userPrincipalName differs from the primary SMTP address. With this feature, an administrator can use TSV Import feature to assign alternate UPN values to the SQL database. To do this, from the Export Notes Directory screen: 1 Export the collection SQL data to a tsv file. 2 Enter the users' UPN values into the UPN column of the tsv file. 3 Import the tsv file back into the SQL database. MNE will read the imported UPN values, if they are present in the database, when licensing Microsoft 365 users. Without this feature, the wizard uses the SMTP address for the userPrincipalName, but this can cause issues in environments where the userPrincipalName is different, since the Microsoft 365 Administrative Operations wizard would not find the users in the target Microsoft 365 environment.

NOTE: Unable to assign the license error. License plan services can have dependencies on other services. When licensing users, MNE does not validate that the combination of services selected is valid. If you disable a service on which another enabled service is dependent, user licensing will fail with the error Unable to assign the license.