Site feedback

JoshuaOjeyi avatar image
0 Votes"
JoshuaOjeyi suggested

No Resolution listed on Microsoft Docs for this Error gotten when trying to move a mailbox from On-Premise to Exchange Online

Error: User 'identity' has a demoted archive in the cloud. Onboarding and offboarding are not supported if a demoted archive is present in the cloud. Please use Set-MailUser -RemoveDisabledArchive or Set-Mailbox -RemoveDisabledArchive to remove it.

However, I discovered the thread below was posted/uploaded on 14/2/2022
Thread: https://docs.microsoft.com/en-us/exchange/troubleshoot/move-mailboxes/cannot-migrate-on-premises-primary-mailbox?source=docs

The steps I used in resolving the issue are almost similar to the steps provided in the thread above. I needed to confirm the resolution since there is no official documentation detailing the error and resolution. Just in case the issue comes up or another user experiences the issue, want to know if there is the best way around the issue, or the thread posted above can also be used to resolve the issue.


The following actions were performed to resolve the issue then:

  • Exported the Archive mailbox to PST

  • Disabled the Archive mailbox on-premise

Then got the error: Mailbox has move status 'none' and remote hostname. you can't enable or disable an archive while the mailbox is being moved

This problem occurs because failed move requests are not yet removed from the system.

Got the following explanation from Microsoft Docs

Connect to Exchange Online by using remote Windows PowerShell.
Verify that the mailbox is being moved. To do this, run the following command:
Get-MoveRequest | fl Status, Protect, "Display Name", Identity

If the "Display Name" placeholder matches the mailbox for which you want to disable archiving, a mailbox move is in progress. The move is preventing the change from being made.
Examine the output, and then do one of the following, as appropriate:
If the Status is Queued or InProgre, wait for the move to finish. This should occur in one or two days. If you can't wait that long, remove the move request by running the following command:
Remove-MoveRequest -Identity IdentityOfFailedRequest

If the Status is Failed, remove the move request by running the following command:
Remove-MoveRequest -Identity IdentityOfFailedRequest

This operation should not affect user access or cause any problems.

However, if the mailbox cannot be seen on the "Move Request" section or with the Get-MoveRequest command and cannot be cleared with the Remove-MoveRequest command.

  • Open ADSIEDIT and navigate to the OU where your broken user account is stored

  • Locate the user account, right-click on it and then choose "Properties".

  • Click on the "Filter" button and make sure "Show only attributes that have values" is checked.

  • Scroll down the attributes and search for entries called "msExchMailboxMoveRemoteHostName", "msExchMailboxMoveFlag", "msExchMailboxMoveStatus"

  • Click on the "Edit" button.

  • Click on the "Clear" button.

  • Click the "OK" button

  • After clearing the attributes on-premise, Perform an AADSync,

  • Try disabling the Archive and perform the move.

Kindly let me know if the information provided so far is clear enough and any further clarification is needed, I am ready to provide additional details.

Regards







office-exchange-hybrid-itprooffice-exchange-online-itpro
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

No Solutions

Your Opinion Counts

Share your feedback, or help out by voting for other people's feedback.