Journaling recipient points to the local server
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2007-01-09
The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine whether the value for the msExchHomeServerName attribute on the journaling recipient object for a mailbox store matches the value for the legacyExchangeDN attribute for the local server. If the values of these attributes match, this indicates that journaling messages are copied to a mailbox on the server that has active journaling running against it. Because of the high volume of journaling traffic that can be generated, it is recommended that the journal recipient mailbox reside on a dedicated journaling server.
If the Exchange Server Analyzer finds that the values for the msExchHomeServerName attribute for the journaling recipient object matches the value for the legacyExchangeDN of the local server, the Exchange Server Analyzer displays a best practice message.
For more information about how to deploy a journaling solution with Exchange Server 2003, see Journaling with Exchange Server (http://go.microsoft.com/fwlink/?LinkId=47581).
For more information about deploying a journaling solution with Exchange Server 2007, see Overview of Journaling (http://go.microsoft.com/fwlink/?LinkId=80820).