Discussion Locked

synching clocks over a network

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a primarily NT 4.0 sp 6a domain. In order to pool some of our software, we need the clocks on all the sytems to be within 10 minutes of each other. We've tried a login script, but the clocks aren't updated as the users don't have admin rights. I'm trying to figure out the timeserv program that came on NT server resource kit, but am running into some confusion. Does anyone have a straight forward and simple way to implement this? Thanks!

12 replies

by agibbs

The easiest way to do this would be to grant your users the "change the system time" right. To do this, fire up User Manager for Domains, click on Policy then User Rights, select "Change the System Time" from the list and add the "Users" group to the list.

by jason.barnett

Unfortunately the previous answer gives the Users group the right to change the system time on all Domain Controllers.

If you want to give the user the rights to change the system time on the local machine you will need to either make them a member of Power Users on the local machine or grant the right to change the system time to the Users group. This is indeed a pain and tricky to get round. I'll have a think and post the answer later unless someone gets there first.

by deb2

You could use the NT Resource Kit utility SystemTimeRights and give the users permission to change the system time. With this utility, you could roll it out to every PC in a batch file. You could also use the set time command in a batch file to set the time to a server, and put it in the All users startup group. Every time the user logged in, they'd get the correct time.

by seadogs

Could you tell me where to find the system time rights on the resource CD? Is that on the server or pc? Thanks,

by clrichardson

I am using TimeServ from the resource kit. I have 1 machine use a modem to set it's clock (Master) twice a day. Then 3 domain controllers set their clocks to to the master three times a day. All other server/workstations set to the DC's again three times a day. All automatically with NO user interaction.

Most of the TimeServ.ini items are optional settings. The ones I've changed for all of the workstations/servers follow. ALL other settings are remarked out or blank.

Type=PRIMARY
PrimarySource=\\XTASCY;\\HECKEL;\\JECKEL (my DC's)
Period=0
timesource=no
Log=yes
RandomPrimary=yes
TAsync=no

This should help get you started.

by clrichardson

I am using TimeServ from the resource kit. I have 1 machine use a modem to set it's clock (Master) twice a day. Then 3 domain controllers set their clocks to to the master three times a day. All other server/workstations set to the DC's again three times a day. All automatically with NO user interaction.

Most of the TimeServ.ini items are optional settings. The ones I've changed for all of the workstations/servers follow. ALL other settings are remarked out or blank.

Type=PRIMARY
PrimarySource=\\XTASCY;\\HECKEL;\\JECKEL (my DC's)
Period=0
timesource=no
Log=yes
RandomPrimary=yes
TAsync=no

This should help get you started.

This discussion is closed to new replies.