Forum Discussion
Searching email not working on both Outlook Desktop and O365 web based mail
It made no sense to me that both Outlook desktop search and Outlook web search were broken. The two are different. One using Windows and one using the web services.
One thing did connect them. The mailbox. Potentially the mailbox was broken in some form. I decided to move the mailbox between servers with the new-moverequest cmdlet. After waiting a while for it to complete the user could suddenly use both searches.
I don't have a full explanation for this just that it was a way for me to make sure that the problem wasn't on the database on O365 in an easy way without raising a Microsoft incident.
This is really just to document this worked because I don't like going to forums where how it was fixed is not documented.
It made no sense to me that both Outlook desktop search and Outlook web search were broken. The two are different. One using Windows and one using the web services.
One thing did connect them. The mailbox. Potentially the mailbox was broken in some form. I decided to move the mailbox between servers with the new-moverequest cmdlet. After waiting a while for it to complete the user could suddenly use both searches.
I don't have a full explanation for this just that it was a way for me to make sure that the problem wasn't on the database on O365 in an easy way without raising a Microsoft incident.
This is really just to document this worked because I don't like going to forums where how it was fixed is not documented.
stephen_dxc122
How did you do that exactly? Officially it is not supported to move between cloud servers, what was the exact command line that you have used? I have the same problem, and did not want to include Microsoft, and it is really annoying, I can't find anything but this.Really appreciate your help!
Its supported.
New-MoveRequest (ExchangePowerShell) | Microsoft Docs
The difference is that on-prem you specify a destination for the mailbox. In the cloud the move request happens but to whatever server Microsoft choose.
You can validate the move afterwards by comparing the database name and the server has changed.
Thanks, I have given the the command without -TargetDatabase (because that is not even a parameter that exists), and it seems like it is doing something right now (if i check it with get-mailbox i can't see the change, but if i enter the command:
New-MoveRequest -Identity username@domain.com
Then I get the following error:
Mailbox 'username' is already being moved to 'EURP191DG002-db022'.
Where I can see the target database is different from the:
Get-Mailbox -Identity username@domain.com results.
I hope it works after it is done with the moving.
