Re: w2k DC time off by 12 hours

Hi John John -

thanks for info.

I will correct the
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones


What about the other registry keys? Do I need to import them into srv1 ?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters


Thanks




"John John - MVP" <audetweld@xxxxxxxxxxx> wrote in message
news:e6NmZCczJHA.4808@xxxxxxxxxxxxxxxxxxxxxxx
srv1 is borked, that's the problem. As I said earlier when you set the
time zone the information for the zone is obtained at the
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones keys and
copied to the Control Set.

Your srv1 has an incorrect TZI value at the key in question. Export this
key from one of your other machines then remove/delete the incorect key on
srv1 and merge the key from the good machine to the srv1 registry. Then
use the Time/Date applet and reapply the time zone, move the machine out
of the present Central Standard Time zone to any other one then move it
back to the CST zone and apply the settings. You should then see
identical information on all the machines at at the
HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation key.

John

msnews.microsoft.com wrote:
another time key in registry -
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time
Zones\Central Standard Time]

srv1:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time
Zones\Central Standard Time]
"Display"="(GMT-06:00) Central Time (US & Canada)"
"Dlt"="Central Daylight Time"
"Std"="Central Standard Time"
"MapID"="36,37"
"Index"=dword:00000014
"TZI"=hex:98,fe,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,0b,00,00,00,05,00,02,00,00,\
00,00,00,00,00,00,00,03,00,00,00,01,00,02,00,00,00,00,00,00,00

srv2:
"Display"="(GMT-06:00) Central Time (US & Canada)"
"Dlt"="Central Daylight Time"
"Std"="Central Standard Time"
"MapID"="36,37"
"Index"=dword:00000014
"TZI"=hex:68,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,00,00,00,05,00,02,00,00,\
00,00,00,00,00,00,00,03,00,00,00,01,00,02,00,00,00,00,00,00,00

srv3:
"Display"="(GMT-06:00) Central Time (US & Canada)"
"Dlt"="Central Daylight Time"
"Std"="Central Standard Time"
"MapID"="36,37"
"Index"=dword:00000014
"TZI"=hex:68,01,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,00,00,00,05,00,02,00,00,\
00,00,00,00,00,00,00,03,00,00,00,01,00,02,00,00,00,00,00,00,00


As TZEdit.exe tool - shows same on all 3 servers, yet registry is
different.

Questions:
1. How many registries entries need to be checked.
2. Which reg entries are correct?

thanks





"John John - MVP" <audetweld@xxxxxxxxxxx> wrote in message
news:ergYYlazJHA.1380@xxxxxxxxxxxxxxxxxxxxxxx
You can copy the
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
from one machine to another but it will take a reboot for the settings
to be applied, when you do it with the Adjust Time/Date applet the
system applies the settings and no reboot is necessary.

Get the TZEdit.exe tool here:

http://support.microsoft.com/kb/914387

Direct link to the download:
http://download.microsoft.com/download/5/8/a/58a208b7-7dc7-4bc7-8357-28e29cdac52f/tzedit.exe

and use it to check the GMT offset on the Central Time (US & Canada), it
should be GMT-06:00.

John

msnews.microsoft.com wrote:
Registry Info
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]

Srv1: "Bias"=dword:fffffe98
Srv2: "Bias"=dword:00000168
Srv3: "Bias"=dword:00000168

Srv1: "StandardName"="Central Standard Time"
Srv2: "StandardName"="Central Standard Time"
Srv3: "StandardName"="Central Standard Time"

Srv1: "StandardBias"=dword:00000000
Srv2: "StandardBias"=dword:00000000
Srv3: "StandardBias"=dword:00000000

Srv1:
"StandardStart"=hex:00,00,0b,00,05,00,02,00,00,00,00,00,00,00,00,00
Srv2:
"StandardStart"=hex:00,00,0b,00,05,00,02,00,00,00,00,00,00,00,00,00
Srv3:
"StandardStart"=hex:00,00,0b,00,05,00,02,00,00,00,00,00,00,00,00,00

Srv1: "DaylightName"="Central Daylight Time"
Srv2: "DaylightName"="Central Daylight Time"
Srv3: "DaylightName"="Central Daylight Time"

Srv1: "DaylightBias"=dword:ffffffc4
Srv2: "DaylightBias"=dword:ffffffc4
Srv3: "DaylightBias"=dword:ffffffc4

Srv1:
"DaylightStart"=hex:00,00,03,00,01,00,02,00,00,00,00,00,00,00,00,00
Srv2:
"DaylightStart"=hex:00,00,03,00,01,00,02,00,00,00,00,00,00,00,00,00
Srv3:
"DaylightStart"=hex:00,00,03,00,01,00,02,00,00,00,00,00,00,00,00,00

Srv1: "ActiveTimeBias"=dword:fffffe5c
Srv2: "ActiveTimeBias"=dword:0000012c
Srv3: "ActiveTimeBias"=dword:0000012c


It appears that srv1 is the server with the mis-configured registry.
Bias and ActiveTimeBias
srv1 holds all the FSMO roles. and is the server that is set to sync
with outside time source.


Is it ok to edit srv1 registry and change values to match the other
servers?

Thanks

















"John John (MVP)" <audetweld@xxxxxxxxxxx> wrote in message
news:uA8BExXzJHA.1196@xxxxxxxxxxxxxxxxxxxxxxx
Hmmm... What about the Time Zones? Are both machines in the same
zone? If both machines are in the same zone the information at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation
should be indentical. You could copy the key and values from the PDC
to srv2.

John

msnews.microsoft.com wrote:
I can set the time / date properly on srv2. At the next sync
period for srv2, the time on srv2 changes from PM to
AM.... or from AM to PM - it jumps 12 hours.




"John John (MVP)" <audetweld@xxxxxxxxxxx> wrote in message
news:OoiQU%23NzJHA.5728@xxxxxxxxxxxxxxxxxxxxxxx
Probably a stupid suggestion but it sounds like the AM/PM might be
wrong on one of the machines, exactly 12 hour difference...

John

msnews.microsoft.com wrote:
have 2 w2k servers, sp4.
srv1 is PDC ( holds all roles) and is set to sync with NTP server.
srv2 is problem. every time srv2 syncs time, it goes off by 12
hours.
srv2 date and time zone setting are correct. srv2 thinks PDC is
offline, which is not true.
suggestions ? thanks


.

Relevant Pages

  • Re: w2k DC time off by 12 hours
    ... some booking or scheduling/agenda type of programs might do calculations based on the information in these time zone keys and you might miss your flight to Rome because the information in that key was off by 10 hours! ... Your srv1 has an incorrect TZI value at the key in question. ... Export this key from one of your other machines then remove/delete the incorect key on srv1 and merge the key from the good machine to the srv1 registry. ... You could copy the key and values from the PDC to srv2. ...
    (microsoft.public.win2000.general)
  • Re: w2k DC time off by 12 hours
    ... Your srv1 has an incorrect TZI value at the key in question. ... Export this key from one of your other machines then remove/delete the incorect key on srv1 and merge the key from the good machine to the srv1 registry. ... Then use the Time/Date applet and reapply the time zone, move the machine out of the present Central Standard Time zone to any other one then move it back to the CST zone and apply the settings. ... You could copy the key and values from the PDC to srv2. ...
    (microsoft.public.win2000.general)
  • Re: Where is my Timezone
    ... zone your server is configured for. ... Now a question for your disaster recovery team & the disaster recovery site. ... Do they set and/or change the time zone of the recovery machine to their ...
    (microsoft.public.dotnet.framework)
  • Re: AP - Indiana Time Zone Fight Creates New Problems
    ... > one zone east: i.e., the Eastern seaboard becomes Atlantic Standard Time ... there would be no difference between year-round DST and ... simply moving every place one time zone to the east. ...
    (misc.transport.road)
  • Re: Herb Martin...Global Catalog SRV record missing!
    ... Netlogon needs to wait for DNS, but what I don't understand is that the first ... server that I setup (SRV1) never had any problems with this _gc._tcp SRV ... I also recommended he delete the Secondary zone and make the ...
    (microsoft.public.windows.server.dns)