How to Change the Location of the Message Tracking Logs in Exchange 2000 Server
Essay by review • February 3, 2011 • Study Guide • 996 Words (4 Pages) • 1,601 Views
Essay Preview: How to Change the Location of the Message Tracking Logs in Exchange 2000 Server
How to change the location of the message tracking logs in Exchange 2000 Server
View products that this article applies to.
Article ID : 317700
Last Review : June 29, 2004
Revision : 1.0
This article was previously published under Q317700
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
On this page
SUMMARY
MORE INFORMATION
APPLIES TO
SUMMARY
When message tracking is enabled on a Microsoft Exchange 2000 Server computer, the tracking logs are written to the location ExchsrvrServerName.log. In this scenario Exchsrvr represents the folder in which Exchange 2000 is installed and ServerName is the host name of the Exchange server itself (for example, C:Program FilesExchsrvrExServer1.log). These logs can increase in size, which depends on the message throughput and the function of a particular server in your environment. Because of this increase in size, you may want to change the location of the message tracking logs to accommodate the size requirements. Because a user interface doe not exist in Exchange System Manager to change the location of message tracking logs, this article describes how to manually apply this adjustment by using Active Directory Editing tools and Registry Editor.
Back to the top
MORE INFORMATION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To move the location of the message tracking logs, follow these steps:1. Quit the following services:Ð'* Microsoft Exchange Message Transfer Agent (MTA) Stacks
Ð'* Microsoft Exchange Post Office Protocol version 3 (POP3)
Ð'* Microsoft Exchange Internet Message Access Protocol, Version 4rev1 (IMAP4)
Ð'* Microsoft Exchange Information Store
Ð'* Microsoft Exchange System Attendant
Ð'* Simple Mail Transport Protocol (SMTP)
2. Use Microsoft Windows Explorer to create the new folder that is to contain the log files, for example, C:Logs.
3. Make note of any special permissions that may have been set on the original folder location. For example, if the original location was C:Program FilesExchsrvrExServer1.log, the folder inherits the folder and file permissions from the parent folder (C:/Program Files). You can view these permissions under the Security tab of the folder permissions. If Exchange 2000 Server is not installed under the default Program Files folder, the file permissions are Everyone with Full Control. Share permissions should be Full Control for the Administrators Group and the computer account (for example, ExServer1$). The Everyone Group should have Read share permissions. These settings are verified in the steps later.
4. Copy the log file folder that exists (for example, C:Program FilesExchsrvrExServer1.log) to the new folder location (for example, C:Logs). To change the location that is recorded in Active Directory, you must modify the msExchDataPath value in Active Directory by using either LDP or ADSI Edit. ADSI Edit and LDP are included in Microsoft Windows 2000 Support Tools (on the Microsoft Windows 2000 CD-ROM). For additional information, see the following article or articles in the Microsoft Knowledge Base:
301423 How to Install the Windows 2000 Support Tools
5. Start ADSI Edit, and then connect to a domain controller.
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft
...
...