Scope Send Connector In Exchange 2016

Environment Details:  

We have two active directory site and services  and have 4 Exchange 2016 servers ( 2 in each site ) with active-active model.  Each site have its own smart host appliance.  I have concluded the environment below.

Two Active Directory sites
Two Exchange 2016 servers in each site ( total 4 in DAG)
Smart Host appliance on Each site.

Questions:  

1. What is best practive to create send connector in above mentioned scenario?

2. Should we need to create two separate send connectors by selecting scope send conntor option and need to assign IP of its respective smart host.
scope-send-connector.PNG
I mean send connector A created for site A and then need to point it to Smart Host appliance IP which is located in Site A and vice versa for send connector and site B.
LVL 2
Muhammad AsifSenior Solutions ArchitectAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jason CrawfordTransport NinjaCommented:
That's exactly right as confirmed by this technet article:

https://msdn.microsoft.com/en-us/library/aa998662(v=exchg.160).aspx

Send connector scope

The source servers for a Send connector determine the destination Exchange server for mail that needs to be routed through the Send connector. The Send connector scope controls the visibility of the connector within the Exchange organization.

By default, Send connectors are visible to all the Exchange servers in the entire Active Directory forest, and are used in routing decisions. However, you can limit the scope of a Send connector so that it's only visible to other Exchange servers in the same Active Directory site. The Send connector is invisible to Exchange servers in other Active Directory sites, and isn't used in their routing decisions. A Send connector that's restricted in this way is said to be scoped.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
Hi Jason,

Thanks for sharing the details. I have already gone through the article mentioned by you.  So for what I have understand that I have to create one send connector  for site A and then need to add site A Exchange servers as soruce servers in senc connector and need to do same for site B.

source-server.PNG
Now these source servers will determine the only Site A Exchange server (Any Site A Exchange server whether it is added as source in send connector or not ) can be selected for mail that needs to be routed through the send connector.

Please add your comments and I really apperciate if you can elaborate in more detail.

Because I am not sure how Excange servers in some specific site know that this specific send Connector they need to use?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.