locked
Enable-RemoteMailbox for Shared Mailboxes Problem RRS feed

  • Question

  • In an Exchange 2016 Hybrid environment I am trying to enable an on-prem user object as a Shared mailbox.  

    Couple of environmental things:

    1) Powershell session is being established with an on-prem Hybrid server without issue.

    2) Creds I am running the script with can successfully perform a "regular" Enable-RemoteMailbox on an on-prem user object

    3) $WorkingDC contains a valid FQDN for a local domain controller.  I am adding this in here because this code is part of a larger automation / provision process for users and I need to make sure that DC focus is consistent.

    4) The user object exists in the on-prem AD.

    Here's the code I am using:

    Enable-RemoteMailbox -Shared -Identity "Shared, Marlin" -Alias MShared -DisplayName "Shared, Marlin" -RemoteRoutingAddress 'MShared@mycustomer.mail.onmicrosoft.com' -PrimarySmtpAddress 'MShared@mycustomer.org' -DomainController $WorkingDC

    It fails with a message telling me that the "-Shared" switch is invalid.


    <o:p></o:p>

    Thursday, January 16, 2020 2:58 PM

Answers

  • Hi,

    Is there any update about your issue? What's the server version your customer using?

    We can see the usage about the parameter -shared from the document:

    Note: This switch is available only in Exchange 2013 CU21 or later and Exchange 2016 CU10 or later. To use this switch, you also need to run setup.exe /PrepareAD. For more information, see KB4133605.

    The Shared switch specifies that the mailbox in the service should be created as a shared mailbox. You don't need to specify a value with this switch.

    And in the KB mentioned that:

    Exchange Server 2016

    To enable the parameter -shared so that it will work, make sure that you prepare Active Directory by running the following command:

    <path_to_Exchange2016CU10_or_LaterBuild>\setup.exe /PrepareAD /OrganizationName:”first_organization_name” /IAcceptExchangeServerLicenseTerms

    And install the same build of Cumulative Update 10 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.

    Regards,

    Joyce Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Friday, January 17, 2020 5:26 AM

All replies