Discussion Locked

permissions to change time

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I want to change the settings on local workstations so that the "change the system time" is set to everyone. I want to do this b/c I want a login script to sync the time up with the server. I can change this setting manually at each workstation, but I can't find a way to set this setting centrally. Can this be done.
What I need done: From the local machine..User Manager...Policies..User Rights..then change system time(grant everyone access) is what I want to do, but I don't want to have to go to every desktop to do it. Thanks.

9 replies

by astute

The ability to change the time on an NT system is a Right that has to be granted through the User Rights Policy in User Manager (This applies only to a DOMAIN environment).

Start User Manager (Start - Programs - Administrative Tools - User Manager)
From the Policies menu select User Rights
From the drop down menu select "Change the System Time)
Click the Add button and add any users you wish to perform this
Click OK to exit the dialog
Close User Manager
The user will need to logoff and log on again

use NET TIME \\ /SET /YES

in login script to sync with the time server.

For work group environment. Create a batch script ( use ntrights command ) & ask all users to execute it.
Hope this helps
good luck

by ped

i'm not sure if i'm missing something but adding a script to each user logon profile should set the time for each user when they login. this can be done centrally.

why grant everyone access when it's done when they login?

by rcc

We're doing it exactly as sharankumar said. It worked well for us and we had no problem

by clrichardson

You can use a cmd prompt from your workstation and run usrmgr \\machinename.
That will get you to the user administration on the remote machine, not the domain, to set the rights, add "local" users, etc.

Why not use TimeServ from the NT resourcekit? It doesn't need any user action after installing since it runs as a service.

I have 1 machine call Naval Observatory in Wash. DC and set its clock twice a day. Three domain controllers set their clocks to that workstation three times a day.All other servers and workstations set their clocks to the DC's, also three times a day. TimeServ also sets the clock every time a machine is rebooted.

Happens automatically, no user action needed, can keep time permission restricted. All clocks are in sync.

Even if set using a script at logon, if you give everyone the right to change the time, some will do just that. And probably to a time of their chosing not the server's.

This discussion is closed to new replies.