Edit Default Settings: Notes Server Configuration
This screen collects the information necessary for the program and its wizards to access the Notes server. Click Apply after you enter new information or changes to existing information. The program cannot read or save new information or changes until Apply is clicked.
-
Notes credentials (Server, User ID file, Password): These credentials authenticate the administrator by whose authority the program will access the Notes server for data export, setting and removing mail- forwarding rules during the migration, and data migration.
-
Always use these values: Select this check box if you want the wizards that need this information to always use these credentials. If this box is selected, the wizard skips the screen that requests credential information. If the box is clear, the wizard takes the values entered as its defaults but displays the screen to provide the option of accepting or changing the default credentials.
-
Apply: Reads and saves new or changed information. Any new information or changes are discarded if you do not click Apply before you exit.
-
More info: Launches the Log Viewer to display the log file associated with this screen. The button is enabled only if the program has encountered significant errors or warnings that typically require resolution before continuing in the migration process. If no significant errors or warnings are encountered, the button appears grayed-out (unavailable).
Edit Default Settings: Exchange Server Configuration
This screen collects the information needed for the applications to access the Exchange server or Microsoft 365. Click Apply after you enter or change information. The program cannot save new or changed information until you click Apply.
Target Exchange server version: Specify the Exchange version of your migration target: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, or Microsoft 365.
This setting determines how the application facilitates mail-enabling and other AD activities.
If you selected an on-premises Exchange target, see Exchange Server Configuration: Migrating to on-premises (proprietary) Exchange on page 19.
If you selected Microsoft 365, see Exchange Server Configuration: Migrating to Microsoft 365 on page 20.
|
|
NOTE: Exchange account must be a mailbox-enabled or, if migrating to Microsoft 365, have a license that includes an Exchange mailbox. |
Exchange Server Configuration: Migrating to on-premises (proprietary) Exchange
Specify the information that will be used as the defaults for migration to on-premises Exchange.
Exchange credentials:
The account used to access Exchange must be granted Receive-As permissions on the mail store. Also, the account cannot belong to a group that is explicitly denied access to the mail stores. These groups include Enterprise Admins, Domain Admins, and the Organization Management role. If the Exchange account is added to any of these groups, MNE cannot connect to the target mailboxes during the migration.
|
|
NOTE: There can be a significant delay between granting Receive-As permission and Exchange allowing the account to access other mailboxes, up to 30 minutes. |
Alternately, you could grant the permissions manually using the following PowerShell cmdlet:
get-mailboxdatabase | add-adpermission -user <username> -extendedrights receive-as
However, if you grant permissions manually using PowerShell, you must reconfigure the account each time a new database is added.
If you use the Automatically grant permissions option, MNE grants permissions on the database container and the permissions are inherited by all databases, even the databases that are added after initial configuration. If you are using the PowerShell cmdlet to grant access, disable the built-in mechanism by clearing the check box.
-
If the Target Exchange server version is 2013, 2016, or 2019:
Exchange Mailbox Server: Name of the Exchange server, which has the Mailbox role installed on it and will be the connection used for all Exchange PowerShell activities in the product.
-
If the Target Exchange server version is 2010:
Exchange CAS Server: Name of the client-access (CAS) server, not an array. This is the connection used for all Exchange PowerShell activities in the product.
|
|
NOTE: IfmigratingtoaCAS,youmustalsosetathrottlingpolicyandWinRM,asdescribedin AppendixA(see How Do I Migrate to an Exchange Environment with a CASArray?). |
-
Administrator SMTP address: The SMTP address of the administrator by whose authority the wizard will perform its mail-related operations.
-
Administrator domain\user or UPN: Enter the migration administrator login name for the Exchange mail server (for the account associated with the Administrator SMTP address) in the following format: domain\name or name@domain.sitraka.com.
-
Administrator password: The password associated with the administrator account.
Always use these values:
Select this check box if you want the wizards to always use these credentials and settings.The wizards will skip the screens that request credential information. If the check box is cleared, the wizards take the values entered here as defaults, but displays the screens to offer the option of accepting or changing the entries.
More info:
Launches the Log Viewer to display the log file associated with this screen. This button is enabled only if the program has encountered significant errors or warnings that warrant attention before continuing in the migration process. If no such significant errors or warnings are encountered, the button appears grayed-out (unavailable).
Exchange Server Configuration: Migrating to Microsoft 365
Specify the information that will be used as the defaults for migration to Microsoft 365 (previously known as Microsoft 365) Exchange Online.
Exchange credentials:
-
Exchange Administrator: Enter the Microsoft 365 account name for the migration administrator in the format of name@domain.sitraka.com. The account must have the role of global administrator on the hosted tenant.
-
Administrator password: The password associated with the administrator account.
Tenant settings
-
Microsoft 365 Environment: Select the appropriate Microsoft 365 environment in the list. The options are:
-
Microsoft 365 User domain: In the drop-down list, select the Microsoft 365 domain that should be used to compose the user Microsoft Online Services ID (logon names and email addresses) in Microsoft 365.
|
|
NOTE: The program loads the drop-down list with the domains registered in Microsoft 365 for the administrator credentials you entered. The Microsoft 365 User domain selected is the portion of each user email address that follows the @ symbol. The left side of each user ID is his/her User ID from the MNE SQL server. |
-
Use Azure Active Directory Synchronization: Select this check box if you are using the Microsoft AD synchronization tool to copy the contents of a local Active Directory to provision your Microsoft 365 directory. Leave this check box clear if you will provision Microsoft 365 by any other method.
-
Resolve attendees for [type] mail (two check boxes): Controls whether MNE looks up SMTP addresses in the user server mail, and/or archives, in the Exchange GAL to get Exchange addresses—so that free- busy lookups succeed. These options are disabled (cleared) by default. Leave the check box empty if you want to migrate data to PST files without connecting to the Exchange server. Disabling the Resolve attendees function can increase migration speed in some environments but can cause lost free/busy information and introduce other issues in Outlook.
-
Microsoft 365 PowerShell Throttling: Click Configure to open a PowerShell Throttle Settings dialog box, which calculates the maximum number of concurrent PowerShell connections each MNE server can open (the MaxPowerShellConnections setting). MNE uses this value to enforce the limit set by Microsoft for the tenant. The default for this throttle is 9 simultaneous runspace connections.
The dialog box calculates the MaxPowerShellConnections setting using the formula R / S, where R is the number of simultaneous runspaces allowed by your tenant (Maximum Tenant Concurrency = 9 by default), and S is the number of migration servers you will use. If the quotient is not a whole integer, MNE rounds down to the next lower whole integer. The default value of MaxPowerShellConnections=0 is interpreted as “no limit,” effectively turning off this limiting feature.
PowerShell Throttle Settings:
-
Maximum Migrations Servers: The maximum number of migration servers to be used for your migration.
-
Migrator for Notes to Exchange MaxPowerShellConnections Setting: The maximum number of concurrent PowerShell connections each migration server can open.
-
Use admin account pool: Select this check box to use the Migrator for Notes to Exchange Admin Account Pool feature (described in chapter 15 of the Administration Guide).
-
Manage: Launches Migrator for Notes to Exchange’s Admin Account Pool utility.
-
Reset: Launches the Migrator for Notes to Exchange Admin Account Pool utility and deletes all admin accounts from the pool.
-
Migrate oversized attachments: Oversized attachments are attachments that exceed the limit defined by the attachment size filter in the Data Migration Wizard. For messages that contain attachments which are not oversized but where the overall message size exceeds the limit imposed by Microsoft 365, all attachments are migrated as oversized attachments.
To migrate oversized attachments to the user OneDrive store, you must register MNE with the Microsoft Azure portal and grant the necessary permissions to OneDrive.
-
Configure: Opens the Microsoft Azure App Registration page. The page is used to register the MNE application with the Microsoft Azure portal. It also allows you grant access to the OneDrive store associated with the user mailbox to store oversized message attachments.
Always use these values:
Select this option if the wizards will always use these credentials and settings. The wizard skips the screen that requests credential information. If the check box is empty, the wizard uses the values entered as defaults, but will display the screen to offer the option of accepting or changing the credentials.
More info:
Launches the Log Viewer to display the log file associated with the functionality of this screen. This button is enabled only if the program has encountered significant errors or warnings that warrant further attention before continuing in the migration. If no significant errors or warnings are encountered, the button appears grayed-out (unavailable).
