none
Exchange 2013: Copy Receive Connectors

    Question

  • Hi,

    with Exchange 2010 and Michel de Rooij 's Script it was super easy to clone/copy Receive Connectors

    http://gallery.technet.microsoft.com/Copying-Receive-Connector-c7c107db

    http://eightwone.com/2012/08/23/copying-receive-connector-definitions/

    But for me this doesn't work any longer with Exchange 2013.

    Every time I try I do get the following error:

    The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive

    connector "SERVER1\Default Frontend SERVER1". Receive connectors assigned to different Transport roles
    on a single server must listen on unique local IP address & port bindings.
        + CategoryInfo          : InvalidOperation: (SERVER1... internal relay:ReceiveConnector) [New-ReceiveConne
       ctor], ReceiveConnectorRoleConflictException
        + FullyQualifiedErrorId : [Server=SERVER1,RequestId=e1b23d49-7115-4fda-8304-de1396fd6061,TimeStamp=03.07.2
       014 08:54:21] [FailureCategory=Cmdlet-ReceiveConnectorRoleConflictException] 7A9BB835,Microsoft.Exchange.Managemen
      t.SystemConfigurationTasks.NewReceiveConnector
        + PSComputerName        : server1.mydomain.com

    CAS and MBX are installed on the same machine.

    Does anyone have a working solution to copy Receive Connectors from one Exchange 2013 server to another?

    Thank you.

    Kind regards

    Carsten

    Thursday, July 3, 2014 10:57 AM

Answers

All replies

  • Hello,

    Have you tried this solution: http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/Powershell/copy-receive-connectors-new-exchange-server.html?

    Hope it helps,

    Adam


    www.codetwo.com

    If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

    Thursday, July 3, 2014 11:35 AM
  • Thanks,

    but when using it I do get:

    A parameter cannot be found that matches parameter name 'ExtendedProtectionTlsTerminatedAtProxy'.
        + CategoryInfo          : InvalidArgument: (:) [New-ReceiveConnector], ParameterBindingException
        + FullyQualifiedErrorId : NamedParameterNotFound,New-ReceiveConnector

    And when I remove

    -ExtendedProtectionTlsTerminatedAtProxy $_.ExtendedProtectionTlsTerminatedAtProxy

    from the script I get:

    The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive
    connector "SERVER1\Default Frontend SERVER1". Receive connectors assigned to different Transport roles
    on a single server must listen on unique local IP address & port bindings.
        + CategoryInfo          : InvalidOperation: (SERVER1... internal relay:ReceiveConnector) [New-ReceiveConne
       ctor], ReceiveConnectorRoleConflictException
        + FullyQualifiedErrorId : [Server=SERVER1,RequestId=e741a736-1de6-424c-aadb-de0e5f24ab17,TimeStamp=03.07.2
       014 11:50:59] [FailureCategory=Cmdlet-ReceiveConnectorRoleConflictException] 7A9BB835,Microsoft.Exchange.Managemen
      t.SystemConfigurationTasks.NewReceiveConnector
        + PSComputerName        : server1.domain.com


    Thursday, July 3, 2014 11:51 AM
  • Hi Carsten,

    According to the error message "Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings." , I find a similar thread for your reference:

    http://social.technet.microsoft.com/Forums/exchange/en-US/d0697f13-1ae8-48a0-9a69-ec08605568b5/failed-cu5-update-need-help-recovering?forum=exchangesvrdeploy

    Details:

    If I am sure that it is the cause then I would use ADSIEdit.msc or ADExploer.exe to modify the msExchangeReceiveBindings at Receive Connector Object in AD carefully... ;)

    Might be around, CN=Protocols,CN=ServerName,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExOrgName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=Com

     

    Thanks

    Mavis


    Mavis Huang
    TechNet Community Support

    Thursday, July 10, 2014 8:50 AM
    Moderator