Controlling Source for Windows Time?

[Will]

How do I control which computer on the network is the time master for use
with the NET TIME command? I understand that the domain controller is
supposed to have this role for use with the Windows Time service, but
whenever I type NET TIME /SET, I am getting a different server on the
network, and I would like to point users back to the domain controller for
manual time updates.

 

[Jerold Schulman]

How do I control which computer on the network is the time master for use
with the NET TIME command? I understand that the domain controller is
supposed to have this role for use with the Windows Time service, but
whenever I type NET TIME /SET, I am getting a different server on the
network, and I would like to point users back to the domain controller for
manual time updates.

You can use
NET TIME \\ServerName /SET /YES

See tip 9712 » How does the Windows Time service guarantee common time usage in your domain?
in the 'Tips & Tricks' at http://www.jsifaq.com

Jerold Schulman
Windows Server MVP
JSI, Inc.
http://www.jsiinc.com
http://www.jsifaq.com

 

[Paul Bergson]

The time master for your domain is the PDCe role holder, but all Domain
Controllers provide time services to down level clients.

You should look at w32time as your time source.

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

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Will]

I'm asking what sets the *default* server used for NET TIME /SET.

It is NOT our domain controller, and I don't understand why or how to change
that behavior.

--
Will

 

[Will]

So on our network NET TIME /SET points to a member server of the domain, not
a PDC. Any explanation for that?

W32Time messages in the eventviewer, however, for any client machine points
to the PDC. So Net Time /SET must be following a slightly different
procedure than does Windows Time.

--
Will

The time master for your domain is the PDCe role holder, but all Domain
Controllers provide time services to down level clients.

You should look at w32time as your time source.

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

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Paul Bergson]

I'm not sure if I have an answer for you, I don't know your environment, but
if you are having troubles try

w32tm /config /syncfromflags:/DOMHIER




--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

So on our network NET TIME /SET points to a member server of the domain,
not
a PDC. Any explanation for that?

W32Time messages in the eventviewer, however, for any client machine
points
to the PDC. So Net Time /SET must be following a slightly different
procedure than does Windows Time.

 

[Will]

I think you may have meant:

w32tm /config /syncfromflagsOMHIER

without the / character before DOMHIER?

I used your e-mail for a web search and came up with this sequence to try:

w32tm /config /syncfromflagsOMHIER /update
net stop w32time
net start w32time

I do the above, but the result from NET TIME /SET still tries to pull time
information from a member server, not the PDC.

 

[Joe Richards [MVP]]

Windows time and NET TIME are using different protocols. Honestly there is no
reason to be using NET TIME /SET any more unless the machine is not part of an
AD Forest.

joe

 

[Will]

That's good news, so I will stop being too concerned about it.

However, I am still quite curious what logic is NET TIME /SET using, and is
there any way to change the server that this directs to?

 

[Joe Richards [MVP]]

Nothing other than what Jerry recommended already in specifying the specific
server. It isn't going to change, NET TIME is deprecated.

 

[Paul Bergson]

Yeah you have it correct, sorry was trying to finish up and get home. Just
drop the net time thing altogether.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[ramymamlouk]

Check out this reg key:
HKLM\System\CurrentControlSet\Services\W32Time\Parameters

On the NtpServer, it should have a value of time.windows.com,0x1
On the Type, it should be NT5DS

Restart the time service and see if that works.