Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2012-07-23
You can use the EMC or the Shell to configure connectivity logging in Microsoft Exchange Server 2010. You must use the Shell to configure size and age restrictions on the connectivity log files.
Connectivity logging records the connection activity of the outgoing message delivery queues that exist on computers running Exchange 2010 that have the Hub Transport server role or Edge Transport server role installed. The purpose of the connectivity log isn't to track the transmission of individual e-mail messages. Rather, the connectivity log tracks the connection activity from the sending queue to the destination Mailbox server, smart host, or domain.
Looking for other management tasks related to transport logs? Check out Managing Transport Logs.
Enable or disable connectivity logging
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.
By default, connectivity logging is disabled on all Exchange 2010 computers that have the Hub Transport server role or Edge Transport server role installed.
Use the EMC to enable or disable connectivity logging
- 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's 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's directly under the server name.
- 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's directly under the
server name.
- On the Properties page, click the Log Settings
tab.
- In the Connectivity log section, perform one of the
following steps:
- Select Enable connectivity logging to enable
connectivity logging.
- Clear Enable connectivity logging to disable
connectivity logging.
- Select Enable connectivity logging to enable
connectivity logging.
- Click Apply to save changes and remain on the
Properties page, or click OK to save changes and exit
the Properties page.
Use the Shell to enable or disable connectivity logging
To enable or disable connectivity logging, use the following syntax.
Copy Code | |
---|---|
Set-TransportServer <Identity> -ConnectivityLogEnabled <$true | $false> |
This example enables connectivity logging on the Exchange 2010 computer Exchange01.
Copy Code | |
---|---|
Set-TransportServer Exchange01 -ConnectivityLogEnabled $true |
For detailed syntax and parameter information, see Set-TransportServer.
Configure the location of the connectivity log files
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.
By default, the connectivity log files are stored in the C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\Connectivity directory. The directory must be local to the Exchange 2010 computer.
Use the EMC to change the location of the connectivity log files
- 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's 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's directly under the server name.
- 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's directly under the
server name.
- On 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 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 on the
Properties page, or click OK to save changes and exit
the Properties page.
Use the Shell to change the location of the connectivity log files
To change the location of the connectivity log files, use the following syntax.
Copy Code | |
---|---|
Set-TransportServer <Identity> -ConnectivityLogPath <LocalFilePath> |
This example changes the location of the connectivity log file to C:\Connectivity on the Exchange 2010 computer Exchange01.
Copy Code | |
---|---|
Set-TransportServer Exchange01 -ConnectivityLogPath "C:\Connectivity" |
Note: |
---|
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 , event log errors are generated. The preferred
method to disable connectivity logging is to use the
ConnectivityLogEnabled parameter with the
Set-TransportServer cmdlet. |
For detailed syntax and parameter information, see Set-TransportServer.
Use the Shell to change the maximum size of individual connectivity log files
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.
Note: |
---|
You can't use the EMC to change the maximum size of individual connectivity log files. |
By default, the maximum size for each connectivity log file is 10 megabytes (MB). When a connectivity log file reaches its maximum size, Exchange 2010 opens a new connectivity log file. This process continues until either the connectivity log directory reaches its specified maximum size or a connectivity log file reaches its specified maximum age. After the maximum size or age limit is reached, circular logging deletes the oldest connectivity log files.
To change the maximum size of individual connectivity log files, use the following syntax.
Copy Code | |
---|---|
Set-TransportServer <Identity> -ConnectivityLogMaxFileSize <FileSize> |
This example sets the maximum size of a connectivity log file to 20 MB on the Exchange 2010 computer Exchange01.
Copy Code | |
---|---|
Set-TransportServer Exchange01 -ConnectivityLogMaxFileSize 20MB |
Note: |
---|
The value of the ConnectivityLogMaxFileSize parameter must be less than or equal to the value of the ConnectivityLogMaxDirectorySize parameter. The valid input range for either parameter is 1 through 9223372036854775807 bytes. |
For detailed syntax and parameter information, see Set-TransportServer.
Use the Shell to change the maximum size of the connectivity log directory
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.
Note: |
---|
You can't use the EMC to change the maximum size of the connectivity log directory. |
By default, the maximum size for the whole connectivity log directory is 250 MB. Circular logging deletes the oldest connectivity log files when either the connectivity log directory reaches its specified maximum size or a connectivity log file reaches its specified maximum age.
To change the maximum size of the connectivity log directory, use the following syntax.
Copy Code | |
---|---|
Set-TransportServer <Identity> -ConnectivityLogMaxDirectorySize <DirectorySize> |
This example sets the maximum size of the connectivity log directory to 400 MB on the Exchange 2010 computer Exchange01.
Copy Code | |
---|---|
Set-TransportServer Exchange01 -ConnectivityLogMaxDirectorySize 400MB |
Note: |
---|
The value of the ConnectivityLogMaxDirectorySize parameter must be greater than or equal to the value of the ConnectivityLogMaxFileSize parameter. The valid input range for either parameter is 1 through 9223372036854775807 bytes. |
For detailed syntax and parameter information, see Set-TransportServer.
Use the Shell to change the maximum age of the connectivity log files
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hub Transport server" and "Edge Transport server" entries in the Transport Permissions topic.
Note: |
---|
You can't use the EMC to change the maximum age of the connectivity log files. |
By default, the maximum age for any connectivity log file is 30 days. Circular logging deletes the oldest connectivity log files when either the connectivity log directory reaches its specified maximum size or a connectivity log file reaches its specified maximum age.
To change the maximum age of the connectivity log files, use the following syntax.
Copy Code | |
---|---|
Set-TransportServer <Identity> -ConnectivityLogMaxAge <Age> |
This example changes the maximum age of a connectivity log file to 45 days on the Exchange 2010 computer Exchange01.
Copy Code | |
---|---|
Set-TransportServer Exchange01 -ConnectivityLogMaxAge 45.00:00:00 |
To specify an age value, enter it as a time span, as
follows: dd.hh:mm:ss, where d = days,
h = hours, m = minutes, and
s = seconds. The valid input range for this
parameter is 00:00:00 through 24855.03:14:07. Setting the value of
the ConnectivityLogMaxAge parameter to 00:00:00
prevents the automatic removal of connectivity log files because of
their age.
For detailed syntax and parameter information, see Set-TransportServer.