I would suggest you read some of the articles that I'll link below, but I will try to summarize to the best of my recollection (without re-reading myself). What you are seeing in the registry is not necessarily in effect. When HKLM\System\CurrentControlSet\Services\W32Time\Parameters\Type is set to "NT5DS", the "NtpServer" key is ignored. The default operation in a domain environment is that all member computers use domain controllers for their time source. Among the domain controllers, the one with the PDC emulator role is authoritative--this is the one that you should set to sync from an external, trusted source. http://technet.microsoft.com/en-us/library/cc773013(WS.10).aspx http://support.microsoft.com/kb/816042/ http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs /en-us/time_w32tm.mspx?mfr=true http://technet.microsoft.com/en-us/library/cc773263(WS.10).aspx
________________________________ From: [email protected] [mailto:[email protected]] Sent: Friday, September 18, 2009 10:58 AM To: NT System Admin Issues Subject: Re: Why is Windows Time service crap? Thanks, but your last question repeats mine... I did find my DCs were using THREE different ntp sources. I have corrected that on all but a couple of VM DCs... (I'll probably correct them shortly.) The two VM DCs had the same time as my "definitive" DC. However, they had "time.microsoft.com" in their registries. Two VoIP controllers (which both slipped 3 minutes yesterday) also had "time.microsoft.com", but again, their time was not the same as the VM DCs claiming the same source. -- RMc Micheal Espinola Jr <[email protected]> wrote on 09/18/2009 09:49:57 AM: > If your servers have slipped that much in 24 hours after a time > sync, then you prolly have battery issues. Does the time sync up > after another forced sync? How is the sync configured for automatic use? > -- > ME2 > > On Fri, Sep 18, 2009 at 10:36 AM, <[email protected]> wrote: > > Greetings! > > I have workstations and servers in my domain whose time is all over the place! > > Two servers I manually sync'd with a domain controller less than 24 > hours ago are now once again 3 minutes behind. > > Workstations are up to 5 minutes one way or the other. > > I know this keeps coming up here, but again, please... > > 1. With multiple domain controllers, does one pick one of them, sync > to an outside time source, then somehow point the other DCs to this > DC? If so, then one puts in the name of the selected DC in the > registry settings for time services? OR, does one make sure all the > DCs point to the same external NTP server? > > 2. Why do servers and workstations drift off, time-wise? How to stop this? > -- > Richard D. McClary > Systems Administrator, Information Technology Group > > ASPCA(r) > 1717 S. Philo Rd, Ste 36 > Urbana, IL 61802 > > [email protected] > > P: 217-337-9761 > C: 217-417-1182 > F: 217-337-9761 > www.aspca.org > > The information contained in this e-mail, and any attachments > hereto, is from The American Society for the Prevention of Cruelty to Animals(r) > (ASPCA(r)) and is intended only for use by the addressee(s) named > herein and may contain legally privileged and/or confidential > information. If you are not the intended recipient of this e-mail, > you are hereby notified that any dissemination, distribution, > copying or use of the contents of this e-mail, and any attachments > hereto, is strictly prohibited. If you have received this e-mail in > error, please immediately notify me by reply email and permanently > delete the original and any copy of this e-mail and any printout thereof. > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
