Lesson 2: Monitoring Mail Flow Chapter 9 433 Retry, which would indicate that connectivity problems may be preventing next-hop delivery. You can resume a message or a message queue or manually retry a queue as appropriate. If this does not result in message delivery, further investigation of the message properties (described earlier in this lesson) may be required. The following command, entered by Kim Akers on a server in the Adatum Exchange organization, gets the message tracking reports for all email messages Jeff Hay has sent to Don Hall and displays a detailed message tracking report for each email message, without resolving display names: Search-MessageTrackingReport -Identity "Don Hall" -Sender "JeffHay@fabrikam .com" -ByPassDelegateChecking -DoNotResolve | ForEach-Object { Get-MessageTrackingReport -Identity $_.MessageTrackingReportID -DetailLevel Verbose -BypassDelegateChecking -DoNotResolve -RecipientPathFilter "DonHall@adatum.com" -ReportTemplate RecipientPath } MORE INFO GET-MESSAGETRACKINGREPORT AND SEARCH- MESSAGETRACKINGREPORT For more information about the Get-MessageTrackingReport cmdlet, see http://technet .microsoft.com/en-us/library/dd351082.aspx. For more information about the Search- MessageTrackingReport cmdlet, see http://technet.microsoft.com/en-us/library/dd351138.aspx. Testing Mail Flow Exchange Server 2010 provides you with tools to test mail ow and resolve situations where email messages are not delivered. The EMC provides the Microsoft Exchange Mail Flow Troubleshooter as part of the Microsoft Exchange Troubleshooting Assistant, but the primary tool for resolving mail ow and resolving nondelivery situations is the EMS Test-Mailow cmdlet. You can use this cmdlet to diagnose whether mail can be successfully sent from and delivered to the system mailbox on a Mailbox server. You can also use it to verify that email is sent between Mailbox servers within a specied time (sometimes termed the latency threshold). The Test-Mailow cmdlet tests mail submission, transport, and delivery. It veries that each Mailbox server can successfully send itself a message. You can also use this cmdlet to verify that the system mailbox on one Mailbox server can successfully send a message to the system mailbox on another Mailbox server. The Test-Mailow cmdlet supports the AutoDiscoverTargetMailboxServer parameter. This species whether a command will automatically populate a list of target Mailbox servers to which a test message is sent. The task queries Active Directory Directory Services (AD DS) to discover all Mailbox servers and then sends each server a test message. You can use the TargetDatabase parameter to specify a target mailbox database to which messages are sent. You can also use the TargetEmailAddress parameter to specify a target email address when you want to send test messages to a Mailbox server in a remote forest. The TargetMailboxServer parameter species one or more Mailbox servers in the 434 Chapter 9 Monitoring Exchange Server 2010 local Exchange organization to which test messages are sent. If more than one of these parameters is specied, the AutoDiscoverTargetMailboxServer parameter takes precedence over the TargetEmailAddress and TargetMailboxServer parameters. The TargetMailboxServer parameter takes precedence over the TargetEmailAddress parameter. A system mailbox must be present on all servers involved in the test. Quick Check 1. You want to copy an email message into a text le so that you can view it, but you do not want to remove the message from its queue. You have suspended the message. What EMS cmdlet do you use to copy the message to a le? 2. What le extension should you use for a le into which you are copying an email message? Quick Check Answers 1. Export-Message 2. The .eml le extension. Several parameters specify time-outs. The ActiveDirectoryTimeout parameter species the number of seconds that elapse before the task provides an informational message about the delay. The default value is 15 seconds. The ErrorLatency parameter species the number of seconds that elapse before an error event is logged in Microsoft System Center Operations Manager 2007. The default value when a test message is sent to the local Mailbox server is 15 seconds. When a test message is sent to a remote Mailbox server, the default value is 180 seconds. The ExecutionTimeout parameter species the maximum time that the task can run before the test is determined to be a failure. If no test message or delivery report arrives before the execution time expires, the task ends, and an error is reported. When the task is run in the EMS, the default setting is 240 seconds. When you include the MonitoringContext parameter, which species that System Center Operations Manager 2007 is being used for server monitoring, the default setting is 15 seconds. MORE INFO SYSTEM CENTER OPERATIONS MANAGER 2007 For more information about System Center Operations Manager 2007, see http://technet .microsoft.com/en-us/library/bb687791.aspx#scop07. The Identity parameter species the source Mailbox server name or source mailbox SMTP address from which a test message is sent. The default value is the local Mailbox server. If you include the Conrm switch, this causes the command to pause and requires you to acknowledge that you want the task to proceed before processing continues. You do not specify a value with the Conrm switch. Lesson 2: Monitoring Mail Flow Chapter 9 435 The following command tests message ow from the Mailbox server VAN-EX1 to the Mailbox server VAN-EX2: Test-Mailflow VAN-EX1 -TargetMailboxServer VAN-EX2 The following command tests message ow from the server VAN-EX1 to the email address DonHall@adatum.com: Test-Mailflow VAN-EX1 -TargetEmailAddress DonHall@adatum.com Figure 9-22 shows that this test was successful. FIGURE 9-22 A successful mail flow test MORE INFO TEST-MAILFLOW For more information about the Test-Mailow cmdlet, see http://technet.microsoft.com/ en-us/library/aa995894.aspx. Back Pressure B ack pressure is a system resource monitoring feature of the Microsoft Exchange Transport service that exists on Hub Transport and Edge Transport servers. System resources such as available hard disk drive space and available memory are monitored. If utilization of a system resource exceeds its specied limit, the Exchange server stops accepting new connections and messages. This prevents the system resources from being completely overwhelmed and enables the server to deliver the existing messages. When utilization of the system resource returns to a normal level, the Exchange server accepts new connections and messages. The following system resources are monitored as part of the back-pressure feature: n Free space on the hard disk drive that stores the message queue database n Free space on the hard disk drive that stores the message queue database transaction logs n The number of uncommitted message queue database transactions that exist in memory n The memory that is used by the EdgeTransport.exe process n The memory that is used by all processes 436 Chapter 9 Monitoring Exchange Server 2010 For each monitored system resource on a Hub Transport server or Edge Transport server, the following three levels of resource utilization are applied: n Normal The resource is not overused. The server accepts new connections and messages. n Medium The resource is slightly overused. Back pressure is applied to the server in a limited manner. Mail from senders in the authoritative domain can ow. However, the server rejects new connections and messages from other sources. n High The resource is severely overused. Full back pressure is applied. All message ow stops, and the server rejects all new connections and messages. Conguration options for back pressure are available in the EdgeTransport.exe .cong application conguration le that is located in the C:\Program Files\ Microsoft\Exchange Server\V14\Bin directory. The EdgeTransport.exe.cong le is an XML application conguration le that is associated with the EdgeTransport.exe le. EdgeTransport.exe and MSExchangeTransport.exe are executable les located in the same directory that are used by the Microsoft Exchange Transport service. This service runs on every Hub Transport or Edge Transport server. Changes that are saved to the EdgeTransport.exe.cong le are applied after the Microsoft Exchange Transport service is restarted. However, Microsoft strongly discourages modifying the back-pressure settings in the EdgeTransport.exe.cong le because such modication may result in poor performance or data loss. You should instead investigate and correct the root causes of any back-pressure events. In other words, nd out what resource is under pressure and why and take the appropriate action such as upgrading server hardware or moving tasks to another server. In general, events with event source MSExchangeTransport and event category Resource Manager that indicate problems due to excessive resource usage are regarded as back-pressure events. Scanning for Disconnected Mailboxes A connected mailbox requires that a mailbox object exists in the Exchange store and the corresponding user object exists and has Exchange properties in AD DS. A disconnected mailbox is a mailbox object in the Exchange store that is not connected to a user object in Active Directory. You can use the Disable-Mailbox EMS cmdlet to disconnect a mailbox and the Connect-Mailbox cmdlet to reconnect a disconnected mailbox to an AD DS user account. You can use the Remove-Mailbox cmdlet to disconnect a mailbox and remove the user object from AD DS. Using the Remove-Mailbox cmdlet permanently removes the mailbox object from the Exchange store. Under normal circumstances, a mailbox is marked as disconnected immediately after the Disable-Mailbox or Remove-Mailbox command completes. However, if you use the Disable-Mailbox cmdlet or the Remove-Mailbox cmdlet while the Microsoft Exchange Lesson 2: Monitoring Mail Flow Chapter 9 437 Information Store service is stopped or if a mailbox is disabled by external means other than the Disable-Mailbox cmdlet or the Remove-Mailbox cmdlet, it is possible that the disconnected mailbox is not marked as disconnected in AD DS, and this can lead to problems if email messages are sent to the user. In this situation, you can use the Clean-MailboxDatabase EMS cmdlet to scan a mailbox database for disconnected mailboxes that have not been marked as disconnected within AD DS. Commands based on this cmdlet also update the status of those mailboxes so that they are correctly marked as disconnected. For example, the following command scans the database Mailbox Database 1363123687 for disconnected mailboxes that are not marked as disconnected within AD DS and updates their status so that they are correctly marked as disconnected: Clean-MailboxDatabase –Identity "Mailbox Database 1363123687" MORE INFO CONNECTING, DISCONNECTING, AND REMOVING A MAILBOX For more information about the Connect-Mailbox cmdlet, see http://technet.microsoft .com/en-us/library/aa997878.aspx. For more information about the Disable-Mailbox cmdlet, see http://technet.microsoft.com/en-us/library/aa997210.aspx. For more information about the Remove-Mailbox cmdlet, see http://technet.microsoft.com/en-us/ library/aa995948.aspx. MORE INFO CLEAN-MAILBOXDATABASE For more information about the Clean-MailboxDatabase cmdlet, see http://technet .microsoft.com/en-us/library/bb124076.aspx. Lesson Summary n The EMS is the primary tool for conguring message tracking and tracking logs. You can use the EMC to perform some tasks, but its functionality is limited. n You can use Queue Viewer in the EMC to monitor or EMS commands to monitor, lter, and manage transport queues on a Hub Transport or Edge Transport server. n You can use Queue Viewer in the EMC to lter messages but the primary tool for managing messages and testing mail ow is the EMS. Lesson Review You can use the following questions to test your knowledge of the information in Lesson 2, “Monitoring Mail Flow.” The questions are also available on the companion CD if you prefer to review them in electronic form. NOTE ANSWERS Answers to these questions and explanations of why each answer choice is correct or incorrect are located in the “Answers” section at the end of the book. 438 Chapter 9 Monitoring Exchange Server 2010 1. You want to enable message tracking on the Mailbox server AdatumMail02. What EMS command do you use? A. Set-TransportServer –Identity AdatumMail02 -MessageTrackingLogEnabled:$false B. Set-MailboxServer –Identity AdatumMail02 -MessageTrackingLogEnabled:$false C. Set-TransportServer –Identity AdatumMail02 -MessageTrackingLogEnabled:$true D. Set-MailboxServer –Identity AdatumMail02 -MessageTrackingLogEnabled:$true 2. You want to change the maximum size of each message tracking log le on the Edge Transport server NY-Edge01 to 15 MB. What command do you enter in the EMS? A. Set-TransportServer –Identity NY-Edge01 -MessageTrackingLogMaxDirectorySize 15MB B. Set-TransportServer –Identity NY-Edge01 -MessageTrackingLogMaxFileSize 15MB C. Set-MailboxServer –Identity NY-Edge01 -MessageTrackingLogMaxDirectorySize 15MB D. Set-MailboxServer –Identity NY-Edge01 -MessageTrackingLogMaxFileSize 15MB 3. You want to display the number of messages in queues on an Edge Transport server in the Contoso.com domain that are bound for the BlueSkyAirlines.com domain. What command do you enter in the EMS? A. Get-Queue –Filter {NextHopDomain –eq “blueskyairlines.com”} B. Get-Queue -Filter {MessageCount -gt 50} C. Get-Queue –Filter {NextHopDomain –eq “adatum.com”} D. Get-Queue -Filter {MessageCount -ge 50} 4. You want to suspend all queues on a Hub Transport server that have a message count equal to or greater than 450 and have a status of Retry. The command should work immediately without requiring conrmation. What EMS command do you enter on the server? A. Suspend-Queue -Filter {MessageCount -ge 450 -and Status -eq “Retry”} B. Suspend-Queue -Filter {MessageCount -gt 450 -and Status -eq “Retry”} -Conrm:$False C. Suspend-Queue -Filter {MessageCount -ge 450 -and Status -eq “Active”} -Conrm:$False D. Suspend-Queue -Filter {MessageCount -ge 450 -and Status -eq “Retry”} -Conrm:$False 5. You want to test the message ow from the Mailbox server NY-EX1 to the Mailbox server NY-EX2. What command do you enter in the EMS? A. Test-Mailow NY-EX1 -TargetMailboxServer NY-EX2 B. Test-Mailow NY-EX2 -TargetMailboxServer NY-EX1 C. Test-Mailow NY-EX1 -TargetDatabase NY-EX2 D. Test-Mailow NY-EX1 -TargetEmailAddress NY-EX2 Lesson 3: Monitoring Exchange Connectivity Chapter 9 439 Lesson 3: Monitoring Exchange Connectivity This lesson looks at communication between the various server and client computers that make up an Exchange Server organization. Computers need to be correctly congured so that they can communicate with each other over IP networks and (unless your email requirements are fully internal) with external networks such as extranets or the Internet. Clients need to be able to connect to servers using the appropriate client protocols, and servers need to be able to communicate with each other. After this lesson, you will be able to: n Test and debug network connectivity. n Use the Telnet tool to test protocol connectivity over various ports and particularly SMTP and Extended Simple Mail Transfer Protocol (ESMTP) connectivity over port 25. n Test connectivity using the various client-to-server and server-to-server protocols that enable users to access and read email messages. n Test Microsoft Exchange Web Services (EWS), Microsoft Outlook Anywhere, and Microsoft Exchange ActiveSync operation. Estimated lesson time: 40 minutes Debugging Network Connectivity The standard tools for troubleshooting network connectivity, such as Ping, Tracert, Nslookup, and Ipcong, are well known but sometimes do not provide the answers you are looking for, particularly on servers such as Windows Server 2008 and Windows Server 2008 R2, whose internal rewalls by default block the Internet Control Message Protocol Echo command. However, the main thrust of this lesson is the use of the Telnet tool and EMS cmdlets to obtain network connection information and to test connectivity over the various client-to-server and server-to-server protocols used to implement an Exchange Server 2010 organization. Using Telnet to Test SMTP Communication On client computers that have a Telnet client installed, you can use the Telnet tool to test connectivity for protocols dened by their port numbers. For example, opening a Telnet session and entering open VAN-EX1.contoso.com 25 tests connectivity to server VAN-EX1 .contoso.com on port 25, and if this connection can be made, the Telnet command ELHO tests that ESMTP connections can be made to that server. You can use the Telnet utility to connect to and verify the functionality of the SMTP service on an Edge Transport server and to test whether this server is able to receive email sent from other SMTP servers on the Internet. By default, SMTP listens on port 25. If you use Telnet on 440 Chapter 9 Monitoring Exchange Server 2010 port 25, you can enter the SMTP commands that are used to connect to an SMTP server and send a message exactly as if your Telnet session were an SMTP messaging server. However, before you use Telnet to test SMTP communication, you need to consider a number of factors. For example, message transfers that occur between Hub Transport servers are encrypted and authenticated by default. You can use Telnet on port 25 to submit messages only to an internal Hub Transport server that has a Receive connector congured to allow anonymous access or basic authentication. Anonymous access is required for Internet-facing servers. When you send a message to a Receive connector that accepts basic authentication, you must have a utility to convert the text strings that are used for the user name and password into the Base64 format. Chapter 7, “Routing and Transport Rules,” discusses Receive connectors. CAUTION BASIC AUTHENTICATION CAN BE A SECURITY RISK Because the user name and password are easily discernible when basic authentication is used, Microsoft recommends that you do not use basic authentication without encryption. Typically, Internet-facing SMTP messaging servers are congured to validate the source IP address, the corresponding Domain Name System (DNS) domain name, and the reverse-lookup IP address of any Internet host that tries to send a message to the server. If you connect a client computer to the Internet and try to send a test message to a remote messaging server by using Telnet on port 25, your message is likely to be rejected. In this case, you should connect to the remote messaging server from your Edge Transport server. The accepted domains that are congured on the Edge Transport server have the appropriate DNS mail exchanger (MX) records, address (A) records, and reverse-lookup records that identify the Edge Transport server as a legitimate and traceable email message source. You can use Telnet to connect to your organization’s Edge Transport server from a host that is located outside your perimeter network and send a test message. You can also use Telnet to connect to a remote messaging server from your organization’s Edge Transport server and send a test message. Note that the syntax of Telnet commands may differ depending on the third-party Telnet client you use. Remember that you cannot use the backspace key after you have connected to a destination SMTP server within the Telnet session. If you make a mistake as you type an SMTP command, you must press Enter and then type the command again. To use Telnet on port 25 to connect to a destination SMTP server, you must rst discover the fully qualied domain name (FQDN) or the IP address of the SMTP server. You can use the Nslookup command-line tool to nd the MX record for the destination domain and hence the address of the SMTP server by carrying out the following procedure: 1. On the computer you are using to run the Telnet session and to connect to a remote SMTP server on the Internet, right-click Command Prompt on the Accessories menu and click Run As Administrator. If you are not logged on with an Administrator-level account, you need to supply credentials. Lesson 3: Monitoring Exchange Connectivity Chapter 9 441 2. Enter the following command: nslookup 3. Enter the following command: set type=mx 4. Enter the following command: set timeout=20 NOTE DNS QUERY TIME-OUT By default, Windows DNS servers have a 15-second recursive DNS query time-out limit. 5. Enter the name of the domain for which you want to nd the MX record, followed by a trailing period. For example, to nd the MX record for the contoso.com domain, enter the following command: contoso.com. NOTE USING A TRAILING PERIOD The trailing period indicates a FQDN. The use of the trailing period prevents any default DNS sufxes congured for your network from being unintentionally added to the domain name. Note also that the domain must be reachable on the Internet and must contain at least one messaging server. 6. Obtain the FQDN and IP address for the server to which you want to connect. The portion of the command’s output that is of signicance to you should look similar to the following (note that the IP addresses will be public Internet addresses and not the private addresses shown here as an illustration): contoso.com mx preference=10, mail exchanger = mail1.contoso.com contoso.com mx preference=20, mail exchanger = mail2.contoso.com mail1.contoso.com internet address = 10.0.10.20 mail2 contoso.com internet address = 10.0.10.30 7. To end the Nslookup session, enter the following command: exit The above procedure discovers the FQDNs and IP addresses of messaging servers in an external Exchange organization reachable over the Internet. To nd the FQDNs of Hub Transport and Edge Transport servers within your internal Exchange Server 2010 organization, enter the following command in the EMS: Get-ExchangeServer | where {$_.isHubTransportServer -eq $true -or $_.isEdgeServer -eq $true} | FL Fqdn,ServerRole 442 Chapter 9 Monitoring Exchange Server 2010 Figure 9-23 shows the output from this command. FIGURE 9-23 Messaging servers in the adatum.com internal organization MORE INFO GET-EXCHANGESERVER For more information about the Get-ExchangeServer cmdlet, see http://technet.microsoft .com/en-us/library/bb123873.aspx. When you have obtained the FQDN of the target messaging server, you can use Telnet on port 25 to test SMTP communication (assuming that a Telnet client is installed in your source computer—remember that Microsoft Windows Vista and Microsoft Windows 7 client computers do not have a Telnet client installed by default). The procedure described below uses the following values: n Destination SMTP server mail01.contoso.com n Source domain adatum.com n Sender’s email address KimAkers@adatum.com n Recipient’s email address TerryAdams@contoso.com n Message subject Test from Adatum n Message body Test message To use Telnet on port 25 to test SMTP communication, carry out the following procedure: 1. On an Edge Transport server in the Adatum.com domain, open a command prompt by specifying Run As Administrator and enter the following command to open the Telnet session: telnet 2. Optionally, to view the characters as you type them, enter the following command: set localecho 3. Optionally, to enable logging of the Telnet session to the log le telnet.log, enter the following command: set logfile C:\Logfiles\telnet.log 4. To access the server mail01.contoso.com on port 25, enter the following command: open mail01.contoso.com 25 If access is successful, you receive a response similar to the following: 220 mail01.contoso.com Microsoft ESMTP MAIL Service ready at <day-date-time> [...]... -BasicAuthEnabled:$true -ExternalURL http://adatum.com /Microsoft- Server- ActiveSync The following example configures the Exchange ActiveSync virtual directory with Basic authentication: Set-ActiveSyncVirtualDirectory -Identity "adatum \microsoft- server- activesync" -BasicAuthEnabled:$true MORE INFO  SET-ACTIVESYNCVIRTUALDIRECTORY For more information about the Set-ActiveSyncVirtualDirectory cmdlet, see http://technet microsoft. com/en-us/library/bb12 367 9.aspx... -MailboxServer:VAN-CAS01 –ConnectionType:TLS B Test-PopConnectivity -ClientAccessServer:VAN-CAS01 –ConnectionType:TLS C Test-PopConnectivity -MailboxServer:VAN-CAS01 –ConnectionType:SSL D Test-PopConnectivity -ClientAccessServer:VAN-CAS01 –ConnectionType:SSL 4 Your organization provides email access to third-party email clients on TCP port 143 on the Client Access server NY-CAS01 Some clients are unable to retrieve... configure the Exchange ActiveSync virtual directory p ­ roperties For example, the following command configures the Exchange ActiveSync virtual Lesson 3: Monitoring Exchange Connectivity Chapter 9 455 directory with Basic authentication and an External URL of http://adatum.com/ Microsoft- Server- ActiveSync: Set-ActiveSyncVirtualDirectory -Identity "http://adatum /microsoft- server- activesync" -BasicAuthEnabled:$true... Monitoring Exchange Connectivity Chapter 9 453 FIGURE 9-2 8  Verifying Autodiscover settings MORE INFO  TEST-OUTLOOKWEBSERVICES For more information about the Test-OutlookWebServices cmdlet, see http://technet microsoft. com/en-us/library/bb124509.aspx Using Exchange Server ActiveSync Exchange Server ActiveSync is the messaging component of Exchange Server 2010 that relays messages to mobile devices Windows Server. .. mobile devices Windows Server 2008 and Windows Server 2008 R2 use Windows Mobile Device Center version 6. 1, which is a version of ActiveSync You can use the EMS to create a Microsoft Exchange ActiveSync virtual directory in M ­ icrosoft Exchange Server 2010 When Exchange server 2010 is installed, a new ­ ctiveSync A virtual directory named Microsoft- Server- ActiveSync is created in the default Internet... the following command: Get-MailboxStatistics –Database Research | FL Figure 9-3 2 shows some of the output from this command FIGURE 9-3 2  Statistics for the Research mailbox database 4 60 Chapter 9 Monitoring Exchange Server 2010 PR ACTICE C  onfiguring the Size and Age of Message Tracking Log Files on a Hub Transport and a Mailbox Server The Exchange Server 2010 server VAN-EX1 is configured with both... information for the local server: Get-NetworkConnectionInfo Figure 9-2 4 shows the output from this command Some of the fields on the Exchange Server 2010 server on your test network will return different information FIGURE 9-2 4  Connection information MORE INFO  GET-NETWORKCONNECTIONINFO For more information about the Get-NetworkConnectionInfo cmdlet, see http://technet microsoft. com/en-us/library/aa998845.aspx... ”: Set-CASMailbox -Identity: –Identity DonHall@adatum.com -ActiveSyncAllowedDeviceIDs: "","" MORE INFO  MANAGING EXCHANGE SERVER ACTIVESYNC For more information about managing Exchange Server ActiveSync, access http://technet microsoft. com/en-us/library/bb1243 96. aspx and follow the links MORE INFO  SET-CASMAILBOX For more information about the Set-CASMailbox cmdlet,... Mailbox server What EMS cmdlet enables you to do so? A Get-NetworkConnectionInfo B Test-WebServicesConnectivity C Test-OutlookWebServices D Set-ActiveSyncVirtualDirectory 3 You want to test POP3 connectivity over an SSL connection between the Client ­ ccess A server VAN-CAS01 and all mailboxes in your Exchange organization What EMS c ­ ommand do you use? A Test-PopConnectivity -MailboxServer:VAN-CAS01... server VAN-EX1: Test-ImapConnectivity -MailboxServer:VAN-EX1 | FL The following example tests IMAP4 connectivity from the Client Access server CAS01 to all mailboxes on all Mailbox servers on the local site: Test-ImapConnectivity -ClientAccessServer:CAS01 | FL The following example tests IMAP4 SSL-protected connectivity from the Client Access server CAS01 to all mailboxes on all Mailbox servers on the local . server? A. Suspend-Queue -Filter {MessageCount -ge 450 -and Status -eq “Retry”} B. Suspend-Queue -Filter {MessageCount -gt 450 -and Status -eq “Retry”} -Conrm:$False C. Suspend-Queue -Filter. Mailbox server NY-EX1 to the Mailbox server NY-EX2. What command do you enter in the EMS? A. Test-Mailow NY-EX1 -TargetMailboxServer NY-EX2 B. Test-Mailow NY-EX2 -TargetMailboxServer NY-EX1 . the EMS: Get-ExchangeServer | where {$_.isHubTransportServer -eq $true -or $_.isEdgeServer -eq $true} | FL Fqdn,ServerRole 442 Chapter 9 Monitoring Exchange Server 2010 Figure 9-2 3 shows the