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

Task Completed

No information is entered into this screen. The screen simply reports the results of the task run.

This screen may also offer an Error Log Report button if the program encountered any errors during its run. If the Error Log Report button does appear, you should 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.

When you are finished using the Error Log Report feature (or if the Error Log Report button does not appear), click Exit to dismiss the screen and exit the wizard.

Exported data elements in the SQL database

The Directory Export Wizard gathers user information from the Domino server(s) to create SQL Server data tables that provide critical input data to several of the Quest Wizards. These other Wizards use the exported data to:

You can 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 populate the SearchKey column with appropriate per-user values for the Provisioning Wizard.

Exported directory data cannot be edited directly within the SQL database. Instead, directory data can be exported from the SQL database to a .tsv-format file, then viewed and edited in Microsoft Excel, and then imported back into the program database from the modified .tsv file. For information on editing .tsv files, see the procedures under User Collections .

The SQL database also stores Global Defaults and Task Parameters, and task-run schedules, project statistics, and other information, but the reference list below 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:

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:
DisplayName: Notes user name of the user. Example:
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:
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 will be derived from the configuration settings defined for the mailbox-enabling task. In certain circumstances, the migration admin may want to specify per-user mailbox store assignments for some or all users. For example:
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's 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:
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'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:
PSTDir: 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 program to create all PSTs, and the program would create a directory subtree under that. If you would rather put each PST in each user's home directory, then each user's home directory can be added here. For example:
SearchKey: A user-identifying value (unique per user) that may 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 may be manually populated with user-identifying values (unique per user) that the Provisioning Wizard can use 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 properly enable mailboxes (used only when the target environment is configured for a resource forest and a user forest, with corresponding user accounts). The wizard will compare 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 may 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 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:
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 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:
SourceAddress: Primary Notes address of the user. Example:
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 address(es) for the user. This field may contain zero, one, or more than one alias; multiple aliases are separated by a percent symbol (%). Example:
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 may be manually populated with suitable data. If this column is empty when the wizard’s forwarding feature is invoked, the wizard will infer suitable values from the values in other database columns. Example:
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:
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 alias(es) found in Notes for the user. This field may contain zero, one, or more than one alias; multiple aliases are separated by a percent symbol (%). When provisioning user accounts, any found alias(es) are added as proxy addresses so any mail previously sent to one of these aliases will still be routed to the user's account. Examples:
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 may be manually populated with suitable values. If this column is empty when the wizard’s forwarding feature is invoked, the wizard will infer suitable values from the values in other database columns. Example:
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.

 

Collection Wizard

Introduction

The Collection Wizard lets you define the member contents of user and group collections, or change the attributes of an existing collection. Migrator for Notes to Exchange provisioning, migration, and other features are applied to collections of users and groups. The Collection Wizard is where these collections are defined. You can add members to a collection by selecting objects from the SQL database, or by importing the contents of a .tsv (tab-separated-values format) file, or both.

Related Documents