Submitted by: Dave Evans(1,014) TimeTools Log in to become a member of Dave Evans's Fan Club!
All PC's have internal Real Time Clocks (RTC) that maintain time and date information. PC real time clocks are battery backed so that they can maintain time even when the PC is powered off. The PC Real Time Clock provides time and date information to operating system processes and user applications. Often this is adequate, however, for many applications PC time may need to be synchronised with other PC's on the network.
For transaction processing in a networked environment or for scheduling purposes, the system time and date may need to be synchronised with every other PC on the local network. Microsoft Windows 2003 has an integrated time service that provides synchronisation between PC's in a domain.
This article describes how the Windows 2003 Time Service synchronises time and date information on servers to a domain controller. It also discuses how the Windows 2003 time synchronisation service uses NTP to synchronise servers in a domain.
Networked computers require an automated time synchronisation service which can automatically synchronise time on each client to an accurate master clock. The Microsoft Windows 2003 time synchronisation service was developed to fulfill this function. The service is installed by default on any Windows 2000, XP and Server 2003 machine.
On power-up, the Windows 2003 time service starts automatically and attempts to synchronise time and date information with a domain controller using the NTP protocol. NTP is an Internet protocol developed for the transfer of accurate time. The Network Time Protocol provides accurate time information along with network transmission delay information, so that a precise time can be obtained.
A domain controller can be configured as either a trusted or an un-trusted time reference. A Windows Time Client will always attempt to synchronise time periodically with a trusted domain controller. In this manner networked Windows 2003 servers maintain synchronisation with a domain controller and each other.
The global Windows 2003 time service configuration settings are set using group policy. The settings are stored as registry entries in the registry at HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesW32Time. A breif description of the more useful time service configuration settings is contained below.
The ‘AnnounceFlags' registry entry indicates whether the server is a trusted time reference. Set the ‘AnnounceFlags' registry entry to 5 indicating a reliable time reference. The ‘Type' registry entry specifies which network peers to accept synchronisation. Set the ‘Type' registry entry to ‘NTP' to specify synchronization to a NTP time server.
The ‘SpecialPollInterval' entry defines the period in seconds that the Windows 2003 operating system should poll the time server. A recommended value is 900, which equates to a polling period of every 15 minutes. The ‘NtpServer' parameter is used to provide domain names or IP addresses of NTP time servers that the operating system can synchronize to. Each domain name or IP address should be separated by a space.
--------
Dave Evans is a technical author with a background in Microsoft Windows time server solutions, reference clocks and telecommunications. Dave provides a technical authoring service to NTP server manufacturers. Dave has also provided a configuration, installation and repair service for time synchronisation systems. Click here fo find out more about Windows 2003 time server solutions.
Disclaimer: All information on this site is provided for informational purposes only! By no means is any
information presented herein intended to substitute for the advice provided to you by any health care or other professional
or organization.
