Windows Time "Allowing" the OS Kernel to sync to CMOS clock after 24H of no valid time sync

hello,
have been observing following scenario following environment:
windows 2008 server r2
not part of domain
cmos clock drifted , not sync'd os ntp aware time.

1. assume windows time has problem syncing time source , produces following when asked "w32tm /query /status /verbose":

leap indicator: 0(no warning)
stratum: 3 (secondary reference - syncd (s)ntp)
precision: -6 (15.625ms per tick)
root delay: 0.2028500s
root dispersion: 7.8420074s
referenceid: 0x413738ce (source ip:  65.55.56.206)
last successful sync time: 2/1/2014 2:33:18 pm
source: time.windows.com,0x9
poll interval: 10 (1024s)

phase offset: -0.0260539s
clockrate: 0.0155992s
state machine: 2 (sync)
time source flags: 0 (none)
server role: 0 (none)
last sync error: 2 (the computer did not resync because stale time data was
 available.)
time since last sync time: 85499.5378040s

2. when "time since last sync time" arrives @ value 86400 (24h) event log message such following registered:

time service has not synchronized system time 86400 seconds because none of time service providers provided usable time stamp. time service not update local system time until able synchronize time source. if local system configured act time server clients, stop advertising time source clients. time service continue retry , sync time time sources. check system event log other w32time events more details. run 'w32tm /resync' force instant time synchronization.

3. if debug log of windows time enabled events (0-300) using "w32tm /debug .." following records can found in log @ time:

 - w32tmservicemain: timeout
 - clockdispln gounsyncd: setunsync: li:3 s:0 rdl:2184500 rds:78611726 tsf:0x0 releaseclock2cmos
 - logging warning: time service has not synchronized system time 86400 seconds because none of time service providers provided usable time stamp. time service not update local system time until able synchronize time source. if local system configured act time server clients, stop advertising time source clients. time service continue retry , sync time time sources. check system event log other w32time events more details. run 'w32tm /resync' force instant time synchronization.
 - w32tmservicemain: waiting 642.223s

4. when above occurs, have observed os kernel begin syncing underlying cmos clock when different each other in more 60 seconds. sync occur on next "sync point" arrive. "sync point" end of 60 minute cycle, counting boot time , repeating.

note: cmos clock off in more 60 seconds example when it's battery dead, or on virtualized environment under conditions. (if interested in more details, please ask in comment)

questions:
a. parts of behavior documented - can confirm analysis of situation correct?
b. have knowledge of term "releaseclock2cmos" appears in windows time log? mean?
c. under conditions kernel avoid syncing underlying 60 seconds-off cmos clock? under conditions sync (aside described)?

info appreciated.

hi,

thank question.

i trying involve familiar topic further @ issue. there might time delay. appreciate patience.

thank understanding , support.

---

jeremy wu

technet community support

Windows Server  >  Server Core