Metalogix Email Migrator 4.7.1 - Help

Introduction Getting started Migration User Interface Configuration Troubleshooting & Tips

Object was not found in the store

ISSUE

I get the following error message:

 

Exception Thrown: Object was not found in the store.

 

 

 

SOLUTION

User has no full permission over mailbox. Add full permission to the user and try again.

 

Uncheck "Use Fast Transfer" option

ISSUE

When I attempt migration, the following error message is displayed:

 

Source server binary data format and target server binary data format do not match! Please uncheck "Use Fast Transfer" on source or target server in connection dialog when connecting to Exchange Server.

 

How do I uncheck Use Fast Transfer option that has been set when the connection was established?

 

Image(342)

 

 

SOLUTION

This message is displayed when Use Fast Transfer option is check for the source connector but not for the target connector. All you need to do is to:

 

- uncheck the Use Fast Transfer option on the source connector

 

or

 

- check the Use Fast Transfer option on the target connector

 

 

Reopen the connection configuration dialog for the given connector and change the connector settings. You just need to right-click the respective Exchange connector and select the Edit Connection option. Then in the uncheck the Use Fast Transfer option.

 

 

Image(426)

 

Changing the size in IIS Manager

ISSUE

When migrating Exchange Server 2010 to Office 365 I got the following error message in the log:

The request Failed with HTTP - status 413. Request entity too long.

 

 

SOLUTION

This behavior is caused by IIS Manager setting restricting the size of files by default to 49152. This has to be increased manually to at least 1000000.

 

To do so, follow the next steps:

 

1.Open Internet Information Services Manager.

2.Unfold the tree down to <SeverNode> / Sites / Default Website / EWS.

3.In the main pane double-click the Configuration Editor.

4.In the Section drop-down select system.webServer/serverRuntime.

5.Change the uploadReadAheadSize default setting to at least 1000000. Then click Apply.

 

Image(660)

 

 

Automating migrations

QUESTION

How can I automate migration of multiple users?

 

ANSWER

Email Migrator supports PowerShell scripting that can be used for the automation

 

To create a PowerShell script that can be used for the automation you have to create a template job you’ll generate the script from.  Follow the steps below to create the template job and script. If you’ve already performed a mailbox to mailbox migration you can generate the script from such job.

1.Select the source mailbox and click Copy.

2.Select the target mailbox and click Paste. The source and target name should match.

3.Configure the job parameters.

4.Click Save. A new job is created in the Job list upon clicking Save.

5.Select the newly created job.

6.From Job list menu select Generate PowerShell Script / For Current User and Machine.

clip0020

7.New Notepad window containing a PowerShell script opens.

8.Add following line to the very beginning of the script.

param([Parameter(Mandatory=$True)][string]$User)

9.Replace all occurrences of the mailbox name you’ve generated the script for with $User

a.There should 4 replacements done – 2 on the line starting $SourceCollection = New-MetalogixSerializableObjectCollection and 2 on the line starting $TargetCollection = New-MetalogixSerializableObjectCollection

10.Add following line to the very end of the script:

exit

 

11.To suppress messages written to console you can add -quiet switch to the end of the line starting $SourceCollection | Copy- (nor success, nor warning, nor fail messages displayed).

Or you can also add $warningPreference = 'SilentlyContinue' - this will suppress only warning messages but e.g. success messages are displayed.

12.Add new parameters in case of distributed migration (change existing JobDatabase parameter to AgentDatabase parameter and add new parameters Certificate and RunRemotely)

 

13.Save the file as a .ps1 file to the location of your choice. We’ll use migrate.ps1 in examples below.

 

 

Examples of using the script

Start Windows PowerShell and change the current directory to a folder where you script is located

1.To start migration of all "Users to Migrate" AD group members use the following cmd-let

Get-ADGroup -Identity 'Users to Migrate' | Get-ADGroupMember |% { $_.Name; .\migrate.ps1 -User $_.Name; }

 

2.To start migration of all users listed in mailboxes.txt file use the following cmd-let

Get-Content -Path .\mailboxes.txt |% { $_; .\migrate.ps1 -User $_ }

 

 

Image(9)

NOTE:

PowerShell are machine and user specific therefore one script cannot be copied to multiple machines.

 

 

Documentos relacionados