Migrator for Notes to Exchange 4.15.2

The $Notes:Server$ and $Exchange:Server$ examples above are commonly used in merge templates, but the most commonly used INI variables are drawn from the [User] section, representing values that vary per user:

•

$user:displayname$: The user’s Notes user name, from the SQL DB DisplayName column.

•

$user:TargetAddress$: The user’s Exchange email address, from the SQL DB TargetAddress column.

•

$user:MovedMsgCnt$: the number of the user’s mail messages that were migrated.

•

$user:MovedContactCnt$: the number of the user’s contacts that were migrated.

•

$user:MovedApptCnt$: the number of the user’s calendar items that were migrated.

•

$user:MovedEncryptedMsgCnt$: the number of the user's encrypted messages (found in the Notes source, but not migrated).

Using environment and system variables in a mail-merge template

An environment or system variable in a mail-merge template takes the form $env:VarName$, as in these examples:

•

$env:date$: the date system variable

•

$env:time$: the time system variable

Windows default environment and system variables can be viewed via the System utility in Windows’ Control Panel: On the Advanced tab of System Properties, click the Environment Variables button. You can also define new variables in the same Environment Variables dialog box.

Batch-migration process

How do I synchronize directory data and update the SQL database?

If synchronization of coexisting directories during the transition period is not a high priority for the organization, the admin may simply add and delete users and update user data in the Exchange environment (only), using Exchange administration software. Otherwise, if it is important to keep the two directories synchronized throughout the transition period:

•

Enter any staff changes in the Domino environment as they occur.

•

Prior to the migration of each user collection:

•

Use Quest’s CMN Directory Connector to re-update Active Directory to match the updated Domino directory. (You need not perform this step explicitly if the CMN Directory Connector is scheduled to automatically re-update the directories at regular intervals.)

•

After the directories are updated: Update the SQL database by using Migrator for Notes to Exchange’s Directory Export Wizard to re-export Domino directory data. (Again, you need not perform this step explicitly if you have used Notes Migration Manager to schedule automatically recurring runs of the Directory Export Wizard—for example, 30 minutes after each scheduled update run of the CMN Directory Connector.)

•

Remember to check the export results (the summary table in the Export Notes Directory screen) to verify the integrity of the exported data. Any format or translation errors should be readily apparent; missing users, or inappropriate data forms in any fields would indicate that the export process was somehow corrupted or otherwise unsuccessful.

•

If any already-migrated user leaves the organization: Delete the user from the Exchange server, using Exchange administration software.

The most efficient updating strategy will be to automate the process by scheduling the CMN Directory Connector and Migrator for Notes to Exchange’s Directory Export Wizard to automatically run successively, in tandem, at regular recurring times—say, every night at midnight or 2am.