Exchange 2010: Delivery Reports Architecture

Delivery Reports in Exchange Server 2010 enables both Information Workers, and administrators to view delivery status of messages and discover answers to questions such as: why a message wasn't delivered, where a message's now, who received a message, why a message was delivered to a particular folder, etc. This post dive a bit further into […]

Delivery Reports in Exchange Server 2010 enables both Information Workers, and administrators to view delivery status of messages and discover answers to questions such as: why a message wasn't delivered, where a message's now, who received a message, why a message was delivered to a particular folder, etc. This post dive a bit further into their architecture and how administrators can use them. “From an admin perspective DRs feature was designed to assist in quickly and easily answering questions users may’ve around why a message they were supposed to receive (or a message they sent) was not delivered. Unlike previous versions of Exchange which forced administrators to manually examine Message Tracking logs on multiple servers when troubleshooting missing (or delayed) messages, MT logs in Exchange 2010 are automatically index and by using DRs feature admins can quickly view a report which displays MT events from all servers a message passed through. There’re a number of ways Admins can access DRs feature, namely: EMC (from the Toolbox), ECP (from Options -> Reporting), or via PowerShell Tasks.”

Full Article: Exchange blog