Connectivity
logging keep tracks of connection from the sending queue to the
destination mailbox server, smart host or domain. It records the
connection activity of the outgoing message delivery queues on Exchange Server 2010 Hub Transport or Edge Transport server. We can use the EMC or the PowerShell to configure connectivity logging in Exchange Server 2010.
By default, connectivity logging is disabled on Exchange Server 2010 that has the Hub Transport or Edge Transport role installed.
How to use EMC Interface to Configure Connectivity Logging
1. Perform of the following steps:
On Edge Transport server, select Edge Transport and then click on Properties in the Action pane.
On Hub Transport server, expand Server Configuration and select Hub Transport. Click the Properties in the Action pane under the server name
2. Click Log Settings tab on the Properties tab.
3. In the Connectivity Log section, we can enable or disable the logging by selecting or clearing check boxes.
4. Click on OK to save the settings.
How to configure Connectivity Logging from the Shell:-
To enable or disable connectivity logging, use the following syntax.
Set-TransportServer <Identity> -ConnectivityLogEnabled <$true | $false>
Below example will enable connectivity logging on Exchange Server 2010 computer PC01.
Set-TransportServer PC01 -ConnectivityLogEnabled $true
How to configure the location of the Connectivity log files
The default location of the connectivity log file is C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\Connectivity directory. This directory must be local to the Exchange Server 2010 computer.
How to change the location of the connectivity log files from Shell
Set-TransportServer <Identity> -ConnectivityLogPath <LocalFilePath>
Example:-
Set-TransportServer PC01 -ConnectivityLogPath "C:\ConnectivityLogs"
How to Change the Maximum Size of Individual Connectivity Log files from the Shell
Default maximum size of connectivity log file is 10MB. When the log file reaches this limit, Exchange Server 2010 creates a new connectivity log file. This process continues until the connectivity log directory reaches its specified maximum size or a connectivity log file reaches it specified maximum age. In any case, circular logging deletes the oldest connectivity log files.
Here is the command to change the maximum size of the individual connectivity log files:-
Set-TransportServer <Identity> -ConnectivityLogMaxFileSize <FileSize>
Example:-
Set-TransportServer PC01 -ConnectivityLogMaxFileSize 40MB
Â
How to change the maximum size of the Connectivity Log Directory
By default, the maximum size of connectivity log directory is 250MB. Circular logging deletes the oldest log file until the connectivity log directory reaches its specified maximum size or a connectivity log file reaches it specified maximum age. Â We cannot use the EMC to change the size of connectivity log directory.
Syntax to change the maximum size of the connectivity log directory:-
Set-TransportServer <Identity> -ConnectivityLogMaxDirectorySize <DirectoySize>
Example:
Set-TransportServer PC01 -ConnectivityLogMaxDirectorySize 500MB
How to change the Maximum Age of the Connectivity Log Files
By default, the maximum age of any connectivity log file is 30 days. Circular logging deletes the oldest log file until the connectivity log directory reaches its specified maximum size or a connectivity log file reaches it specified maximum age. Â We cannot use the EMC to change the size of connectivity log directory.
Syntax to change maximum age of the connectivity log files:-
Set-TransportServer <Identity> -ConnectivityLogMaxAge <Age>
Example:
Set-TransportServer PC01 -ConnectivityLogMaxAge 45
No comments:
Post a Comment