| |
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 describes how the Windows Time Service utilises the Network Time Protocol (NTP) to achieve network time synchronisation of servers in a domain.
In networked environments, a completely automated time synchronisation service is required to automatically set the clocks on each client to that of a master reference clock. The Windows 2003 Time Service provides such functionality. 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 protocol provides time offset information along with round-trip delay information in order to accurately synchronise time.
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 obtained from registry entries, which are located in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesW32Time. Below is a description of some of the more useful configuration settings.
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.
 EasyPublish™ this article - publishers click here
More articles by David Evans
- Email Investigations - What Can You Find Out? (Ed Opperman)
You may be surprised to learn what you can find out with a reverse email search. A great deal of information can be obtained from just an email account. - Video Software Converter (Thomas Lonberg)
This new video software converter makes video production an easy and a fun thing to do. You use videos for a business presentations or a fun video for your site to help increase traffic to your site and much more.
|