Remote Logging

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1

You can write log data to a remote share over a network using a full Universal Naming Convention (UNC) path for centralized log file storage and backup. Be aware that remote logging can negatively affect performance because IIS writes the log file and log file data over the network.


Logging to a UNC share is not supported by IIS FTP. You must configure FTP log files location to a path on the local machine.


It is highly recommended that you enable Internet Protocol security (IPSec) between your Web server running IIS and the remote server before configuring remote logging. If IPSec is not enabled between the Web server running IIS and the remote server, data packets containing log data are potentially at risk of being intercepted by malicious individuals and wire-sniffing applications while the data packet travels through the network.


Setting up remote logging requires the following actions:

  1. Configuring IIS to Log Data on a Remote Share

  2. Configuring Permissions for Remote Logging

  3. Setting Up a Null Session for Cross-Domain Logging (if applicable)