IIS logging shows that requests between 7:00 PM and midnight are appearing in the following day’s log file. You need each day’s web activity to be recorded in that same day’s log. What should you change on the web site?

Introduction / Context:
IIS (Internet Information Services) supports multiple log formats. The common W3C Extended Log File Format timestamps entries in Coordinated Universal Time (UTC) by default, and there is a separate option controlling when log files roll over and how they are named. If rollover uses UTC while you expect local time, evening requests may appear in the next day's log.

Given Data / Assumptions:

• Web sites have logging enabled.
• Third-party reporting expects daily files aligned to local dates.
• Entries from 7:00 PM to midnight are shifted to the next day's file.

Concept / Approach:

Adjust the logging configuration so that IIS rolls logs based on local time. In IIS 5/Windows 2000, under the site's Logging Properties, choose 'Daily' rollover and enable 'Use local time for file naming and rollover.' This keeps timestamps consistent with reporting expectations without changing the server's system time zone.

Step-by-Step Solution:

Verification / Alternative check:

After one day, confirm that a new log starts exactly at local 00:00 and the previous day's late-evening entries remain in the correct file.

Why Other Options Are Wrong:

Changing the log format alone does not alter rollover timing.

Changing the host time zone is unnecessary and may disrupt other services.

Time service account context is unrelated to log rollover.

None: There is a specific logging property that fixes the issue.

Common Pitfalls:

Confusing UTC timestamps in log lines with file naming/rollover time; forgetting to adjust each site if multiple exist.

Final Answer:

Change the log rollover property for the web site to roll over based on local time (daily)