time observation bug 2016


hello all,

this go undiscovered in environements manufacturing , time critical. explain best can.

summary:

we have 2 data centers , 60 remote sites. domain controllers 2012r2 , functionality high go, 2012r2. time within 3 seconds across entire company.

i added 2 new 2016 domain controllers (forest @ 1 , domain @ other data center) , moved fsmo's them accordingly. 60 plus domain controllers recognized change , reflected update nt5ds, all domain controllers in perfect time.

however, discovered "all clients" 29 seconds behind in time, constantly. reduce temporarily running these commands https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/ time goes being 29 seconds behind on "clients". weird huh.

so add 2016 domain controller 1 of sites , demote 2012r2 domain controller , clients exact time. didn't matter if clients server os, windows 7 or 10 reacted same.

my fix 2016 domain controllers @ locations, other ideas? weird huh.

these ones might help.

https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/get-started/windows-time-service/accurate-time

https://support.microsoft.com/en-us/help/939322/support-boundary-to-configure-the-windows-time-service-for-high-accura

you can report issues discovered / requested on here on uservoice.

https://windowsserver.uservoice.com/forums/295047-general-feedback

 

 

 



regards, dave patrick ....
microsoft certified professional
microsoft mvp [windows server] datacenter management

disclaimer: posting provided "as is" no warranties or guarantees, , confers no rights.



Windows Server  >  Windows Server 2016 General



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607