Configure the Windows Time Service on the Forest Root Domain Controller
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
When deploying a single domain forest, it is important to correctly configure the Windows Time Service on the forest root domain controller to meet your organization’s needs. The Windows Time Service provides time synchronization to peers and clients, ensuring that there is consistent time throughout an enterprise.
By default, the first domain controller that is deployed holds the PDC emulator operations master role, and should be set to synchronize from a valid Network Time Protocol (NTP) source. If no source is configured, the service will log a message to the event log, and use the local clock when providing time to clients. Although internet NTP sources are valid for this configuration, it is recommended that a dedicated hardware device, such as a GPS, or Radio clock be employed in the interest of security.
It is recommended that you repeat this operation when the PDC emulator operations master role is transferred or seized in the forest root domain.
To configure the Windows Time Service on first forest root domain controller
Log on to the domain controller.
At the command line, type:
W32tm /config /manualpeerlist:<peers> /syncfromflags:manualwhere <peers> is a space–delimited list of DNS and/or IP addresses. When specifying multiple peers, enclose the list in quotation marks.
Update the Windows Time Service configuration. At the command line, type:
W32tm /config /update– or –
Net stop w32time Net start w32time
Note
- When specifying a manual peer, do not use the DNS name or IP address of a computer that uses the forest root domain controller as its source for time, such as another domain controller in the forest. The time service will not operate correctly if there are cycles in the time source configuration.
For more information about configuring and deploying the Windows Time Service, see the Active Directory Collection of the Windows Server 2003 Technical Reference (or see the Active Directory Collection on the Web at https://www.microsoft.com/reskit).