This guide does not discuss configuring the Windows Time service. There are several different topics on Microsoft TechNet and in the Microsoft Knowledge Base that do explain procedures for configuring the Windows Time service. If you require configuration information, the following topics should help you locate the appropriate information. To configure the Windows Time service for the forest root primary domain controller PDC emulator, see:. Configuring a time source for the forest. To configure the Windows Time service on any domain member client or server, or even domain controllers that are not configured as the forest root PDC emulator, see Configure a client computer for automatic domain time synchronization.
Some applications may require their computers to have high-accuracy time services. If that is the case, you may choose to configure a manual time source, but be aware that the Windows Time service was not designed to function as a highly accurate time source.
Ensure that you are aware of the support limitations for high-accuracy time environments as described in Microsoft Knowledge Base article , Support boundary to configure the Windows Time service for high-accuracy environments.
To configure the Windows Time service on any Windows-based client or server computers that are configured as workgroup members instead of domain members see Configure a manual time source for a selected client computer. To configure the Windows Time service on a host computer that runs a virtual environment, see Microsoft Knowledge Base article , How to configure an authoritative time server in Windows Server.
The procedure will also remove any errors in the Event Viewer, if any existed. Do not use if you are using a third party stratum service and refer to the vendor's documentation for further instructions.
Do not perform on any other DC in any domain in the forest. PDC in the forest root only. If any of the procedures did not work or event log errors indicate any issues, you can reset the time service registry entries back to default.
The procedure should be done on the DC that you are experiencing issues with and not necessarily on each DC. Please bear in mind that the Windows W32Time service is not a full featured, accurate service for time sensitive application requirements, nor will Microsoft support it as such.
You must use a third party time service that will support this requirement. Windows Time Service Tools and Settings Includes specific w32tm command switches and registry entries. We also recommend that you reduce your time correction settings for your servers and stand-alone clients. These recommendations provide more accuracy and security to your domain. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No.
Any additional feedback? Note If an authoritative time server that is configured to use an AnnounceFlag value of 0x5 does not synchronize with an upstream time server, a client server may not correctly synchronize with the authoritative time server when the time synchronization between the authoritative time server and the upstream time server resumes. Therefore, if you have a poor network connection or other concerns that may cause time synchronization failure of the authoritative server to an upstream server, set the AnnounceFlag value to 0xA instead of to 0x5.
If an authoritative time server that is configured to use an AnnounceFlag value of 0x5 and to synchronize with an upstream time server at a fixed interval that is specified in SpecialPollInterval , a client server may not correctly synchronize with the authoritative time server after the authoritative time server restarts. Video Steps. These are typically provided by government or other network organizations.
Log onto the domain controller with administrative credentials and launch a command prompt 3. Stop the time service with the following command: net stop w32time 4. The command should complete successfully. Restart the time service: net start w32time 7.
Ensure the settings are the desired ones. Then close the command prompt. The NTP servers have now been configured. Author: Rodney Barnhardt. LVL Windows Server Active Directory 9. LVL 7. Active Directory 3. Windows Server 3. LVL 2. LVL 1. Expert Comment by: andrew nyc Overall: Level
0コメント