Forum Discussion
NetSysEngMN
Mar 13, 2021Brass Contributor
Exchange 2010 to Exchange Online Public Folder Migration Failed
Looking for any advice on an issue that I am facing. Currently in process of migrating from Exchange 2010 to Exchange Online and everything has gone relatively well up to this point. I have successfu...
- Mar 19, 2021Support got back to me and said this error can happen if the Public Folder name and the Display Name do not match. To check the names in PowerShell: Get-Mailbox -PublicFolder Mailbox1 | fl name,displayname
If mismatched (like mine are), I wrote the following PowerShell script to rename all of the public folder mailboxes to match the display name. If you only have a couple of mailboxes you could also just rename them in the EAC.
# Connect to EXO
$Credential = Get-Credential
Connect-ExchangeOnline -Credential $credential -ShowProgress $true
# Get all public folders
$PFM = Get-Mailbox -PublicFolder | Select-Object Name,DisplayName
# Loop through each public folder
ForEach ($M in $PFM){
# Define the mailbox display name
$MBDN = $M.DisplayName
# Define the mailbox name
$MBN = $M.Name
# Compare the name vs. display name
If ($MBN -ne $MBDN){
Write-Host "Name mismatch! Updating $MBDN now." -ForegroundColor Yellow
# Rename the mailbox to match the display name
Set-Mailbox -PublicFolder $MBDN -Name $MBDN
}
ElseIf ($MBN -eq $MBDN){ Write-Host "$MBDN is set correctly." -ForegroundColor Green}
}
I'm sure there is better/more efficient code but that worked for me. After the mailboxes have been renamed, try resuming the failed mailboxes and see if they start syncing as expected. In my case (still monitoring it) they at least did not fail right away so I believe it's working but only time will tell.
MDadarkar
Mar 15, 2021Brass Contributor
Hi NetSysEngMN ,
If you need to move your public folders to Exchange Online but your on-premises servers aren't running the minimum support versions of Exchange 2010 (minimum SP3 + RU8), Microsoft strongly recommends that you upgrade your on-premises servers and use batch migration, which is the only supported public folder migration method.
Please go through with the below link.
Thank you,
Regards,
MD
please do like and share this post, if my answer resolved your issue..
- NetSysEngMNMar 15, 2021Brass ContributorThanks for your response MDadarkar,
I am running a support version of Exchange 2010 and I am already following the batch migration process as I mentioned (and linked) in my original post.- Patdu31Mar 16, 2021Copper Contributor
NetSysEngMN You are not alone, I've the same behavior... 😞
- Patdu31Mar 16, 2021Copper ContributorOn the EAC, the 3 mailboxes are in status Failed with the same error:
Error: MigrationMailboxNotFoundException: Organization migration mailbox not found or invalid
(exact french error: La boîte aux lettres de migration de l‎'organisation est manquante ou non valide.)
This error can occur when environment is Exchange 2013 and Migration.8f3e7716-2011-43e4-96b1-aba62d229136 arbitration mailbox is missing.
But my environment is Exchange 2010 (only one server).
MigrationEndPoint is validated: I try to changed the password with a wrong password= error, when a set the right password the config is OK.
When I start the migrationbatch, I don't see that Office365 is trying to connect to my onprem server.
Maybe this behavior is on Exchange Online side after a config change on their side?
Thank you for you help.