Schedule Summary
Schedule Summary
This screen appears only if you have selected One or more times... Once or Manually as your scheduling option on the preceding Specify Task Schedule screen. The screen shows a summary of the task schedule you specified in the Specify Task Schedule screen, or notes that the task will be run only Manually.
Review this information to confirm that it describes the schedule you want to define. If you want to change anything, click Back to return to the Specify Task Schedule screen, to change the schedule specification, or click Cancel to return to the Export Notes Directory screen in Notes Migration Manager. From the preceding screen within this wizard, you can click Next to return to this Schedule Summary screen.
When you are satisfied that the displayed summary describes the task schedule you want to create, click Finish to dismiss this screen:
-
Finish: Clears this Schedule Summary screen, to return to the Export Notes Directory screen in Notes Migration Manager.
The remaining screens documented for this Wizard are skipped if you have selected One or more times... or
Manually as your scheduling option on the preceding Specify Task Schedule screen.
Task Progress
Task Progress
The screen reports the program's progress as it performs the defined task. When the process is complete, the program displays its Task Completed screen to report the results.
Task Completed
Task Completed
The screen reports the results of the task run.
This screen may also offer an Error Log Report button if the program encountered errors during its run. If the button does appear, click it to view the program log and assess the severity of the errors. The Error Log Report button launches the MNE Log Viewer utility (see The Log Viewer chapter) to help you interpret and resolve the errors.
Other buttons can display that allow you to view .TSV files that are created to capture data for auto-resolved addresses or for duplicate SMTP addresses that were skipped by the wizard.
When you are finished using the Error Log Report feature or viewing any .TSV files, (or if no buttons appear), click Exit to exit.
Exported data elements in the SQL database
Exported data elements in the SQL database
The Directory Export Wizard gathers user information from the Domino servers to create SQL Server data tables that provide critical input data to several of the MNE wizards. These wizards use the exported data to:
-
Define collections (subsets) of users and groups for provisioning and migration.
-
Provision users and groups in AD and identify which AD/Exchange accounts correspond to which Notes source accounts.
-
Merge Exchange contacts into corresponding AD accounts to create a single mail-enabled security object per user.
-
Migrate user data from Notes source accounts into the correct corresponding AD/Exchange accounts.
-
Convert Notes-format addresses in messages, address books, and contacts to the appropriate SMTP (Internet) address for each user.
You might edit the exported directory data and the same data elements as they are associated with defined user collections (but not group collections) for a variety of reasons including:
-
To manually edit one or more addresses before using them for the migration—for example, if your organization is consolidating on a new SMTP domain as part of the migration process.
-
To populate the SearchKey column with appropriate per-user values for the Provisioning Wizard.
-
To specify the locations of user PABs, if they reside in diverse, per-user locations.
-
To prepare the data so the Data Migration Wizard can associate the resource accounts with the user accounts and enable mailboxes—if your target environment is configured for a resource forest and a user forest, with the corresponding user accounts.
Exported directory data cannot be edited directly in the SQL database. Instead, directory data can be exported from the SQL database to a .tsv-format file, viewed and edited in Microsoft Excel, and imported back into the SQL database from the modified .tsv file. For information about editing .tsv files, see the procedures under User Collections on page 29.
The SQL database also stores Global Defaults and Task Parameters, and task-run schedules, project statistics, and other information, but the reference list that follows contains only the data elements of the exported directory data tables.
The Migrator for Notes to Exchange SQL database table column headings appear in the table in this order, left to right:
NMEObjectGUID | DisplayName | ObjectType | SourceAddress | SourceAlias | Target-Address | TargetAlias | PSTDir | ExchangeMailboxStore | SearchKey | SearchKey2 | MailFilePath | PABPaths | SharedPABDirs | ArchivePaths | SharedArchiveDirs | TargetForwardingAddress | SourceForwardingAddress | DominoServerAddress
The bulleted list below presents the same column headings in alphabetical order by their names:
-
ArchivePaths: 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\
-
DisplayName: Notes user name of the user. Example: John Doe
The DisplayName is copied by the Directory Export Wizard from the first value of 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/...”).
-
DominoServerAddress: Full address of Notes mail file, including server, generated by the Directory Export Wizard by joining the Mail server and Mail file fields from Notes Person Documents, like this:
[Mail server]!![Mail file]
-
ExchangeMailboxStore: The home mailbox store in Exchange for a migrating user, used when mailbox- enabling users in the Exchange Administrative Operations of the Data Migration Wizard. If left blank, a suitable default value is derived from the configuration settings defined for the mailbox-enabling task. In certain circumstances, the migration administrators may want to specify per-user mailbox store assignments for some or all users. For example:
CN=Mailbox Store (MOBE),CN=First Storage Group,CN=InformationStore,CN=MOBE, CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=User, CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Example,DC=com
|
|
NOTE: The Exchange admin credentials for the mailbox-enabling task must have sufficient rights to create mailboxes on the Exchange server specified in this ExchangeMailboxStore column. |
|
|
NOTE: The value in the ExchangeMailboxStore column is not immediately applied to users' AD objects when the value is imported into the SQL database. The value is applied in AD only when the corresponding mail-enabling task is performed. |
-
MailFilePath: The specific path and NSF filename to a user mail file, used when an administrator knows the specific path and NSF file name for each user. If this MailFilePath column does not exist or is left empty, the program will find the user's mail file by appending the MailFile column value to the path entered on the Specify Notes Data Directory screen. Example:
\\server\home\user\jdoe.nsf
-
NMEObjectGUID: Reserved internal database identifier — do not change!
-
ObjectType: Reserved internal database identifier for object type in Notes — do not change!
-
PABPaths: The specific UNC path and filename for a user Notes address book. 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\
-
PSTDir: The directory where PSTs are stored for the user—used if each user PST will go to a separate directory. Normally the administrator would specify a central location for the program to create all PSTs, and the program would create a directory subtree under that. If you would rather put each PST in the user home directory, each user home directory can be added here. For example:
\\server\home\user
-
SearchKey: A user-identifying value (unique per user) that can be used by the Provisioning Wizard to match objects for merging, as described in chapter 8 (see Provisioning Wizard). This column is not populated by the Directory Export Wizard but can be manually populated with user-identifying values (unique per user). The Provisioning Wizard can use these values to match objects for merging if none of the other column options is suitable for the merge process.
-
SearchKey2: A user-identifying value (unique per user) that is used by the Data Migration Wizard to properly associate resource accounts with corresponding user accounts, and enable mailboxes (used only when the target environment is configured for a resource forest and a user forest, with corresponding user accounts). The wizard compares the values in the SearchKey2 column with the values of a particular AD attribute to associate corresponding accounts, as explained in Appendix A, see How Do I Prepare the SQL database for Mailbox-Enabling (If AD Is Configured for a Resource Forest and a User Forest)? This column is not populated by the Directory Export Wizard, but can be manually populated with user-identifying values as explained in Appendix A.
-
SharedArchiveDirs: 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 are not 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
-
SharedPABDirs: 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 are not 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
-
SourceAddress: Primary Notes address of the user. Example: John Doe/MyOrganization
The SourceAddress value is derived by the Directory Export Wizard from the first value of Notes’ FullName attribute that is a DN ("CN=Joe Schmoe/O=OurCompany"), with "CN=" and "O=" stripped out (leaving "Joe Schmoe/OurCompany").
-
SourceAlias: Any additional Notes addresses for the user. This field may contain zero, one, or more than one alias; multiple aliases are separated by a percent symbol (%). Example:
John Doe%Jdoe%Johnny D
-
SourceForwardingAddress: Notes-format address used to forward mail from Exchange to Notes, used in the Data Migration Wizard for the Set Mail Routing feature. This column is not populated by the Directory Export Wizard, but can be manually populated with suitable data. If this column is empty when the wizard’s forwarding feature is invoked, the wizard infers suitable values from the values in other database columns. Example:
NOTES:John Doe/MyOrganization@NOTES
|
|
NOTE: The value in this SourceForwardingAddress column is not immediately applied to the users’ Active Directory objects when the value is imported into the SQL database. The value is applied in AD only when the corresponding forwarding feature is invoked. |
-
TargetAddress: Exchange address of the user. Example: JDoe@example.com
The TargetAddress is copied by the Directory Export Wizard from the Notes internetAddress attribute. 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).
-
TargetAlias: Any user aliases found in Notes for the user. This field can contain zero, one, or more than one alias. Multiple aliases are separated by a percent symbol (%). When provisioning user accounts, any found aliases are added as proxy addresses so any mail previously sent to one of these aliases is still routed to the user account. Examples:
John.Doe@example.com Jane.Doe@example.com%JaneD@example.com
-
TargetForwardingAddress: SMTP-format address used to forward mail from Notes to Exchange, used in the Data Migration Wizard for the Set Mail Routing features. This column is not populated by Directory Export Wizard, but can be manually populated with suitable values. If this column is empty when the wizard’s forwarding feature is invoked, the wizard infers suitable values from the values in other database columns. Example:
Jdoe@migrate.example.com
|
|
NOTE: The value in the TargetForwardingAddress column is not immediately applied to the users’ Active Directory objects when the value is imported into the SQL database. The value is applied in AD only when the corresponding forwarding feature is invoked. |
