Did you know ... in addition to the Windows Server 2003 system and security logs, you should configure IIS to log site visits. When users access your server running IIS 6.0, IIS logs the information. The logs provide valuable information that you can use to identify any unauthorized attempts to compromise your Web server.
Depending on the amount of traffic to your Web site, the size of your log file (or the number of log files) can consume valuable disk space, memory resources, and CPU cycles. You might need to balance the gathering of detailed data with the need to limit files to a manageable size and number. If you are planning to put thousands of Web sites on one Web server with high traffic volumes and disk writes, you might want to use centralized binary logging to preserve server resources. Also, consider limiting log size by changing the frequency of log file creation.
For more information check MS site here - http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/b344f84e-bc77-4019-859c-9d483bc85c77.mspx?mfr=true
Ok, you can convert your IIS logs into SQL database as well so that you can do more efficent reporting
Also, you can write your custom logging modules and have logs displayed on ASP page as well. Check all about IIS logging here -
Do you need a tool to do all this - "Log Parser" (command line utility) :)
Log Parser allows you to do universal query access to text-based data such as log files, XML files and CSV files, as well as key data sources on the Windows® operating system such as the Event Log, the Registry, the file system, and Active Directory®.
Download it from here -
CRM 3.0 does not have functionality inbuilt for profiling transactions? To get reports like ...which user accessed Contacts, Case or a particular page number of times or any unauthorized access we need to use IIS logs to meet the needs. Credits to Ronald for sharing this info
Thanks - DJ