Mecanismos de interacción

The process begins with existing user accounts and mailboxes on a Lotus Domino server. These Necessary Pre-Migration Preparations are performed only once, before the Data Migration Wizard or Self-Service Desktop Migrator is run the first time to migrate any users.

Step 1: Verify that All System Requirements and Prerequisites Are Satisfied

Make sure that your network environments, your source and destination servers, your users’ desktop environments, and your own administrator’s workstation all conform to the System Requirements specified in chapter 1 of this Guide.

System Requirements include the admin accounts that will be used to run the Quest applications and access data and features in the Notes/Domino and Exchange/AD environments. If these accounts do not already exist, be sure to create and configure them now, as described in the System Requirements.

Remember also that any antivirus software on the admin workstation must be configured to not scan the Quest program files directory or %temp% directory, or may simply be turned off, prior to running any Quest admin application.

(Although it may be restored after the program runs.) If an antivirus scan misinterprets an NME temporary file as a threat, it will try to "clean" the file, which will generate an error when the NME program call fails.

Step 2: Verify SQL Server and Default Settings

Most of the features and Wizards of Notes Migrator for Exchange require access to information stored in a central database on the SQL Server. Most also require access to the Notes server, Exchange server, Active Directory, and the Shared Directories that contain the Self-Service Desktop Migrator and its log and status files, and admin application log files. The features and Wizards therefore need to know the pertinent server names, configuration information, access credentials and so forth for the various servers.

These Default Settings can be entered now, into Notes Migration Manager, before other program features or the Wizards are used, so that it will be available to them and need not be entered again. If the information is not entered now or upon installation, the product features and Wizards will prompt for the values as needed, and most of them will have to be entered more than once—for each feature and Wizard that needs it.

Quest therefore recommends you use the five Edit Default Settings screens of Notes Migration Manager to enter this information now. The Notes Migration Manager is documented in chapter 1 of the NME Administration Guide.

Step 3: Create Mail-Enabled AD Accounts for All Users

Provisioning may be accomplished by a variety of methods, but the typical and most direct approach begins with a directory update by Quest’s CMN Directory Connector. The CMN Directory Connector extracts data from the Notes/Domino source and creates mail-enabled contacts in AD for all Notes users.

Many organizations will have already defined their migrating Notes users in AD as security objects for network authentication, and in this case the directory update will create new contacts in AD that correspond to the existing security objects. (CMN’s Directory Connector detects and merges potential duplicate entities by their addresses, but security objects typically have not been assigned email addresses.) But NME’s AD Object Merging Wizard can (in a later step below) merge the contact information into the original AD object record, and

then delete the contact, leaving a single mail-enabled object in AD. Future directory updates will then see the merged AD object’s address attribute, and so will not re-copy the corresponding Notes object.

This process provisions and mail-enables the AD accounts. Another NME Wizard can then mailbox-enable the AD accounts.

NME’s AD Object Merging Wizard cannot merge objects until after the Notes directory contents have been exported, because the merge process requires data that will be exported from the Notes directory. The AD Object Merging Wizard is therefore run only after the Directory Export Wizard has been run, in a later step below.

Step 4: Configure SMTP Mail Routing

If you will use smart hosts (within a single domain):

The creation of mail-enabled AD accounts (preceding step) will have entered the necessary targetAddress values into the AD object records.

Establish and configure the Domino and Exchange smart host servers. The details of configuring smart-host SMTP mail routing are beyond the scope of this Guide, but see your Domino and Exchange documentation and online resources for more information about configuring smart hosts for those servers.

To configure smart-host SMTP routing with Quest's CMN, both smart hosts are configured to point to the CMN server. Within CMN, one set of SMTP IN and SMTP OUT queues is configured to accept mail from Domino and deliver it to the receiving Exchange server, while another set is configured to accept mail from Exchange and deliver it to Domino. Multiple CMN servers can be deployed for load balancing and redundancy. The CMN User Guide explains this scenario in more detail (see chapter 3).

If you will use subdomains (two or more domains):

Create a temporary subdomain for the migration (e.g., exch.domain.com) and assign it to the Exchange email server in DNS. The subdomain will differentiate the Exchange server from the Domino server internally (within your organiza-tion’s network) during the transition. Internal mail from other Notes users that arrives in the Notes accounts of migrated users will be forwarded to the appro-priate Exchange mailboxes using the exch.domain.com subdomain.

Also: Create a recipient policy to generate a secondary SMTP address, so that all Exchange users will be able to receive mail at exch.domain.com.

Step 5: Redirect External Inbound Mail to Exchange

At some point after routing has been configured between the two systems, you should redirect your external inbound (Internet) email to the Exchange server.

If migrating without coexistence:

External inbound email should be rerouted to Exchange before you begin the data migration. This will prevent new mail from arriving in Notes after the migration has begun, and will route all mail, whether migrated from Notes or newly received from outside, to the users’ new Exchange mailboxes.

If migrating with coexistence:

Redirect your external inbound email for your primary SMTP domain (for example, domain.com) to the Exchange server. This is commonly done through the DNS configuration on your AD Domain Controller by changing the MX (Mail eXchange) record for your primary domain to point to the new Exchange server.

Some companies may use other types of external inbound mail routing configurations—for example, mail sentries or spam filters.

For users who have not yet migrated, the SMTP routing configuration (set when the user accounts were provisioned) will route this inbound mail back to the corresponding Notes mailboxes. These routing rules can then be automatically removed by the Data Migration Wizard as each user is migrated, so the user's mail will thereafter be routed to the corresponding Exchange mailbox.

We list this task here, among the Necessary Pre-Migration Preparations, but the external inbound mail can actually be changed at any time after the email rout-ing has been configured. Many administrators choose to defer changrout-ing the ex-ternal inbound routing until half of their users have migrated to Exchange, to minimize internal mail traffic during the transition period.

Step 6 (If Necessary): Define Free/Busy