How to Increase Concurrent Mailbox Moves Limit in Exchange Server (MSExchangeMailboxReplication.exe.config for 2010, 2016, 2019 & SE)

When performing bulk local database migrations (New-MoveRequest / New-MigrationBatch) or hybrid onboarding moves to Exchange Online, administrators frequently notice that dozens of move requests sit in the Queued or StalledDueToTarget_MdbReplication state while only a handful of mailboxes move concurrently.

These concurrency limits are governed by the Microsoft Exchange Mailbox Replication Service (MRS) configuration file (MSExchangeMailboxReplication.exe.config). In this updated guide covering Exchange Server 2010, 2016, 2019, and Exchange Server Subscription Edition (SE), we show where MSExchangeMailboxReplication.exe.config is located, which exact XML attributes control concurrent moves, and how to update them across all servers using PowerShell.


Architecture: How MRS Throttles Concurrent Mailbox Migrations

Mailbox Replication Service (MRS) Concurrency Control Plane
Symptom
Queued / Stalled Moves
  • StatusDetail: Queued
  • StalledDueToTarget_MdbReplication
  • Default source/target DB caps reached
Config File
MRSConfiguration XML
  • MSExchangeMailboxReplication.exe.config
  • Tune MaxActiveMovesPerSourceMDB
  • Tune MaxActiveMovesPerTargetMDB
Apply & Accelerate
Restart MRS + Priority
  • Restart-Service MSExchangeMailboxReplication
  • Use -Priority Emergency for VIPs
  • Monitor DAG `CopyQueueLength` during burst

Default MSExchangeMailboxReplication.exe.config File Location & Values

Parameter in <MRSConfiguration>Exchange 2010 DefaultExchange 2016 / 2019 / SE DefaultRecommended High-Throughput Migration Value
Config File PathC:\Program Files\Microsoft\Exchange Server\V14\Bin\C:\Program Files\Microsoft\Exchange Server\V15\Bin\ ($env:ExchangeInstallPath\Bin\)Always back up .config before editing
MaxActiveMovesPerSourceMDB5 (or 2 on throttled profiles)2050 – 100
MaxActiveMovesPerTargetMDB22050 – 100
MaxActiveMovesPerSourceServer50100150 – 200
MaxActiveMovesPerTargetServer5100150 – 200
MaxTotalRequestsPerMRS100100200 – 300
Queued Mailbox Move Requests

Method 1: Automated PowerShell Script to Update MSExchangeMailboxReplication.exe.config

Instead of manually opening Notepad on every Exchange server in your DAG, run this PowerShell script as Administrator in the Exchange Management Shell (EMS) to automatically back up MSExchangeMailboxReplication.exe.config, update the XML attributes under <MRSConfiguration>, and restart the MSExchangeMailboxReplication service:

POWERSHELL
$ConfigPath = Join-Path $env:ExchangeInstallPath "Bin\MSExchangeMailboxReplication.exe.config"
$BackupPath = "$ConfigPath.bak_$(Get-Date -Format 'yyyyMMdd_HHmmss')"

# 1. Create a timestamped backup of MSExchangeMailboxReplication.exe.config
Copy-Item -Path $ConfigPath -Destination $BackupPath -Force
Write-Host "[+] Backed up MRS config to: $BackupPath" -ForegroundColor Cyan

# 2. Load the XML configuration and update the concurrency limits
[xml]$MrsXml = Get-Content -Path $ConfigPath -Raw
$MrsNode = $MrsXml.configuration.MRSConfiguration

$MrsNode.MaxActiveMovesPerSourceMDB    = "50"
$MrsNode.MaxActiveMovesPerTargetMDB    = "50"
$MrsNode.MaxActiveMovesPerSourceServer = "150"
$MrsNode.MaxActiveMovesPerTargetServer = "150"
$MrsNode.MaxTotalRequestsPerMRS        = "200"

$MrsXml.Save($ConfigPath)

# 3. Restart the Microsoft Exchange Mailbox Replication Service to apply changes
Restart-Service MSExchangeMailboxReplication
Write-Host "[+] Updated MRS concurrency limits and restarted MSExchangeMailboxReplication!" -ForegroundColor Green

# 4. Verify the active XML values
[xml]$VerifyXml = Get-Content -Path $ConfigPath -Raw
$VerifyXml.configuration.MRSConfiguration |
    Select-Object MaxActiveMovesPerSourceMDB, MaxActiveMovesPerTargetMDB, MaxActiveMovesPerSourceServer, MaxActiveMovesPerTargetServer, MaxTotalRequestsPerMRS
Editing MSExchangeMailboxReplication.exe.config

Method 2: What If Moves Still Show StalledDueToTarget_MdbReplication?

In Exchange 2016, 2019, and Exchange Server SE, even after increasing MaxActiveMovesPerTargetMDB, Resource Health Manager (WLM) may temporarily pause moves with StalledDueToTarget_MdbReplication if DAG log shipping (CopyQueueLength or ReplayQueueLength) lags behind during heavy write bursts.

To bypass resource health throttling for an urgent maintenance window or VIP mailbox migration:

  1. Pass -Priority Emergency on your New-MoveRequest or Set-MoveRequest command:
POWERSHELL
# Bypass WLM resource health throttling for critical mailbox moves
Get-MoveRequest -MoveStatus InProgress | Set-MoveRequest -Priority Emergency
  1. Remember that Cumulative Updates (CUs) overwrite MSExchangeMailboxReplication.exe.config, so re-run the PowerShell script above after installing any Exchange CU!