Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Time Server in NT4-domain; user rights problem

Status
Not open for further replies.

Xypriz

Technical User
Oct 30, 2002
6
NL
Hello all,

I've got a problem setting up a good time synchronization in our NT4-domain (with NT4 and 2k workstations)

The problem does not lay on the time server itself. I can use TimeServ.exe (M$), a third-party time-synchronize tool or maybe even a Atomclock-card.

The problem is the workstations which have to synchronize the time with the time server when a user logs on. The synchronize command is executed by a KiXtart script. In most cases this command fails because users doesn't have sufficient rights to set time.

I tried to set a policy for all domain users, so they have specific time synchronize rights (User Manager). This doesn't work out because it seems to that the local settings overrides the domain settings.

Is there any way to get this problem resolved? For example, is it possible to let the time server PUSH the time to the workstation when a user logs on?

Thanks in Advance...
 
Tedious, but you can use User Manager for Domains to remotely connect to the local machines, and modify their local permissions as to who can edit the time. [auto] MCSE NT4/W2K
 
Thnx for your reply.

I know that's an option... but is there no way to automatize this process using policies or time pushing?

We are talking about approx. 150 workstations... it's a bit cumbersome when I've to configure them all manually :'(
 
You may want to try a better solution - something like Tardis (server) & k9 (client) (don't know where to get them sorry). The client runs as a service, listening on a port specific for updates from a Time Server. We have that set up on site, with updates every 5 minutes and it works a dream.

As the client is a service, it runs with enough permissions to modify the clock. K9 installation is easy, and can be scripted in about 3 lines (Copy, Install, Start). I assume that the server you are using can make time broadcasts (tho the port number escapes me at the moment, it is UDP) and any client such as k9 will work.

Good Luck

Cheers,
Sam

Please let members know if you found their posts helpful.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top