Configure Windows Time Service

pollardhimself

Senior member
Nov 6, 2009
281
0
0
i want to configure my server 2008 as a time server using group policy. What should the ntp server address look like "\\servername" ? so i can assign it to the clients

20100505171024.png


20100505170913.png
 

stash

Diamond Member
Jun 22, 2000
5,468
0
0
You don't need to do this. Domain controllers are authoritative time sources by default and domain members sync automatically. You should configure the DC holding the PDC role to sync with an external source by running w32tm /config /manualpeerlist:time.nist.gov /syncfromflags:manual.
 

pollardhimself

Senior member
Nov 6, 2009
281
0
0
You don't need to do this. Domain controllers are authoritative time sources by default and domain members sync automatically. You should configure the DC holding the PDC role to sync with an external source by running w32tm /config /manualpeerlist:time.nist.gov /syncfromflags:manual.

I got a client thats not getting the right time, Its a sp2 client that doesnt have the daylights savings time patch
 

dawks

Diamond Member
Oct 9, 1999
5,071
2
81
I got a client thats not getting the right time, Its a sp2 client that doesnt have the daylights savings time patch

If the client is joined to the domain, which it would have to be for GPO to work, its getting its time from the Domain Controller. It HAS to be properly sync'ed with the domain controller otherwise logins and authentication won't work properly.

A good possibility is the hardware clock on the mobo is malfunctioning. I've seen this with two computers. I'd have Windows XP do a time sync, and within 12 hours the clock would have fell behind by 2+ hours. My only fix was to find an app that would sync the clock more often (once per 1/2 hr). I was unsuccessful getting the time service to sync more often via the registry for some reason, something you might want to try.
 

rasczak

Lifer
Jan 29, 2005
10,437
22
81
If the client is joined to the domain, which it would have to be for GPO to work, its getting its time from the Domain Controller. It HAS to be properly sync'ed with the domain controller otherwise logins and authentication won't work properly.

A good possibility is the hardware clock on the mobo is malfunctioning. I've seen this with two computers. I'd have Windows XP do a time sync, and within 12 hours the clock would have fell behind by 2+ hours. My only fix was to find an app that would sync the clock more often (once per 1/2 hr). I was unsuccessful getting the time service to sync more often via the registry for some reason, something you might want to try.

He could create a batch script that could run as a scheduled task no?