Jaa

Configure connectivity logging in Exchange Server

  • Artikkeli

Connectivity logging records outbound connection activity (source, destination, number and size of messages, and connection information) for the transport services on Exchange servers. For more information about connectivity logging, see Connectivity logging in Exchange Server.

What do you need to know before you begin?

  • Estimated time to complete: 15 minutes

  • You can use the Exchange admin center (EAC) to enable or disable connectivity logging and set the log path for the Transport service on Mailbox servers only. For all other connectivity logging options in the other transport services, you need to use the Exchange Management Shell. For more information about the EAC, see Exchange admin center in Exchange Server. To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see Open the Exchange Management Shell.

  • The folder for connectivity logging needs the following permissions:

    • Network Service: Full Control

    • System: Full Control

    • Administrators: Full Control

    If the folder doesn't exist, but the parent folder has these permissions, the new folder is created automatically.

  • You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Transport service", "Front End Transport service", and "Mailbox Transport service" entries in the Mail flow permissions topic.

  • For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.

Tip

Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.

Use the EAC to configure connectivity logging in the Transport service on Mailbox servers

  1. In the EAC, go to Servers > Servers.

  2. Select the Mailbox server you want to configure, and then click Edit Edit icon..

  3. On the server properties page that opens, click Transport Logs.

  4. In the Connectivity log section, change any of these settings:

    • Enable connectivity log: To disable connectivity logging for the Transport service on the server, clear the check box. To enable connectivity logging for the Transport service on the server, select the check box.

    • Connectivity log path: The value you specify must be on the local Exchange server. If the folder doesn't exist, it will be created for if the parent folder has the required permissions.

    When you're finished, click Save.

Use the Exchange Management Shell to configure connectivity logging

On Mailbox servers, connectivity logging is available on the following transport services:

  • The Transport service (use the Set-TransportService cmdlet).

  • The Front End Transport service (use the Set-FrontEndTransportService cmdlet).

  • The Mailbox Transport Delivery and Mailbox Transport Submission services (use the Set-MailboxTransportService cmdlet to configure both).

On Edge Transport servers, connectivity logging is available on the Transport service (use the Set-TransportService cmdlet).

To configure connectivity logging, use the following syntax:

<Set-TransportService | Set-MailboxTransportService | Set-FrontEndTransportService> -Identity <ServerIdentity> -ConnectivityLogEnabled <$true | $false> -ConnectivityLogMaxAge <dd.hh:mm:ss> -ConnectivityLogMaxDirectorySize <Size> -ConnectivityLogMaxFileSize <Size> -ConnectivityLogPath <LocalFilePath>

This example sets the following connectivity log settings in the Transport service on the Mailbox server named Mailbox01:

  • Location of the connectivity log: D:\Connectivity Log\Hub. Note that if the folder doesn't exist, it will be created for you if the parent folder has the required permissions.

  • Maximum size of a connectivity log file: Sets the maximum size of a connectivity log file to 20 MB.

  • Maximum size of the connectivity log folder: Sets the maximum size of the connectivity log directory to 1.5 GB.

  • Maximum age of a connectivity log file: Sets the maximum age of a connectivity log file to 45 days.

Set-TransportService -Identity Mailbox01 -ConnectivityLogPath "D:\Connectivity Log\Hub" -ConnectivityLogMaxFileSize 20MB -ConnectivityLogMaxDirectorySize 1.5GB -ConnectivityLogMaxAge 45.00:00:00

For detailed syntax and parameter information, see Set-TransportService, Set-FrontendTransportService, and Set-MailboxTransportService.

Notes:

  • Setting the ConnectivityLogPath parameter to the value $null, effectively disables connectivity logging. However, this value generates event log errors if the value of the ConnectivityLogEnabled parameter is also $true.

  • When you use the ConnectivityLogPath parameter on the Set-MailboxTransportService cmdlet, two subfolders are automatically created in the folder you specify:

    • Delivery for the Mailbox Transport Delivery service.

    • Submission for the Mailbox Transport Submission service.

  • Setting the ConnectivityLogMaxAge parameter to the value 00:00:00 prevents the automatic removal of connectivity log files because of their age.

How do you know this worked?

To verify that you've successfully configured connectivity logging, use these steps:

  1. Run the following command in the Exchange Management Shell to verify the connectivity log settings on the Exchange servers:

    Write-Host "Front End Transport service:" -ForegroundColor yellow; Get-FrontEndTransportService | Format-List Name,ConnectivityLog*; Write-Host "Mailbox Transport Submission and Mailbox Transport Delivery services:" -ForegroundColor yellow; Get-MailboxTransportService | Format-List Name,ConnectivityLog*; Write-Host "Transport service:" -ForegroundColor yellow; Get-TransportService | Format-List Name,ConnectivityLog*

  2. Open the location of the connectivity log in Windows Explorer or File Explorer to verify that the log files exist, that data is being written to the files, and that the files are being recycled based on the maximum file size and maximum directory size values that you configured. If you disabled connectivity logging, verify that the log files aren't being updated.