Migrator for Notes to Exchange 4.17

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 merged. During the wizard run, the Choose Your Method... screen requires that you specify the AD attribute and the database column to use for the comparisons. You specify the attributes and columns using drop-down lists of 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:

[ActiveDirectoryMatchList]
Count=26
ADML0=cn
ADML1=mail
ADML2=mailNickname
ADML3=proxyAddresses
ADML4=sAMAccountName
[...]
ADML25=extensionAttribute15

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):

•

ADML[#]=<AttribName>

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 unirupted 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).


	NOTE: Migrator for Notes to Exchange’s Provisioning Wizard merge function requires that any AD attribute added to the list be replicated to the Global Catalog. You can configure AD to replicate an attribute to the Global Catalog; see How do I configure AD to replicate an AD attribute to the Global Catalog?

•

Count=<##>

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:

[ActiveDirectoryMatchList]
Count=6
ADML0=cn
ADML1=mail
ADML2=mailNickname
ADML3=proxyAddresses
ADML4=sAMAccountName
ADML5=userPrincipalName
ADML6=targetAddress
ADML7=employeeNumber

... then the wizard will read all the parameters except ADML6 and ADML7, since Count=6, and neither 6 nor 7 is less than 6.

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:

[ActiveDirectoryMatchList]
Count=27
ADML0=cn
ADML1=mail
ADML2=mailNickname
ADML3=proxyAddresses
ADML4=sAMAccountName
[...]
ADML25=extensionAttribute15
ADML26=NewAttributeName

How do I configure AD to replicate an AD attribute to the Global Catalog?

If the AD attribute you want to use for the Provisioning Wizard 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. This procedure is explained elsewhere in this Appendix (see How do I add to the list of AD attributes available for the merge function?).

Any AD attribute added to the list must be replicated to the Global Catalog, or the merge function will fail. You can configure AD to replicate an AD attribute to the Global Catalog as explained in the following procedure:


	CAUTION: This procedure manipulates AD configuration parameters, and an error could generate adverse consequences throughout the Active Directory environment. Use extreme caution whenever manipulating AD configuration parameters in this way.

To configure AD to replicate an AD attribute to the Global Catalog:

At a computer where you can manage your Active Directory, open a command prompt and e:

regsvr32 schmmgmt.dll

Launch the Microsoft Management Console (mmc.exe).

On the File menu, select Add/Remove Snap-in.

Click Add, select Active Directory Schema, click Add, and then return to the main window.

Click Attributes, and wait for the list to expand.

Find the name of the attribute you want to replicate, then right-click it and select Properties.

Select Replicate the attribute to the Global Catalog, and click OK.

Wait for the Global Catalog to replicate the attribute.

How do I specify per-user locations for Notes source data?

Per-user locations for users’ source data are (if necessary) specified in the SQL database. To edit the contents of that database, you must export the data to a .tsv (tab-separated-values format) file, then edit the contents of the table, and then import the edited .tsv file back into the SQL database.


	NOTE: After importing values into any of the listed columns, you must run the Notes Data Locator Wizard so the data stores that are specified by the values you provide are located and the user's datastore information is updated. To run the Notes Data Locator Wizard, select the Locate Notes Data Stores page in Notes Migration Manager.

For PABs: To designate the locations of user PABs, enter the appropriate per-user values into one of these columns (not both):

•

PABPaths column: The specific UNC path and filename for a user's Notes address book(s). Multiple address books can be designated by separating them with a pipe ( | ) character. Ordinarily the full path and file name are given, and file ownership is not checked. If a directory (only) is specified, all PABs found in the directory are assumed to be owned by the user. Examples:

\\server\data\addr1.nsf | \\server\data\addr2.nsf
\\server\data\user\address_book.nsf
\\server\data\

•

SharedPabDirs column: A file system directory or Notes server directory that contains NSF files for multiple users. This column can be used to specify a more specific set of directories to scan for a user's data, so the application can scan a subset of a larger shared directory structure and determine the owner based on profile documents and/or ACLs. This is useful if a group of users to be migrated shares a directory structure and you can't be certain that all address books belong to one user. If a file system path is specified here, ownership is checked based on the profile documents and/or ACLs. Examples:

\\server\data\groupdir
\\server\data\groupdir\address_book.nsf

For Archives: To designate the locations of user archives, enter the appropriate per-user values into one of these columns (not both):

•

ArchivePaths column: The specific UNC path and filename for a user's Notes archive file(s). Multiple archives can be designated by separating them with a pipe ( | ) character. Ordinarily the full path and file name are given, and file ownership is not checked. If a directory (only) is specified, all archives found in the directory are assumed to be owned by the user. Examples:

\\server\data\arch1.nsf | \\server\data\arch2.nsf
\\server\data\user\archive_jdoe.nsf
\\server\data\

•

SharedArchiveDirs column: A file system directory or Notes server directory that contains NSF files for multiple users. This column can be used to specify a more specific set of directories to scan for a user's data, so the application can scan a subset of a larger shared directory structure and determine the owner based on profile documents and/or ACLs. This is useful if a group of users to be migrated shares a directory structure and you can't be certain that all address books belong to one user. If a file system path is specified here, ownership is checked based on the profile documents and/or ACLs. Examples:

\\server\data\archives
\\server\data\archives\archive_jdoe.nsf

For Mail Files: To specify per-user locations and filenames for users’ source mail files in the SQL database rather than from entries in the Data Migration Wizard, enter the appropriate per-user values into this column:

•

MailFilePath column: The specific path and NSF filename to a user's mail file, used when an administrator knows the specific path and NSF file name for each user. Example:

\\server\home\user\jdoe.nsf

If the MailFilePath column does not exist or is left empty, the program will look for the user's mail file in the path entered in the Notes Data Locator Wizard (on the Specify Notes Mail File Directories screen).

How do I specify per-user destination locations for users' PST files?

How do I specify per-user destination locations for users’ PST files?

Per-user destination locations for users’ new PST files are (if necessary) specified in the SQL database. To edit the contents of the SQL database, you must export the data to a .tsv (tab-separated-values format) file, then edit the contents of the table, and then import the edited .tsv file back into the SQL database.

To specify per-user destinations for users’ new PST files in the SQL database rather than from entries in the Data Migration Wizard, enter the appropriate per-user values into this column:

•

PSTdir column: The directory where PSTs are stored for the user, used if each user's PST will go to a separate directory. Normally the admin would specify a central location for the wizard to create all PSTs, and the wizard would create a subtree under that. If the admin would rather put each PST in each user's home directory, then each user's home directory can be added here. Example:

\\server\home\user

Seleziona il prodotto:

Per una maggiore efficacia, compilare l'Obiettivo della chat:

Soluzioni consigliate per il problema

Migrator for Notes to Exchange 4.17 - Administration Guide

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

How do I configure AD to replicate an AD attribute to the Global Catalog?

How do I specify per-user locations for Notes source data?

How do I specify per-user destination locations for users' PST files?