Time clock sync troubleshooting
I've noticed some strange events can cause the time clock on our computers to become out of sync with the actual time. Things like unexpected power outages, your laptop dying from low battery, or even traveling to a different time zone with your work computer which can prevent it from fixing itself.
Here are a few different methods to try on command prompt to resync the time with the CBA Domain Controller. Command Prompt must be Ran As Administrator.
These 3 commands are telling the machine to resync the time service
- w32tm /resync
- w32tm /resync /force
- w32tm /resync /rediscover
These commands basically delete and reprogram the windows time service on the machine
- net stop w32time
- w32tm /unregister
- w32tm /register
- net start w32time
This command forces the computer to sync it's time with the domain controller. Note: If the domain controller time is also off, the time on the computer will still be off after running this command. I have had the most success with running this command on user's machines that wouldn't sync after trying the above steps
-
net time \\cobardc04.internal.cobar.org /set /y
Keep in mind, this command is syncing the machines time with the current domain controller (which is cobardc04 and cobardc05 is the backup). When we upgrade to a newer OS down the road and migrate to a new domain controller, (I'm assuming will be cobardc06 and cobardc07) that will have to be used in the command line instead of cobardc04.
Also, it is a good idea to connect to the VPN if you work remote or connect to the office Wi-Fi (if you come into the office) for several hours, which can help sync the time and keep the time accurate on computers. It seems to be a fairly slow process for time to sync across the domain.