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:
[ActiveDirectory2] AdSearchCol=SearchKey2 AdAttribute=userPrincipalName
... 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.
To configure the Global Default settings:
-
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 saved as a part of the SQL database rather than as an independent INI file.
-
In the [ActiveDirectory2] section, set the appropriate parameter value for AdAttribute, as described above.
-
Close Notepad. Notes Migration Manager will then copy the new parameter value back into the SQL database.
If you need to enter or edit the AdSearchCol column values in the SQL database:
-
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.
-
Use Microsoft Excel (or some other program that can edit a tsv-format file) to enter or edit the contents of the column you have designated as the AdSearchCol column.
-
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 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).
[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: ThisproceduremanipulatesADconfigurationparameters,andanerrorcouldgenerateadverse consequences throughout theActive 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).
