Converse agora com nosso suporte
Chat com o suporte

Binary Tree Migrator Express for Exchange 20.10 - Requirements

Requirements

This section details the requirements for implementing Migrator Express for Exchange.

Hardware Requirements

Migrator Express for Exchange requires the use of a Windows 7 or Windows 8 client, or a Windows 2008 R2 or Windows 2012 R2 server 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

Disk Space Requirements

Minimum: 100 MB for application installation and 2 GB for database storage.

Display

1280 x 768 or higher resolution monitor

Other

DVD Drive, Keyboard and Microsoft Mouse (or compatible pointing device), Internet access

Migrator Express for Exchange should not be installed on an Exchange server.

Software Requirements

The following is required to install Migrator Express for Exchange:

  • Windows 7 or 8 client

    Or

    Windows Server 2008 R2 or 2012 R2 Server

  • Outlook 2010 32-bit SP2 or Outlook 2013 32-bit

  • SQL Server 2012 Express R2 64-bit.  The Migrator Express for Exchange installer can download and install SQL Server 2012 Express R2 64-bit (the SA password is automatically set to Password1).  Alternately, the installation of SQL Server Express 2012 R2 64-bit can be skipped and an existing SQL Server can be used.

If not already installed, the following prerequisites will be downloaded and installed automatically if there is an Internet connection:

  • .NET 4.5.2 Framework. The install will also activate .NET 3.5.1 if it is not already activated.

  • Microsoft Management Pack (PowerShell) v3.0

  • Windows Management Framework 3.0 (for Windows 7 and Windows 2008 R2 installs)

Network Requirement

  • During installation, an internet connection is needed to automatically download any missing prerequisites.

  • An internet connection is needed to view training videos hosted by YouTube.

SQL Server Installation Requirements

  • SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, or SQL Server 2008 R2 Express

    • If using SQL Server 2008 R2 Express, ensure the SQL browsing service is running and set to automatic. If running SQL Server 2008 R2 Express on a remote server, ensure that the TCP/IP protocol is enabled and the TCP port is set to 1433. See SQL Server Configuration Manager>SQL Server Network Configuration>Protocols for SQLEXPRESS to enable TCP/IP Protocol, and Properties>IP Addresses>IPAll to set the TCP port.

  • Network connectivity to SQL Server

Additional Requirements

  • The fully qualified domain name (FQDN) of the SQL server.

  • Install appropriate Exchange security certificates on the Migrator Express for Exchange workstation.

  • Firewalls on the local machine should be turned off or Migrator Express for Exchange should be added to the Firewall whitelist. To migrate archives, MAPIMigrate.exe should also be added to the Firewall whitelist.

  • Outlook Anywhere should be configured for Exchange 2013 or 2016.

  • Cached Exchange Mode must be disabled for any Outlook profiles selected in the Migrator Express for Exchange settings. Migrator Express for Exchange will attempt to automatically disable Cached Exchange Mode for selected Outlook profiles. If Cached Exchange Mode cannot be automatically disabled, it can be manually disabled from the Control Panel by opening Mail > Show Profiles > Properties > E-mail Accounts, and then double-clicking the email account associated with the profile and deselecting the Use Cached Exchange Mode option.

  • Migrator Express for Exchange supports profiles for Microsoft Exchange or compatible service (MAPI) only.

Account Permissions

Administrative account(s) require the following permissions:

  • Local administrator on the Migrator Express for Exchange workstation

  • Source domain account with full access to mailboxes being migrated

    • Account must reside on the server where mailboxes are migrated

  • Target domain account with full access to target mailboxes where content will be copied

    • Account must reside on the server where mailboxes are migrated

Granting Mailbox Permissions

Below is a PowerShell command to grant FullAccess to all mailboxes within an OU where ‘Finance’ is the OU and “mapiadmin” is the account. This must be executed for all mailboxes in the source and target domains.

Get-Mailbox -OrganizationalUnit Finance | Add-MailboxPermission -AccessRights FullAccess -User "mapiadmin" -InheritanceType "All"

Required Permissions for Source Exchange 2003

As Exchange 2003 does not support PowerShell, the Exchange System Manager should be used to grant the required permissions to perform the migration.

By default, the security tab is not visible on Exchange System Manager, at the organization level.

To display this tab, verify that the console is closed and then modify or create the following registry key:

  1. Start Registry Editor (regedit) and navigate to the following key: HKEY_CURRENT_USER\Software\Microsoft\Exchange\ExAdmin

  2. On the Edit menu, click Add Value, and then add the following registry value:

    Value Name: ShowSecurityPage

    Data Type: REG_DWORD

    Value: 1

  3. Close Registry Editor.

Now determine which service account will be used to access the source mailboxes. This account MUST NOT be a member of Domain Admins, as this group is explicitly denied from having read access to mailboxes.

  1. 1From Exchange System Manager, right click on the upper most entry (the organization) and select properties.

  2. Go to the Security tab.

  3. Click Add, and append your designated source service account, granting it Full Control.

  4. Click OK. It may take up to an hour for the service account to assert its new rights against source mailboxes across your various servers. Restarting the Microsoft Exchange Information Store service will force these changes on that particular server.

SQL Accounts and Permissions

Accounts must be created with the following SQL permissions before starting installation of Migrator Express for Exchange.

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 Express 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 least dbcreator rights, and can either be a Windows or SQL Login.

    • dbcreator rights

    • Windows (Current User)

    • SQL Login

  • Application SQL Account

    • db_datareader

    • db_datawriter

    • db_ddladmin

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 accounts and rights are applied when the database is created. If you are using a single SQL account for application access, it will need db_datareader, db_datawriter, and db_ddladmin rights.

Migrator Express for Exchange Agent Supported Platforms

The following platforms are supported for the Migrator Express for Exchange Agent:

  • Source Exchange versions: 2003, 2007, 2010, 2013, 2016, and O365

  • Target Exchange versions:  2010, 2013, 2016, and O365

  • Windows 7, 8, 8.1, and 10, both 32-bit and 64-bit

  • Outlook 2007 32-bit, Outlook 2010, 2013, and 2016 32-bit and 64-bit

 

Hardware Requirements

This section details the requirements for implementing Migrator Express for Exchange.

Migrator Express for Exchange requires the use of a Windows 7 or Windows 8 client, or a Windows 2008 R2 or Windows 2012 R2 server 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

Disk Space Requirements

Minimum: 100 MB for application installation and 2 GB for database storage.

Display

1280 x 768 or higher resolution monitor

Other

DVD Drive, Keyboard and Microsoft Mouse (or compatible pointing device), Internet access

Migrator Express for Exchange should not be installed on an Exchange server.

Software Requirements

The following is required to install Migrator Express for Exchange:

  • Windows 7 or 8 client

    Or

    Windows Server 2008 R2 or 2012 R2 Server

  • Outlook 2010 32-bit SP2 or Outlook 2013 32-bit

  • SQL Server 2012 Express R2 64-bit.  The Migrator Express for Exchange installer can download and install SQL Server 2012 Express R2 64-bit (the SA password is automatically set to Password1).  Alternately, the installation of SQL Server Express 2012 R2 64-bit can be skipped and an existing SQL Server can be used.

If not already installed, the following prerequisites will be downloaded and installed automatically if there is an Internet connection:

  • .NET 4.5.2 Framework. The install will also activate .NET 3.5.1 if it is not already activated.

  • Microsoft Management Pack (PowerShell) v3.0

  • Windows Management Framework 3.0 (for Windows 7 and Windows 2008 R2 installs)

Network Requirement

  • During installation, an internet connection is needed to automatically download any missing prerequisites.

  • An internet connection is needed to view training videos hosted by YouTube.

SQL Server Installation Requirements

  • SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, or SQL Server 2008 R2 Express

    • If using SQL Server 2008 R2 Express, ensure the SQL browsing service is running and set to automatic. If running SQL Server 2008 R2 Express on a remote server, ensure that the TCP/IP protocol is enabled and the TCP port is set to 1433. See SQL Server Configuration Manager>SQL Server Network Configuration>Protocols for SQLEXPRESS to enable TCP/IP Protocol, and Properties>IP Addresses>IPAll to set the TCP port.

  • Network connectivity to SQL Server

Additional Requirements

  • The fully qualified domain name (FQDN) of the SQL server.

  • Install appropriate Exchange security certificates on the Migrator Express for Exchange workstation.

  • Firewalls on the local machine should be turned off or Migrator Express for Exchange should be added to the Firewall whitelist. To migrate archives, MAPIMigrate.exe should also be added to the Firewall whitelist.

  • Outlook Anywhere should be configured for Exchange 2013 or 2016.

  • Cached Exchange Mode must be disabled for any Outlook profiles selected in the Migrator Express for Exchange settings. Migrator Express for Exchange will attempt to automatically disable Cached Exchange Mode for selected Outlook profiles. If Cached Exchange Mode cannot be automatically disabled, it can be manually disabled from the Control Panel by opening Mail > Show Profiles > Properties > E-mail Accounts, and then double-clicking the email account associated with the profile and deselecting the Use Cached Exchange Mode option.

  • Migrator Express for Exchange supports profiles for Microsoft Exchange or compatible service (MAPI) only.

Account Permissions

Administrative account(s) require the following permissions:

  • Local administrator on the Migrator Express for Exchange workstation

  • Source domain account with full access to mailboxes being migrated

    • Account must reside on the server where mailboxes are migrated

  • Target domain account with full access to target mailboxes where content will be copied

    • Account must reside on the server where mailboxes are migrated

Granting Mailbox Permissions

Below is a PowerShell command to grant FullAccess to all mailboxes within an OU where ‘Finance’ is the OU and “mapiadmin” is the account. This must be executed for all mailboxes in the source and target domains.

Get-Mailbox -OrganizationalUnit Finance | Add-MailboxPermission -AccessRights FullAccess -User "mapiadmin" -InheritanceType "All"

Required Permissions for Source Exchange 2003

As Exchange 2003 does not support PowerShell, the Exchange System Manager should be used to grant the required permissions to perform the migration.

By default, the security tab is not visible on Exchange System Manager, at the organization level.

To display this tab, verify that the console is closed and then modify or create the following registry key:

  1. Start Registry Editor (regedit) and navigate to the following key: HKEY_CURRENT_USER\Software\Microsoft\Exchange\ExAdmin

  2. On the Edit menu, click Add Value, and then add the following registry value:

    Value Name: ShowSecurityPage

    Data Type: REG_DWORD

    Value: 1

  3. Close Registry Editor.

Now determine which service account will be used to access the source mailboxes. This account MUST NOT be a member of Domain Admins, as this group is explicitly denied from having read access to mailboxes.

  1. 1From Exchange System Manager, right click on the upper most entry (the organization) and select properties.

  2. Go to the Security tab.

  3. Click Add, and append your designated source service account, granting it Full Control.

  4. Click OK. It may take up to an hour for the service account to assert its new rights against source mailboxes across your various servers. Restarting the Microsoft Exchange Information Store service will force these changes on that particular server.

SQL Accounts and Permissions

Accounts must be created with the following SQL permissions before starting installation of Migrator Express for Exchange.

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 Express 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 least dbcreator rights, and can either be a Windows or SQL Login.

    • dbcreator rights

    • Windows (Current User)

    • SQL Login

  • Application SQL Account

    • db_datareader

    • db_datawriter

    • db_ddladmin

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 accounts and rights are applied when the database is created. If you are using a single SQL account for application access, it will need db_datareader, db_datawriter, and db_ddladmin rights.

Migrator Express for Exchange Agent Supported Platforms

The following platforms are supported for the Migrator Express for Exchange Agent:

  • Source Exchange versions: 2003, 2007, 2010, 2013, 2016, and O365

  • Target Exchange versions:  2010, 2013, 2016, and O365

  • Windows 7, 8, 8.1, and 10, both 32-bit and 64-bit

  • Outlook 2007 32-bit, Outlook 2010, 2013, and 2016 32-bit and 64-bit

 

Software Requirements

This section details the requirements for implementing Migrator Express for Exchange.

Hardware Requirements

Migrator Express for Exchange requires the use of a Windows 7 or Windows 8 client, or a Windows 2008 R2 or Windows 2012 R2 server 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

Disk Space Requirements

Minimum: 100 MB for application installation and 2 GB for database storage.

Display

1280 x 768 or higher resolution monitor

Other

DVD Drive, Keyboard and Microsoft Mouse (or compatible pointing device), Internet access

Migrator Express for Exchange should not be installed on an Exchange server.

The following is required to install Migrator Express for Exchange:

  • Windows 7 or 8 client

    Or

    Windows Server 2008 R2 or 2012 R2 Server

  • Outlook 2010 32-bit SP2 or Outlook 2013 32-bit

  • SQL Server 2012 Express R2 64-bit.  The Migrator Express for Exchange installer can download and install SQL Server 2012 Express R2 64-bit (the SA password is automatically set to Password1).  Alternately, the installation of SQL Server Express 2012 R2 64-bit can be skipped and an existing SQL Server can be used.

If not already installed, the following prerequisites will be downloaded and installed automatically if there is an Internet connection:

  • .NET 4.5.2 Framework. The install will also activate .NET 3.5.1 if it is not already activated.

  • Microsoft Management Pack (PowerShell) v3.0

  • Windows Management Framework 3.0 (for Windows 7 and Windows 2008 R2 installs)

Network Requirement

  • During installation, an internet connection is needed to automatically download any missing prerequisites.

  • An internet connection is needed to view training videos hosted by YouTube.

SQL Server Installation Requirements

  • SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, or SQL Server 2008 R2 Express

    • If using SQL Server 2008 R2 Express, ensure the SQL browsing service is running and set to automatic. If running SQL Server 2008 R2 Express on a remote server, ensure that the TCP/IP protocol is enabled and the TCP port is set to 1433. See SQL Server Configuration Manager>SQL Server Network Configuration>Protocols for SQLEXPRESS to enable TCP/IP Protocol, and Properties>IP Addresses>IPAll to set the TCP port.

  • Network connectivity to SQL Server

Additional Requirements

  • The fully qualified domain name (FQDN) of the SQL server.

  • Install appropriate Exchange security certificates on the Migrator Express for Exchange workstation.

  • Firewalls on the local machine should be turned off or Migrator Express for Exchange should be added to the Firewall whitelist. To migrate archives, MAPIMigrate.exe should also be added to the Firewall whitelist.

  • Outlook Anywhere should be configured for Exchange 2013 or 2016.

  • Cached Exchange Mode must be disabled for any Outlook profiles selected in the Migrator Express for Exchange settings. Migrator Express for Exchange will attempt to automatically disable Cached Exchange Mode for selected Outlook profiles. If Cached Exchange Mode cannot be automatically disabled, it can be manually disabled from the Control Panel by opening Mail > Show Profiles > Properties > E-mail Accounts, and then double-clicking the email account associated with the profile and deselecting the Use Cached Exchange Mode option.

  • Migrator Express for Exchange supports profiles for Microsoft Exchange or compatible service (MAPI) only.

Account Permissions

Administrative account(s) require the following permissions:

  • Local administrator on the Migrator Express for Exchange workstation

  • Source domain account with full access to mailboxes being migrated

    • Account must reside on the server where mailboxes are migrated

  • Target domain account with full access to target mailboxes where content will be copied

    • Account must reside on the server where mailboxes are migrated

Granting Mailbox Permissions

Below is a PowerShell command to grant FullAccess to all mailboxes within an OU where ‘Finance’ is the OU and “mapiadmin” is the account. This must be executed for all mailboxes in the source and target domains.

Get-Mailbox -OrganizationalUnit Finance | Add-MailboxPermission -AccessRights FullAccess -User "mapiadmin" -InheritanceType "All"

Required Permissions for Source Exchange 2003

As Exchange 2003 does not support PowerShell, the Exchange System Manager should be used to grant the required permissions to perform the migration.

By default, the security tab is not visible on Exchange System Manager, at the organization level.

To display this tab, verify that the console is closed and then modify or create the following registry key:

  1. Start Registry Editor (regedit) and navigate to the following key: HKEY_CURRENT_USER\Software\Microsoft\Exchange\ExAdmin

  2. On the Edit menu, click Add Value, and then add the following registry value:

    Value Name: ShowSecurityPage

    Data Type: REG_DWORD

    Value: 1

  3. Close Registry Editor.

Now determine which service account will be used to access the source mailboxes. This account MUST NOT be a member of Domain Admins, as this group is explicitly denied from having read access to mailboxes.

  1. 1From Exchange System Manager, right click on the upper most entry (the organization) and select properties.

  2. Go to the Security tab.

  3. Click Add, and append your designated source service account, granting it Full Control.

  4. Click OK. It may take up to an hour for the service account to assert its new rights against source mailboxes across your various servers. Restarting the Microsoft Exchange Information Store service will force these changes on that particular server.

SQL Accounts and Permissions

Accounts must be created with the following SQL permissions before starting installation of Migrator Express for Exchange.

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 Express 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 least dbcreator rights, and can either be a Windows or SQL Login.

    • dbcreator rights

    • Windows (Current User)

    • SQL Login

  • Application SQL Account

    • db_datareader

    • db_datawriter

    • db_ddladmin

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 accounts and rights are applied when the database is created. If you are using a single SQL account for application access, it will need db_datareader, db_datawriter, and db_ddladmin rights.

Migrator Express for Exchange Agent Supported Platforms

The following platforms are supported for the Migrator Express for Exchange Agent:

  • Source Exchange versions: 2003, 2007, 2010, 2013, 2016, and O365

  • Target Exchange versions:  2010, 2013, 2016, and O365

  • Windows 7, 8, 8.1, and 10, both 32-bit and 64-bit

  • Outlook 2007 32-bit, Outlook 2010, 2013, and 2016 32-bit and 64-bit

 

Network Requirement

This section details the requirements for implementing Migrator Express for Exchange.

Hardware Requirements

Migrator Express for Exchange requires the use of a Windows 7 or Windows 8 client, or a Windows 2008 R2 or Windows 2012 R2 server 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

Disk Space Requirements

Minimum: 100 MB for application installation and 2 GB for database storage.

Display

1280 x 768 or higher resolution monitor

Other

DVD Drive, Keyboard and Microsoft Mouse (or compatible pointing device), Internet access

Migrator Express for Exchange should not be installed on an Exchange server.

Software Requirements

The following is required to install Migrator Express for Exchange:

  • Windows 7 or 8 client

    Or

    Windows Server 2008 R2 or 2012 R2 Server

  • Outlook 2010 32-bit SP2 or Outlook 2013 32-bit

  • SQL Server 2012 Express R2 64-bit.  The Migrator Express for Exchange installer can download and install SQL Server 2012 Express R2 64-bit (the SA password is automatically set to Password1).  Alternately, the installation of SQL Server Express 2012 R2 64-bit can be skipped and an existing SQL Server can be used.

If not already installed, the following prerequisites will be downloaded and installed automatically if there is an Internet connection:

  • .NET 4.5.2 Framework. The install will also activate .NET 3.5.1 if it is not already activated.

  • Microsoft Management Pack (PowerShell) v3.0

  • Windows Management Framework 3.0 (for Windows 7 and Windows 2008 R2 installs)

  • During installation, an internet connection is needed to automatically download any missing prerequisites.

  • An internet connection is needed to view training videos hosted by YouTube.

SQL Server Installation Requirements

  • SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, or SQL Server 2008 R2 Express

    • If using SQL Server 2008 R2 Express, ensure the SQL browsing service is running and set to automatic. If running SQL Server 2008 R2 Express on a remote server, ensure that the TCP/IP protocol is enabled and the TCP port is set to 1433. See SQL Server Configuration Manager>SQL Server Network Configuration>Protocols for SQLEXPRESS to enable TCP/IP Protocol, and Properties>IP Addresses>IPAll to set the TCP port.

  • Network connectivity to SQL Server

Additional Requirements

  • The fully qualified domain name (FQDN) of the SQL server.

  • Install appropriate Exchange security certificates on the Migrator Express for Exchange workstation.

  • Firewalls on the local machine should be turned off or Migrator Express for Exchange should be added to the Firewall whitelist. To migrate archives, MAPIMigrate.exe should also be added to the Firewall whitelist.

  • Outlook Anywhere should be configured for Exchange 2013 or 2016.

  • Cached Exchange Mode must be disabled for any Outlook profiles selected in the Migrator Express for Exchange settings. Migrator Express for Exchange will attempt to automatically disable Cached Exchange Mode for selected Outlook profiles. If Cached Exchange Mode cannot be automatically disabled, it can be manually disabled from the Control Panel by opening Mail > Show Profiles > Properties > E-mail Accounts, and then double-clicking the email account associated with the profile and deselecting the Use Cached Exchange Mode option.

  • Migrator Express for Exchange supports profiles for Microsoft Exchange or compatible service (MAPI) only.

Account Permissions

Administrative account(s) require the following permissions:

  • Local administrator on the Migrator Express for Exchange workstation

  • Source domain account with full access to mailboxes being migrated

    • Account must reside on the server where mailboxes are migrated

  • Target domain account with full access to target mailboxes where content will be copied

    • Account must reside on the server where mailboxes are migrated

Granting Mailbox Permissions

Below is a PowerShell command to grant FullAccess to all mailboxes within an OU where ‘Finance’ is the OU and “mapiadmin” is the account. This must be executed for all mailboxes in the source and target domains.

Get-Mailbox -OrganizationalUnit Finance | Add-MailboxPermission -AccessRights FullAccess -User "mapiadmin" -InheritanceType "All"

Required Permissions for Source Exchange 2003

As Exchange 2003 does not support PowerShell, the Exchange System Manager should be used to grant the required permissions to perform the migration.

By default, the security tab is not visible on Exchange System Manager, at the organization level.

To display this tab, verify that the console is closed and then modify or create the following registry key:

  1. Start Registry Editor (regedit) and navigate to the following key: HKEY_CURRENT_USER\Software\Microsoft\Exchange\ExAdmin

  2. On the Edit menu, click Add Value, and then add the following registry value:

    Value Name: ShowSecurityPage

    Data Type: REG_DWORD

    Value: 1

  3. Close Registry Editor.

Now determine which service account will be used to access the source mailboxes. This account MUST NOT be a member of Domain Admins, as this group is explicitly denied from having read access to mailboxes.

  1. 1From Exchange System Manager, right click on the upper most entry (the organization) and select properties.

  2. Go to the Security tab.

  3. Click Add, and append your designated source service account, granting it Full Control.

  4. Click OK. It may take up to an hour for the service account to assert its new rights against source mailboxes across your various servers. Restarting the Microsoft Exchange Information Store service will force these changes on that particular server.

SQL Accounts and Permissions

Accounts must be created with the following SQL permissions before starting installation of Migrator Express for Exchange.

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 Express 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 least dbcreator rights, and can either be a Windows or SQL Login.

    • dbcreator rights

    • Windows (Current User)

    • SQL Login

  • Application SQL Account

    • db_datareader

    • db_datawriter

    • db_ddladmin

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 accounts and rights are applied when the database is created. If you are using a single SQL account for application access, it will need db_datareader, db_datawriter, and db_ddladmin rights.

Migrator Express for Exchange Agent Supported Platforms

The following platforms are supported for the Migrator Express for Exchange Agent:

  • Source Exchange versions: 2003, 2007, 2010, 2013, 2016, and O365

  • Target Exchange versions:  2010, 2013, 2016, and O365

  • Windows 7, 8, 8.1, and 10, both 32-bit and 64-bit

  • Outlook 2007 32-bit, Outlook 2010, 2013, and 2016 32-bit and 64-bit

 

Ferramentas de autoatendimento
Base de conhecimento
Notificações e alertas
Suporte a produtos
Downloads de software
Documentação técnica
Fóruns de usuário
Tutorial em vídeo
Feed RSS
Fale conosco
Obtenha assistência de licenciamento
Suporte técnico
Visualizar tudo
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação