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

Specify Notes Login Information

This screen appears only if the information it requests has not already been collected in the Notes Migration Manager (in the Notes Server Configuration screen), or if the Always Use option was not selected there.

These fields specify Notes server access credentials, to authenticate the administrator by whose authority the program will perform its administrative functions:

•
Domino Server: Enter the name of the Domino server to be connected.
•
User ID file: Click Browse to find and specify the path and filename of the User ID file, or type or paste the path and filename into the text box.
•
Password: Type the password associated with this User ID file.

Enter the requested information, and click Next.

Select Date and Size Filters

This screen appears only if you have selected Migrate users in the Operations screen. Select the desired date and attachment size filters, and click Next.

•
Mail dates: You may migrate all mail, or no mail, or use date-based filtering to migrate only mail items that are time-stamped before or after a particular date, or within a range of dates.
•
Calendar dates: You may migrate all calendar items, or no calendar items, or use date-based filtering to migrate only calendar items time- stamped before or after a particular date, or within a range of dates.
•
Attachment sizes: You may use size-based filtering to limit the size of attachments migrated, or migrate all attachments regardless of size. Migrating only attachments smaller than a specified size will reduce the amount of disk space needed to create the new .pst files or server database.
 
* 
NOTE: Even if you filter attachments based on size, all messages are migrated. The filter excludes only attachments that exceed the size limit; the messages to which oversized attachments were attached are still migrated.

If Office 365 is selected as the Target Exchange System: The Attachment size defaults to 24.5 MB, which is the maximum message size allowed by Office 365. If the limit is set higher than Office 365 allows, the program reads and attempts to migrate larger attachments, but they will be disallowed by Office 365 and logged as an error unless the migration has the [Exchange] MigrateOversizedAttachments feature enabled in which the program attempts to upload large attachments to the user OneDrive store.

For Office 365, you can configure MNE to migrate oversized attachments to the Microsoft OneDrive store associated with the user mailbox. For details, see Exchange Server Configuration: Migrating to Office 365 .

Select Destination Exchange Server

This screen appears only if you have selected Migrate users in the Operations screen, and if the information it requests has not already been collected in the Notes Migration Manager (in the Exchange Server Configuration screen), or if the Always Use option was not selected there.

Enter the information that will authorize and characterize (or forgo) the program’s connection to the Exchange server, and click Next.

* 
NOTE: The Exchange account must be mailbox enabled or, if migrating to Office 365, have a license that includes an Exchange mailbox.
•
Do not connect to an Exchange server: This feature makes possible the migration of data to Outlook personal folder (.pst) files prior to the setup of your Exchange server, but the check box will be available only if none of your entries on earlier screens will require a connection to an Exchange server. (For example, if you have told the program to create Exchange mailboxes, or to migrate any data to server-based mailboxes, this check box will appear grayed-out and unavailable.) If you do forgo a connection to an Exchange server, attendees’ free/busy information will be unavailable in migrated calendar appointments.
•
If you are migrating to Exchange 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 you are migrating to Exchange 2010:
Exchange CAS Server (displayed when migrating to Exchange 2010): Name of the client-access server (a specific CAS server, not the array), if any.
 
* 
NOTE: If migrating to a CAS, you must also set a throttling policy and WinRM, as described in Appendix A (see How Do I Migrate to an Exchange Environment with a CAS Array?).
•
If you are migrating to an on-premises Exchange server:
Administrator SMTP address: SMTP address of the administrator by whose authority the wizard will perform its mail-related operations. The associated profile must have “Receive As” rights.
•
If you are migrating to an on-premises Exchange server:
Administrator domain\user or UPN: The migration administrator login name to the Exchange mail server (for the administrator account associated with the Administrator SMTP address). This field entry should take the form domain\name or name@domain.sitraka.com.
•
If you are migrating to Office 365:
Exchange Administrator: The migration administrator Office 365 account name. This field entry should take the form name@domain.sitraka.com.
•
Administrator password: The password associated with the migration administrator.
•
Use admin account pool (check box, available only when migrating to Office 365): Select the check box if you want to use the Migrator for Notes to Exchange Admin Account Pooling features (as described in chapter 15 of the Administration Guide).
•
Manage: Launches the Migrator for Notes to Exchange Admin Account Pool utility.
•
Reset: Launches the Migrator for Notes to Exchange Admin Account Pool utility, deletes all admin accounts from the pool, and exits.

Resolve attendees for [type] mail (two check boxes, available only for Office 365 target): Controls whether MNE will look up SMTP addresses in user server mail and/or archives in the Exchange Global Address List (GAL) to get Exchange addresses so free-busy lookups succeed. These options are disabled by default, but can be enabled by selecting one or more of the check boxes. For example, you could select a check box 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 may cause lost free/busy information and may introduce other issues in Outlook.

Personal Archive Location

This screen appears only if you have selected (in Select Destinations for Migrated Data) to migrate one or more types of data to Outlook personal folders (.pst) files. Select the desired location and name for delivering any Outlook personal folders (.pst) files generated during the migration, and click Next.

 
* 
NOTE: When migrating to .pst files, a program parameter in the Global Defaults and Task Parameters lets you specify whether the wizard should migrate all data into a single .pst file per user, or to multiple .pst files. See in Appendix A, How Do I Specify Whether to Migrate to a Single PST File (Per User) or Multiple PST Files? for information about this option.

The options to specify the .pst output file name and directory are listed below.

•
Subdirectories of root directory specified below: Places .pst files in subdirectories under the .pst output root directory designated in the accompanying text box. This option creates a directory structure that matches the user's Notes folder hierarchy.
When this option is selected, you must also specify the file name format in the Generate the .pst filename using field.
•
Directory specified by the PSTDir column from database: Places new .pst files in the directory specified for each user in the PSTdir column of the SQL database. The PSTdir column values must be in the SQL database prior to this program run (see the Pre-Migration Preparations in chapter 2 of the Migrator for Notes to Exchange Scenarios Guide).
•
Generate the .pst filename as: When this check box is enabled, you can enter a file name string in the text field. When the check box is disabled, you must specify the file name format in the Generate the .pst filename using field.
•
Generate the .pst filename using: You can select one of the following options for the .pst file name format:
•
Source Notes filename
•
User display name
•
User id
•
SMTP email address
•
Notes email address

In addition to specifying the location for new .pst files, you must also specify the file format (by Outlook version) for which you want the files created:

•
Use Outlook 97-2002 Personal Folders File (.pst): Tells the program to format .pst files in this format (supports 2GB of data).
•
Use Office Outlook Personal Folders File (.pst): Tells the program to format the .pst files in this format, which supports up to 20GB of Unicode data. This option requires that Outlook 2010 be installed on the migration machine, and will otherwise appear grayed-out as an unavailable option.

You can specify a language for personal archive folder names using the [General] LanguageCode parameter. See the Programming Parameters Reference guide.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating