Chat now with support
Chat with Support

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

How do I migrate from a Notes environment with Symantec E-Vault?

When migrating from a Notes environment with Symantec E-Vault, Exchange propagation issues may interfere with Migrator for Notes to Exchange setting custom attributes when the destination mailbox has never been accessed either by Outlook or by the migration application. One simple work-around would be to first run a "dummy" migration (e.g., use a date filter where date > 1/1/2100) to open all the target mailboxes before running the real migration.

How do I migrate to an Exchange environment with a CAS Array?

The following instructions do not apply to Exchange 2013. Please see this Knowledge Base article for instructions for Exchange 2013.

To configure Migrator for Notes to Exchange for an Exchange target environment configured with a CAS (Client Access Server) array:

How do I prepare the SQL database for mailbox-enabling (if AD is configured for a resource forest and a user forest)?

This section applies only if your AD/Exchange environment is configured for a resource forest and a user forest, with corresponding user accounts. In that case, you must configure the Global Default Settings in Notes Migration Manager, and then prepare (or verify) the values in a column of the exported directory data, for the Data Migration Wizard to properly associate the resource accounts with the user accounts and properly enable mailboxes.

Before you begin, you must determine which column in the SQL database will correspond to which AD attribute, for the wizard to match corresponding user accounts in the resource forest and user forest. The column (AdSearchCol) and attribute (AdAttribute) are both specified in the [ActiveDirectory2] section of the Global Default Settings of Notes Migration Manager:

AdSearchCol: The column in the SQL database whose values the program should search for each particular AdAttribute value, to match corresponding user accounts in the resource forest and user forest. Note that the column specified here and its per-user values must exist before the Data Migration Wizard is run.
IMPORTANT: In the current Migrator for Notes to Exchange version, this AdSearchCol parameter value must be set to SearchKey2 (the default for this parameter) for the mailbox-enabling process to succeed.
AdAttribute: The AD attribute whose values the program should read in the AdSearchCol column of the SQL database, to match corresponding user accounts in the resource and user forests. For example:
... tells the wizard to match AD objects with users such that the value of each AD object’s userPrincipalName attribute matches the value of the corresponding user’s SearchKey2 column in the SQL database.
1
Within Notes Migration Manager, select File | Global Default Settings. The program then opens the program’s configuration settings into Windows Notepad. Within Notepad, the settings look like the contents of an INI file, but they are actually saved as a part of the SQL database rather than as an independent INI file.
1
Within Notes Migration Manager, in the Export Notes Directory screen: Click Export objects to TSV. A dialog box will prompt you for a destination folder and filename for the exported file.
3
In the Export Notes Directory screen: 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.

How do I add to the list of AD attributes available for the merge function?

The Provisioning Wizard associates contacts with AD objects by comparing the unique values of a particular AD object attribute to the unique values of a corresponding column in the SQL database. Where these values match, the associated contact and AD object are assumed to represent the same entity, and the two are therefore merged. During the wizard's run, the Choose Your Method... screen requires that you specify the AD attribute and the database column to use for these comparisons. The designations on that screen are accomplished by drop-down list boxes that list available options for the database column and AD attribute, respectively.

By default, the list of choices for the AD attribute contains these 26 options:

 

cn
mail
mailNickname
proxyAddresses

sAMAcountName
userPrincipalName
targetAddress
employeeNumber

distinguishedName
altRecipient
legacyExchangeDN

extensionAttribute1
extensionAttribute2
extensionAttribute3
... [to 15]

The 26 defaults are defined by a series of ADML[#] parameters in the [ActiveDirectoryMatchList] section of the Global Defaults and Task Parameters:

If the AD attribute you want to use is not among the 26 defaults, you can add one or more other attributes to the list by defining each addition in the Global Defaults or Task Parameters. See How do I add or edit program parameters? above for the procedure to add and edit these parameter(s):

Each ADML[#] parameter names an AD attribute that the Provisioning Wizard will include in its list of options, from which one attribute must be chosen to facilitate the matching of contacts with AD objects. The digit(s) appended to an ADML[#] key name differentiate one parameter from another. The multiple ADML[#] parameters need not appear in numerical order, and need not form an uninterrupted numerical sequence. But the wizard will read only ADML[#] parameters whose differentiating digits are less than a value specified by a Count parameter (see below).
A limit to the number of ADML[#] parameters (see above) that the Provisioning Wizard will process in this section. The wizard will read only ADML[#] parameters whose differentiating digits are less than the Count parameter value. For example, if:
If unspecified, the Count parameter defaults to 26. If specified, the parameter must occur as the first line of the section, as shown above.

For example: If the ADML[#] parameters are set for only their 26 defaults, and you want to add a single new AD attribute option, you would add an ADML26 parameter and change the Count parameter to 27, like this:

Related Documents