> 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

> 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

"John John (MVP)" <audetw***@nbnot.nb.ca> wrote in message
news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
> 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

> 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)" <audetw***@nbnot.nb.ca> wrote in message
> news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
>> 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
>
>

"John John (MVP)" <audetw***@nbnot.nb.ca> wrote in message
news:uA8BExXzJHA.1196@TK2MSFTNGP03.phx.gbl...
> 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)" <audetw***@nbnot.nb.ca> wrote in message
>> news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
>>> 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
>>

> srv1 - reg info
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
> "Bias"=dword:fffffe98
> "StandardName"="Central Standard Time"
> "StandardBias"=dword:00000000
> "StandardStart"=hex:00,00,0b,00,05,00,02,00,00,00,00,00,00,00,00,00
> "DaylightName"="Central Daylight Time"
> "DaylightBias"=dword:ffffffc4
> "DaylightStart"=hex:00,00,03,00,01,00,02,00,00,00,00,00,00,00,00,00
> "ActiveTimeBias"=dword:fffffe5c
>
> srv2 - reg info
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
> "Bias"=dword:00000168
> "StandardName"="Central Standard Time"
> "StandardBias"=dword:00000000
> "StandardStart"=hex:00,00,0b,00,05,00,02,00,00,00,00,00,00,00,00,00
> "DaylightName"="Central Daylight Time"
> "DaylightBias"=dword:ffffffc4
> "DaylightStart"=hex:00,00,03,00,01,00,02,00,00,00,00,00,00,00,00,00
> "ActiveTimeBias"=dword:0000012c
>
>
> dcdiag output - run from srv2
> C:\tmp>dcdiag
> Domain Controller Diagnosis
> Performing initial setup:
>    Done gathering initial info.
> Doing initial required tests
>    Testing server: Default-First-Site-Name\srv2
>       Starting test: Connectivity
>          ......................... srv2 passed test Connectivity
> Doing primary tests
>    Testing server: Default-First-Site-Name\srv2
>       Starting test: Replications
>          ......................... srv2 passed test Replications
>       Starting test: NCSecDesc
>          ......................... srv2 passed test NCSecDesc
>       Starting test: NetLogons
>          ......................... srv2 passed test NetLogons
>       Starting test: Advertising
>          ......................... srv2 passed test Advertising
>       Starting test: KnowsOfRoleHolders
>          ......................... srv2 passed test KnowsOfRoleHolders
>       Starting test: RidManager
>          ......................... srv2 passed test RidManager
>       Starting test: MachineAccount
>          ......................... srv2 passed test MachineAccount
>       Starting test: Services
>          ......................... srv2 passed test Services
>       Starting test: ObjectsReplicated
>          ......................... srv2 passed test ObjectsReplicated
>       Starting test: frssysvol
>          ......................... srv2 passed test frssysvol
>       Starting test: kccevent
>          ......................... srv2 passed test kccevent
>       Starting test: systemlog
>          ......................... srv2 passed test systemlog
>    Running enterprise tests on : jumper.local
>       Starting test: Intersite
>          ......................... jumper.local passed test Intersite
>       Starting test: FsmoCheck
>          ......................... jumper.local passed test FsmoCheck
>
> C:\tmp>
>
> I can set the time on srv2 to correct time.  However, when system does sync,
> it goes back 12 hours.
>
> Thanks
>
>
>
>
>
>
>
>
> "John John (MVP)" <audetw***@nbnot.nb.ca> wrote in message
> news:uA8BExXzJHA.1196@TK2MSFTNGP03.phx.gbl...
>> 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)" <audetw***@nbnot.nb.ca> wrote in message
>>> news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
>>>> 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
>

"John John (MVP)" <audetw***@nbnot.nb.ca> wrote in message
news:uA8BExXzJHA.1196@TK2MSFTNGP03.phx.gbl...
> 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)" <audetw***@nbnot.nb.ca> wrote in message
>> news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
>>> 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
>>

> 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)" <audetw***@nbnot.nb.ca> wrote in message
> news:uA8BExXzJHA.1196@TK2MSFTNGP03.phx.gbl...
>> 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)" <audetw***@nbnot.nb.ca> wrote in message
>>> news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
>>>> 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
>

"John John - MVP" <audetw***@nbnot.nb.ca> wrote in message
news:ergYYlazJHA.1380@TK2MSFTNGP05.phx.gbl...
> 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)" <audetw***@nbnot.nb.ca> wrote in message
>> news:uA8BExXzJHA.1196@TK2MSFTNGP03.phx.gbl...
>>> 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)" <audetw***@nbnot.nb.ca> wrote in message
>>>> news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
>>>>> 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
>>

"John John - MVP" <audetw***@nbnot.nb.ca> wrote in message
news:ergYYlazJHA.1380@TK2MSFTNGP05.phx.gbl...
> 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)" <audetw***@nbnot.nb.ca> wrote in message
>> news:uA8BExXzJHA.1196@TK2MSFTNGP03.phx.gbl...
>>> 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)" <audetw***@nbnot.nb.ca> wrote in message
>>>> news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
>>>>> 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
>>

> 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" <audetw***@nbnot.nb.ca> wrote in message
> news:ergYYlazJHA.1380@TK2MSFTNGP05.phx.gbl...
>> 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)" <audetw***@nbnot.nb.ca> wrote in message
>>> news:uA8BExXzJHA.1196@TK2MSFTNGP03.phx.gbl...
>>>> 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)" <audetw***@nbnot.nb.ca> wrote in message
>>>>> news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
>>>>>> 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
>
>

"John John - MVP" <audetw***@nbnot.nb.ca> wrote in message
news:e6NmZCczJHA.4808@TK2MSFTNGP06.phx.gbl...
> 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" <audetw***@nbnot.nb.ca> wrote in message
>> news:ergYYlazJHA.1380@TK2MSFTNGP05.phx.gbl...
>>> 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)" <audetw***@nbnot.nb.ca> wrote in message
>>>> news:uA8BExXzJHA.1196@TK2MSFTNGP03.phx.gbl...
>>>>> 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)" <audetw***@nbnot.nb.ca> wrote in message
>>>>>> news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
>>>>>>> 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
>>

> 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" <audetw***@nbnot.nb.ca> wrote in message
> news:e6NmZCczJHA.4808@TK2MSFTNGP06.phx.gbl...
>> 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" <audetw***@nbnot.nb.ca> wrote in message
>>> news:ergYYlazJHA.1380@TK2MSFTNGP05.phx.gbl...
>>>> 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)" <audetw***@nbnot.nb.ca> wrote in message
>>>>> news:uA8BExXzJHA.1196@TK2MSFTNGP03.phx.gbl...
>>>>>> 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)" <audetw***@nbnot.nb.ca> wrote in message
>>>>>>> news:OoiQU%23NzJHA.5728@TK2MSFTNGP03.phx.gbl...
>>>>>>>> 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
>