Forum Discussion
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...
- Support 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.
NetSysEngMN You are not alone, I've the same behavior... 😞
On 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.
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.
- Patdu31 I'm engaged with Microsoft support so I will let you know if it goes anywhere. To clarify a few points in my case - my on premise environment is running Exchange 2010, Version 14.3.513.0 (Update Rollup 32, SP3). All testing that I have done so far:
- Deleted the Public Folder endpoint and migration job and recreated them both
- Tested Outlook connectivity via. https://testconnectivity.microsoft.com/tests/exchange (all connections are successful)
- Tested the migration server availability using the “Test-MigrationServerAvailability -PublicFolder” PowerShell command. Full command used: “Test-MigrationServerAvailability -PublicFolder -RPCProxyServer $Source_OutlookAnywhereExternalHostName -Credentials $Source_Credential -SourceMailboxLegacyDN $Source_RemoteMailboxLegacyDN -PublicFolderDatabaseServerLegacyDN $Source_RemotePublicFolderServerLegacyDN –Authentication Ntlm (Variables used are the variables that are defined in step # 5 of the batch migration instructions)
- Confirmed I can still migrate user accounts from on-prem to EXO
- Confirmed arbitration mailboxes are present in the on-prem Exchange environment using the PowerShell command: Get-Mailbox –Arbitration
- Also as you mentioned – while looking at live traffic logs I do not see any connection attempt either (at first I thought maybe something was being blocked but that was quickly ruled out).
I am leaning toward either;
A) Public folder migrations are no longer supported coming from Exchange 2010 or
B) Something is wrong/misconfigured on the Exchange Online side looking for something that doesn't exist (such as a migration mailbox).
I am hoping there is a solution to migrate as is, otherwise I assume I may have to make a jump from Exchange 2010 to Exchange 2016 then to Exchange Online.
If the solution is no longer supported, I would assume Microsoft would need to take down the article saying it is still supported (the article was last updated about a month ago) and then I would be curious to know when that change was made.Thank you for your feed back.
I'm exactly in the same situation, same Exchange version SP3 RU32).
The test migration command runs successfully also:
RunspaceId : 9e45203b-0b80-xxxxxxxxx
Result : Success
Message :
SupportsCutover : False
ErrorDetail :
TestedEndpoint : mail.xxxxxx.com
IsValid : True
Identity :
ObjectState : NewAll users are migrated to Online and they waiting for public folder migration to uninstall onprem server....
So I will wait for your feedback about the case opened to Microsoft.
If answer is negative, the only option will be to migrate first to Exchange 2013/16 onprem and after to Online...
Patrick
