You are the messaging engineer for your company. Your messaging system has both Microsoft Exchange Server 2003 servers and Exchange Server 2007 servers. You plan to enable message tracking on all Exchange servers. You need to instruct the administrators which tools to use to review the message tracking information. Which tools should you instruct the administrators to use? (Each correct answer presents part of the solution. Choose two)
A.
The Exchange Server 2003 management tools.
B.
The Exchange Server 2007 management tools.
C.
The Log Parser Resource Kit tool.
D.
The Winroute and MSGanalyzer tools.
Explanation:
EMC > Toolbox > Mail Flow Tools > Message Tracking…In Exchange 2003, message tracking, recording SMTP activity for all processed mail, is enabled on a per-server basis, using ESM. The resulting logs are useful for mail forensics, flow analysis, reporting, and troubleshooting. By default, theyre stored in Program Filesexchsrvr{servername}.log folder.
In Exchange 2007, message tracking is enabled by default on Mailbox and Transport servers, with logs stored in %Exchange Server%TransportRolesLogsMessageTracking. You must use the EM Shell to configure tracking:
Set-TransportServer <Identity> -MessageTrackingLogEnabled <$true | $false>
Set-MailboxServer <Identity> -MessageTrackingLogEnabled <$true | $false>
http://technet.microsoft.com/en-us/library/aa997984.aspx
http://www.msexchange.org/tutorials/Exchange-2007-Message-Tracking-Part2.html
Log parser is a powerful tool providing universal query access to text-based data, such as log, XML, and CSV files, as well as information sources, such as the Event Log, the Registry, the file system, and AD. You tell Log Parser what data you need and how you want it processed. Query results can be forma++ed in text output, or persisted to specialized targets like SQL, SYSLOG, or a chart.
Most software is designed to accomplish a limited number of specific tasks. Log Parser is different. How to use it is limited only by your needs and imagination. The world is your database with Log Parser.
http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&displaylang=en
The WinRoute tool connects to TCP Port 691 on a legacy Exchange server, and extracts the link state data for the organization. WinRoute presents this information in its original format.
http://support.microsoft.com/kb/281382
Message Tracking Logs contain lots of information about message flow. The MSGAnalyzer.exe tool can extract this to determine both End2End Message Delivery Latency and Server Latency. You can determine how much time it takes for Exchange to deliver a message, called End2End Message Delivery Latency. When a Hub server receives a message, it records the original arrival time, if this hasn’t been done yet. When the server delivers a message (via the Store Driver), it generates the DELIVER event, which also contains the original arrival time. The interval between these two times measures the End2End Message Delivery Latency. Tracking Logs can also determine how long it takes any server to transit a message, called Server Latency.
http://msexchangeteam.com/archive/2007/02/05/434194.aspx