
Configuring the Location of Message Tracking Logs
By default, the message tracking logs are stored in the C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\MessageTracking directory. The directory must be local to the Exchange 2007 computer. In a single copy cluster (SCC) environment, move the message tracking log directory to a physical disk resource that is located on the shared storage resource. This enables searches of message tracking logs to continue to function if a failover occurs.
Note: |
|---|
|
You can configure the location of the message tracking logs by using the Exchange Management Console only in Exchange 2007 SP1.
|

To use the Exchange Management Console to change the location of the message tracking logs on a Hub Transport server or Edge Transport server in Exchange 2007 SP1
-
Open the Exchange Management Console. Perform one of the following steps:
-
On a computer that has the Edge Transport server role installed, select Edge Transport, and then in the action pane, click the Properties link that is directly under the server name.
-
On a computer that has the Hub Transport server role installed, in the console tree, expand Server Configuration, and select Hub Transport. In the action pane, click the Properties link that is directly under the server name.
-
In the Properties page, click the Log Settings tab.
-
In the Message tracking log section, click Browse next to Message tracking log path.
-
In the Browse for folder window, browse to the new location where you want to store the message tracking log files. If you want to create a new folder, select a parent folder, click Make New Folder, and then type the name of the new folder. After you make your folder selection, click OK to close the Browse for folder window.
-
Click Apply to save changes and remain in the Properties page, or click OK to save changes and exit the Properties page.

To use the Exchange Management Shell to change the location of the message tracking logs on a Hub Transport server or Edge Transport server in Exchange 2007 SP1 or Exchange 2007 RTM
-
Run the following command:
Set-TransportServer <Identity> -MessageTrackingLogPath <LocalFilePath>
For example, to change the location of the message tracking log to C:\Message Tracking on an Exchange 2007 computer that is named Exchange01, run the following command:
Set-TransportServer Exchange01 -MessageTrackingLogPath "C:\Message Tracking"

To use the Exchange Management Shell to change the location of the message tracking logs on a Mailbox server in Exchange 2007 SP1 or Exchange 2007 RTM
-
Run the following command:
Set-MailboxServer <Identity> -MessageTrackingLogPath <LocalFilePath>
For example, to change the location of the message tracking log to C:\Message Tracking on an Exchange 2007 computer that is named Mailbox01, run the following command:
Set-MailboxServer Mailbox01 -MessageTrackingLogPath "C:\Message Tracking"
If you set the value of the MessageTrackingLogPath parameter to $null, you effectively disable message tracking. However, if you set the value of the MessageTrackingLogPath parameter to $null when the value of the MessageTrackingLogEnabled attribute is $true, you will generate event log errors. The preferred method to disable message tracking is to use the MessageTrackingLogEnabled parameter with the Set-TransportServer cmdlet or the Set-MailboxServer cmdlet.
When you change the location of the message tracking log directory, this change does not copy any existing log files from the old directory to the new directory. The new message tracking log directory is active almost immediately after the configuration change, but any existing log files are left in the old directory.
The following permissions are required on the message tracking log directory:
-
Administrator: Full Control
-
System: Full Control
-
Network Service: Read, Write, and Delete Subfolders and Files
By default, the Exchange Transport service uses the security credentials of the Network Service user account to create the new message tracking log directory and apply the correct permissions. If the new message tracking log directory does not already exist, and the Network Service account has the rights that are required to create folders and apply permissions at the new location, the new message tracking log directory is created and the correct permissions are applied to the new directory. If the new message tracking log directory already exists, the existing folder permissions are not checked. Whenever you move the message tracking log directory by using the MessageTrackingLogPath parameter with the Set-TransportServer cmdlet or the Set-MailboxServer cmdlet, it is always a good idea to verify the new message tracking log directory and to verify that the new directory has the correct permissions applied to it. If your change to the message tracking log directory is not successful, you can create the new message tracking log directory and apply the correct permissions to it before you use the MessageTrackingLogPath parameter with the Set-TransportServer cmdlet or the Set-MailboxServer cmdlet.