![]() ![]() Be advised that this involves registry editing which is always something to be done cautiously and even moreso when it is on your PDC emulator. This will show you exactly what you’re doing and where. There is a “Fix it for me” button, but I recommend that you go to the “Let me fix it myself” section and click on “Click here for directions about how to resolve this issue yourself”. Scroll down to the section titled “Configuring the Windows Time service to use an external time source”. The steps are well-documented in Microsoft Knowledge Base entry 816042. This post will only discuss how to set it up for a Windows Server computer. You can use any computer or device that runs an NTP server. All clients, including the server, will need it open outbound, at least to the authoritative host’s IP. Your authoritative server will need that port open inbound. Time synchronization traffic travels on UDP port 123. You could also have one machine pull external time and have your PDC emulator use that as its source while still serving as the authoritative server for the rest of the computers in your domain. You could have multiple machines serving as authoritative time sources, but more than one per site is generally unnecessary. The machine that you choose will be regularly consulting Internet sources, so if you’re in a high-security facility you might consider delegating this role to a different computer. According to Microsoft’s documentation, that’s supposed to be the highest authority on the matter anyway, although it doesn’t seem to work out that way in practice. In most cases, I choose the domain controller that holds the PDC emulator role. The first thing you want to do is decide what machine you want to serve as the authority on time within your domain. Pick a Computer to Server as the Authoritative Internal Time Source Fortunately, it doesn’t take a lot of work to get everything in sync. ![]() If a Hyper-V host’s clock becomes out of sync, it usually affects all of its virtual machines, sometimes catastrophically. To compound matters, the default method of handling time synchronization within a Windows network isn’t exactly reliable or even predictable. A skewed system clock can affect your ability to log on, can cause problems with mail flow in Exchange, and be the source of a great many difficult-to-locate problems. Microsoft operating systems and server applications have become increasingly dependent on proper time synchronization. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |