Bug with TZEdit.exe tool, for daylight savings tim changes?

[CAMC1]

I used TZEdit.exe tool from Micropsoft to set correct time zone on my
windows 2000 SP4 domain controllersa nd windows 2000 pro PCs

After this change, I expected daylight savings time to change automatically
on these 2000 servers and workstations, but did not. I verified that I had
set correct time zone.

I had to go back and manually set the clock on each of these servers

Is there a bug in this tool that did not make correct changes in the system?

Thanks
MC

 

[Herb Martin]

I used TZEdit.exe tool from Micropsoft to set correct time zone on my
windows 2000 SP4 domain controllersa nd windows 2000 pro PCs

After this change, I expected daylight savings time to change
automatically
on these 2000 servers and workstations, but did not. I verified that I had
set correct time zone.

I had to go back and manually set the clock on each of these servers

The "clock" was NOT what was patched so setting the "clock" implies they
had the WRONG time.

This update was about the DISPLAY of the time.

Set the TIME correctly based on a UTC (aka GMT) source, such as
your DC or PDC Emulator or NTP Internet server.

If it didn't update the DISPLAY correctly then then the correct procedure
is to set the Timezone, Timezone offset, DST BIAS (offset), and Automatic
DST
correctly.

IF this fails to correct the display time then the work around is to alter
the
time ZONE settings until the problem can be correct but you should/must NOT
use the "time" value itself, especially for domain machines.

Is there a bug in this tool that did not make correct changes in the
system?

Someone has claimed an "order specific" process was required -- something
about clearing the auto checkbox, resetting the zone, then resetting the
check
box (this is NOT exactly what was reported) but I remained unconvinced as
thousands of people (including us) saw no problems with Win2000 machines
using TZEdit.

It just worked.

(An odd bug is possible, but I would look to local mistakes or assumptions
first.)

 

[peter stickney]

I have the same setup and problem. I followed http://support.microsoft.com/kb/914387,
deploying the patch over GPO and using the TZEdit tool to confirm the
changes. On Friday, TZEdit confirmed the registry edit changed. Yet,
I come in this morning, and the time displayed is an hour off.

A few mins of googling turned up another thread
( novell.support.netware.client.winnt-2x-xp : DST not correct on
stations ). The solution seems to be to go to the Date/Time Control
Panel applet, go to the Time Zone tab, uncheck the DST box, Hit Apply,
Check the DST box, hit apply. That should fix it.

In the few mins Ive been looking at it, it seems that the internal
clock is actually correct, meaning the patch and TZEdit were correct.
But for some reason, the time displayed is off by an hour.

I hope that makes sense.

-peter

 

[John John]

I used TZEdit.exe tool from Micropsoft to set correct time zone on my
windows 2000 SP4 domain controllersa nd windows 2000 pro PCs

After this change, I expected daylight savings time to change automatically
on these 2000 servers and workstations, but did not. I verified that I had
set correct time zone.

I had to go back and manually set the clock on each of these servers

Is there a bug in this tool that did not make correct changes in the system?

There is no bug in the tool. Had you taken the time to read the help
and instruction files you would have found out the following:

Editing the current time zone entry

Data for the current time zone is saved in a different location in the
registry than the data for the time zone entries in the Date/Time Icon.
Therefore, if you change the settings for the current time zone, the
changes will not immediately take effect. In order for the new
information to be used by the system, use the following procedure.

To edit the time zone entry for the current time zone

1 Use the Time Zone Editor to edit the time zone entry.
2 Open Control Panel and click the Date/Time icon.
3 Click the Time Zone tab.
4 Select or re-select the time zone you have changed.
5 Click OK.

The system clock will be reset to take into account the changes you have
made.

[End quote]

John

 

[peter stickney]

This is certainly a problem with this whole process. I read the
entire KB and it never mentioned having to check and uncheck boxes for
it to work.

It seems I am also noticing an error in reporting time zones. I am in
EST ( GMT -5 ). However, net time on some stations shows they are in
GMT -4. We're still trying to piece it all together here.

-peter

 

[Herb Martin]

Mr Herb,
I guess I did not make it clear
TZEdit supposed to fix your Time Zone Settings, so that your computer
automatically changes the display time of the computer after 2Am of
second
sunday of March, did not happen.

YOU can also completely (or partially) RUIN your time zone values
with that tool.

It is a fairly low-level editor.

 

[CAMC1]

Some of the windows 2003 servers that I have are fully patched and shows
correct settings for the time zone, however I saw few of them had the time
was set 2 hour forward from origional time.

Something odd here

MC

 

[CAMC1]

Why?
That is the most safest (SUPPOSED TO BE) tool for anyone who are not too
comfortable with playing registry.

Off-course you could be right, just like anything else it may have glitches
that it may or may not do a good job, thus ruining it.

MC

 

[CAMC1]

Mr Herb,
I guess I did not make it clear
TZEdit supposed to fix your Time Zone Settings, so that your computer
automatically changes the display time of the computer after 2Am of second
sunday of March, did not happen.

MC

 

[CAMC1]

Why don't you fellows read my e-mail?
I menationed I used TZEdit.exe tool from Microsoft Site to do all that.
Thanks
MC

I used TZEdit.exe tool from Micropsoft to set correct time zone on my
windows 2000 SP4 domain controllersa nd windows 2000 pro PCs

After this change, I expected daylight savings time to change automatically
on these 2000 servers and workstations, but did not. I verified that I had
set correct time zone.

I had to go back and manually set the clock on each of these servers

Is there a bug in this tool that did not make correct changes in the

system?

There is no bug in the tool. Had you taken the time to read the help
and instruction files you would have found out the following:

Editing the current time zone entry

Data for the current time zone is saved in a different location in the
registry than the data for the time zone entries in the Date/Time Icon.
Therefore, if you change the settings for the current time zone, the
changes will not immediately take effect. In order for the new
information to be used by the system, use the following procedure.

To edit the time zone entry for the current time zone

1 Use the Time Zone Editor to edit the time zone entry.
2 Open Control Panel and click the Date/Time icon.
3 Click the Time Zone tab.
4 Select or re-select the time zone you have changed.
5 Click OK.

The system clock will be reset to take into account the changes you have
made.

[End quote]

John

 

[CAMC1]

Thank God I was not the only one who noticed this problem.
Thanks
MC

 

[Herb Martin]

Why?
That is the most safest (SUPPOSED TO BE) tool for anyone who are not too
comfortable with playing registry.

Sure it is safer (and easier) than using the Registry directly but a lot of
stuff is exposed.

Off-course you could be right, just like anything else it may have
glitches
that it may or may not do a good job, thus ruining it.

Anyone can be "off by 1" or go positive instead of negative.

Google GROUPS for My Name, since Saturday, TZEdit, and
contained on "microsoft.public.*" (any MS group).

There is an response by the fellow who asked for help and then
claimed that "order dependent" procecure for checking /unchecking
the auto adjust worked for him.

It actually has a date of either today or yesterday but if you find the
thread then his procedure may help you.

 

[CAMC1]

Because of this issue,
everyone had brief interruption login on to domain shares, and exchange
authentication issues. I see a lot of "kerberos authentication" related
security errors on my domain controllers event log

Changing display clock manually did not work untill actually I set the flag
you mentioned off and on.

MC

It took a a couple of hours for servers to be in sync.

 

[John John]

When all else fails read the instructions! You have to change the
information in 2 registry keys. The tzedit tool does the changes in one
of the keys only. Again, in case you didn't see it in the other post:

To edit the time zone entry for the current time zone

1 Use the Time Zone Editor to edit the time zone entry.
2 Open Control Panel and click the Date/Time icon.
3 Click the Time Zone tab.
4 Select or re-select the time zone you have changed.
5 Click OK.

You did step 1 and neglected to do the others.

John

Why don't you fellows read my e-mail?
I menationed I used TZEdit.exe tool from Microsoft Site to do all that.
Thanks
MC

CAMC1 wrote:

I used TZEdit.exe tool from Micropsoft to set correct time zone on my
windows 2000 SP4 domain controllersa nd windows 2000 pro PCs

After this change, I expected daylight savings time to change

automatically

on these 2000 servers and workstations, but did not. I verified that I

had

set correct time zone.

I had to go back and manually set the clock on each of these servers

Is there a bug in this tool that did not make correct changes in the

system?

There is no bug in the tool. Had you taken the time to read the help
and instruction files you would have found out the following:

Editing the current time zone entry

Data for the current time zone is saved in a different location in the
registry than the data for the time zone entries in the Date/Time Icon.
Therefore, if you change the settings for the current time zone, the
changes will not immediately take effect. In order for the new
information to be used by the system, use the following procedure.

To edit the time zone entry for the current time zone

1 Use the Time Zone Editor to edit the time zone entry.
2 Open Control Panel and click the Date/Time icon.
3 Click the Time Zone tab.
4 Select or re-select the time zone you have changed.
5 Click OK.

The system clock will be reset to take into account the changes you have
made.

[End quote]

John

 

[CAMC1]

I am just wondering if the clock will roll back 1hour in First Sunday of
November due to this issue. If not I guess, we will have to face the same
issue every time daylight savings time need to change.

Some Windows 2003 Servers that are on my domain, did not roll forward
properly also, when they were fully patched. I saw my windows 2003 server
2hour off, where it should have been only 1hour

MC

Does anyone else seen this also?

 

[Herb Martin]

I am just wondering if the clock will roll back 1hour in First Sunday of
November due to this issue. If not I guess, we will have to face the same
issue every time daylight savings time need to change.

Some Windows 2003 Servers that are on my domain, did not roll forward
properly also, when they were fully patched. I saw my windows 2003 server
2hour off, where it should have been only 1hour

You have likely seen this stuff by now but below are two of the messages
from people who claimed to have figured out the problem (the remainder
are QUOTES and are not directed from me to you):

When all else fails read the instructions! You have to change the
information in 2 registry keys. The tzedit tool does the changes in one
of the keys only. Again, in case you didn't see it in the other post:

To edit the time zone entry for the current time zone