Time sync problem on Domain contoller

Hi, We are having problems with time synchronisation on our domain. Mix of 2003 and 2008 Dc's across two sites. There is some ntp settings in the "default domain policy" :

System/Windows Time Service/Time Providershide
Policy Setting Comment
Configure Windows NTP Client Enabled  
NtpServer companyserver1
Type NT5DS
CrossSiteSyncFlags 2
ResolvePeerBackoffMinutes 15
ResolvePeerBackoffMaxTimes 7
SpecialPollInterval 3600
EventLogFlags 0
Policy Setting Comment
Enable Windows NTP Client Enabled  
Enable Windows NTP Server Enabled

I want to delete this policy because I think it was put there by past admins. I've read up on this and as I understand it the policy setting is not needed because the pdc emulator provides this service. My plan is to set the PDC DC to an extern NTP.

I'm just hesitant in doing it because it must be there for a reason.
Who is Participating?
Seth SimmonsConnect With a Mentor Sr. Systems AdministratorCommented:
i'm guessing the past admins didn't know what they were doing - particularly putting that config in the default domain policy
remove that policy and configure it properly on the PDC emulator directly
i have used pool.ntp.org servers as external time source


no need to touch any other systems to configure ntp client

How to configure an authoritative time server in Windows Server
Peter HutchisonSenior Network Systems SpecialistCommented:
Yes, your PDC should be your primary source for NTP (swhich should be in turn syncing to a trusted external NTP source).
Any member servers should be set to NT5DS with an optional list of DCs to sync from.
So deleting that policy will help you to set up NTP properly.
VB ITSSpecialist ConsultantCommented:
Looks that like that policy was used to force the machines in the domain to use companyserver1 as it's NTP time source. If companyserver1 is not your PDC then you can remove the policy.
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

capnetAuthor Commented:
Thanks for the responses I will change the configuration at the weekend and let you know how I get on. Additional question, pdc emulator is on a different physical site but connection between sites is good. can't any info thats says don't do this though.
Seth SimmonsSr. Systems AdministratorCommented:
the AD site doesn't matter
as long as clients can communicate with it, it's fine
Rob GMicrosoft Systems EngineerCommented:
You might want to be careful with this..
There technically isn't such a thing in 2k8 server environments as PDC/BDC, they are all just DC's.
They are load balanced, based on how much is going on with each DC. if you change the time server settings you can run into other issues... especially if you are still rolling on a 2k based group policy...
capnetAuthor Commented:
Hi Rob thanks for the response. We have 2  x 2003 R2 domain controllers in site A and 1 2008 DC in site B. When I check the FSMO the 2008 server holds all the roles. I guess because there is only one 2008 server it won't do the load balancing and I should be ok to delete the policy settings?
Seth SimmonsSr. Systems AdministratorCommented:
delete the policy
other domain controllers are irrelevant because domain members only go to the domain controller having the PDC emulator role
if the 2008 server holds the roles then they will go to the 2008 server for time
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.