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:
|
• |
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. |
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.
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. |
• |
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. |
• |
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. |
NOTE: You can also edit any of the template files to add or delete or modify content to better suit your organization’s needs. For information about editing and creating these template files, see in Appendix A: How Do I Create or Edit a Template for Personalized User-Notification Emails? |
• |
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. |
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. |
• |
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. |
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.
NOTE: The Data Migration Wizard preserves ACL information, including calendar and task folder ACLs, as it migrates Notes source data to Exchange. To disable this feature, you could set ACLs=0 in the [General] section of Task Parameters or Global Defaults. |
|
• |
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. |
NOTE: Active Mail processing is an optional feature that is disabled by default but can be enabled by the following check box, under the Migrate mail data check box:
[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. |
• |
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. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center