How long does it take for the workstations to get their time from the PDC

I just set the time on our PDC.  Server 2008
How long before the workstations get this new time?  
Can I force the workstations to get the time without going to each one?
Do you need to use an external time source for the PDC or can you just set the clock?
J.R. SitmanIT DirectorAsked:
Who is Participating?
 
andreibutuConnect With a Mentor Commented:
actually the clients sync the time with their domain controllers in the site. Domain controllers sync with the PDC`s domain and the syncronization is immeadtely.
0
 
andreibutuCommented:
The PDC Emulator in the root domain is generally configured to sync its local clock with an authoritative NTP server. This NTP server may be located on the internet, such as time.windows.com, or it can be a device on your internal network, such as a GPS atomic clock. The PDC Emulators in the child domains will synchronize their time with the root PDC Emulator. Domain Controllers in the domain sync with the PDC Emulator in their respective domains. Clients will then sync their clocks with the DCs in their domain. Time Synchronization is critical for the Kerberos protocol to authenticate successfully.

BR,
Andrei
0
 
J.R. SitmanIT DirectorAuthor Commented:
how often do the clients sync with the PDC
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
J.R. SitmanIT DirectorAuthor Commented:
what is the proper command on a 2008 server to set it clock to time.windows.com.  I tried net time /setsntp:time.windows.com, but it doesn't work.
0
 
J.R. SitmanIT DirectorAuthor Commented:
The article didn't help.  I used the syncfromflags:time.windows.com and got unknown parameter for syncfromflags: 'time.windows.com
0
 
andreibutuConnect With a Mentor Commented:
On the DC with the PDCEmulator FSMO:

w32tm /config /manualpeerlisteers /syncfromflags:manual /reliable:yes /update

With "peers" you can set the time source, either DNS name (time.windows.com)
or an ip address from a reliable time source.

If some domain machines have problems, run this command as it is:

w32tm /config /syncfromflags:domhier /update

After that run:
net stop w32time
net start w32time
0
 
J.R. SitmanIT DirectorAuthor Commented:
I think I got it.  I ran w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update.  It stated it was successful.  Did I do it correctly?

0
 
andreibutuCommented:
yep, that`s correct.
0
 
J.R. SitmanIT DirectorAuthor Commented:
Thanks.  FYI the post 34878754 has a typo.  /manualpeerlisteers, should be /manualpeerlist:peers
0
 
J.R. SitmanIT DirectorAuthor Commented:
thanks
0
 
J.R. SitmanIT DirectorAuthor Commented:
hope you're still monitoring this.  I have three locations.  one I enter the command
w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update. on one of the PDC's then run w32tm /query /source.  It states free-running system clock.  I tried three times?  why wont it change to time.windows.com?
0
 
J.R. SitmanIT DirectorAuthor Commented:
I just looked in the registry and it states the NTPServer is time.windows.com
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.