B
Brenton Frahn
We have a number of users spanning three time zones, connecting to a Windows
2003 Terminal Server Farm from either Windows 2000/XP/Vista computers or Wyse
Winterm (Windows CE) thin client terminals. Timezone redirection policy is
enabled and has been working for some time ... until now when daylight
savings has clicked in.
For us the problem occurs when a user from a thin client connects, the
correct timezone appears to be applied BUT the time is one hour behind (we
are in the southern hemisphere so we've just set our clocks forward one hour)
When the user right clicks over the clock on the taskbar and clicks Adjust
Date/Time, the correct Time Zone is set as too the option to Automatically
adjust clock for daylight savings changes. Without changing anything the
users click OK.
Now here's the funky part, the next time the minute changes, the clock now
displays the correct time!
For users using Remote Desktop from Windows 2000/XP/Vista this doesn't
appear to be an issue as the correct time is displayed.
From this it looks like some incompatibility with Timezone Redirection and
non Windows RDP to update the clock for daylight savings time
2003 Terminal Server Farm from either Windows 2000/XP/Vista computers or Wyse
Winterm (Windows CE) thin client terminals. Timezone redirection policy is
enabled and has been working for some time ... until now when daylight
savings has clicked in.
For us the problem occurs when a user from a thin client connects, the
correct timezone appears to be applied BUT the time is one hour behind (we
are in the southern hemisphere so we've just set our clocks forward one hour)
When the user right clicks over the clock on the taskbar and clicks Adjust
Date/Time, the correct Time Zone is set as too the option to Automatically
adjust clock for daylight savings changes. Without changing anything the
users click OK.
Now here's the funky part, the next time the minute changes, the clock now
displays the correct time!
For users using Remote Desktop from Windows 2000/XP/Vista this doesn't
appear to be an issue as the correct time is displayed.
From this it looks like some incompatibility with Timezone Redirection and
non Windows RDP to update the clock for daylight savings time