Mark Morowczynski posted about a developing situation where the public usno.navy.mil time clock jumped back to 2000, and if your DCs were syncing from it, what to do about it.

We are seeing some reports that some Active Directory Domain times are reverting to November 2000. So what just happened? I thought the Mayans said this type of stuff didn’t happen until December.

For the fixup and DC reassurance instructions, head over to the post. (Bonus: great byline at the bottom!)

He mentions – as it’s worth mentioning – that setting an allowable time skew is a Really Good Idea for DCs, and that it’s something covered in our AD Risk Assessment Program, which is designed to identify configuration and operational risks to your AD environment, so they can be addressed before they become a crisis.

How Did This Happen?

you most likely do not have the regkeys set for MaxPosPhaseCorrection and MaxNegPhaseCorrection - follow this KB http://support.microsoft.com/kb/884776.

This type of thing is also caught in our famous Active Directory Risk Assessment (ADRAP).Never had one? Contact your TAM and let them know you need one right away and this blog told you so. Not a Premier customer? Contact us here and we’ll get you in touch with the right folks. 

Our new AD RAP as a Service also covers this configuration setting (as well as hundreds of others), and the toolset can be used to assess and reassess your environment.


Posted by Tristan Kington, MSPFE Editor, and wasn’t the US F1 GP in Austin exciting!?