Migrator for Notes to Exchange 4.16.1

The Provisioning Wizard is applied to a particular user collection that you specify when you launch the wizard from Notes Migration Manager (see User Collections: Provision Users). The “match” attribute that the wizard uses to compare and match AD contacts and users must correspond to an attribute in the MNE SQL database from which the collections are drawn. For each user in the designated collection, the wizard reads the match attribute value, and looks in AD for the single contact and the single user whose corresponding attribute values both match the value from the user record in the SQL database. When it finds a match, it merges the contact information into the user object record, and deletes the contact, leaving a single mailbox- enabled object per user in Active Directory.

Before you run the Provisioning Wizard

Before running the Provisioning Wizard, you must:

•

Verify that the SQL database contains a column whose per- contact values are unique and that match the values for a corresponding AD object attribute. If the database does not contain a populated column for this purpose, you must enter appropriate values into the SearchKey column as described following. The Provisioning Wizard provides the following options in a drop-down list:

•

DisplayName: Copied by Directory Export Wizard from the first value of the Notes FullName attribute that is not a DN ("CN=Joe Schmoe/O=Acme") or SMTP address (Joe.Schmoe@acme.com) or, if every FullName is a DN or SMTP address, the “CN” portion of the first FullName that is a DN ("CN=xxx/...").

•

GivenName: Copied by Directory Export Wizard from the Notes FirstName.

•

Userid: Copied by Directory Export Wizard from the first value of the Notes ShortName that is not an SMTP address (same as Nickname column below).

•

Surname: Copied by Directory Export Wizard from the Notes LastName attribute.

•

PhoneticName: Copied by Directory Export Wizard from the Notes AltFullNameSort attribute.

•

Nickname: Copied by Directory Export Wizard from the first value of the Notes ShortName that is not an SMTP address (same as Userid column).

•

EmployeeID: Copied by Directory Export Wizard from the Notes EmployeeID.

•

SourceAddress: Derived by Directory Export Wizard from the first value of the Notes FullName attribute that is a DN ("CN=Joe Schmoe/O=OurCompany"), with “CN=” and “O=” stripped out (leaving “Joe Schmoe/OurCompany”).

•

TargetAddress: Copied by the Directory Export Wizard from the Notes internetAddress. If there is no internetAddress attribute defined in the Notes person document, the wizard generates a TargetAddress from ShortName@ the default domain (designated on the Find Domains screen).

•

SearchKey: Column not populated by Directory Export Wizard. May be manually populated with user-identifying values (unique per user) that the Provisioning Wizard can use to match objects for merging if none of the other column options is suitable for the merge process. The procedure to edit these values is explained in the following section.

•

SearchKey2: Column is not populated by Directory Export Wizard. Can be manually populated with user-identifying values (unique per user) that the Data Migration Wizard can use to properly associate resource accounts with corresponding user accounts, and properly enable mailboxes (used only when Active Directory is configured for a resource forest and a user forest, with corresponding user accounts). This process is explained in Appendix A, under How Do I Prepare the SQL database for Mailbox-Enabling (If AD Is Configured for a Resource Forest and a User Forest)?

•

SourceForwardingAddress: Column is not populated by Directory Export Wizard. Can be manually populated to contain addresses used by the Data Migration Wizard to forward mail from Notes to Exchange. If this column is empty and the Data Migration Wizard set for Notes-to-Exchange forwarding, the wizard will infer suitable values from the values in other database columns.

•

TargetForwardingAddress: Column is not populated by Directory Export Wizard. Can be manually populated to contain addresses used by the Data Migration Wizard to forward mail from Exchange to Notes. If this column is empty and the Data Migration Wizard set for Exchange-to-Notes forwarding, the wizard will infer suitable values from the values in other database columns.

To edit the SearchKey column of the data table

In the Manage Users (User Collections) screen of Notes Migration Manager, select the collection whose contacts you want to merge.

Click Export objects to TSV to export the data to a .tsv (tab-separated values format) file.

Enter the destination folder and file name in the dialog box.

Use Microsoft Excel (or some program that can edit a tsv-format file) to edit the contents of the table.

You can add, edit, and delete the contents of any existing cell in the table, but any addition or deletion of an entire row or column is ignored when you import the data back into the database.

Find a column in the exported data table that is suitable for the merge process—containing values that are unique per user, and that correspond to the values of the pertinent AD object attribute.

Copy the values of that column into the SearchKey column. If no column exactly corresponds to the pertinent AD attribute, you can find a column with values that can be massaged to match by appending or stripping some segment of the data string, or merging the values with the data in another column or from some other source.

In Notes Migration Manage, click Import objects from TSV to import the edited .tsv file into the SQL database. A dialog box will prompt you for the filename and its location.

Verify that the drop-down list in the Choose Your Method... screen offers the AD attribute you want for the merge function. By default, the drop-down list contains these options:


	cn mail mailNickname proxyAddresses sAMAcountName userPrincipalName targetAddress employeeNumber distinguishedName	altRecipient legacyExchangeDN extensionAttribute1 extensionAttribute2 extensionAttribute3 extensionAttribute4 extensionAttribute5 extensionAttribute6 extensionAttribute7	extensionAttribute8 extensionAttribute9 extensionAttribute10 extensionAttribute11 extensionAttribute12 extensionAttribute13 extensionAttribute14 extensionAttribute15