ATZ Server.NET Deployment options.

Because of ATZ Server.NETs extensive support for time protocols, including all major time protocols, and its own ATZ Server.NET Client protocol, deployment options are extensive as well.

Deploying the included ATZ Server.NET Client

To the left is a picture of the ATZ Server Client.NET. Deploying this client is as simple as installing it on the machines you wish to use it on and then configuring it. The ATZ Server Client.NET clients use the ATZ Server Client Protocol via TCP/IP which was built specifically for ATZ Server.NET. To install this client on a client machine, run the ATZSN_Client.exe located in your ATZ Server.NET folder on the client machine. You may download an editable ATZ_Client.REG file to easily configure many machines with the same information.

  The ATZ Server Client.NET Clients also use the Microsoft.NET Framework, and thus it should also be installed on the client machines. If you require the older version of the client, or simply have some Win95 machines you need synchronized with ATZ Server.NET, simply download and install the other client here.

  These clients support logging, and also running as a Windows Service. To install the clients as a Windows Service, vs using the GUI edition, simply select the option during installation.

  While logging, the ATZ Server Client.NET clients record the returned time from the server, its version, and the local machines time. This is useful if you need strict record keeping of time adjustments.

  To configure the clients to use secondary servers in case one is unreachable due to network error, simply enter the IP or address names of the secondary servers and seperate them by a : (colon).

  Of all the ATZ Server.NET time protocols, NTP/SNTP and the Atomic Time Zone Server Client Protocol provide the highest accuracy. The accuracy obtained with these clients is within milliseconds of true Atomic Time.

Using the Built in Windows Time Services

  Windows NT, 2000, and XP all include built in time synchronization clients. Under Windows, this service is called W32Time and is also known as the "net time" command. These clients can be utilized to easily deploy atomic time across an enterprise quickly because no extra software is required to be installed on the client machines. All thats required is configuring the clients to synchronize to the ATZ Server.NET. This isn't needed if ATZ Server.NET is installed on a domain controller, or in the domain heirarchy as this allows the W32Time clients to utilize their default settings. If ATZ Server.NET isn't installed on a domain controller, or you simply want to manually configure each client to point to the ATZ Server.NET, you may edit the following ATZ_WinClient.REG file and apply it to the client machines. The W32Time service utilizes the NTP protocol, so make sure this is enabled on the ATZ Server.NET Server.

Using other time clients to synchronize with ATZ Server.NET

  Cable Modems and Cable modem networks utilize the ToD or Time protocol. All thats required for these clients is that their DHCP packet contain the hostname or address of the ATZ Server.NET machine. Once the cable modems receive their DHCP packet they will contact the ATZ Server.NET server for their atomic time.

  Unix flavored operating systems all include time synchronization clients. To configure these to synchronize with the ATZ Server.NET server, please refer to their documentation.