Reg add HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider /v Enabled /t reg_dword /d 0 I choose to disable it via the registry in almost all of my guest VMs, and I also generally de-select it in the Hyper-V integration settings (you know, belt and suspenders). To disable the synchronization in Hyper-V, you can manage the settings in Hyper-V for the Hyper-V server or for each VM, or you can disable it in the VM by adding a registry key.
#I am the master of my domain windows#
In the worst case, the two types of synchronization start fighting with each other and Really Bad Things happen to your Windows time-keeping as the clock changes constantly. In practice, I'd rather have my domain members behaving like domain members, and my non-domain members being independent. Independent of all this goodness, Hyper-V will attempt to synchronize the Host and the Guests, blissfully ignoring all the hard work you've just done. Many colleges and universities offer NTP servers just make sure, that you are within their published guidelines. Since my servers are in Canada, I use ca. as my first listed external source. The US government operates several publicly-available NTP servers, including, and many people operate regional pools of time servers through the initiative. Microsoft operates an NTP time server at. Lucky for us, NTP is built into the Windows Time Service (called w32time).
Super-time-sensitive environments (and makers) might set up hardware that relies on GPS signals or maybe you have a spare cesium atomic clock in your basement.įor our purposes, using the Network Time Protocol (NTP) to sync with a well-known source will do just fine. I've had batteries give out, and I've had motherboards with clocks that just weren't very accurate. If your battery never gives out, then this might be enough, but. Where does the PDC get it's time? I'm sorry but the little watch-battery and the CMOS clock don't do it for me. Domain members get their time from the PDC.
0 kommentar(er)
