Do i require send and receive connector for internal exchange, My exchange is not connected to outside world?
Do i need MX record internally?
Some of my applications use SMTP to send messages, my exchange 2013 will be of different ip.
How to solve this issue? Even if i give the same ip after the migration but the name of the server is different.
If any of the application is using server name?
do legacy host record pointing to old exchange will help me?
Hi ,
1.Do i require send and receive connector for internal exchange, My exchange is not connected to outside world?
Send connectors are used by exchange severs to send email to other exchange organisation and also emails to internet .Within the exchange organisation exchange uses intra-organisation send connector and it is implicit by default.
But all the receive connectors in exchange 2007 and exchange 2013 will be used frequently by exchange servers during the mail flow.
Note : My suggestion will be to leave the default send and receive connectors as it is.
2.Do i need MX record internally?
There is no need to have the MX records for the mail flow between the exchange 2007 and exchange 2013.
3.Some of my applications use SMTP to send messages, my exchange 2013 will be of different ip.
How to solve this issue? Even if i give the same ip after the migration but the name of the server
is different.
If any of the application is using server name?
do legacy host record pointing to old exchange will help me?
For all the above questions , my answer would be to do a message track on the exchange 2007 server to export the client ip details to the csv file and then remove the duplicated client ip address on the csv file so that we will get the consolidated output.Based on that we can able to know which of the application servers are sending emails via exchange sever .Based on the output ,the final step would be to ask the application team to reconfigure their smtp servers to exchange 2013 ip address to relay emails.
Another way is to enable the protocol logging on the receive connectors to find out the ip address of the application servers.
Note : I would not suggest you to add the exchange 2007 ip address as the additional ip address in exchange 2013 server.
thank alot
After decommissioning Exchange 2007 , i can assign that ip to exchange 2013. Will this solve the issue, and i will create another host record pointing to exchange 2007(i.e i will have two host records with same ip(exchange 2007 and exchange 2013). Will this work out.
Can you help me how to enable message track on exchange 2007 and exporting to csv.