Atomic Time Zone Server as a Windows Server

Atomic Time Zone Server can operate as a full replacement for the Windows Time Service also known as W32Time. ATZ Server can also replace the Windows "DayTime" service - which operates on port 13. W32Time included with Windows 2000 Server, and Professional, and Windows XP Professional editions is not as good as ATZ Server - we'll tell you why.

Why default Windows Time Services can't out perform ATZ Server.

#1 - Bad W32Time Defaults to a several second accuracy (vs less than 1 with ATZ Server). This means that although W32Time can communicate with Time Servers, and also set the time, it doesn't do so with the accuracy meant for a atomic time server. Atomic Time Zone Server does operate with the accuracy meant for a time server.
#2 - Bad W32Time Operates in 8 hr intervals regularly. In fact, to operate it automatically less than once every 45 minutes isn't possible as a feature. It won't check your clock as frequently as ATZ Server will, and thus ATZ Server, again, is more accurate. Inaccurate Server time means inaccurate client times. We know this, and this is another reason Atomic Time Zone Server is superior.
#3 - Bad W32Time Implements a much less recent RFC Internet Time Standard called Simple Network Time Protocol version 3. As documented in this Microsoft Knowledge Base report, W32Time is using an older version of SNTP. ATZ Server uses the most recent SNTP implementation meaning its ready to handle the most recent clients, and also provide them with accurate time.
#4 - Bad Windows DayTime Service While we can understand how easy it is for the service to simply send out a timestamp and forget about it, ATZ Server doesn't operate this way. While the Windows DayTime Service will send out a timestamp (not of much use because it doesn't contain region info), ATZ Server does much more. ATZ Server sends out an industry standard timestamp format, which uses UTC. A further and more advanced implementation of the DayTime protocol was carried out by The National Institute of Standards and Technology (NIST). This protocol, an adaption of their ACTS, provides a wealth of more information, and can be used by any NIST time client or ATZ Time client.
#5 - Bad Windows DayTime Service The Windows Daytime service is "hidden" under the "Windows Simple TCP/IP Services" Service. ATZ Server makes the Daytime Server clear as day, and easily configurable.
#6 - Bad Windows DayTime Service Any options? We don't think so. With Windows DayTime Service, you're stuck with a simple timestamp. With ATZ Server, you have the option of using the more advanced NIST/ACTS protocol (default), or a timestamp conformed to the UTC standard. That means accurate timestamps that clients can use, not inaccurate ones like the Windows DayTime Service.
#7 - Bad - No UnixTime UnixTime on Windows? Well, not until ATZ Server came along. The ATZ Server UnixTime server sends out a valid and accurate to the second UnixTime.
#8 - Bad - No Time Service in Windows. Just because Windows Time Service is called Windows Time Service doesn't mean it's using the standard "Time Protocol". In fact, you won't find the "Time Protocol" implementation included with Windows. ATZ Server comes with all 4 major time protocols in the world. Time Protocol is one of them.
#9 - Can I Log any of this? With ATZ Server, yes. With Windows Time Service, not in the industry standard Internet log file format - WC3 Extended.
#10 - Redundancy So Windows lets you configure a few time Servers. What if these few fail? Not only does Atomic Time Zone Server pair itself up with a time server near you, generally there are much more than a few per region. Because ATZ Server can also randomly pick which server it uses and when, it is highly improbable ATZ Server will ever have a problem synching itself.
#11 - Good ATZ Server Atomic Time Zone Server can not only operate as a Windows Service, it can operate each of the Windows Time Services, and much more, all under a single Service. ATZ Server not only runs each of the Windows Time Services, it also adds a few of its own making it the most robust Windows Time Service in the history of Windows.

Configuring Atomic Time Zone Server as a replacement for Windows Time Services.

  Note: These Windows Time Services only come with Windows NT/2000, and Windows XP Business Editions.

  To replace the Windows "DayTime" Service, proceed to the Services Control (Under Administrator Tools). Locate the "Simple TCP/IP Services" and stop it. Set this Windows Service to Startup Type: Manual. Now Simply enable the "DayTime Service" within Atomic Time Zone Server.
   * ATZ Server "DayTime" Service defaults to using the more advanced daytime protocol in use by the NIST. To use a standard UTC time stamp, change the ATZ Server "UseJulian" registry key to "NO".

  To replace the Windows "Time" NTP Service, locate "Windows Time" in the Services applet. Stop the Windows Time Service. Set the Windows Time Service to "Startup Type: " Manual. Now, simply enable the "Network Time Protocol Server" in ATZ Server.

  To run Atomic Time Zone Server as a Windows Service, and from the Administrator Services control, when installing ATZ Server, select the option "Enable Atomic Time Zone Server to run as a Windows Service Automatically." or from the ATZ directory, run "amo_atz_server_svc.exe -install". Once the ATZ Server Service has been installed, you must configure it. You can configure ATZ Server from either the standalone ATZ Server application (amo_atz_server.exe), or by using the "-config" command line option with the ATZ Service Application.

  The ATZ Server Windows Service defaults to running without a Graphical User Interface as per the Windows Service Specifications. It can however be run with an interface briefly to update, or configure using the "-config" command line option.

  To determine whether the ATZ Server Service is installed and currently running, locate its entry from the Services Control and select properties. If the ATZ Server services are running, it will state "Started". When configuring the ATZ Server Service, you must stop the ATZ Server Service, and run "amo_atz_server_svc.exe -config" from the command line. Once you have completed any configuration, close the ATZ Server, and restart the ATZ Server Service from the Services Control.

  To install or uninstall the ATZ Server Service at anytime, simply use the "-install or -uninstall" command line options from the "amo_atz_server_svc.exe" service application.