clocks on clients change

Time synchronizers are not standard with WinNT. However you can go to www.download.com and do a search for "clock sync" and you will pull up 40 hits. A lot of these hits are freeware.

Ultimately, you can choose how you want to set clock sync up. You can setup your server and client computer to pull the current time from a remote atomic clock server. You can serup your server to pull from a remote atomic clock server and have your client computers pull from the server you setup.

CMOSbatteries may need to be changed, but they should generally last more than 2 years -- but it will also depend on how these computers are used. You might want to purchase one or two batteries and monitor how the clocks behave thereafter. You could start loosing other settings if the batteries are going bad.

In many cases, if your users are using a batch file, or login scripts from your Dell Server running NT server 4.0, you can sync and set time from your server environment which can be more stable most of the time compared to workstations. If you are having CMOS battery problems on only 2 year old machines, this is not good. It is also unlikely that all machines in question are having CMOS problems. Either way, this can be directly affected by how many times a machine is shutdown and startedup in its lifetime.

Here is the Batch file command native to NT, called 'net time' that you might want to try:

net time \\server_name /set /y

Good Luck!

Paul M. Chavez