Chat now with support
Chat con el soporte

Metalogix Email Migrator 4.7.1 - Help

Introduction Getting started Migration User Interface Configuration Troubleshooting & Tips

32-bit Outlook on 64-bit system

ISSUE

I have 32-bit Outlook on 64-bit system. During migration I want to delete/recreate shortcuts (see Shortcut Options). I use MAPI connection to Exchange Server.

 

 

SOLUTION

Install 64-bit Outlook on 64-bit system.

 

 

Failed Item Remigration

ISSUE

Migration finished with failures - some items have not been migrated. It is indicated in the Job list under Log Summary column.

 

clip0032

 

SOLUTION

Try remigrating quickly only the failed items. Simply right click the job in question and from the context menu select Migrate Failed Items option. This action is available for all kinds of migrations.

 

clip0029

 

 

 

Image(9)

NOTE:

In case of Archive-To-Archive migration job dialog with configuration options pops-up (see below):

·Create shortcuts for all migrated emails – if selected, a shortcut will be created for every single migrated item in the user mailbox, i.e. shortcuts will be created also for items that originally had no shortcuts in the user mailbox or user has deleted the shortcut

·Recreate shortcuts only if the original shortcuts exist – if selected, shortcuts will be created only for items that have shortcuts also in the source system

·Do not create shortcuts – Email Migrator will migrate the items to the target system but no new shortcuts will be created, i.e. users will still access archived items in the source system (via the original shortcuts). Archive Manager (target system) items will be available only via ArchiveWeb application for them.

·Delete original shortcuts – can be combined with every option above; when checked, source system shortcuts will be deleted from the user mailbox

 

 

clip0031

Unreadable console display

 

ISSUE

Email Migrator console does not display correctly.

 

 

SOLUTION

Your computer's display text size must be set to 100% (default) option. This settings can be found under Control Panel / Display.

 

 

Image(215)

 

 

Impersonation

 

When migrating from/to Exchange Server using EWS connection, the migrating user (<serviceAccountName>) must be assigned ApplicationImpersonation role. This topic describes how to assign this role to the migration user on different Exchange Servers.

Exchange 2013/2016 and Office 365

1. Using Exchange Control Panel (ECP)

Impersonation can be either added to an existing role group or a new role group with impersonation role can be created. Both possibilities are described below.

 

Image(9)

NOTE:

If impersonation role was added as it is described in 1.a and impersonation errors still occurs then try to add impersonation role by following instructions in 1.b.

 

1.a        Add impersonation to the existing role group as follows:

Log into ECP -> click Permissions -> click Admin roles -> double-click the Discovery Management. Under Roles click +Add and include the ApplicationImpersonation role. Then add the desired user to Members.

Snap17

1.b        Create new role group:

Log into ECP -> click Permissions -> click Admin roles -> click the + (NEW) for adding a new role -> in the pop-up enter "ApplicationImpersonation" as the name, add ApplicationImpersonation role, add the desired user(s)

 

2. Using PowerShell

Impersonation can be either added to an existing role group or a new role group with impersonation role can be created. Both possibilities are described below.

2.a        Add impersonation to the existing role group:

New-ManagementRoleAssignment -SecurityGroup "Discovery Management" -Role "ApplicationImpersonation"

2.b         Create new role group:

New-RoleGroup -Name "Impersonation" -Roles "ApplicationImpersonation" -Members administrator

 

Exchange 2010

New-ManagementRoleAssignment -Name ApplicationImpersonationRole -Role ApplicationImpersonation -User <serviceAccountName>

 

Exchange 2007

Get-ExchangeServer | where {$_.IsClientAccessServer -eq $TRUE} | ForEach-Object {Add-ADPermission -Identity $_.distinguishedname -User (Get-User -Identity <serviceAccountName>| select-object).identity -extendedRight ms-Exch-EPI-Impersonation}

Get-MailboxDatabase | ForEach-Object {Add-ADPermission -Identity $_.DistinguishedName -User <serviceAccountName> -ExtendedRights ms-Exch-EPI-May-Impersonate}

 

Documentos relacionados