Moving Mailbox to 365 Not working with script

Question

Ever since upgrading to 3.16.21906.0 the script here no longer works: https://www.adaxes.com/script-repository/move-mailbox-tofrom-microsoft-365-s579.htm

Not sure what the issue is as I can't find any errors in the log.

Comments

Hello,

What exactly do you mean by no longer works? Do you face any errors/warnings? If so, please, provide screenshots. Also, please, follow steps 1-4 from this article and provide us with a screenshot.

You can post the screenshots here or send to us at support@adaxes.com. Any additional details will be much appreciated.

---

I was noticing similar behavior in our environment and wanted to share what we found. I was attempting to use the same script to move a Shared mailbox from OnPremise to ExO M365. I enabled Exchange tracing in Adaxes. Running Adaxes 2023.2 version 3.16.21906.0 as well.

[01/10/2024 10:28:48] New-MoveRequest -Identity "3478596c-bb45-484f-9a47-e341dd6c88f8" -Remote "True" -RemoteHostName "XXXX.XXXX.com" -TargetDeliveryDomain "XXXXX.mail.onmicrosoft.com" [01/10/2024 10:28:59] System.Management.Automation.ParameterBindingException: Parameter set cannot be resolved using the specified named parameters. at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input) at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke) at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync) at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection1 input, PSDataCollection1 output, PSInvocationSettings settings) at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection1 input, PSDataCollection1 output, PSInvocationSettings settings) at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings) at #Dh.#Jh.#l.#5w.#VZc(RunspacePool runspacePool, PSCommand psCommand, String[]& warnings) at #Dh.#Jh.#l.#5w.Execute(#Gh command) at #Dh.#Fsf.Execute(#Gh command) at #ik.#hXe.Execute(#Gh command)

When I ran the new-moverequest command by itself on our on-premise Exchange 2016 server the error became more clear.

[PS] C:\Windows\system32>New-MoveRequest -Identity "3478596c-bb45-484f-9a47-e341dd6c88f8" -Remote "True" -RemoteHostName "XXXX.XXXX.com" -TargetDeliveryDomain "XXXX.mail.onmicrosoft.com" A positional parameter cannot be found that accepts argument 'True'.

• CategoryInfo : InvalidArgument: (:) [New-MoveRequest], ParameterBindingException
• FullyQualifiedErrorId : PositionalParameterNotFound,New-MoveRequest
• PSComputerName : XXXX-exch04.XXXX.com

So it appears the -Remote "true" is the extra positional parameter it did not like. If you remove "true" and just leave -Remote you get positive results, and the command gets farther.

I am still having issues on my end with the move requests because the GUID is not being found, and if i change it to the shared mailbox samAccountname it gets farther but then fails with

Target user 'sharedMailboxName' already has a primary mailbox.

That part may be entirely on my end. But I think the Remote part is what is causing the issue I saw and CurtisA saw as well.

---

Hello,

What you see in the tracing is not an issue and is not the actual command sent to exchange. It is just the way it has to be and works fine as per our check.

For troubelshooting purposes, please, follow steps 1-4 from this article and provide us with a screenshot. You can post the screenshot here or send to us at support@adaxes.com.