>>>>>>SNIP ..
>>>>George, thanx for the reply but I will have to go in a new direction. For the short term I will just suppress the DOS window that appears when executing net.exe.
>>>>
>>>Since it appears that you are using Netware, what version?
>>>I ask, because 4.x has a utility called systime which we run at login and causes the client system to set it's time to the server's time.....
>>>
>>>Paul M.
>>
>>
>>What's to stop the user from changing the time after they log in? We had this happen. The boss said "We have to fix this immediately" So, we bought GPLib and we now pull the time from the server. We'll need a different methodology when we go to an NT server, but it shouldn't be difficult to use an automation server.
>
>I don't think you *can* stop the user from changing the time once his or her workstation is booted, short of having a program running continually that checks :^P
>I thought the question was: 'How do I reliably ensure all my workstations' clocks are set to the same time?'. You'll *never* get around an obnoxious user....
>
>Paul M.

Actually, assuming that not all users need 'administrative' access to the functions in the Control Panel, you can construct a set of System Policies for each user using POLEDIT (it comes with the O/S, and can also be downloaded from MS' site as part of ZAK). Admittedly, you can bypass login-level protections in Win95, but then they won't get connected to the network either if they cancel out of the login dialog. Obviously, admin users will be able to mung about at will, but you can block access to virtually all applets under the Control Panel, including the ability to alter time and date.

Under NT with an NTFS file system it's even easier, since you can assign permissions at the file level based on login ID and you can't bypass the login assignment.

hth,

Ed