0

Error: A valid Migration mailbox could not be found for this organization

We like to migrate mailboxes in Exchange Admin Center. Only this time we do get an error: A valid Migration mailbox

When we try to migrate mailboxes in Exchange Admin Center. We get an error below

“error: A valid Migration mailbox could not be found for this organization”

Error

 It happens before the migration started in wizard. What’s going on? and what is the best solution?

Create a new migration batch and you will get the error: A valid Migration mailbox could not be found for this organization.

When we try in Exchange Management PowerShell, it shows the below error.

 
[PS] C:\>New-MigrationBatch -Local -Name "MigrationBatch-01" -CSVData ([System.IO.File]::ReadAllBytes("C:\migration\MigrationBatch-01.csv")) -TargetDatabases DataBase02 -BadItemLimit 10 -AutoStart -AutoComplete
A valid Migration mailbox could not be found for this organization.
    + CategoryInfo          : NotSpecified: (:) [], MigrationPartit...tFoundException
    + FullyQualifiedErrorId : [Server=EXCH-01,RequestId=153c6v19-f5e9-4f0d-a29a-8df7815959f8,TimeStamp=10/3/2022 5:1
   0:38 PM] [FailureCategory=Cmdlet-MigrationPartitionMailboxNotFoundException] C530F54C
    + PSComputerName        : EXCH-01-mycompany.local

Why the error?

When we want to migrate / move mailboxes within Exchange Admin Center or with the command the New-MigrationBatch, it requires the Migration mailbox. Now that the mailbox Migration is invalid, corrupted, or may be removed from Active Directory, it won’t work. The Migration mailbox which is an built-in mailbox is one of the arbitration mailboxes.

Solution:

To address this error, we will do:

  1. Delete Migration mailbox in Active Directory Users (if exists)
  2. Recreate Migration mailbox by using /PrepareAD command
  3. Enable Migration mailbox from Microsoft Exchange Management Shell

  • Delete Migration mailbox in Active Directory Users (if exists)
  • Usually this user places in users OU, otherwise we can search it from domain OU, Now remove it.

    We must have verify in Exchange Management Shell if the Migration mailbox is present. If it shows up in the output, that mean it’s present and activated. The output may be empty.

     
    [PS] C:\>Set-ADServerSettings -ViewEntireForest $true; Get-Mailbox -Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration | Format-Table Name, ServerName, Database, AdminDisplayVersion, ProhibitSendQuota
    
    • Recreate Migration mailbox by using /PrepareAD command

    Now we have to Run Command Prompt as administrator and execute the command

    I:\Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareAD.

    The command will recreate the Migration mailbox.

    Open Active Directory users and computers and click the refresh button in the toolbar or press F5. If that doesn’t work, close and reopen ADUC. Verify that the PrepareAD setup created the Migration mailbox in console or not.

    Open Exchange Management Shell as administrator. Run the command to display Migration mailbox. The results are empty, but why is that? That’s because we have to enable the mailbox.

     
    [PS] C:\>Set-ADServerSettings -ViewEntireForest $true; Get-Mailbox -Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration | Format-Table Name, ServerName, Database, AdminDisplayVersion, ProhibitSendQuota
    

  • Enable Migration mailbox from Microsoft Exchange Management Shell
  •  
    [PS] C:\>Enable-Mailbox -Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration
    
    Name                      Alias                ServerName       ProhibitSendQuota
    ----                      -----                ----------       -----------------
    Migration.8f3e7716-201... Migration.8f3e771... ex01-2016        Unlimited
    
    
    [PS] C:\>Set-Mailbox -Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration -Management $true -ProhibitSendQuota 300MB -Force
    
     
    [PS] C:\>Set-ADServerSettings -ViewEntireForest $true; Get-Mailbox -Identity "Migration.8f3e7716-2011-43e4-96b1-aba62d229136" -Arbitration | Format-Table Name, ServerName, Database, AdminDisplayVersion, ProhibitSendQuota
    
    Name                                           ServerName Database AdminDisplayVersion         ProhibitSendQuota
    ----                                           ---------- -------- -------------------         -----------------
    Migration.8f3e7716-2011-43e4-96b1-aba62d229136 ex01-2016  DB01     Version 15.1 (Build 1979.3) 300 MB (314,572,800 bytes)
    

    The Migration mailbox is recreated and enabled. We can start the migration batch and move mailboxes. This time without the error that a valid migration couldn’t be found. Did it work for you?

    Conclusion

    In this article, we have learned the possible solution to the “error A valid Migration mailbox could not be found for this organization”. Find the Migration mailbox in Active Directory and delete it. then recreated and enabled the Migration mailbox. and finally, verified that the Migration Mailbox which was enabled. Now We are ready to migration of mailboxes smoothly.

    Donate! If you like this Article and saved your Day...
    BTC Addres:
    • Send only BTC to this deposit address.
    • Ensure the network is BNB Smart Chain (BEP20).

    Leave a Reply

    Your email address will not be published. Required fields are marked *




    Enter Captcha Here :