There is a bug creating Frontend Transport Connectors from Exchange Administrative Center in Exchange 2016 CU2.
Currently it is not possible to select Hub Transport or Frontend Transport when creating a new connector as the option is greyed out.
In Exchange 2013, it is possible as shown below:
Microsoft are aware of this bug and will be fixing it in Exchange 2016 CU3.
Until this bug is fixed, you need to create Frontend Transport receive connectors from shell as follows:
New-ReceiveConnector -Name "Application Receive Connector" -Bindings ("0.0.0.0:25") -RemoteIPRanges ("10.1.10.10") -MaxMessageSize 50MB �TransportRole FrontendTransport -Usage Custom �Server Bentley-EXCH
Currently it is not possible to select Hub Transport or Frontend Transport when creating a new connector as the option is greyed out.
In Exchange 2013, it is possible as shown below:
Microsoft are aware of this bug and will be fixing it in Exchange 2016 CU3.
Until this bug is fixed, you need to create Frontend Transport receive connectors from shell as follows:
New-ReceiveConnector -Name "Application Receive Connector" -Bindings ("0.0.0.0:25") -RemoteIPRanges ("10.1.10.10") -MaxMessageSize 50MB �TransportRole FrontendTransport -Usage Custom �Server Bentley-EXCH
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon