Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I know how to set an authoritative time server in Server 2008 R2. That's not what this question is. I want to know how I can change the time on a network where the PDC (and therefore everything) is a month out of date?

I know that a 5 minute difference in time between clients and the domain prevents logons, so just changing the time on the PDC will break everything.

What is the best way to fix this?

share|improve this question
Please avoid the term PDC discussing post NT Domain Controllers. Your PDC is a normal Domain Controller with the PDC Emulator FSMO role. It's a little thing, but you don't have a PDC on your network. – Dan Sep 5 '12 at 9:13
Sure, I know that, but when you are talking about time servers then it is important to mention the server with the PDC role. – Kieran Walsh Sep 5 '12 at 9:16

As a high level overview my approach would be to try and do the following:

  1. Ensure that NTP is functioning correctly on your domain and make sure you know which server(s) control the time.

  2. Ensure that all of your clients and servers are actually using NTP

  3. On your clients, reduce the MaxPollInterval and increase MaxPosPhaseCorrection. (This may help:

  4. Make the change, allow everything to synchronise

  5. Reverse the client changes

  6. Now, because you did all of the above in a lab, try it in real life ;)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.