Hacker News Reader

I find some humor in this being somewhat familiar with the history of clocks and watches. Forever the battle was making the most accurate time pieces possible, with wrist watches eventually reaching a few seconds per day variance before digital watches took over. And new we have something trillions of times more complicated and is performing worse

There are ways said to circumvent the enterprise policy on the autosync side, like unregistering win32tm or deleting all servers from the registry. No idea about setting the time though…

(A smarter time daemon like chrony would've kept track of the RTC drift.)

I have the exact same issue at my office. Do anyone has a solution to that. I'd appreciate it greatly. Thanks