|
The SNTPService product consists of 2 main components: The 2000/XP/2003/Vista service application, that runs in the background as an 2000/XP/2003/Vista service performing various time synchronization tasks, and the control panel applet that is run from the system control panel to set up synchronization parameters.
Targeting the time synchronization function to the Windows 2000/XP/2003/Vista service framework has many advantages that cannot be exploited by our desktop product YATS32, which has a more general mandate. For example: The service application does not incorporate a graphical user interface (GUI). The required control interface is provided by the service control panel applet. The service component, the part that is constantly running in the background, does not need to include the Microsoft Foundation Classes (MFC) drastically reducing its memory requirements. This leaner application is also specifically optimized to execute as an Windows 2000/XP/2003/Vista service with access to a Winsock 2 network API. What this means is that the SNTP Service application runs with lower system overhead and consumes less of the host's resources. Another key advantage is the use of 'clock slewing'. Using constant monitoring and adjustment of the system clock frequency SNTP Service keeps the time accurate without resorting to step adjustments to the system clock. These 'time warps' can have very detrimental consequences to systems that require chronological consistency.
The built-in control panel applet transparently uses WMI to allow the management, and monitoring of the SNTPService running on the local or remote systems. Customers with advanced requirements can create VB scripts that interface directly to WMI in order to create custom, enterprise-wide, time management schemes.
Requirements: Windows 2000, XP, Server 2003, or Vista.
A complete list of benefits:
 |
No GUI included drastically reducing size and resource consumption. |
 |
Optimized for performance as Windows 2000/XP/2003/Vista service. |
 |
Uses advanced WINSOCK 2 features, such as support for muti-homed systems |
 |
Low overhead minimizes impact on server resources. |
 |
Built-in protection against denial of service attacks. |
 |
Logging of 4 levels of events to the system application log. |
 |
Full support for broadcast and multicast in client and server mode. |
 |
Supports all versions of Win2K, and all versions of Windows XP. |
 |
Takes advantage of clock frequency adjustment to avoid stepping (time warps). |
 |
Supports any combination of time servers polled in a sequential or parallel fashion for maximum flexibility and accuracy. |
 |
Remote provisioning and control. |
Limitations of Microsoft's W32TIME service:
 |
Different implementations for Windows NT4, Windows 2000 and Windows XP. |
 |
Limited SNTP support. Only PDC can select arbitrary Internet time server. |
 |
Weak accuracy target of +/-2 seconds. Can lead to large time offsets in multi server timing chain. |
 |
No support for remote provisioning and control. |
Limitations of Microsoft's NET TIME command:
 |
Special user rights are required under Windows 2000, XP. and Server 2003. Modified user account is required to set the local time. |
 |
Does not compensate for time zone differences. Doesn't support roving systems such as laptops and networks that span time zones? |
 |
Usually run at boot time via startup script. Doesn't support systems that are rarely booted? |
 |
Does not compensate for network delays. |
 |
Inconsistent implementation across versions of Windows. |
 |
No support for remote provisioning and control. |

|