It is also available, but not enabled on client operating systems beginning with Windows Vista. The trace log exists, but it is not enabled on Windows Server 2008. Note This log is automatically enabled on server operating systems beginning with Windows Server 2008 R2. If the time zone is never set, there is no entry in this trace log. This is because an event gets written to this trace log when the time zone is set. But I decided to use the Get-WinEvent cmdlet and check the DateTimeControlPanel operational trace log.
There are several ways to approach this problem, including using Windows Management Instrumentation. This made me curious…did I forget to do this on other servers on the network? Detecting time zone settings on servers I checked, and noticed that I had forgotten to set the time zone when I built the computer. I was working with one of my servers, comparing different event log entries among machines, when I noticed what appeared to be a time skew.
Take for example, a situation I ran across today. Of course, on these occasions she is more than delighted to show off her scripting skills. One of the cool things about the Scripting Wife is that from time to time I can ask her if she would like to help with some of the system admin duties around the house. Microsoft Scripting Guy, Ed Wilson, is here. Summary: Learn how to use a Windows PowerShell cmdlet to determine if the time zone on remote servers has been changed from the default.
