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: |
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. |
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:
extensionAttribute1 |
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):
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:
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?).
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. |
2 |
3 |
4 |
5 |
Click Attributes, and wait for the list to expand. |
7 |
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: |
• |
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 just one user. If a file system path is specified here, ownership is checked based on the profile documents and/or ACLs. Examples: |
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: |
• |
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 just one user. If a file system path is specified here, ownership is checked based on the profile documents and/or ACLs. Examples: |
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: |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center