How about using the TimeZone.exe command in the Resource Kit tools, and
launching it in a startup script for the Windows 2000 workstations?
I'm from Europe and I have no idea what are the new correct values (from
April to March, perhaps), but the command sample is the following:
TIMEZONE /s 02:0:5:04 02:2:1:10
Timezone will be changed to:
Daylight Saving Time begins at 2:00 on last Sunday in April
(02:0:5:04)
Daylight Saving Time ends at 2:00 on forth Tuesday in October
(02:2:4:10)
Yours, Sakari
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Bradley
Sent: 1. tammikuuta 2007 0:27
To: [email protected]
Subject: RE: [ActiveDir] OT: Sorta... AD and the 3/07 Time Change
This has been discussed on the www.patchmanagement.org listserve as well
and has been a concern there too.
(The issue is this is not seen as a security patch and 2k machines only
get security patches, thus the daylight fix patches are only being
released for XP/2k3, and not 2k)
There are also issues with Exchange/OWA and those patches for supported
versions of Exchange (my understanding) will be mu'd/wsus out later.
I know for a fact that once when I had a machine that had the "auto
change for daylight savings" unchecked when it should have been
checked.. regardless of it's sync status with the server, for a few days
after daylight savings, that machine saw everyone else's calendar an
hour off and visa versa.
There are scripts discussed on that listserve to get the 2k machines in
line and in the right sync'ing.
Brian Desmond <[EMAIL PROTECTED]> wrote:
Hi Richard-
The time sync process is just going to set the actual time
(think UTC) not the timezone. If the client thinks it is GMT-5 then it
will set the time accordingly.
Given the rochester.rr address - U of R or RIT?
Thanks,
Brian Desmond
[EMAIL PROTECTED]
c - 312.731.3132
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Richard Kline
Sent: Sunday, December 31, 2006 2:45 PM
To: [email protected]
Subject: [ActiveDir] OT: Sorta... AD and the 3/07 Time Change
This question addresses the March'07 Dailylight Saving's time
change in the US and Canada (has Mexico joined in?).
I work for an institute of higher learning where the policies
(human, not domain) get a little... unevenly suggested. So please
grant me some leniency as to why this question is even asked :)
Does belonging to a domain with properly configured time
synchronization lessen the concern for applying the XP patches as they
relate to the March 2007 time change? Or the need to take special care
with Windows 2000 workstations?
In other words, will AD sync the PC clock on Windows 2000
workstations to the correct hour during next next March's "leap ahead"
Speaking of time: Happy New Year to Everyone!
Thank you.
Richard
