Error: Enable-RemoteMailbox with archive

Question

I've found that when I attempt to enable a remotemailbox (on-prem Exchange Management Shell then synchronized with AD Connect) I get the following error at the end of this post.  I've found that PowerShell intellesense doesn't include "Archive" as a possible command if "RemoteRoutingAddress" is included in the command... and then viceversa, if "Archive" is included in the command then "RemoteRoutingAddress" isn't available.  RemoteRoutingAddress is a required parameter.  What gives?  I noticed that the get-help info for this cmdlet gives an example of an Enable-RemoteMailbox command with both RemoteRoutingAddress and Archive parameters.  Running this on an Exchange 2016 CU2 system.   If I run the Enable-RemoteMailbox without the Archive parameter the RemoteMailbox is created successfully.  Then I can either go into EAC and enable the archive in the GUI or run Enable-RemoteMailbox again with only the Archive parameter.... success.    Why can't I run a single Enable-RemoteMailbox cmd with both RemoteRoutingAddress and Archive?

Enable-RemoteMailbox -Identity "@o365tenant.com" -Alias "meeee" -PrimarySmtpAddress "@o365tenant.com" -RemoteRoutingAddress "******@myTenant.onMicrosoft.com" -Archive

Enable-RemoteMailbox : Parameter set cannot be resolved using the specified named parameters.

At line:1 char:1

• Enable-RemoteMailbox -Identity "******@o365tenant.com" -Alias "meeee" - ...

    + CategoryInfo          : InvalidArgument: (:) [Enable-RemoteMailbox], ParameterBindingException

    + FullyQualifiedErrorId : AmbiguousParameterSet,Microsoft.Exchange.Management.RecipientTasks.EnableRemoteMailbox

Answer 1

Hi Me_5555,

Thanks for your information.

I have reported it to our related team and you can also submit your feedback via clicking “Is this page helpful?” button on the Enable-RemoteMailbox command page (at the bottom). Given the situation, please use the workaround as I mentioned above. Your time is highly appreciated.

Best Regards,

Erick

Answer 2

Hi Me_5555,

I have tried the PowerShell command and get the same errors. I will consult our related team about it. Given the situation, we suggest you use the workaround as you mentioned (run these commands separately). If there is any update, I will post it here.

Your understanding is highly appreciated.

Best Regards,

Erick