
Configuring the Location of the Connectivity Log Files
By default, the connectivity log files are stored in the C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\Connectivity directory. The directory must be local to the Exchange 2007 computer.
Note: |
|---|
|
You can configure the location of the connectivity log files by using the Exchange Management Console only in Exchange 2007 SP1.
|

To use the Exchange Management Console to change the location of the connectivity log files 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 Connectivity log section, click Browse next to Connectivity log path.
-
In the Browse for folder window, browse to the new location where you want to store the connectivity 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 connectivity log files in Exchange 2007 SP1 or Exchange 2007 RTM
-
Run the following command:
Set-TransportServer <Identity> -ConnectivityLogPath <LocalFilePath>
For example, to change the location of the connectivity log file to C:\Connectivity on an Exchange 2007 computer that is named Exchange01, run the following command:
Set-TransportServer Exchange01 -ConnectivityLogPath "C:\Connectivity"
If you set the value of the ConnectivityLogPath parameter to $null, you effectively disable connectivity logging. However, if you set the value of the ConnectivityLogPath parameter to $null when the value of the ConnectivityLogEnabled attribute is $true, you will generate event log errors. The preferred method to disable connectivity logging is to use the ConnectivityLogEnabled parameter with the Set-TransportServer cmdlet.
When you change the location of the connectivity log directory, this change does not copy any existing log files from the old directory to the new directory. The new connectivity 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 connectivity log directory:
-
Administrator: Full Control
-
System: Full Control
-
Network Service: Read, Write, and Delete Subfolders and Files
By default, the Microsoft Exchange Transport service uses the security credentials of the Network Service user account to create the new connectivity log directory and apply the correct permissions as follows:
-
If the new connectivity log directory does not already exist, and the Network Service account has the rights necessary to create folders and apply permissions at the new location, the new connectivity log directory is created and the correct permissions are applied to the new directory.
-
If the new connectivity log directory already exists, the existing folder permissions are not checked.
Whenever you move the connectivity log directory by using the ConnectivityLogPath parameter with the Set-TransportServer cmdlet, it is a good idea to verify the new connectivity log directory and to make sure that the new directory has the correct permissions applied to it. If your change to the connectivity log directory is not successful, you can create the new connectivity log directory and apply the correct permissions to it before you use the ConnectivityLogPath parameter with the Set-TransportServer cmdlet.