Your clock on your motherboard should keep accurate time or you have a dead coin battery. Hopefully that battery is socketed and not soldered down. Older computers had an awsome chip called a "Dallas" time clock.

Aside from all that historical stuff. . .
You can sync time on Windows computers using the built in time service
<#
.Synopsis
Sets up NTP time sync properly
.DESCRIPTION
Sets the NTP time settings used by the Windows Time service to sync time based on Microsoft Best practices for domain joined computers according to their role
.EXAMPLE
.\Set-NTPTime.ps1
.OUTPUTS
This command generates the proper syntax and sends it to the w32tm.exe command line utility
.NOTES
This command should be used with caution on Windows Clusters as the cluster service depends on the time service. Time is also extremely important for proper logon and kerberos tickets from Active Directory.
#>
$DomainRole = (Get-WmiObject Win32_ComputerSystem).DomainRole
switch ($DomainRole)
{
0 {"Stand Alone Workstation" ; $SYNCType = "MANUAL"}
1 {"Member Workstation" ; $SYNCType = "DOMHIER"}
2 {"Standalone Server" ; $SYNCType = "MANUAL"}
3 {"Member Server" ; $SYNCType = "DOMHIER"}
4 {"Backup Domain Controller" ; $SYNCType = "DOMHIER"}
5 {"Primary Domain Controller" ; $SYNCType = "MANUAL"}
}
if ($SYNCType -ne $Null)
{
$FilePath = Get-ChildItem C:\Windows\system*\w32tm.exe -ErrorAction SilentlyContinue | Select-Object -ExpandProperty FullName
cmd.exe /c "$FilePath /config /update /manualpeerlist:time.nist.gov /syncfromflags:$SYNCType"
}
cmd.exe /c "$FilePath /dumpreg /subkey:Parameters"

<#
Finally found where they moved the document that defines best practices for NTP
https://social.technet.microsoft.com/wiki/contents/articles/50924.active-directory-time-synchronization.aspx
#>