I removed -whatif and find that the moves do queue up and are in progress. I’d still like to know why the pipeline error occurs.
]]>The input object cannot be bound to any parameters for the command either because the command does not take pipeline
input or the input and its properties do not match any of the parameters that take pipeline input.
+ CategoryInfo : InvalidArgument: (:PSObject) [New-MoveRequest], ParameterBindingException
+ FullyQualifiedErrorId : InputObjectNotBound,New-MoveRequest
Same technique should work.
]]>So even just the Get-Content cmdlet is failing? What’s the exact command you’re trying to run?
]]>Works fine for Exchange 2013 and I am actually running it from the new Exchange 2016
]]>To check the current migration status of the mailboxes you guys can run the following command.
Get-MoveRequestStatistics -MoveRequestQueue “target database name” (with the quotes)
This way you will be able to check the status of the move
]]>Each of these have one DB each DB001 & DB002
How can I use these commands to move a mailbox in DB001 on EX001 to DB002 on EX002.
In GUI, 4 mailboxes are moved at a time. Can we move 4 or 5 mailboxes using these cmdlet script.
]]>