Metalogix Email Migrator 4.7.1 - Help

Introduction Getting started Migration User Interface Configuration Troubleshooting & Tips

Connect to Exchange Mailbox

An individual mailbox can also function as Email Migrator source. The advantage of  this approach is no need to have rights to the Exchange Server as a whole.

Email Migrator capabilities regarding item migration and feature handling in respect to Exchange mailbox are summarized in the table below.

 

 

Platform

CAPABILITIES

Microsoft Exchange Mailbox

User Mailbox Items

Journal Mailbox Items

Public Folder Items

3rd party message classes

Shortcut Replace

Retention Preserv.

clip0003

clip0004

clip0004

clip0003

N/A

N/A

 

The user under which the migration from Exchange Server runs must have full permissions to the migrated mailboxes. The instructions how to assign these permissions to the migration user does not belong to the scope of this manual but they can be found in the Microsoft technet articles, e.g. http://technet.microsoft.com/en-us/library/bb676551%28v=exchg.141%29.aspx .

 

Image(58)

IMPORTANT:

Email Migrator supports Exchange Mailbox connection for Microsoft Exchange Server 2010 SP1 and higher. Exchange Mailbox connection for Microsoft Exchange Server 2003/2007 is NOT supported. Only connection to whole Exchange Server 2003/2007 is supported (see the Connect to Exchange (incl. Office 365) topic).

 

 

To establish connection:

To create connection to Exchange Mailbox as source/target, go to Connection > Connect to Exchange Mailbox.

Image(501)

This will open the Connect to Exchange Mailbox dialog containing the following options:

Connect to individual mailbox - this option allows connection to individual mailbox of your Exchange Server without the need to configure connection to the server itself; then enter the required information:

        EWS url (address where the Exchange web services are running, it is filled in automatically but if necessary, it can be changed)

        Email address,  Password,  First name,  Last name,  Full name

 

Import mailboxes from CSV - this option enables connection to several individual mailboxes at once; simply create your CSV file with columns corresponding to the above mentioned properties (EwsUrl, EmailAddress, Password, FirstName, LastName, FullName) and load it to Email Migrator via the Browse button

 

Image(9)

NOTE:

Comma must be used as a separator.

 

Image(545)

 

After all of the desired connection options have been set, click OK to establish the connection.

If Email Migrator is successful making the connection, a new node appears in the Explorer View.

Connect to Exchange (incl. Office 365)

Exchange Server (including Office 365) itself can function as source system as well. This section deals with connecting to and handling Exchange Server.

Exchange Server can contain various types of archived items. Email Migrator capabilities regarding item migration and feature handling in respect to Exchange Server are summarized in the table below.

 

Platform

CAPABILITIES

Microsoft Exchange and Office 365

User Mailbox Items

Journal Mailbox Items

Public Folder Items

3rd party message classes

Shortcut Replace

Retention Preserv.

clip0003

clip0004

clip0003

clip0003

N/A

N/A

 

The user under which the migration fromo Exchange Server runs must have full permissions to the migrated mailboxes. The instructions how to assign these permissions to the migration user does not belong to the scope of this manual but they can be found in the Microsoft technet articles, e.g. http://technet.microsoft.com/en-us/library/bb676551%28v=exchg.141%29.aspx .

 

 

To establish connection:

To create connection to Exchange Server as source/target, go to Connection > Connect to Exchange Server.

 

Image(500)

 

This will open the Connect to Exchange dialog containing the following fields:

Exchange version – from the drop-down menu select your Exchange Server version; Office 365 connection option is located above the default Exchange 2016 option; dialog options updates accordingly as not all settings are accessible for all Exchange versions

 

Image(9)

NOTE:

1)  Exchange Server 2003 and 2007 (without service pack) support only Messaging Application Programming Interface (MAPI) connection. Therefore if Outlook is not installed on the Archive Migration machine or Outlook bitness does not match the machine bitness, these two options - Exchange 2003 and Exchange 2007 - are disabled.

 

2) Additionally, Exchange Server 2003 requires Outlook 2010 or older. The connection will not work with newer Outlook.

                                       

Exchange Server – server name or IP address of your Exchange Server; in case of Office 365  the respective URL is filled in automatically

 

 

 

Connector type:

 

o Exchange Web Services (EWS) –  this type of connection is available and recommended for Exchange 2007 (SP1 or higher) and later

 

Image(9)

NOTE:

EWS is the recommended connection type. The second one - Messaging Application Programming Interface (MAPI) - should be used only for Exchange Server 2003.

EWS requires that Application Impersonation role is assigned to migrating user. (See the section on Impersonation.)

 

§ Use https – uncheck this option if EWS is running without SSL (https)

§ Use Fast Transfer – for Exchange Server 2010 SP1 and higher it is possible to use Microsoft Fast Transfer protocol for connecting to Exchange; since it is faster it's recommended option; if any archive is used as a source connector at the migration, Fast Transfer is not applicable

 

Image(9)

NOTE:

Should folder or PST file be an intended migration target, the Use Fast Transfer option must be UNCHECKED.

 

o Messaging Application Programming Interface (MAPI) – this type of connection is available for Exchange 2003 SP2 and later, but for Exchange Server versions above Exchange 2003 SP2 this is not the preferred option. If the logged on user does not have full access permissions to the selected mailbox, the following error message appears:

Error in IMsgStore.OpenEntry: MAPI_E_NOT_FOUND

 

Image(6)(1)

ATTENTION:

To use this type of connection:

·Outlook is necessary on the Email Migrator machine and the bitness of Outlook and OS must be the same. (For solving the problems with different bitness, see this troubleshooting section.)

·Connection to Office 365 is only possible when Outlook 2013/2016 is installed on the Email Migrator machine.

·Connection to Exchange Server 2003 is only possible when Outlook 2010 or older is installed on the Email Migrator machine.

·Email Migrator must be in the same domain as the Exchange Server (does not apply for Office 365)

·Migrating user must have full access permissions to migrated mailboxes.

 

 

clip0014

 

EWS url - address where the Exchange web services are running, it is filled in automatically but if necessary, it can be changed

PowerShell url - address for PowerShell; it is filled in automatically but if necessary, it can be changed; applicable only for Exchange 2010 and above

PowerShell auth - remote PowerShell uses different types of authentication. Applicable only for Exchange 2010 and above. This drop-box allows you to select the authentication that's right for you. The most commonly used authentication types are the following:

o Kerberos - recommended when Exchange Server is in the same domain as Email Migrator; for this type of authentication the Exchange Server must be specified by server name (not the IP address)

o Basic - recommended when Exchange Server is in different domain as Email Migrator; the basic authentication must be enabled for PowerShell Web Service on the target Exchange Server

o Default -  will try to use Kerberos or Negotiate authentication mechanism

o NegotiateWithImplicitCredential - Windows authentication must be enabled for PowerShell Web Service on the Exchange Server

Image(9)

NOTE:

Other authentication types can be used at administrator's convenience. For more information on individual authentication options and necessary settings, see the PowerShell Authentication section.

 

 

 

Domain - Exchange Server domain

User & Password – user that should be used for connecting to the Exchange Server; BEWARE of case sensitivity

To view/list the mailboxes to which the user has access rights, the specified user must be a member of Organization Management group in Active Directory (AD). If he is not, he will see only his own mailbox. To add the user to this group go to AD machine:

Active Directory Users and Computer -> Users -> select user -> Properties -> Member --> add Organization Management group

Image(9)

NOTE:

The administrator account should be a member of Organization Management group by default.

 

Domain controller - name of the Domain Controller                              

Store password - (Not recommended) if checked, Email Migrator will remember password for the connection and will not ask the password when Email Migrator runs next time

 

After all of the desired connection options have been set click OK to establish the connection.

If Email Migrator is successful making the connection, a new node appears in the Explorer View. You can expand this node and navigate user mailboxes.

Image(9)

NOTE:

After updating Email Migrator to newer version, some Exchange connections may disappear from the list of connections and it may be necessary to re-establish them.

 

Connect to Gmail

Email Migrator allows connection to different email/archive systems. This section deals with connecting to Gmail.

Mailboxes can contain various types of items. Email Migrator capabilities regarding item migration and feature handling in respect to Gmail are summarized in the table below.

 

Platform

CAPABILITIES

Gmail

User Mailbox Items

Calendar Items

Task Items

Contact Items*

clip0003

clip0003

clip0003

clip0003

* Except Google+ contacts

 

To access Gmail in Email Migrator, you will need a domain administrator account for Gmail, who can read all users within the domain, as well as access any person's personal Gmail account. Email Migrator uses this account to connect to Gmail, and upon a successful connection, all of the Gmail users will be accessible.

 

This section guides you through the process as follows:

Creating a Gmail Service Account

Granting Gmail Service Account Access

Connecting to Gmail

 

 

Creating a Gmail Service Account

In order to connect to Gmail users will need to enter the Service Email, Secret, and Private Key File field values into the Connect to Gmail dialog box. These three items make up the credentials of the service account required to authenticate with Gmail. This section will review how to create the service account and get the necessary values.

 

 

Image(9)

NOTE:

Chrome is the recommended browser. With other browsers, not all functions may work as indicated.

 

1. Login to the Google Developers console at "https://console.developers.google.com/project".

2. In the account drop-down menu, click the Create a project.

Gmail1

 

3. When the project is created, open the All projects list and select created project (from the account drop-down menu). In the upper left corner, clickclip0089(Products & Services), in the left hand pane click IAM & Admin, click Service accounts and then Create Service Account.

Gmail2

 

4. Enter account name. Check the Furnish a new private key option and under Key type switch to P12. Click Create.

Gmail3

 

After clicking Create, new P12 Key file will be created and downloaded. Save the file where you can easily find it, as you will need to browse for the file in the Private Key File section when connecting to your Gmail Account in Email Migrator.

Also, Private Key password will be shown. This is the key that you will enter in the Secret field when connecting to your Gmail Account in Email Migrator. Once you have recorded the Private Key password, click Close.

 

5. In the Service accounts list click the View Client ID next to the newly created service account. The Client Id is required to grant service account access to the corresponding APIs. Please see the Granting a Gmail Service Account Access section below for instructions on how to do this.

 

Gmail4

6. Client ID and Service account will be displayed. Save both, as they have to be entered when creating Gmail connection in Email Migrator.

NOTE: Service account is the Service Email required when connecting to your Gmail Account in Email Migrator.

 

Gmail5

 

 

 

 

 

Granting a Gmail Service Account Access

The following steps will grant the Gmail service account access to the required APIs.

1. Login to "https://admin.google.com" with an administrator user account.

2. Click on the Security application.

Image(630)

3. Click on the Show more button at the bottom, and select Advanced Settings.

Image(631)

4. In the Advanced Settings screen, select Manage API client access.

Image(632)

5. Paste the Client ID you copied from the Creating a Gmail Service Account section above, into the Client Name field.

6. Copy and paste the following scopes into the One or More API Scopes field:

https://mail.google.com/

https://www.googleapis.com/auth/admin.directory.user.readonly

https://www.googleapis.com/auth/calendar

https://www.googleapis.com/auth/gmail.readonly

https://www.googleapis.com/auth/tasks

https://www.googleapis.com/auth/contacts.readonly

https://www.google.com/m8/feeds

 

7. Click Authorize.

 

 

Connecting to Gmail

 

To establish the connection:

1. First in the Email Migrator ribbon menu click the Connection > Connect to Gmail.

 

Image(593)

 

2. This will open the Connect To Gmail dialog allowing user to enter specific Gmail account connection information of the user whose Gmail will be connected.

 

 

Image(592)

 

 

3. Enter an Admin user name (<user>@<organization>.net), this should be a domain administrator that can read all users within the domain, as well as access any person's personal Gmail.

4. Enter the Domain Name. In order to find the Domain Name follow these steps:

a) Login to "https://admin.google.com" with the administration user account.

b) Click on the Domains application.

Image(617)

c) The domain you need to use for accessing your Google Account will be located under the Domain heading. An example using "examplematrixapps.net" is show below.

Image(618)

5. Enter the Service Email, Secret, and Private Key File. These three items make up the credentials of the service account required to authenticate with Gmail. Please see the Creating a Gmail Service Account section of this page for more details on how to create this service account (and Granting a Gmail Service Account Access section for how to grant it the required access). You can also find information on the Gmail service account at following page: https://developers.google.com/drive/web/delegation.

6. Once all the information has been entered click OK.

7. Once connected, the Gmail will appear in the Explorer View section of the Email Migrator UI. From there, it can be navigated and acted on using the features available in Email Migrator.

 

Connect to PST file

Besides connection to different email/archive systems, Email Migrator allows also connection to PST files stored on the network. PST file can be the source of migration. The following lines describe this type of connection.

 

 

Platform

CAPABILITIES

PST file

User Mailbox Items

Journal Mailbox Items

Public Folder Items

3rd party message classes

Shortcut Replace

Retention Preserv.

clip0003

clip0004

clip0003

clip0003

N/A

N/A

 

 

There may be a huge number of PST files in the domain, especially in case of large organizations. Email Migrator facilitates the handling of PST files by providing two ways of connecting:

A.Search for PST Files - PST discovery feature performing domain scanning for PST files

B.Connect to PST File - connecting to single PST file in the network

 

 

A. Search for PST files

This option lists all existing PST files in the Email Migrator.

First in the Email Migrator ribbon menu click the Connection > Search for PST Files.

(To connect to a PST file, its full name (full path\name) must have max. 254 characters.)

 

clip0010

 

This will open the Search PST File dialog where you specify the domain to be searched through. The domain must be either the current domain of Email Migrator or trusted domain:

 

clip0007

As the whole domain scanning for PST files can take a considerable time in case of large organizations, the prompt on all domain computer scanning appears. Select:

YES - to let Email Migrator search all domain computers for PST files and list them in the administrative console between other connections (see the screenshot below)

NO - to avoid possible time-consuming listing of PST files and display only the root (domain) node between other connections

 

Image(9)

NOTE:

The searching for computers or PST files in the domain can be initiated from the context menu as described further.

 

 

clip0009

 

The context menu of the root (domain) node facilitates the task of managing PST. It offers the following actions:

·Find Computers - click this option to list all computers from the domain

·Add Computers - click this option to add just specific computer existing in the domain (computer name, not the IP address)

·Search PST files - (available also for individual computer nodes - e.g. TSO-WIN7 in the screenshot above) click this option to look up all PST files in the given domain/computer. The number of existing PST files appears in the brackets next to the given computer. Unfold the computer node to see and manage these PST files.

·Assign PST Owners - (available also for individual computer nodes - e.g. TSO-WIN7 in the screenshot above) when clicked, the PST file name(s) change(s) (ONLY in Email Migrator!) and the PST is named after its owner. PST file name is not changed when the owner cannot be resolved (e.g. when multiple owners exist). It is recommended to run assigning of owners before migration).

 

 

B. Connect to PST Files

This option is useful when connecting to a single PST file.

First in the Email Migrator ribbon menu click the Connection > Connect to PST File.

(To connect to a PST file, its full name (full path\name) must have max. 254 characters.)

 

Image(493)

 

This will open the Connect To PST File dialog with the following options:

 

Image(406)

 

PST file - enter the path to the desired PST file or use the Browse button to locate it

No password - select if the PST file is not password protected

Use password - select if access to the PST file requires a password; enter the password and check Remember my password if the password should be stored in the system for future use

 

 

After all of the desired connection options have been set, click OK to establish the connection.

If Email Migrator is successful making the connection, a new node appears in the Explorer View.

Documentos relacionados