Transport Basics in Exchange Server 2010 and 2013

In this blog we will be discussing on some of the basics of mail flow troubleshooting which will help to get started with while troubleshooting transport related issues in both Exchange Server 2010 and 2013. Although there are many architectural changes in Exchange Server 2013, however some of the power shell commands are same with little different output.

Lets Explore

Figure 1: Test-Mailflow 2010

In figure 1 the command was executed on Exchange Server 2010 box.

Figure 2: Test-Mailflow 2013

In figure 2 the command was executed on Exchange Server 2013 box which is almost same.

In both version a test email is sent to the user from a system mailbox as shown below.

Figure 3: Probe message

In figure 3 if the user receives the test message then it proves that the internal transport components are working fine.

As a best practices it is also advisable to confirm SMTP connectivity. To do that we can just run the simple commands to get the health of the SMTP Protocol.

Figure 4: Test-SmtpConnectivity in 2010

Figure 5: Test-SmtpConnectivity in 2013

There is a vast difference in SmtpConnectivity as shown in Figure 4 and 5. All StatusCode must show as Success.

To know more on Exchange Server 2013 Mailflow. Please read the excellent article written by Richard Schwendiman in Exchange 2013 Mail Flow Demystified…Hopefully!



Tagged , , , , . Bookmark the permalink.

One Response to Transport Basics in Exchange Server 2010 and 2013

  1. CH says:

    We have exchange 2013 HA environment (2 CAS and 2 MBX).
    i would like to know if the command test-smtpconnectivity can be run from any server to any server?
    for example can i run the command from MBx1 and provide it with MBx2 as the identity parameter?
    Also can we run it from the CAS servers?