Powershell Script - Move Mailbox on-premise to Exchange Online not working

Question

Hi All,

I'm trying to use the powershell script provided here: https://www.adaxes.com/script-repository/move-mailbox-tofrom-microsoft-365-s579.htm

Unfortuntately when executing the script I get this error:

I have enabled exchange tracing and pulled this error from the log:

[07/31/2023 14:39:01] New-MoveRequest -Identity "3d65d95b-3114-4bd4-bde0-c85a96ec545b" -BadItemLimit "10" -Remote "True" -RemoteHostName "redacted" -TargetDeliveryDomain "redacted"

[07/31/2023 14:39:01] 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)

Pulling the command and running it in Exchange Powershell I get a similar error:

This appears to be due to credentials, but I am unsure how to overcome it in Adaxes. I can perform moves indepednently in my exchange on prem but I have to add -RemoteCredential(Get-Credential) then provide my exchange on prem credentials.

The adaxes service account already has these credentials but I do not know why this error is happening.

Thanks in advance

Answer 1

Hello,

Do we understand correctly that the corresponding AD domain is registered in Adaxes using option Adaxes service account? For information on how to check that, see https://www.adaxes.com/help/ChangeManagedDomainServiceAccount.

If that is correct, use option This account. You can specify the credentials of the Adaxes service account, but it has to be done explicitly. This is a known issue with Exchange move requests and it is related to the way authentication is handled.

Comments

The Domain is registered, however our setup is a little unique perhaps.

Our domain is abc.org in Azure however on premise we are abc.def.org where the primary domain is a subdomain of another domain on premise.

In Adaxes we have the abc.def.org registered, and exchange exists in the forest of def.org, would this imply I need to use credentials of def.org? The service account is located in the child domain but has all the appropriate rights in Exchange and with using the -RemoteCredential option in powershell I am able to use my account or the service account without issue, the issue only happens in Adaxes.

---

Hello,

Thank you for the provided details. Per your description the Adaxes service account should work just fine no matter where you make the request. It is only that you need to explicitly specify the credentials for the domain in Adaxes using option This account like we mentioned in the previous post. Once done, the script should work just fine.

---

Thanks for the quick responses,

I did try this last night but just to be safe I tried it again and it still does not work:

The Service Account is a memberOf Organizational Management and Recipient Management, I also re-tested by using the New-MoveRequest cmdlet and once I add -RemoteCredential it works but I still cannot get this to work in Adaxes itself.

Is there anything else I can do?

---

Hello,

For troubleshooting purposes, please, provide us with the following:

1. The version of Adaxes you are currently using. For information on how to check it, have a look at the following help article: https://www.adaxes.com/help/CheckServiceVersion.
2. The full script you are using in TXT format.
3. A screenshot of the Service Account dialog (like the one in our initial post) for the corresponding domain.

Also, please, enable tracing of requests sent to Exchange servers, reproduce the issue and send us (support@adaxes.com) the log file. For information on how to enable the tracing, have a look at the following help article: https://www.adaxes.com/help/EnableExchangeRequestLogging.

---

Actually, I was just able to get this to work with the service account instructions you mentioned initially, how I got this to work was I switched it back to "Adaxes service account", rebooted, then switched it back to "This Account" and rebooted again.

I'm not sure if the reboots did anything but switching it over again has resolved the issue: