I read that OpConfig has a GUI for it but apparently I don't have OpConfig.

Why don't Open-audIT's GUI config pages include time zone setting?

Why doesn't the installer get the time zone from a Windows API and set the default?

Addendum: I changed the time zone to Asia/Tokyo and saved the file. I used Windows's Services GUI to restart Apache 2.2 because apache_stop.bat and apache_start.bat don't work. After these operations, a new log entry appeared, and it's still 1 hour in the future. Now what am I missing?

Please adjust the FAQ page. I adjusted php.ini's line back to Brisbane but should not have touched that file in the first place.
In c:\omk\log, auth.log and opDaemon.log appear to have correct timestamps (Japan time).
index.php ... I didn't install vim in that virtual PC that's isolated from the internet, so just looking with Notepad, I see something that uses Windows APIs. I wonder where the hour inaccuracy comes from.

I'm away from that machine today but from memory, it's in the UI page that displays log messages. For example after submitting a discovery operation, the page automatically transitions to the page displaying the log. Each event is stamped 1 hour later than the correct time.
When does Australia switch to daylight savings time? It might be helpful to observe if timestamps after that are 2 hours later than the correct time. (Japan doesn't have daylight savings time.)

Not sure what version you're using. If you're on the latest then this time is being generated by MySQL. You can confirm it's off by running the following:
{code}
mysql -u openaudit -popenauditpassword -e "SELECT NOW();"
{code}
If that confirms it, then MySQL is somehow off by an hour. Let me know and I'll see if I can find anything.

Sorry I don't understand. If the Windows clock in the taskbar is off, it's off by less than 1 minute. It's not 60 minutes in the future and not 59 minutes in the future. Why is MySQL 59 minutes in the future from Windows?

I know not to complain to a volunteer, but does your silence mean that you're busy elsewhere, or working on this, or that you thought you reported the answer? Is it clear that the Windows clock is not off by 59 or 60 minutes (though I don't know if it's off by a fraction of 1 minute).

OK, I'll look for an answer in the future 1 hour after you have time ^_^
Google found some non-answers for me so far. If a PHP script is running in a different time zone from the SQL server (i.e. differernt machines in different time zones), or if an admin changes the Windows time or timezone but doesn't restart MySQL. My virtual PC is in Tokyo, running Windows and Active Directory and Open-audIT Enterprise (for learning and experimentation) so all in the same time zone with no changes. I'm suspicious that someone thinks we have daylight savings time so they add an hour.

From another Google search, I tried two more SQL commands.
SELECT @@TIME_ZONE; says Australia/Melbourne which could explain a 1 hour error but not 59 minute error, and I'm not sure where to fix it.
SELECT @@SYSTEM_TIME_ZONE; displays some question marks becaue someone doesn't know how to handle locales correctly. I conjecture that Windows reports the time zone name in Japanese, maybe ???/?? which is Japanese for Asia/Tokyo. Since Microsoft has learned the benefits of scripting I don't really think Windows would do that in an API unless someone forces it to give a localized answer. And next, something else in MySQL tries to convert the string to some non-Japanese locale, which would work if the string had been in English.