Daylight savings time blues

[Scott Marquardt]

Despite having the time zone widget set to automatically adjust for
daylight savings time, many of our XP machines are giving users bogus times
in their Outlook calendars (an hour off from the folks calling the meeting,
for example). These users are all in the same time zone.

Examination of our domain's workstations using a WMI Win32_TimeZone script
shows that just one value is at variance: DaylightName. Manual examination
of HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation shows that
indeed, only this value is at variance across our domain. Some machines
have it right, others don't. However, all machines are set to pick up the
zone automatically.

Interestingly, unchecking the setting, checking it again, and applying the
setting yields a change in the time zone to the desired value (Central
Daylight Time, rather than Central Standard Time).

It appears that the automatic feature is not working in some cases (I
emphasize that *all* other values in the registry are identical, including
the DaylightStart and StandardStart values).

Any ideas?

 

[Milly Staples [MVP - Outlook]]

Interestingly enough, the Outlook MVPs had a discussion of this issue on a
clean install of Windows XP SP-1 and Office 2003. Some of us had the DST
configured correctly under both Control Panel and Outlook Calendar settings.
Others of us did not and had to manually set DST under the Outlook Calendar.

We finally gave up as there were too many variables but by consensus thought
that perhaps the BIOS of the system had some control over the setting. Do
you, by any chance, have a mix of computers in your setup? If yes, does
this problem only occur on one particular brand of computer/motherboard?


--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After searching google.groups.com and finding no answer, Scott Marquardt
asked:

| Despite having the time zone widget set to automatically adjust for
| daylight savings time, many of our XP machines are giving users bogus
| times in their Outlook calendars (an hour off from the folks calling
| the meeting, for example). These users are all in the same time zone.
|
| Examination of our domain's workstations using a WMI Win32_TimeZone
| script shows that just one value is at variance: DaylightName. Manual
| examination of
| HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation shows that
| indeed, only this value is at variance across our domain. Some
| machines have it right, others don't. However, all machines are set
| to pick up the zone automatically.
|
| Interestingly, unchecking the setting, checking it again, and
| applying the setting yields a change in the time zone to the desired
| value (Central Daylight Time, rather than Central Standard Time).
|
| It appears that the automatic feature is not working in some cases (I
| emphasize that *all* other values in the registry are identical,
| including the DaylightStart and StandardStart values).
|
| Any ideas?

 

[Michael P Gabriel]

Despite having the time zone widget set to automatically adjust for
daylight savings time, many of our XP machines are giving users bogus times
in their Outlook calendars (an hour off from the folks calling the meeting,
for example). These users are all in the same time zone.

Examination of our domain's workstations using a WMI Win32_TimeZone script
shows that just one value is at variance: DaylightName. Manual examination
of HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation shows that
indeed, only this value is at variance across our domain. Some machines
have it right, others don't. However, all machines are set to pick up the
zone automatically.

Interestingly, unchecking the setting, checking it again, and applying the
setting yields a change in the time zone to the desired value (Central
Daylight Time, rather than Central Standard Time).

It appears that the automatic feature is not working in some cases (I
emphasize that *all* other values in the registry are identical, including
the DaylightStart and StandardStart values).

Any ideas?

enjoying a little fun!

 

[Scott Marquardt]

Milly Staples [MVP - Outlook] opined thusly on Jul 7:

Interestingly enough, the Outlook MVPs had a discussion of this issue on a
clean install of Windows XP SP-1 and Office 2003. Some of us had the DST
configured correctly under both Control Panel and Outlook Calendar settings.
Others of us did not and had to manually set DST under the Outlook Calendar.

We finally gave up as there were too many variables but by consensus thought
that perhaps the BIOS of the system had some control over the setting. Do
you, by any chance, have a mix of computers in your setup? If yes, does
this problem only occur on one particular brand of computer/motherboard?

No. We haven't found any rhyme or reason all summer. And now we've fallen
back and the times are OK, but the freakin' Daylight setting is still all
over the map.

Meanwhile, no source I've been able to find in the last couple hours --
including usenet posts -- offers anything helpful. Nothing! I have an
entire freakin' domain with machines in one state or another for no obvious
reason, with their setting for "automatically update for DST checked," and
there's no action.

Geez. Does ANYONE have any idea what it takes to remotely set machines to
one state or another, with respect to DST?

 

[Diane Poremsky [MVP]]

Geez. Does ANYONE have any idea what it takes to remotely set machines to

one state or another, with respect to DST?

logon script. It's a Windows setting, not OL - possibly one of these values:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\TimeZoneInformation

 

[Scott Marquardt]

Diane Poremsky [MVP] opined thusly on Nov 1:

logon script. It's a Windows setting, not OL - possibly one of these values:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\TimeZoneInformation

Yup. Covered that ground. I could recite every web page or usenet post that
touches on that key, by heart. However, I won't bore you. ;-)

Seriously, I've found no information that would help my build such a
script.

What I'd REALLY like to know, of course, is why the deuce XP isn't
automatically changing though the check box is made. Unchecking it and
checking it again, and clicking "apply," does the trick. That I can't do
this with a script is among the stupidest things I've yet seen.