Hello!
As you may have seen from the Microsoft 365 roadmap item, the O365 migration team has been working on improvements to the way we detect inconsistencies or data loss during migrations or move...
Updated Dec 21, 2020
Version 3.0
Blog Post
I noticed a bug with this feature DCS. You can recreate it like this:
- Create a new batch, say onboarding mailboxes in a Hybrid deployment, and set Bad Item Limit to something (let's say 10), and leave Large Item Limit blank.
- Next, in EXO PowerShell change the move requests' Large Item Limits to something other than 0, let's say 10 again.
- If there are large items, the large item limit will be ignored and the move will fail.
- You'll see this in the Get-MoveRequestStatistics: LargeItemLimt 10
- And this won't matter it will just be ignored.
I'm testing the solution of also updating the migration batch in the GUI with the new Large Item Limit value. But it's strange that I would need to when other overrides like -CompleteAfter still work just fine via Set-MoveRequest.