Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Binary Tree Migrator Pro for Exchange 20.10.1 - Fast Start Guide

Prepare and Verify Your Environment

 

Some migration scenarios require specific Exchange servers and/or roles. Find your planned migration path below to see if you can migrate directly, or if you will need additional components.

Mailbox Migration Paths

   

 

   

Public Folder Migration Paths

   

 

   

 

 

Mailbox Migration Paths

 

Some migration scenarios require specific Exchange servers and/or roles. Find your planned migration path below to see if you can migrate directly, or if you will need additional components.

   

 

   

Public Folder Migration Paths

   

 

   

 

 

Public Folder Migration Paths

 

Some migration scenarios require specific Exchange servers and/or roles. Find your planned migration path below to see if you can migrate directly, or if you will need additional components.

Mailbox Migration Paths

   

 

   

   

 

   

 

 

Prepare for Installation

 

 

Assemble credentials for:

  • An existing SQL server, if you do not plan to use the optional SQL installation offered as part of the Migrator Pro for Exchange install process.

  • Active Directory (AD), to create some Global Groups, such as “E2E_Admins

  • Exchange (source and target): accounts with membership in the Exchange Organization Administrators and Organization Management groups, and Global Administrators if migrating to Office365.

  • Local administrator access on the server that will be used for Migrator Pro for Exchange.

  • If you are migrating Public Folders, you will need mailbox-enabled accounts in both source and target, that are members of their respective Public Folder Management Exchange groups.

Prepare the servers:

  • Choose a Windows Server 2012 R2, 2016, or 2019 machine for the Migrator Pro for Exchange installation. 

  • If you will migrate Public Folders, you may want to take advantage of Automated Workload Distribution. This will allow you to create a “farm” of worker machines that can process Public Folders. You can choose Windows Server 2012, Windows Server 2012R2, Windows Server 2016, or Windows Server 2019 for the worker machines.  You will also need to install Outlook 2010 SP2 (32-bit only), Outlook 2013 (32-bit only), or Outlook 2016 (32-bit only) for Public Folder migration.

  • Public Folder migration to Exchange 2013 requires Exchange 2013 CU5+.

  • Choose the servers to use as PowerShell hosts.

  • On the PowerShell host servers, you will need to enable PowerShell remoting using Enable-Psremoting

  • You will need to configure authentication on PowerShell hosts using

    • Set-PowerShellVirtualDirectory “<Exchange Server name>\PowerShell (Default Web Site)” –BasicAuthentication $true -WindowsAuthentication $true (for Non-SSL mode)

    • Set-PowerShellVirtualDirectory “<Exchange Server name>\PowerShell (Default Web Site)” –BasicAuthentication $true     (for SSL mode)

  • If you will use PowerShell in SSL mode, you will need SSL certificates (not self-signed) that are trusted by the Migrator Pro for Exchange server.

  • The date-time format of the operating system must be set to mmddyyyy for Migrator Pro for Exchange to rationalize Office 365 mailboxes.

  • Internet Explorer Enhanced Security Configuration (IE ESC) must be disabled.

  • The registry must be modified to disable User Account Control (UAC). In the registry, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system, set DWORD EnableLUA to 0, and then reboot.

 

Outils libre-service
Base de connaissances
Notifications et alertes
Support produits
Téléchargements de logiciels
Documentation technique
Forums utilisateurs
Didacticiels vidéo
Flux RSS
Nous contacter
Obtenir une assistance en matière de licence
Support Technique
Afficher tout
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation