Hardware Prerequisites
|
|
Migrator Pro for Exchange should not be installed on an Exchange server. |
Migrator Pro for Exchange requires the use of a Windows Server 2012 R2, 2016, or 2019 to host the migration management software.
|
Component |
Requirement |
|---|---|
|
Processor |
Minimum: Intel Xeon quad core 1.8 Ghz (x64) or AMD equivalent |
|
Memory |
Minimum: 8 GB 8GB of RAM on the Migrator Pro for Exchange server should be sufficient for an environment containing 15,000 mailboxes or less. But for larger environments, or for environments containing large Public Folder hierarchies, increasing the memory to 16GB is recommended. |
|
Disk Space Requirements |
Minimum: 100 MB for application installation and 4 GB for database storage. |
|
Display |
1280 x 768 or higher resolution monitor |
|
Other |
Keyboard and Microsoft Mouse (or compatible pointing device), Internet access |
Supported Migration Paths
Supported Mailbox Migration Paths
The current release of Migrator Pro for Exchange supports mailbox migration for these source/target scenarios:
Supported Public Folder Migration Paths
Migrator Pro for Exchange supports inter-org (only) Public Folders migration for these source/target scenarios:
Supported Mailbox Migration Paths
The current release of Migrator Pro for Exchange supports mailbox migration for these source/target scenarios:
Supported Public Folder Migration Paths
Migrator Pro for Exchange supports inter-org (only) Public Folders migration for these source/target scenarios:
Software Prerequisites
General Installation Requirements
-
Windows Server 2012 R2, 2016, or 2019
-
PowerShell 2.0, 3.0, or 4.0
-
IIS (included with Windows Server 2012 R2, 2016, and 2019).
-
.NET 4.8 Framework (if not already installed, it will be downloaded and installed automatically if there is an Internet connection)
-
Internet Explorer 8 or later or Firefox
|
|
|
When running Migrator Pro for Exchange with PowerShell 3.0 or 4.0 installed, you may experience a small increase in memory usage of the MCP service compared with environments which use PowerShell 2.0. |
|
|
|
Migrator Pro for Exchange cannot rationalize Office 365 mailboxes when the WhenChanged DateTime format is ddMMyyyy, due to a remote PowerShell error claiming invalid date time format. Changing the date-time format of the operating system to mmddyyyy resolves the issue. |