We've received several tickets involving broken domain trust relationships, with affected computers showing a time difference of roughly two minutes. Has anyone else seen this after the latest August Windows updates, or is it more likely a coincidence? I'm especially interested in whether the issue is related to time policies, NTP fallback, or machines that haven't completed provisioning.
4 Answers
I’ve run into this mostly with Autopilot devices that were still waiting at the sign-in screen and hadn’t finished provisioning. Autopilot would fail until I opened a command prompt, manually set the clock close to the correct time, and restarted the Windows Time service.
Check whether your time policy allows domain-joined devices to fall back to an NTP source when they can’t reach the domain. That fixed almost all of the cases I’ve seen. The remaining ones were usually machines that had been powered off or unused for months or even years.
We had five machines lose their domain relationship, although those incidents lined up more closely with the July patches. I’ve also seen several recent reports of time drift, so there may be a pattern, but the update connection isn’t confirmed yet.
We’re seeing something similar, but so far it seems limited to the first batch of updated machines. It would be useful to compare whether the affected computers are on the July or August patch levels.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures