SQL Accounts and Permissions
The following accounts must be created with the respective permissions in SQL before commencing installation of Migrator Pro for Exchange.
If you are using a single account to connect to your database, and Active Directory and Exchange connectivity, you must grant these database permissions to the account:
-
Migrator Pro for Exchange MCP Service Identity - Only requires a SQL Login Account unless the account is also used as the SQL setup account, then it must have the following server role assigned: dbcreator
After the database has been created, you can remove dbcreator and assign the following specific permissions:
-
db_datareader
-
db_datawriter
-
db_ddladmin
If you are using multiple accounts to connect to your database, and Active Directory and Exchange connectivity, you must grant the following database permissions:
-
Setup SQL Account – This allows the SQL server administrator to retain accounts for Migrator Pro for Exchange that require the least amount of privileges when the application is running in a production environment. The setup login must exist prior to the configuration and requires at a minimum dbcreator rights, and can either be a Windows or SQL Login.
-
dbcreator rights
-
Windows (Current User)
-
SQL Login
-
Application SQL Account
-
db_datareader
-
db_databwriter
-
db_ddladmin
-
Migrator Pro for Exchange MCP Service Identity: public
-
Public Folders Identity - The “Migrator Pro for Exchange Worker” runs in the context of the currently logged on user. This user must have read/write access to the Migrator Pro for Exchange database if SQL Server authentication is not being used.
|
|
|
As stated, the SQL login account(s) must already exist in order for the mapping to be established to the database account using these rights. This is important as these database accounts and rights are established when the database is created. If you are using a single SQL account for application access, it will need db_datareader/db_datawriter /db_ddladmin. The Migrator Pro for Exchange MCP account requires db_ddladmin to control the schema (identity values and constraints) when using bulk copy operations as part of the data population. |
Migrator Pro for Exchange Worker Prerequisites
The Migrator Pro for Exchange Worker is utilized to distribute the provisioning and migration of Public Folders. There can be multiple Migrator Pro for Exchange Workers installed for this purpose, and the following operating systems are supported:
-
Windows Server 2012
-
Windows Server 2012 R2
-
Windows Server 2016
-
Windows Server 2019
-
Windows Server 2022
Migrator Pro for Exchange Worker requires a 64-Bit Operating System to run.
Hardware Requirements
Hardware Requirements
-
Processor: Minimum 4 cores for server OS’s.
-
Memory: Minimum 6GB.
-
Disk Space Requirements: Minimum 4GB free disk space.
Software Requirements
-
The Migrator Pro for Exchange Worker requires Microsoft .NET 4.8 framework. The Migrator Pro for Exchange Worker installer will download this framework from Microsoft if not already installed. If the end user network environment does not allow the workstations to access the internet, the end user must acquire and install this.
-
We recommend all Microsoft updates and service packs be installed before using the Migrator Pro for Exchange Worker.
-
The Migrator Pro for Exchange Worker requires Outlook 2016 32-bit or Outlook 2019.
-
The worker computers should be joined to the same domain as the main Migrator Pro for Exchange server and logged into with the <domain>\ExchangeProServiceAccount. This account should be a member of the worker computer’s Local Administrators group.
-
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.