You are the Exchange administrator for your company. The company operates two offices.
The Exchange organization contains eight servers that run Exchange Server 2003. Each office contains four Exchange servers. Each office is configured as a routing group.
The routing groups are connected by a routing group connector. In each office, one Exchange server is configured as a bridgehead server.
Each bridgehead server is configured with two SMTP virtual servers. One SMTP virtual server is configured as the bridgehead server for the SMTP connector for email messages sent to and from the Internet.
The other SMTP virtual server is configured as the bridgehead server for the routing group connector.
You need to ascertain the number and size of email messages sent between the two offices, and to and from the Internet, every day.
You need to specify the number of messages sent, the total size of messages sent, and the appropriate queue length on each server. You will use this data to plan for future growth.
How should you modify each bridgehead server?
A.
Configure a counter log to monitor both SMTP virtual servers.
B.
Configure a counter log to track all messages sent by the Microsoft Exchange MTA Stacks service.
C.
Configure SMTP logging on both SMTP virtual servers.
D.
Configure SMTP logging on the SMTP virtual server that sends and receives email messages to and from the Internet. Configure a counter log to track all messages sent between routing groups by the Microsoft Exchange MTA Stacks service.
Explanation:
Some may be think that configuring SMTP logging on both SMTP virtual servers will accomplishall necessary tasks. You can�t
accomplish all necessary tasks only using SMTP logging. Besides the Store.exe process, other processes that consume memory
(and may affect performance) include:
Inetinfo.exe Process that handles Internet protocols
Emsmta.exe Microsoft Exchange Message Transfer Agent (MTA) Stacks service
Mad.exe Microsoft Exchange System Attendant Microsoft Exchange MTA Stacks (MSExchangeMTA) maintain the link state
table between SMTP and the routing engine that is used to communicate link state information between routing groups and
throughout the organization Is supposed that this service is only needed for backwards compatibility, but is also used when mailbox
moves, or if there are X.400 connectors on the computer and for error handling of some messages The message transfer agent
(MTA) in Exchange now uses Gwart.dll to make a legacy compatible gateway address routing table (GWART). MTA uses
Mtaroute.dll as the connection between the legacy MTA and the Microsoft Exchange Routing Engine
Incorrect answers:
A. Configuring a counter log to monitor both SMTP servers is incorrect because it is vague. No mention of what counters are
needed or where to do the logging is named. In addition, it is unclear what is meant by �monitoring the servers�. Do they mean
the physical servers? SMTP virtual servers? This is not the best answer.
B. MTA stacks service will not help here. They can�t log items daily for review. The MTA Stacks service is only used for
compatibility between Exchange 5.5 and Exchange 200x servers. Since there are no Exchange 5.5 servers here, this counter is
not needed.
C. You can�t do it the entire required job just using SMTP logging,
Reference
An e-mail message is not delivered and an event ID 210 "content conversion failed" warning message is logged for the MTA in
Exchange Server 2003 KB 834570 The Microsoft Exchange MTA Stacks service cannot start in Exchange 2003 and event IDs 137
and 9405 appear in the application event log KB 840470 Microsoft Operations Manager Message Transfer Agent Rule Group