How do I confirm that my time server is running and that my work stations are pointed to it?

[Greg O]

You don't need to set it in the registry, if you do then you could damage
the installation. You use the Group Policy (in the case of a domain) or
Local Security (in the case of a member server) console in Administrative
Tools. All those settings are in there.


"Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
news:eKz6efvyHHA.1204@TK2MSFTNGP03.phx.gbl...
> is this one a valid entry?
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
> "NtpServer"="time-a.nist.gov, 0X1"
>
> When I run "w32tm /resync" on the DC it updates the time on the server
> fine, but I get the following event in Event Viewer (with a red stop sign)
>
> ++++++++++++++++++++++++++++++++
> Event Type: Error
> Event Source: W32Time
> Event Category: None
> Event ID: 17
> Date: 7/20/2007
> Time: 12:40:59 PM
> User: N/A
> Computer: SERVERNAME
> Description:
> Time Provider NtpClient: An error occurred during DNS lookup of the
> manually configured peer '0X1'. NtpClient will try the DNS lookup again in
> 15 minutes. The error was: No such service is known. The service cannot be
> found in the specified name space. (0x8007277C)
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ++++++++++++++++++++++++++++++++
>
> Any ideas?
>
> Kelvin
>
>
> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
> news:Owrn35uyHHA.1208@TK2MSFTNGP03.phx.gbl...
>> Ok this artical has lists, how does one enter this in the registy?
>> http://support.microsoft.com/kb/262680/en-us
>>
>> Thanks
>>
>> Kelvin
>>
>>
>> "Greg O" <none@all.com> wrote in message
>> news:emUqNFpyHHA.3908@TK2MSFTNGP05.phx.gbl...
>>> This should explain it:
>>>
>>> http://www.microsoft.com/technet/pr.../technologies/security/ws03mngd/26_s3wts.mspx
>>>
>>>
>>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>>> news:uHT$XMhyHHA.748@TK2MSFTNGP04.phx.gbl...
>>>> Hi Greg
>>>>
>>>> "You need to set up the time service in Group Policy" can you give me a
>>>> little more to go on to look this up?
>>>>
>>>> Thanks
>>>>
>>>> Kelvin
>>>>
>>>> "Greg O" <gregorme@gmail.com> wrote in message
>>>> news:1184829962.603065.182880@z28g2000prd.googlegroups.com...
>>>>> On Jul 17, 12:35 pm, "Kelvin Beaton" <kelvin at mccsa dot com> wrote:
>>>>>> I have a Windows 2003 server that is my DC.
>>>>>> My XP SP2 workstations are not getting their time from that server.
>>>>>> Their
>>>>>> times are not the same anyway.
>>>>>> All the workstations are port of my domain.
>>>>>>
>>>>>> Is there a good check list I can go throught to make sure everything
>>>>>> is
>>>>>> configured correclty?
>>>>>>
>>>>>> The Windows Time service is running and is set to start
>>>>>> automatically.
>>>>>> Event view doesn't have any Time Service event that I can see.
>>>>>>
>>>>>> Where do I find the "Peerlist" ?
>>>>>>
>>>>>> If I change the time on my DC, how long should I have to wait to see
>>>>>> it
>>>>>> change back to the correct time?
>>>>>> How long should it take on the work station?
>>>>>>
>>>>>> Any help would be appreciated!
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> Kelvin
>>>>>
>>>>> You need to set up the time service in Group Policy.
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

 

[Kelvin Beaton]

Ok, where in GP are these settings? I've looked and can't see them...

Now that I've been trying to do this other then using the GP how do I get
the registry back to the default state it was in?

Thanks

Kelvin


"Greg O" <none@all.com> wrote in message
news:%23wSfID1yHHA.484@TK2MSFTNGP06.phx.gbl...
> You don't need to set it in the registry, if you do then you could damage
> the installation. You use the Group Policy (in the case of a domain) or
> Local Security (in the case of a member server) console in Administrative
> Tools. All those settings are in there.
>
>
> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
> news:eKz6efvyHHA.1204@TK2MSFTNGP03.phx.gbl...
>> is this one a valid entry?
>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
>> "NtpServer"="time-a.nist.gov, 0X1"
>>
>> When I run "w32tm /resync" on the DC it updates the time on the server
>> fine, but I get the following event in Event Viewer (with a red stop
>> sign)
>>
>> ++++++++++++++++++++++++++++++++
>> Event Type: Error
>> Event Source: W32Time
>> Event Category: None
>> Event ID: 17
>> Date: 7/20/2007
>> Time: 12:40:59 PM
>> User: N/A
>> Computer: SERVERNAME
>> Description:
>> Time Provider NtpClient: An error occurred during DNS lookup of the
>> manually configured peer '0X1'. NtpClient will try the DNS lookup again
>> in 15 minutes. The error was: No such service is known. The service
>> cannot be found in the specified name space. (0x8007277C)
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> ++++++++++++++++++++++++++++++++
>>
>> Any ideas?
>>
>> Kelvin
>>
>>
>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>> news:Owrn35uyHHA.1208@TK2MSFTNGP03.phx.gbl...
>>> Ok this artical has lists, how does one enter this in the registy?
>>> http://support.microsoft.com/kb/262680/en-us
>>>
>>> Thanks
>>>
>>> Kelvin
>>>
>>>
>>> "Greg O" <none@all.com> wrote in message
>>> news:emUqNFpyHHA.3908@TK2MSFTNGP05.phx.gbl...
>>>> This should explain it:
>>>>
>>>> http://www.microsoft.com/technet/pr.../technologies/security/ws03mngd/26_s3wts.mspx
>>>>
>>>>
>>>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>>>> news:uHT$XMhyHHA.748@TK2MSFTNGP04.phx.gbl...
>>>>> Hi Greg
>>>>>
>>>>> "You need to set up the time service in Group Policy" can you give me
>>>>> a little more to go on to look this up?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Kelvin
>>>>>
>>>>> "Greg O" <gregorme@gmail.com> wrote in message
>>>>> news:1184829962.603065.182880@z28g2000prd.googlegroups.com...
>>>>>> On Jul 17, 12:35 pm, "Kelvin Beaton" <kelvin at mccsa dot com> wrote:
>>>>>>> I have a Windows 2003 server that is my DC.
>>>>>>> My XP SP2 workstations are not getting their time from that server.
>>>>>>> Their
>>>>>>> times are not the same anyway.
>>>>>>> All the workstations are port of my domain.
>>>>>>>
>>>>>>> Is there a good check list I can go throught to make sure everything
>>>>>>> is
>>>>>>> configured correclty?
>>>>>>>
>>>>>>> The Windows Time service is running and is set to start
>>>>>>> automatically.
>>>>>>> Event view doesn't have any Time Service event that I can see.
>>>>>>>
>>>>>>> Where do I find the "Peerlist" ?
>>>>>>>
>>>>>>> If I change the time on my DC, how long should I have to wait to see
>>>>>>> it
>>>>>>> change back to the correct time?
>>>>>>> How long should it take on the work station?
>>>>>>>
>>>>>>> Any help would be appreciated!
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> Kelvin
>>>>>>
>>>>>> You need to set up the time service in Group Policy.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

 

[Greg O]

You shouldn't touch the registry without backing up the keys. However if you
set the group policy it might fix any wrong settings you may have made
there. You go to to the group policy management console in administrative
tools, or on 2003 servers without the GPMC addon you go to Active Directory
Users and Computers and right click on the domain name, or OU or whatever
you are applying the group policy on. Then you go to computer
management/Administrative Templates/System/Windows Time Service and adjust
the settings according to the Microsoft link I posted earlier.


"Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
news:ubWIMtUzHHA.3908@TK2MSFTNGP05.phx.gbl...
> Ok, where in GP are these settings? I've looked and can't see them...
>
> Now that I've been trying to do this other then using the GP how do I get
> the registry back to the default state it was in?
>
> Thanks
>
> Kelvin
>
>
> "Greg O" <none@all.com> wrote in message
> news:%23wSfID1yHHA.484@TK2MSFTNGP06.phx.gbl...
>> You don't need to set it in the registry, if you do then you could damage
>> the installation. You use the Group Policy (in the case of a domain) or
>> Local Security (in the case of a member server) console in Administrative
>> Tools. All those settings are in there.
>>
>>
>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>> news:eKz6efvyHHA.1204@TK2MSFTNGP03.phx.gbl...
>>> is this one a valid entry?
>>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
>>> "NtpServer"="time-a.nist.gov, 0X1"
>>>
>>> When I run "w32tm /resync" on the DC it updates the time on the server
>>> fine, but I get the following event in Event Viewer (with a red stop
>>> sign)
>>>
>>> ++++++++++++++++++++++++++++++++
>>> Event Type: Error
>>> Event Source: W32Time
>>> Event Category: None
>>> Event ID: 17
>>> Date: 7/20/2007
>>> Time: 12:40:59 PM
>>> User: N/A
>>> Computer: SERVERNAME
>>> Description:
>>> Time Provider NtpClient: An error occurred during DNS lookup of the
>>> manually configured peer '0X1'. NtpClient will try the DNS lookup again
>>> in 15 minutes. The error was: No such service is known. The service
>>> cannot be found in the specified name space. (0x8007277C)
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>> ++++++++++++++++++++++++++++++++
>>>
>>> Any ideas?
>>>
>>> Kelvin
>>>
>>>
>>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>>> news:Owrn35uyHHA.1208@TK2MSFTNGP03.phx.gbl...
>>>> Ok this artical has lists, how does one enter this in the registy?
>>>> http://support.microsoft.com/kb/262680/en-us
>>>>
>>>> Thanks
>>>>
>>>> Kelvin
>>>>
>>>>
>>>> "Greg O" <none@all.com> wrote in message
>>>> news:emUqNFpyHHA.3908@TK2MSFTNGP05.phx.gbl...
>>>>> This should explain it:
>>>>>
>>>>> http://www.microsoft.com/technet/pr.../technologies/security/ws03mngd/26_s3wts.mspx
>>>>>
>>>>>
>>>>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>>>>> news:uHT$XMhyHHA.748@TK2MSFTNGP04.phx.gbl...
>>>>>> Hi Greg
>>>>>>
>>>>>> "You need to set up the time service in Group Policy" can you give me
>>>>>> a little more to go on to look this up?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Kelvin
>>>>>>
>>>>>> "Greg O" <gregorme@gmail.com> wrote in message
>>>>>> news:1184829962.603065.182880@z28g2000prd.googlegroups.com...
>>>>>>> On Jul 17, 12:35 pm, "Kelvin Beaton" <kelvin at mccsa dot com>
>>>>>>> wrote:
>>>>>>>> I have a Windows 2003 server that is my DC.
>>>>>>>> My XP SP2 workstations are not getting their time from that server.
>>>>>>>> Their
>>>>>>>> times are not the same anyway.
>>>>>>>> All the workstations are port of my domain.
>>>>>>>>
>>>>>>>> Is there a good check list I can go throught to make sure
>>>>>>>> everything is
>>>>>>>> configured correclty?
>>>>>>>>
>>>>>>>> The Windows Time service is running and is set to start
>>>>>>>> automatically.
>>>>>>>> Event view doesn't have any Time Service event that I can see.
>>>>>>>>
>>>>>>>> Where do I find the "Peerlist" ?
>>>>>>>>
>>>>>>>> If I change the time on my DC, how long should I have to wait to
>>>>>>>> see it
>>>>>>>> change back to the correct time?
>>>>>>>> How long should it take on the work station?
>>>>>>>>
>>>>>>>> Any help would be appreciated!
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> Kelvin
>>>>>>>
>>>>>>> You need to set up the time service in Group Policy.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

 

[Bruce Sanderson]

Kelvin:

1. the w32tm command sets the appropriate registry entries correctly
1.a. the command
w32tm /config /syncfromflags:manual
will set the registry entry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters!Type
to "NTP"

1.b. the command
w32tm /config /manualpeerlist:time-a.nist.gov
will set the registry entry at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters!NtpServer
to "time-a.nist.gov" - note that the "0X01" is NOT required. If you have a
space between "time-a.nist.gov," and "0x1", the time service will try to get
time from a computer with the DNS name "0x1", which, of course, does not
exist.

1.c. the command
w32tm /config /reliable:YES
will, on Domain Controllers, configure this computer as a "reliable
time source", which is suggested for the Domain Controller that is at the
root of the domain hierarchy, which is where the rest of the domain will
synchronize from.

1.d the command
w32tm /config /update
will instruct the time service to re-read the registry entries

1.e the command
w32tm /resync /rediscover
will instruct the time service to retrieve time from the specified time
sources, after redetecting the network configuration and rediscovering the
time sources


The commmand w32tm /? will give you help information on all the available
options for the w32tm command.

2. if you have made settings in a GPO for the Time Service, all of the
settings you can make for the Time Service via GPO are "true policies",
which means that anything in
Computer Configuration
Administrative Templates
System
Windows Time Service
will be automatically undone on the target computers if you either:

2.a. change the settings to "Not Configured"
or
2.b unlink (delete) the GPO from the OU containing the targeted computers
or
2.c move the computer accounts to an OU that is not in the scope of the GPO

The settings made the "Windows Time Service" configuration in the GPO
actually go into the registry at
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\w32time. When you remove the
computer from the scope of the GPO, these settings are removed. The way
this work is that the values set in the Policies part of the registry, if
they exist, are used by the service instead of the ones at the "normal"
place in the registry. The settings at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time are not changed
by the GPO, so when the GPO is removed (the computer falls out of scope and
the group policy settings are refreshed), the time service will revert to
using whatever is in the ...Services\W32Time key.

Note that the Windows Time Service settings are "boot" time settings; they
will only get removed if the target computer is restarted or the gpupdate
/force /boot command is used on the target computer.

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
news:ubWIMtUzHHA.3908@TK2MSFTNGP05.phx.gbl...
> Ok, where in GP are these settings? I've looked and can't see them...
>
> Now that I've been trying to do this other then using the GP how do I get
> the registry back to the default state it was in?
>
> Thanks
>
> Kelvin
>
>
> "Greg O" <none@all.com> wrote in message
> news:%23wSfID1yHHA.484@TK2MSFTNGP06.phx.gbl...
>> You don't need to set it in the registry, if you do then you could damage
>> the installation. You use the Group Policy (in the case of a domain) or
>> Local Security (in the case of a member server) console in Administrative
>> Tools. All those settings are in there.
>>
>>
>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>> news:eKz6efvyHHA.1204@TK2MSFTNGP03.phx.gbl...
>>> is this one a valid entry?
>>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
>>> "NtpServer"="time-a.nist.gov, 0X1"
>>>
>>> When I run "w32tm /resync" on the DC it updates the time on the server
>>> fine, but I get the following event in Event Viewer (with a red stop
>>> sign)
>>>
>>> ++++++++++++++++++++++++++++++++
>>> Event Type: Error
>>> Event Source: W32Time
>>> Event Category: None
>>> Event ID: 17
>>> Date: 7/20/2007
>>> Time: 12:40:59 PM
>>> User: N/A
>>> Computer: SERVERNAME
>>> Description:
>>> Time Provider NtpClient: An error occurred during DNS lookup of the
>>> manually configured peer '0X1'. NtpClient will try the DNS lookup again
>>> in 15 minutes. The error was: No such service is known. The service
>>> cannot be found in the specified name space. (0x8007277C)
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>> ++++++++++++++++++++++++++++++++
>>>
>>> Any ideas?
>>>
>>> Kelvin
>>>
>>>
>>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>>> news:Owrn35uyHHA.1208@TK2MSFTNGP03.phx.gbl...
>>>> Ok this artical has lists, how does one enter this in the registy?
>>>> http://support.microsoft.com/kb/262680/en-us
>>>>
>>>> Thanks
>>>>
>>>> Kelvin
>>>>
>>>>
>>>> "Greg O" <none@all.com> wrote in message
>>>> news:emUqNFpyHHA.3908@TK2MSFTNGP05.phx.gbl...
>>>>> This should explain it:
>>>>>
>>>>> http://www.microsoft.com/technet/pr.../technologies/security/ws03mngd/26_s3wts.mspx
>>>>>
>>>>>
>>>>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>>>>> news:uHT$XMhyHHA.748@TK2MSFTNGP04.phx.gbl...
>>>>>> Hi Greg
>>>>>>
>>>>>> "You need to set up the time service in Group Policy" can you give me
>>>>>> a little more to go on to look this up?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Kelvin
>>>>>>
>>>>>> "Greg O" <gregorme@gmail.com> wrote in message
>>>>>> news:1184829962.603065.182880@z28g2000prd.googlegroups.com...
>>>>>>> On Jul 17, 12:35 pm, "Kelvin Beaton" <kelvin at mccsa dot com>
>>>>>>> wrote:
>>>>>>>> I have a Windows 2003 server that is my DC.
>>>>>>>> My XP SP2 workstations are not getting their time from that server.
>>>>>>>> Their
>>>>>>>> times are not the same anyway.
>>>>>>>> All the workstations are port of my domain.
>>>>>>>>
>>>>>>>> Is there a good check list I can go throught to make sure
>>>>>>>> everything is
>>>>>>>> configured correclty?
>>>>>>>>
>>>>>>>> The Windows Time service is running and is set to start
>>>>>>>> automatically.
>>>>>>>> Event view doesn't have any Time Service event that I can see.
>>>>>>>>
>>>>>>>> Where do I find the "Peerlist" ?
>>>>>>>>
>>>>>>>> If I change the time on my DC, how long should I have to wait to
>>>>>>>> see it
>>>>>>>> change back to the correct time?
>>>>>>>> How long should it take on the work station?
>>>>>>>>
>>>>>>>> Any help would be appreciated!
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> Kelvin
>>>>>>>
>>>>>>> You need to set up the time service in Group Policy.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

 

[Kelvin Beaton]

Hi Bruce

Thanks for the detailed reply!!!

My server seems to be running just fine.

Now I need to confirm that my work stations are working correctly...

If I run W32TM /resync should this set the time on my PC?
I can't see that I have any GPO with Windows Time setting configured.

I'm thinking with all my fiddling around that I've got my PC messed up...

Can you help me with the rest of this?

Thanks!!

Kelvin


"Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message
news:5F3536DE-C296-4300-A2EB-18D409774F7E@microsoft.com...
> Kelvin:
>
> 1. the w32tm command sets the appropriate registry entries correctly
> 1.a. the command
> w32tm /config /syncfromflags:manual
> will set the registry entry
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters!Type
> to "NTP"
>
> 1.b. the command
> w32tm /config /manualpeerlist:time-a.nist.gov
> will set the registry entry at
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters!NtpServer
> to "time-a.nist.gov" - note that the "0X01" is NOT required. If you have a
> space between "time-a.nist.gov," and "0x1", the time service will try to
> get time from a computer with the DNS name "0x1", which, of course, does
> not exist.
>
> 1.c. the command
> w32tm /config /reliable:YES
> will, on Domain Controllers, configure this computer as a "reliable
> time source", which is suggested for the Domain Controller that is at the
> root of the domain hierarchy, which is where the rest of the domain will
> synchronize from.
>
> 1.d the command
> w32tm /config /update
> will instruct the time service to re-read the registry entries
>
> 1.e the command
> w32tm /resync /rediscover
> will instruct the time service to retrieve time from the specified time
> sources, after redetecting the network configuration and rediscovering the
> time sources
>
>
> The commmand w32tm /? will give you help information on all the available
> options for the w32tm command.
>
> 2. if you have made settings in a GPO for the Time Service, all of the
> settings you can make for the Time Service via GPO are "true policies",
> which means that anything in
> Computer Configuration
> Administrative Templates
> System
> Windows Time Service
> will be automatically undone on the target computers if you either:
>
> 2.a. change the settings to "Not Configured"
> or
> 2.b unlink (delete) the GPO from the OU containing the targeted computers
> or
> 2.c move the computer accounts to an OU that is not in the scope of the
> GPO
>
> The settings made the "Windows Time Service" configuration in the GPO
> actually go into the registry at
> HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\w32time. When you remove
> the computer from the scope of the GPO, these settings are removed. The
> way this work is that the values set in the Policies part of the registry,
> if they exist, are used by the service instead of the ones at the "normal"
> place in the registry. The settings at
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time are not
> changed by the GPO, so when the GPO is removed (the computer falls out of
> scope and the group policy settings are refreshed), the time service will
> revert to using whatever is in the ...Services\W32Time key.
>
> Note that the Windows Time Service settings are "boot" time settings; they
> will only get removed if the target computer is restarted or the gpupdate
> /force /boot command is used on the target computer.
>
> --
> Bruce Sanderson MVP Printing
> http://members.shaw.ca/bsanders
>
> It is perfectly useless to know the right answer to the wrong question.
>
>
>
> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
> news:ubWIMtUzHHA.3908@TK2MSFTNGP05.phx.gbl...
>> Ok, where in GP are these settings? I've looked and can't see them...
>>
>> Now that I've been trying to do this other then using the GP how do I get
>> the registry back to the default state it was in?
>>
>> Thanks
>>
>> Kelvin
>>
>>
>> "Greg O" <none@all.com> wrote in message
>> news:%23wSfID1yHHA.484@TK2MSFTNGP06.phx.gbl...
>>> You don't need to set it in the registry, if you do then you could
>>> damage the installation. You use the Group Policy (in the case of a
>>> domain) or Local Security (in the case of a member server) console in
>>> Administrative Tools. All those settings are in there.
>>>
>>>
>>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>>> news:eKz6efvyHHA.1204@TK2MSFTNGP03.phx.gbl...
>>>> is this one a valid entry?
>>>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
>>>> "NtpServer"="time-a.nist.gov, 0X1"
>>>>
>>>> When I run "w32tm /resync" on the DC it updates the time on the server
>>>> fine, but I get the following event in Event Viewer (with a red stop
>>>> sign)
>>>>
>>>> ++++++++++++++++++++++++++++++++
>>>> Event Type: Error
>>>> Event Source: W32Time
>>>> Event Category: None
>>>> Event ID: 17
>>>> Date: 7/20/2007
>>>> Time: 12:40:59 PM
>>>> User: N/A
>>>> Computer: SERVERNAME
>>>> Description:
>>>> Time Provider NtpClient: An error occurred during DNS lookup of the
>>>> manually configured peer '0X1'. NtpClient will try the DNS lookup again
>>>> in 15 minutes. The error was: No such service is known. The service
>>>> cannot be found in the specified name space. (0x8007277C)
>>>>
>>>> For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>> ++++++++++++++++++++++++++++++++
>>>>
>>>> Any ideas?
>>>>
>>>> Kelvin
>>>>
>>>>
>>>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>>>> news:Owrn35uyHHA.1208@TK2MSFTNGP03.phx.gbl...
>>>>> Ok this artical has lists, how does one enter this in the registy?
>>>>> http://support.microsoft.com/kb/262680/en-us
>>>>>
>>>>> Thanks
>>>>>
>>>>> Kelvin
>>>>>
>>>>>
>>>>> "Greg O" <none@all.com> wrote in message
>>>>> news:emUqNFpyHHA.3908@TK2MSFTNGP05.phx.gbl...
>>>>>> This should explain it:
>>>>>>
>>>>>> http://www.microsoft.com/technet/pr.../technologies/security/ws03mngd/26_s3wts.mspx
>>>>>>
>>>>>>
>>>>>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>>>>>> news:uHT$XMhyHHA.748@TK2MSFTNGP04.phx.gbl...
>>>>>>> Hi Greg
>>>>>>>
>>>>>>> "You need to set up the time service in Group Policy" can you give
>>>>>>> me a little more to go on to look this up?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Kelvin
>>>>>>>
>>>>>>> "Greg O" <gregorme@gmail.com> wrote in message
>>>>>>> news:1184829962.603065.182880@z28g2000prd.googlegroups.com...
>>>>>>>> On Jul 17, 12:35 pm, "Kelvin Beaton" <kelvin at mccsa dot com>
>>>>>>>> wrote:
>>>>>>>>> I have a Windows 2003 server that is my DC.
>>>>>>>>> My XP SP2 workstations are not getting their time from that
>>>>>>>>> server. Their
>>>>>>>>> times are not the same anyway.
>>>>>>>>> All the workstations are port of my domain.
>>>>>>>>>
>>>>>>>>> Is there a good check list I can go throught to make sure
>>>>>>>>> everything is
>>>>>>>>> configured correclty?
>>>>>>>>>
>>>>>>>>> The Windows Time service is running and is set to start
>>>>>>>>> automatically.
>>>>>>>>> Event view doesn't have any Time Service event that I can see.
>>>>>>>>>
>>>>>>>>> Where do I find the "Peerlist" ?
>>>>>>>>>
>>>>>>>>> If I change the time on my DC, how long should I have to wait to
>>>>>>>>> see it
>>>>>>>>> change back to the correct time?
>>>>>>>>> How long should it take on the work station?
>>>>>>>>>
>>>>>>>>> Any help would be appreciated!
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>> Kelvin
>>>>>>>>
>>>>>>>> You need to set up the time service in Group Policy.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>

 

[Bruce Sanderson]

The same commands should work on the clients (XP and later). There is no
need to have a GPO to configure the time. You only need to do that if you
want to do something abnormal.

For the clients, use the command:

w32tm /config /syncfromflags:domhier
w32tm /config /update
w32tm /resync /rediscover

Unless you have really done something peculiar, this should rectify the
situation. When "syncfromflags" is set to "domhier" the "peer list" is
ignored. The Value "Type" in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
should be "NT5DS" after the first command above.

You should see (on the client) Event Log entries from the Time Service
indicating success or otherwise, especially just after the OS starts (e.g.
after a restart).

When a computer is "joined" to the domain, "Type" is set to "NT5DS"
automatically - there's usually no reason to adjust the Time Service
parameters on clients.

Sometimes I test that the "resync" is working by using Control Panel, Date
and Time to change the local machine's (client's) time to be off by a few
minutes, then issuing the "resync" command. If the Time Service is working
correctly, the time should jump back to being correct.

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"Kelvin Beaton" <kelvin dot beaton at mccsa dot c o m> wrote in message
news:eSITvSjzHHA.5476@TK2MSFTNGP03.phx.gbl...
> Hi Bruce
>
> Thanks for the detailed reply!!!
>
> My server seems to be running just fine.
>
> Now I need to confirm that my work stations are working correctly...
>
> If I run W32TM /resync should this set the time on my PC?
> I can't see that I have any GPO with Windows Time setting configured.
>
> I'm thinking with all my fiddling around that I've got my PC messed up...
>
> Can you help me with the rest of this?
>
> Thanks!!
>
> Kelvin
>
>
> "Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message
> news:5F3536DE-C296-4300-A2EB-18D409774F7E@microsoft.com...
>> Kelvin:
>>
>> 1. the w32tm command sets the appropriate registry entries correctly
>> 1.a. the command
>> w32tm /config /syncfromflags:manual
>> will set the registry entry
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters!Type
>> to "NTP"
>>
>> 1.b. the command
>> w32tm /config /manualpeerlist:time-a.nist.gov
>> will set the registry entry at
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters!NtpServer
>> to "time-a.nist.gov" - note that the "0X01" is NOT required. If you have
>> a space between "time-a.nist.gov," and "0x1", the time service will try
>> to get time from a computer with the DNS name "0x1", which, of course,
>> does not exist.
>>
>> 1.c. the command
>> w32tm /config /reliable:YES
>> will, on Domain Controllers, configure this computer as a "reliable
>> time source", which is suggested for the Domain Controller that is at the
>> root of the domain hierarchy, which is where the rest of the domain will
>> synchronize from.
>>
>> 1.d the command
>> w32tm /config /update
>> will instruct the time service to re-read the registry entries
>>
>> 1.e the command
>> w32tm /resync /rediscover
>> will instruct the time service to retrieve time from the specified time
>> sources, after redetecting the network configuration and rediscovering
>> the time sources
>>
>>
>> The commmand w32tm /? will give you help information on all the available
>> options for the w32tm command.
>>
>> 2. if you have made settings in a GPO for the Time Service, all of the
>> settings you can make for the Time Service via GPO are "true policies",
>> which means that anything in
>> Computer Configuration
>> Administrative Templates
>> System
>> Windows Time Service
>> will be automatically undone on the target computers if you either:
>>
>> 2.a. change the settings to "Not Configured"
>> or
>> 2.b unlink (delete) the GPO from the OU containing the targeted computers
>> or
>> 2.c move the computer accounts to an OU that is not in the scope of the
>> GPO
>>
>> The settings made the "Windows Time Service" configuration in the GPO
>> actually go into the registry at
>> HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\w32time. When you remove
>> the computer from the scope of the GPO, these settings are removed. The
>> way this work is that the values set in the Policies part of the
>> registry, if they exist, are used by the service instead of the ones at
>> the "normal" place in the registry. The settings at
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time are not
>> changed by the GPO, so when the GPO is removed (the computer falls out of
>> scope and the group policy settings are refreshed), the time service will
>> revert to using whatever is in the ...Services\W32Time key.
>>
>> Note that the Windows Time Service settings are "boot" time settings;
>> they will only get removed if the target computer is restarted or the
>> gpupdate /force /boot command is used on the target computer.
>>
>> --
>> Bruce Sanderson MVP Printing
>> http://members.shaw.ca/bsanders
>>
>> It is perfectly useless to know the right answer to the wrong question.
>>
>>
>>
>> "Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
>> news:ubWIMtUzHHA.3908@TK2MSFTNGP05.phx.gbl...
>>> Ok, where in GP are these settings? I've looked and can't see them...
>>>
>>> Now that I've been trying to do this other then using the GP how do I
>>> get the registry back to the default state it was in?
>>>
>>> Thanks
>>>
>>> Kelvin
>>>
>>>

 

[Sasha B]

"Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message
news:288304D3-55A4-458E-A3BD-B2F7737E99AD@microsoft.com...
> The same commands should work on the clients (XP and later). There is no
> need to have a GPO to configure the time. You only need to do that if you
> want to do something abnormal.
>
> For the clients, use the command:
>
> w32tm /config /syncfromflags:domhier
> w32tm /config /update
> w32tm /resync /rediscover
>

> --
> Bruce Sanderson MVP Printing
> http://members.shaw.ca/bsanders
>
> It is perfectly useless to know the right answer to the wrong question.
>
Should I do it on every machine?!

 

[Bruce Sanderson]

Sasha: when a computer is joined to a domain, part of the joining process
does the equivalent of those commands, so, usually, one doesn't need to do
anything for computers in a domain (except on the Domain Controller that is
the root of the time synchronization hierarchy - usually the Domain
Controller that holds the PDC Emulator FSMO role for the root domain in the
Forest).

These commands would only be necessary on domain members that for some
reason have had their time synchronization modified from the default by
someone.

For computers that are NOT domain members, the "/syncfromflags:domier"
setting has no meaning - the computer will use the configured "peer list" .
The default for computers that are NOT domain members is:
/syncfromflags:manual /manualpeerlist:time.windows.com.
This default also usually works fine, unless there is a firewall or
something else blocking the NTP protocol between the computer and the
time.windows.com server.

So, without understanding more about the context of the question, I'd say
no - the Windows Time Service "should be" correctly configured already (by
default). If there are no Event Log entries from the Time Service on the
machines indicating a problem, you're most likely OK.


--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"Sasha B" <ABassin@unitymgmt.com> wrote in message
news:eOp3gYu0HHA.2484@TK2MSFTNGP06.phx.gbl...
>
> "Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message
> news:288304D3-55A4-458E-A3BD-B2F7737E99AD@microsoft.com...
>> The same commands should work on the clients (XP and later). There is no
>> need to have a GPO to configure the time. You only need to do that if
>> you want to do something abnormal.
>>
>> For the clients, use the command:
>>
>> w32tm /config /syncfromflags:domhier
>> w32tm /config /update
>> w32tm /resync /rediscover
>>
>
>> --
>> Bruce Sanderson MVP Printing
>> http://members.shaw.ca/bsanders
>>
>> It is perfectly useless to know the right answer to the wrong question.
>>
> Should I do it on every machine?!
>

 

[Sasha B]

Thank you, Bruce.

"Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message
news:5EFDAB02-C4F2-4239-B8A8-B79BD92A06B6@microsoft.com...
> Sasha: when a computer is joined to a domain, part of the joining process
> does the equivalent of those commands, so, usually, one doesn't need to do
> anything for computers in a domain (except on the Domain Controller that
> is the root of the time synchronization hierarchy - usually the Domain
> Controller that holds the PDC Emulator FSMO role for the root domain in
> the Forest).
>
> These commands would only be necessary on domain members that for some
> reason have had their time synchronization modified from the default by
> someone.
>
> For computers that are NOT domain members, the "/syncfromflags:domier"
> setting has no meaning - the computer will use the configured "peer list"
> . The default for computers that are NOT domain members is:
> /syncfromflags:manual /manualpeerlist:time.windows.com.
> This default also usually works fine, unless there is a firewall or
> something else blocking the NTP protocol between the computer and the
> time.windows.com server.
>
> So, without understanding more about the context of the question, I'd say
> no - the Windows Time Service "should be" correctly configured already (by
> default). If there are no Event Log entries from the Time Service on the
> machines indicating a problem, you're most likely OK.
>
>
> --
> Bruce Sanderson MVP Printing
> http://members.shaw.ca/bsanders
>
> It is perfectly useless to know the right answer to the wrong question.
>
>
>
> "Sasha B" <ABassin@unitymgmt.com> wrote in message
> news:eOp3gYu0HHA.2484@TK2MSFTNGP06.phx.gbl...
>>
>> "Bruce Sanderson" <bsanders@newsgroups.nospam> wrote in message
>> news:288304D3-55A4-458E-A3BD-B2F7737E99AD@microsoft.com...
>>> The same commands should work on the clients (XP and later). There is
>>> no need to have a GPO to configure the time. You only need to do that
>>> if you want to do something abnormal.
>>>
>>> For the clients, use the command:
>>>
>>> w32tm /config /syncfromflags:domhier
>>> w32tm /config /update
>>> w32tm /resync /rediscover
>>>
>>
>>> --
>>> Bruce Sanderson MVP Printing
>>> http://members.shaw.ca/bsanders
>>>
>>> It is perfectly useless to know the right answer to the wrong question.
>>>
>> Should I do it on every machine?!
>>
>