Lately I've been designing a company-wide migration to Windows 10 1607 using the in-place upgrade option with System Center Configuration Manager Current Branch. One issue that came up was time ... or rather display time ... being WAY off (and by way off I mean hours, up to 3 hours in some case).
Now you may be thinking "But Terry, doesn't that mean your users can't log in?" ... and the answer is .. well .. no! See, the issue being experienced only affects the time that is displayed on the system tray and lock screen, not the system time. System time is critical for domain-joined systems as if you are off by more than 5 minutes, you can't authenticate with AD, so the default behavior is workstations sync time with your local Domain Controller or the PDC Emulator. System time is done in UTC, and Display Time is UTC +/- your time zone offset. This means that it is technically possible for time to be correct and incorrect at the same time!
How to tell if you have this problem
- Open Windows PowerShell (right-click Run As Administrator, you will find out why later)
- Type this command: w32tm /query /peers
Time Remaining: (up to 24 hours, in seconds)
In my case I have systems spread out over multiple time zones. In some cases the time displayed properly but it was not syncing from the local DC. In other cases the display time was out by up to 3 hours!.
How to fix the problem
You still have that PowerShell window open right? Here are the commands you need to run (in order):