We've received several support tickets involving broken domain trust relationships alongside computer clocks being roughly two minutes off. Has anyone else noticed this after the recent July or August Windows updates, or is the timing probably coincidental?
3 Answers
I’ve mainly seen this on Windows Autopilot machines that haven’t finished provisioning and are sitting at the factory-image sign-in screen. Provisioning can fail when the clock is too far off; correcting the time from the command line and restarting the Windows Time service usually gets them moving again.
We had about five machines lose their domain relationship around the same period, although they were still on the July patches. We’re also seeing some clock drift, so there may be a connection, but the current reports don’t clearly point to the August update specifically.
Check the time policy for domain-joined devices. Setting them to fall back to an NTP source when they can’t reach the domain controller fixed almost all of our cases. The remaining problems were mostly machines that had been powered off or unused for months.
That’s useful context. A few of our affected systems may also have been on the July patches, so I’m keeping the update correlation tentative for now.