Setting source server priority in Send Connector

Question

Hi,

I've configured DAG with two Exchange Server 2016, whenever I add secondary server to Send Connector mails are getting routed through secondary server instead of primary where mailbox databases are activated, for now I've removed secondary server from connector, is it default behaviour of Send Connector? or we can set priority on source servers?

Any suggestion will be appreciated.

Answer 1

Ok, in that case, your source server will have to remain 16A and you will need to manually add or remove source servers if the network situation changes. There is no way to prioritize the source servers other than not adding the ones you dont want to use if these are in the same AD site/DAG

Answer 2

Why the need for the secondary connector? By default they are scoped to the entire org so any server can use it, yes.
If you want to scope to an AD site, check this option:

https://learn.microsoft.com/en-us/exchange/mail-flow/connectors/internet-mail-send-connectors?view=exchserver-2019

Answer 3

Hi Andy,

Thanks for your response, I'm not talking about multiple send connectors, i'm talking about single send connector having multiple source servers...

Answer 4

Ah, ok, sorry, need more coffee!
Yes, that is expected as well. The servers are really peers in that respect because of two factors:

1. The DAG is the transport boundary: https://learn.microsoft.com/en-us/exchange/mail-flow/transport-high-availability/transport-high-availability?view=exchserver-2019
2. Shadow redundancy ensures a copy is made of every message: https://learn.microsoft.com/en-us/exchange/mail-flow/transport-high-availability/shadow-redundancy?view=exchserver-2019 So, I guess the question is, why the need to ensure they only go out where the databases are mounted since the DBs could be mounted on any server at some point?

Answer 5

a

• reason is that WAN interface is not enabled on EXCH16B , only EXCH16A have internet access....