General discussion

Locked

Changing System Time

By pete_may ·
Can anybody see any problems with giving domain users the right to change system time. It'll save me from logging on and doing it for them but this right is restricted to Administrators and server operators by default.
Any comments
Peter

This conversation is currently closed to new comments.

19 total posts (Page 2 of 2)   Prev   01 | 02
Thread display: Collapse - | Expand +

All Comments

Collapse -

Changing System Time

by bill.parks In reply to Changing System Time

Yes, one of the most important elements of corporate computer use is the ability to track time. As Bill mentioned in post #1, not only will email times be potentially off, but the ability to exploit that is definately more significant.
Imagine a corporate user in a legal bind, his ability to "go back in the past" and send out a corrective email is not something the business should allow. Local file time stamps are also affected by this. Think carefully and consult your executives before allowing this.
An alternative is TimeServ, or W32Time, both found in the resource kits. These allow you to sync NT machines to a central time source. These run as services and are not affected by typical user interaction.
I agree with Bill, in post#1.

Collapse -

Changing System Time

by pete_may In reply to Changing System Time

Poster rated this answer

Collapse -

Changing System Time

by bobspearing In reply to Changing System Time

Bill is dead right about confusion, I was using win98 to edit system policies on the NT server, when I checked the server the files had last been edited the following day !
The user of that workstation had set his system to pacific time.
As you can imagine it raised my heartbeat for a while.
Bob

Collapse -

Changing System Time

by pete_may In reply to Changing System Time

Poster rated this answer

Collapse -

Changing System Time

by gowen In reply to Changing System Time

If you want to remove the hassle of having to modify the time of all the computers on your network, then you should think about deploying something like Tardis. See http://www.kaska.demon.co.uk/ for details.

It can find out what the right time is in various ways including using networked timeservers, GPS (The Global Positioning System), and by listening for time broadcasts over a LAN. You can even configure it to use one machine on your network as the master time source.

Collapse -

Changing System Time

by pete_may In reply to Changing System Time

Poster rated this answer

Collapse -

Changing System Time

by Blackbeard In reply to Changing System Time

Many good replies... Assuming that your clients are NT workstation:
-using NET TIME in the login script will still require you to give permissions that will allow users to manually change the time.
-i'd go with the suggestion of using the TIMESERVservice rather than TARDIS. Timeserv is free and Tardis is shareware. You can set the timeserv service to run as a system acct and don't have to grant the user any permissions. If you roll out a standard timeserv.ini file, all the workstations can be pointed to a master time server. Then you can have that master server synchronizing it's time with an atomic clock over the Internet. We actually use Tardis on our master time server because we're behind a firewall and it supports using port 80 through a proxy server. Timeserv will only use the standard NTP port. We didn't want to open another port on our firewall.

Collapse -

Changing System Time

by pete_may In reply to Changing System Time

Poster rated this answer

Collapse -

Changing System Time

by pete_may In reply to Changing System Time

This question was closed by the author

Back to Windows Forum
19 total posts (Page 2 of 2)   Prev   01 | 02

Related Discussions

Related Forums