Managing the Hub Transport Server Role • Chapter 6 357 In order to launch the Message Tracking tool, perform the following steps: 1. Open the Exchange Management Console. 2. Select the Toolbox work center node. 3. Click the Message Tracking icon and select Open Tool in the Action pane. The tool will launch after a few seconds and look for any available updates. If updated, click Go to Welcome screen and you will be brought to the Message Tracking Parameters screen shown in Figure 6.32. Here you can check the different parameters you want to include in your search criteria. In this example, I have specifi ed to get a list of all messages sent to me between January 1 and January 30, 2007 from a specifi c e-mail address. When the relevant parameters have been checked and specifi ed, click Next. NOTE The Message Tracking directory, which is responsible for holding the message tracking log fi les, has a default size limit of 250 MB. Figure 6.32 The Message Tracking Parameters Page 358 Chapter 6 • Managing the Hub Transport Server Role The Message Tracking tool will now search for all messages matching the search criteria specifi ed on the previous screen, as shown in Figure 6.33. Here we get all sorts of information about the messages, and if we want to further fi lter our search, we can click Next and check or change any relevant parameters. Figure 6.33 List of Messages Included Based on Search Criteria TIP In order to use the message tracking feature to search for particular messages via the Exchange Management Shell, you can use the Get-MessageTrackingLog cmdlet. Managing the Hub Transport Server Role • Chapter 6 359 Using the Exchange 2007 Queue Viewer Typically, mail fl ow within the organization just simply works; however, as an Exchange administrator, one of your jobs is to regularly keep an eye on the message queues within the Exchange organization. This is where the Queue Viewer comes in. With the Queue Viewer, now an Exchange tool, and therefore located under the Toolbox work center node in the Exchange Management Console, you can view information about queues and examine the messages held within them. Exchange Server 2007 uses fi ve different types of queues, and the routing of a message determines the type of queue where a particular message is stored. In the following, I list the fi ve different queues types: Submission Queue The submission queue is a persistent queue used by the categorizer in order to gather the messages that need to be resolved, routed, and processed by Transport agents. Each message received by the categorizer is a component of Exchange transport and therefore processes all inbound messages as well as determines what to do with the messages based on information about the intended recipients. All messages received by a transport server enter processing in the Submission queue. Messages are submitted through SMTP-receive, the Pickup directory, or the store driver. The categorizer retrieves messages from this queue and, among other things, determines the location of the recipient and the route to that location. After categorization, the message is moved to a delivery queue or to the unreachable queue. Each Exchange 2007 transport server has only one Submission queue. Messages that are in the Submission queue cannot be in any other queues at the same time. Mailbox Delivery Queue The Mailbox Delivery queues hold messages that are being delivered to a mailbox server by using encrypted Exchange RPC. Mailbox Delivery queues exist on Hub Transport servers only. The Mailbox Delivery queue holds messages that are being delivered to mailbox recipients whose mailbox data is stored on a Mailbox server not located in the same site as the Hub Transport server. More than one mailbox delivery queue can exist on a Hub Transport server. The next hop for a Mailbox Delivery queue is the distinguished name of the mailbox store. Remote Delivery Queue Remote Delivery queues hold messages that are being delivered to a remote server using SMTP. Remote Delivery queues can exist on both Hub Transport servers and Edge Transport servers, and more than one Remote Delivery queue can exist on each server. Each Remote Delivery queue contains messages that are being routed to recipients that have the same delivery destination. On a Hub Transport server, these destinations are outside the Active Directory site in which the Hub Transport server is located. Remote Delivery queues are dynamically created when they are required 360 Chapter 6 • Managing the Hub Transport Server Role and are automatically deleted from the server when they no longer hold messages and the confi gurable expiration time has passed. By default, the queue is deleted three minutes after the last message has left the queue. The next hop for a Remote Delivery queue is an SMTP domain name, a smart host name or IP address, or an Active Directory site name. Poison Message Queue The Poison Message queue is a special queue used to isolate messages that are detected to be potentially harmful to the Exchange 2007 system after a server failure. Messages that contain errors potentially fatal to the Exchange Server system are delivered to the Poison Message queue. This queue is typically empty, and if no poison messages exist, the queue does not appear in the queue viewing interfaces. The Poison Message queue is always in a ready state. By default, all messages in this queue are suspended. The messages can be deleted if they are considered to be harmful to the system. In the event a message in the Poison Message queue is determined to be unrelated to the message itself, delivery of the message can be resumed. When delivery is resumed, the message enters the Submission queue. Unreachable Queue The Unreachable queue contains messages that cannot be routed to their destinations. Typically, an unreachable destination is caused by confi guration changes that have modifi ed the routing path for delivery. Regardless of the destination, all messages that have unreachable recipients reside in this queue. Each transport server can have only one Unreachable queue. When a message is received by transport, the mail item will be created and then saved into the queue database. TIP With Exchange Server 2007, message queues are stored in the ESE database unlike previous versions of Exchange, where the messages (.EML fi les) were stored in a queue folder in NTFS. As mail items are saved in the queue database, they are assigned a unique identifi er. If a particular mail item is routed or being sent to more than one recipient, the item can have more than one destination. Each destination represents a separate routing solution for the mail item, and each routing solution causes a routed mail item to be created. A message that is being sent to recipients in two different domains appears as two distinct messages in the delivery queues, even if only one transport mail item is in the database. Managing the Hub Transport Server Role • Chapter 6 361 To launch the Queue Viewer, perform the following steps: 1. Open the Exchange Management Console. 2. Click the Toolbox work center node. 3. Click the Queue Viewer icon, and then select Open Tool in the Action pane. If you have launched the Queue Viewer from a Hub Transport server, it will connect to the local queue by default. If you want to connect to a queue stored on another Hub Transport server, click Connect to Server in the Action pane (Figure 6.34). Figure 6.34 The Queue Viewer Tool From within the Queue Viewer, you can view queues and messages, as well as suspend and resume them. In addition, you can retry a queue or message, remove a queue or message completely, or export either of them so they can be transferred to another Hub Transport server for further delivery. . Message Tracking icon and select Open Tool in the Action pane. The tool will launch after a few seconds and look for any available updates. If updated, click Go to Welcome screen and you will be brought. of all messages sent to me between January 1 and January 30, 2007 from a specifi c e-mail address. When the relevant parameters have been checked and specifi ed, click Next. NOTE The Message. 6.33. Here we get all sorts of information about the messages, and if we want to further fi lter our search, we can click Next and check or change any relevant parameters. Figure 6.33 List of