DST 2007 Please Help!

  • Thread starter Thread starter j.lichtenberger
  • Start date Start date
J

j.lichtenberger

Hello-

We have a Win2k domain with mostly 2k workstations and a few XP pro
machines.

I ran TXedit on the Domain controllers and updated the registry on all
my workstations by deploying the registry file and script using Group
Policy as described in KB article 914387.

The DCs updated fine, but the workstations advanced by 2 hours. If I
go to a workstation and uncheck the automatically adjust clock for
daylight savings time option, the machine will display the correct
time.

Does anyone know where I went wrong? Or know of another way to fix
this besides touching every workstation?

Thanks-
Joel
 
Hello-

We have a Win2k domain with mostly 2k workstations and a few XP pro
machines.

I ran TXedit on the Domain controllers and updated the registry on all
Click to expand...

TZEdit (but I have trouble typing an X by mistake instead of Z too said:
my workstations by deploying the registry file and script using Group
Policy as described in KB article 914387.

The DCs updated fine, but the workstations advanced by 2 hours. If I
go to a workstation and uncheck the automatically adjust clock for
daylight savings time option, the machine will display the correct
time.
Click to expand...

Did you perhaps edit the BIAD for DST incorrectly?

Re-open TZEdit, select your time zone and double check the DST
Bias which should be +1 hour. (Lower right)
Does anyone know where I went wrong? Or know of another way to fix
this besides touching every workstation?
Click to expand...

If you used the Registry import method it is possible you did the equivalent
of the TZEdit mistake but you should still be able to check it with TZEdit
which will give you a much more "interactive feel".

You might also have accidentally set the incorrect time zone value....
 
Did you perhaps edit the BIAD for DST incorrectly?

Re-open TZEdit, select your time zone and double check the DST
Bias which should be +1 hour. (Lower right)
Click to expand...

No Bias was set correctly...
If you used the Registry import method it is possible you did the equivalent
of the TZEdit mistake but you should still be able to check it with TZEdit
which will give you a much more "interactive feel".

You might also have accidentally set the incorrect time zone value....
Click to expand...

I was able to fix this by
1. un-checking the "Automatically adjust clock for daylight saving
changes" on the Win 2k DCs
2. apply changes
3. updating the time on our DCs manually
4. apply changes
5. check the "Automatically adjust clock for daylight saving changes"
6. apply changes

All workstations now display the correct time. If anyone else has
this problem, or knows why this happened please post.

Thanks for the input Herb.

J
 
Did you perhaps edit the BIAD for DST incorrectly?

Re-open TZEdit, select your time zone and double check the DST
Bias which should be +1 hour. (Lower right)
Click to expand...

No Bias was set correctly...
If you used the Registry import method it is possible you did the equivalent
of the TZEdit mistake but you should still be able to check it with TZEdit
which will give you a much more "interactive feel".

You might also have accidentally set the incorrect time zone value....
Click to expand...

I was able to fix this by
1. un-checking the "Automatically adjust clock for daylight saving
changes" on the Win 2k DCs
2. apply changes
3. updating the time on our DCs manually
4. apply changes
5. check the "Automatically adjust clock for daylight saving changes"
6. apply changes

All workstations now display the correct time. If anyone else has
this problem, or knows why this happened please post.

Thanks for the input Herb.

J
 
No Bias was set correctly...

I was able to fix this by
1. un-checking the "Automatically adjust clock for daylight saving
changes" on the Win 2k DCs
2. apply changes
3. updating the time on our DCs manually
4. apply changes
5. check the "Automatically adjust clock for daylight saving changes"
6. apply changes

All workstations now display the correct time. If anyone else has
this problem, or knows why this happened please post.

Thanks for the input Herb.

J
Click to expand...
 
I have the same problem except I also have one DC that is running 2003 and is
also ahead by an hour. The 2k DC is the PDC. When you say in your steps 1-6
that you updated the time on the DCs manually, are you referring to using
TZedit? How exactly did you change the time? Thanks.
 
Back
Top