Chat now with support
Chat mit Support

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

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 checkbox 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 checkbox 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:
Exchange Mailbox Server: Name of the Exchange server, which has the Mailbox role installed on it and will be the primary connection used for all Exchange required 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.
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 Exchange 2010, 2013, or 2016:
Administrator domain\user or UPN: The migration admin’s login name to the Exchange mail server (for the admin account associated with the Administrator SMTP address cited above). 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 admin’s Office 365 account name. This field entry should take the form name@domain.sitraka.com.
Administrator password: The password associated with the migration admin specified above.
Use admin account pool (checkbox, available only when migrating to Office 365): Mark this checkbox if you want to use Migrator for Notes to Exchange’s Admin Account Pooling features (as described in chapter 15 of the Administration Guide).
Manage button: Launches Migrator for Notes to Exchange’s Admin Account Pool utility.
Reset button: Launches Migrator for Notes to Exchange’s Admin Account Pool utility, and then automatically deletes all admin accounts from the pool and exits.

Exchange MAPI Profile:

If you are migrating to Exchange 2010:
Automatically configure profile: Use Exchange autodiscover to create and configure a MAPI profile.
If you are migrating to Exchange 2013 or 2016
Connect using Outlook Anywhere: If Automatically configure profile is unchecked, Connect using Outlook Anywhere is automatically enabled. The Data Migration Wizard will use Remote Procedure Calls (RPC) within HTTP packets to communicate with Exchange.

Exchange Proxy Settings

Connect using SSL only: Determines whether the Data Migration Wizard will use a secure socket layer (SSL) to connect to the Exchange proxy server. Note that this option can be disabled only if the Use this authentication field (bottom of the dialog box) is set to NTLM Authentication.
Mutually authenticate the session when connecting with SSL: Determines whether the Data Migration Wizard will mutually authenticate the session, by the proxy server certification server name specified below.
Principal name for proxy server: The Exchange proxy server certification server name (URL).
On fast networks, connect using HTTP first, then connect using TCP/IP: Determines whether the Data Migration Wizard will, when communicating on a fast network, connect using HTTP first, and then connect using TCP/IP.
On slow networks, connect using HTTP first, then connect using TCP/IP: Determines whether the Data Migration Wizard will, when communicating on a slow network, connect using HTTP first, and then connect using TCP/IP.
Proxy authentication settings / Use this authentication...: Specify the authentication method the Data Migration Wizard should use when connecting to the Exchange proxy server.

Resolve attendees for [type] mail (two checkboxes, available only for Office 365 target): Control whether Migrator for Notes to Exchange will look up SMTP addresses in user server mail and/or archives in the Exchange GAL, to get Exchange addresses—e.g., so free-busy lookups will succeed. These options are both disabled by default, but either or both can be enabled by marking the checkboxes. For example, you could mark a checkbox to migrate data to PST files without connecting to the Exchange server. Disabling the Resolve attendees function may 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.

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.
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:

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.

Specify Migration Run Information

Enter the requested information to control this program run and its log file, and click Next.

Number of migration threads (simultaneous user migrations): The number of simultaneous processes the program will use to perform migrations. The optimum number of threads depends on several factors such as processor speed and bandwidth. Most administrators report optimum performance from settings of 8 to 12 concurrent processes. You may want to experiment with different values to determine the optimum setting for your network configuration and processing capacity.

Generating Task

No information is entered into this screen.

This screen reports the wizard's progress as it determines the details and associated work items of the task you have prepared it to create. You will then (in the next screen) have a chance to review the details and associated work items, and decide whether to create the task, or go back and change any of the specifications that define the task.

When this generation process is complete, the wizard automatically advances to the next screen.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen