Article ID: 969304 - View products that this article applies to.
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
In Windows Time Services by default PDC operations master at the root of the forest becomes authoritative for the organization. It is recommended to configure the authoritative time server to gather the time from a hardware source.
These recommendations provide more accuracy and security to your domain.
For more information about this recommendation see the following Microsoft article:
How to configure an authoritative time server in Windows Server 2003.
When you configure an authoritative time server in Windows Server 2003 Windows Time Synchronization does not appear to be working correctly and you receive the following error:
Error Message in the Event Log:
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 12
Time: 3:42:27 PM
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
The W32tm Command generates the following error message:
w32tm /resync /rediscover
The computer did not resync because no time data was available.
This problem occurs if there is a Domain Level Policy applied to the PDC Operations Master role.
Computer Configuration -> Administrative Templates -> System -> Windows Time Service -> Configure Windows NTP Client.
NtpServer = a known NTP Server
Type = NT5DS
Though Registry have been configured to use Type as NTP, it is overridden by NT5DS being applied from the Group Policy.
Remove the Group Policy setting for the PDC Operations Master which has the configuration setting of "Type" = "NT5DS".
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Article ID: 969304 - Last Review: March 19, 2009 - Revision: 1.0
Contact us for more help
Connect with Answer Desk for expert help.