Albert Widjaja
asked on
Exchange 2013: Send Connector Source type modification ?
People,
Can anyone here please assist me with adding all of my Exchange 2013 CAS server roles from the same AD domain to the Source Server below:
From the picture above, there is just one old CAS server that I will be decommissioned PRODEXC14, so can I add PRODEXC42 and PRODEXC01-VM to give more resiliency in case one of the exchange servers is rebooted or shut down for maintenance ?
Here’s my Exchange Server deployment in the Single AD forest domain:
Is my assumption correct to allow outbound email flow resiliency with adding the remaining CAS (Transport Service enabled) servers to the Source Server lists ?
I hope there is no need for reboot or restart after adding the additional servers above.
Can anyone here please assist me with adding all of my Exchange 2013 CAS server roles from the same AD domain to the Source Server below:
From the picture above, there is just one old CAS server that I will be decommissioned PRODEXC14, so can I add PRODEXC42 and PRODEXC01-VM to give more resiliency in case one of the exchange servers is rebooted or shut down for maintenance ?
Here’s my Exchange Server deployment in the Single AD forest domain:
Name Site ServerRole Edition AdminDisplayVersion
---- ---- ---------- ------- -------------------
PRODEXC14 Domain.com/Configuration/Sites/Default-First-Site-Name Mailbox, ClientAccess Standard Version 15.0 (Build 1130.7)
PRODEXC42 Domain.com/Configuration/Sites/HQ Mailbox, ClientAccess Standard Version 15.0 (Build 847.32)
PRODMAIL1-VM Domain.com/Configuration/Sites/SiteOffice Mailbox Standard Version 15.0 (Build 847.32)
PRODEXC01-VM Domain.com/Configuration/Sites/Default-First-Site-Name Mailbox, ClientAccess Standard Version 15.0 (Build 847.32)
PRODEXC43-VM Domain.com/Configuration/Sites/HQ Mailbox Standard Version 15.0 (Build 847.32)
PRODMAIL2-VM Domain.com/Configuration/Sites/SiteOffice Mailbox Standard Version 15.0 (Build 847.32)
Is my assumption correct to allow outbound email flow resiliency with adding the remaining CAS (Transport Service enabled) servers to the Source Server lists ?
I hope there is no need for reboot or restart after adding the additional servers above.
CAS servers are just working as proxy for transmitting the e-mails, they don't work as SMTP routing. You can add Mailbox servers along CAS server as a source server in send connector. But make sure if you are adding all of them then respective servers must have connectivity to next hop either next gateway or DNS resolution access (May be internet)
ASKER
ok, so how do I test that ?
The next device to filter the emails are the two Linux appliances (Anti-Spam). As I can see the IP address in the Smart Hosts.
So assuming, I can telnet to the list of IP addresses under the Smart Host, does it means I can safely add them all not just with Mailbox, ClientAccess roles ?
The next device to filter the emails are the two Linux appliances (Anti-Spam). As I can see the IP address in the Smart Hosts.
So assuming, I can telnet to the list of IP addresses under the Smart Host, does it means I can safely add them all not just with Mailbox, ClientAccess roles ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, so under my single Send Connector, if I add multiple Exchange Servers in the Source Server, would I get more email resilliency?
Suggestion is given and solution must work