Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.16.1 - 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

Select Office 365 Administrative Operations

This screen appears if you selected the Office 365 administrative functions check box on the Operations screen. It lets you select the following options.

Reset user passwords: Resets the user passwords for mailboxes in the collection. This function assigns random one-time-only passwords that permit a user to log onto Office 365 the first time.The user must reset the password to something more durable and memorable.
Assign user licenses: When this option is selected, MNE performs a new Office 365 user licensing operation.
NOTE: The Data Migration Wizard can license Office 365 users when the userPrincipalName differs from the primary SMTP address. With this feature, an administrator can use TSV Import feature to assign alternate UPN values to the SQL database. To do this, from the Export Notes Directory screen:

MNE will read the imported UPN values, if they are present in the database, when licensing Office 365 users.

Without this feature, the wizard uses the SMTP address for the userPrincipalName, but this can cause issues in environments where the userPrincipalName is different, since the Office 365 Administrative Operations wizard would not find the users in the target Office 365 environment.

License users: Select this option to assign licenses to users.
Unlicense users: Select this option to remove user licenses.
Usage Location: Use the drop-down list to specify your users’ Usage Location. This is a mandatory designation that Microsoft requires for its Office 365 licenses (see this Microsoft article). Your selection corresponds to a two-letter Usage Location code that is saved in MNE Global Defaults and Task Parameters as the [Exchange] O365UsageLocation=<xx> parameter.
Product License: Office 365 is available in a variety of plans (see this Microsoft article). MNE populates the Product License field with the Office 365 licensing plans available to your organization and the number of licenses available for each plan. If the [Exchange]O365AccountSkuId parameter is set, the specified license plan is the default selection.

License plan services can have dependencies on other services. When licensing users, MNE does not validate that the combination of services selected is valid. If you disable a service on which another enabled service is dependent, user licensing will fail with the error Unable to assign the license.

Configure Migration Notification Messages

This screen is displayed if you selected Migrate users on the Operations screen, or if you selected Send migration notification messages on the Administrative Operations screen. You can define personalized (mail-merge) migration notification emails to send to the users in this collection or define emails containing migration status summary information to send to administrators.

The first two check boxes let you specify whether to send migration notification messages to Notes mailboxes only, Exchange mailboxes only, or both. The third check box allows you to send migration status summary messages to one or more administrators.

The wizard generates the emails by merging a template file with per-user variable values drawn from the collection data table in the SQL database.

Select options for these message types:

Send “You’ve been migrated” messages to Notes mailboxes: The wizard generates a merged email to the Notes mailbox of every user in the collection, notifying them of their migration to Exchange. (The wizard inserts these messages directly into users’ Notes mailboxes, so they are not intercepted by any forwarding rules that would re-route them to Exchange.) The email typically explains to users that they have been migrated to Exchange, and should use the Outlook client for future email and calendar activities. The email also typically provides each user’s new Outlook login credentials, and any other special instructions or helpful tips. The default Template file for this email varies depending on your Exchange destination:
ybm_template.html: for migration to any on-premises Exchange server, or to a hosted-Exchange environment other than Office 365.
ynma_template.html: for migration to Office 365.
Another template file (o365_pwreset.html) is provided for Office 365 migrations, with language and a merge variable to notify users of their new one-time-only Office 365 passwords. The notice delivers a randomly generated password (generated by Migrator for Notes to Exchange), and explains that the user should use it to log on to Office 365 the first time, and change the password to something more durable and memorable.
Send “Welcome to Exchange” messages to Exchange mailboxes: The wizard generates a merged email to the Exchange mailbox of every user in the collection, welcoming them to the Exchange environment and the Outlook client, and often including an attachment to orient users to their new tools. The template file for these “Welcome to Exchange” messages is wte_template.html.
Two text boxes also ask you to specify the SMTP address and Display Name to be identified as the Sender of the messages (usually the migration administrator).
Subject: Enter the text to be inserted into the email Subject line.
Template file: Click Browse to locate and specify the template file to be used for the body of the mail-merge message. You can choose one of the standard templates installed with Migrator for Notes to Exchange, or create and use your own.
Send “Migration summary” messages to administrators: The wizard sends a merged email to all the SMTP addresses that are specified in the Recipient SMTP address text box. The email provides the migration summary and often includes an attachment containing logs of the migration statistics for each user in the collection. The email message might also include an attachment that contains a log of deferred Notes emails to be sent at a future date and time by Domino.
Recipient SMTP address: Enter the SMTP address for each administrator that will receive the migration summary email. You can enter multiple SMTP addresses, separated by a ; (semi-colon).
Subject: Enter the text to be inserted into the email Subject line.
Template file: Click Browse to locate and specify the template file to be used for the body of the mail-merge message. The template file for the migration summary messages is named migration_summary_template.html.
Note: If the sent email is triggered by the Migrate mailbox data operation, the migration summary information describes the current migration statistics. If the sent email is triggered by the General administrative functions (visibility and directory sync flags, migration notifications) operation, the migration summary information describes the migration statistics of last data migration that performed the Migrate mailbox data operation.

Select Notes Administrative Operations

This screen appears if you have selected Notes administrative functions in the Operations screen. Specify which Notes administrative functions you want to perform for users in the selected collection and click Next.

Set Notes foreign directory sync (feature available only when not performing mail routing): Allows the CMN Directory Connector to extract user data from the Notes directory during its directory synchronization. (This corresponds to the Notes parameter Allow foreign directory synchronization.) To disable foreign directory synchronization, leave the check box selected but select Disable in the drop-down list. In some configurations, migrated objects that were merged or mailbox-enabled in AD become unrecognizable to a Notes directory update, so the update mistakenly creates duplicate objects in AD.
You should Disable foreign directory sync if all of the following conditions apply:
The Notes person documents are not set to turn users into Exchange objects.
Set Notes user visibility: Lets you specify the preferred scope of user visibility in the Domino directory. If this check box is selected, the wizard will later display another screen for you to specify user visibility.
Set Notes Person Document Attributes (appears only if Migrate users is selected on the Operations screen and the Count=<#> parameter value is greater than zero in the [PersonDocCustom] section of the Task Parameters): Tells the wizard whether to assign attribute values to Notes person documents as defined by parameters in the same [PersonDocCustom] section. (See the Program Parameters Reference Guide for information about how to assign the values.) If this check box is clear, the wizard ignores the [PersonDocCustom] parameters.
Send migration notification messages: Select this option to send mail-merge messages when a data migration is not in progress. It displays the Configure mail-merge messages to migrating users screen.

Specify Data for Migration

This screen appears only if you selected Migrate users in the Operations screen. Select items to define the scope of this migration and click Next. A later screen asks you to specify whether each type of data should be migrated to personal folder (.pst) files or to server-based mailboxes.

This screen is designed to let you migrate email messages, calendar data, and the trash folder independently from the server and/or from the archives.

Migrate mail data: You can specify one or more of email messages, “Active Mail,” calendar data, task data, the trash folder, and/or iNotes contacts.
[P] Migrate Active Mail [Configure]

This Migrator for Notes to Exchange feature can detect and convert Notes rich-content features whereby messages carry “live” or “active” functional content. For more information about Active Mail, see Migrating Notes “Active Mail” in chapter 3 of Migrator for Notes to Exchange’s Pre-Migration Planning Guide.

To enable Active Mail processing: Select the Migrate Active Mail check box, click Configure and enter your preferences in the pop-up dialog box:
[ ] Encrypted mail
P] Stored forms
[P] Hotspots
[P] Rich markup
Click OK to save your preferences and return to the Specify Data to Migrate screen.
The Notification message (whose file path is specified in the dialog box) is a file containing a text string that the wizard inserts at the top of the body of any migrated message containing Active Mail. MNE installs a default file, ActiveMailNotificationMessage.txt, to the installation directory, but you can specify a different filename and/or folder in the dialog box.
The text file must be UTF-8 encoded and must contain a placeholder, called $ActiveMailAttachment$, that MNE replaces with the Active Mail NSF attachment when the message is migrated. Since the contents of this text file become part of an RTF body, characters such as "\", "{", and "}" must be escaped with a leading "\" (so they become, respectively, "\\", "\{", and "\}").
Migrate archives: You can specify one or more of email messages, calendar data, task data, and/or the trash folder.
Migrate personal address books: The Notes user PABs typically are stored locally (per user), but can also reside with the mailfile, or on a server, and can be migrated by any of four different methods. The Send PAB Replicator Wizard can help users copy their PABs to a central location on the Domino server so that this feature can migrate them. For more information about migrating PABs, see “Migrating PABs” in chapter 3 of the Pre-Migration Planning Guide.
Merge into folder named: Enter the name for the folder that will contain the migrated PABs—a Contacts folder in a mailbox or .pst file, not a file system folder.
NOTE: If Contacts were migrated to a folder other than the default Contacts folder, the wizard will remigrate Contacts only to the same folder, even if you specify a different folder name. To remigrate Contacts to a different folder name, you must hard-delete the previous Contacts folder and its contents. If you try to remigrate Contacts to a different folder name without deleting the previous folder, the wizard migrates them (excluding duplicates) to the previous folder.
Migrate recent contacts into folder named: Enter the name for the folder that will contain the migrated PABs' Recent Contacts lists.
Set contact 'File as' to: Determines the format of the contact’s File As attribute in Exchange. The File As attribute is used by Outlook to alphabetize your contacts. The options for this setting are:
Use current display name: Use the Display Name attribute of the address book entry. By default, the wizard migrates contacts using display names that match the display name of the contact in Notes, however the contact’s display format can be modified using the [General] ContactDisplayNameFormat parameter.
FirstLast: Create the File As using the first name and last name attributes separated by a space. The middle name and name suffix are included if present.
LastFirst: Create the File As using the last name and first name attributes separated by a comma. The middle name is included if present.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating