How do you prevent users from changing the system time in Win98?

[yukichigai]

We're having a problem with users changing the time on the system clocks on the Win98 machines. Why is this a problem? Because the electronic timecard software uses the system time to determine when you clock in/out. Yeah, dumb, I know. Anyway, I've prevented users from changing the system time on all the 2k+ machines, but I can't figure out how to do it on the 98 machines. Does anybody know how?

 

[pcgeek11]

Originally posted by: yukichigai
We're having a problem with users changing the time on the system clocks on the Win98 machines. Why is this a problem? Because the electronic timecard software uses the system time to determine when you clock in/out. Yeah, dumb, I know. Anyway, I've prevented users from changing the system time on all the 2k+ machines, but I can't figure out how to do it on the 98 machines. Does anybody know how?

I don't think you can on windows 98 as it is not permissions based etc. Anybody can do anything pretty much. Why don't you use W2k for the timeclock software, much better anyway.

pcgeek11

 

[yukichigai]

Originally posted by: pcgeek11

Originally posted by: yukichigai
We're having a problem with users changing the time on the system clocks on the Win98 machines. Why is this a problem? Because the electronic timecard software uses the system time to determine when you clock in/out. Yeah, dumb, I know. Anyway, I've prevented users from changing the system time on all the 2k+ machines, but I can't figure out how to do it on the 98 machines. Does anybody know how?

I don't think you can on windows 98 as it is not permissions based etc. Anybody can do anything pretty much. Why don't you use W2k for the timeclock software, much better anyway.

pcgeek11

The Timecard software is actually on a 2k server, and run on the 2k server via network share. (It's really quite bizzare) It doesn't matter what the time on the server says, it pays attention the system times on the individual workstations. It'd be nice if we could upgrade them all to 2k+, but we can't.

 

[pcgeek11]

Originally posted by: yukichigai

Originally posted by: pcgeek11

Originally posted by: yukichigai
We're having a problem with users changing the time on the system clocks on the Win98 machines. Why is this a problem? Because the electronic timecard software uses the system time to determine when you clock in/out. Yeah, dumb, I know. Anyway, I've prevented users from changing the system time on all the 2k+ machines, but I can't figure out how to do it on the 98 machines. Does anybody know how?

I don't think you can on windows 98 as it is not permissions based etc. Anybody can do anything pretty much. Why don't you use W2k for the timeclock software, much better anyway.

pcgeek11

The Timecard software is actually on a 2k server, and run on the 2k server via network share. (It's really quite bizzare) It doesn't matter what the time on the server says, it pays attention the system times on the individual workstations. It'd be nice if we could upgrade them all to 2k+, but we can't.

I guess It makes it quite convenient for the employees to just come in whenever they want change the time on the PC clock in and then set it back to the correct time. I wouldn't allow a windows 98 machine on my business network especially for a timecard machine. Wide open and asking for trouble. It would be easier to set it up to only allow timekeeping functions from the Win 2K machines than to attempt to safegard the Win98 machines.

pcgeek11

 

[robphelan]

ha! 'dem some sneaky folks.. reminds me of a 'friend' back in the late 90's who wrote some VB scripts to auto populate Word & Excel with data every few minutes.

In case someone walked by afte he'd gone home, his machine would look different than the last time. Later, at a preset time, this 'friend' used a script to shoot an email to his boss letting him know he was leaving for the day.

 

[yukichigai]

Originally posted by: pcgeek11

Originally posted by: yukichigai
The Timecard software is actually on a 2k server, and run on the 2k server via network share. (It's really quite bizzare) It doesn't matter what the time on the server says, it pays attention the system times on the individual workstations. It'd be nice if we could upgrade them all to 2k+, but we can't.

I guess It makes it quite convenient for the employees to just come in whenever they want change the time on the PC clock in and then set it back to the correct time. I wouldn't allow a windows 98 machine on my business network especially for a timecard machine. Wide open and asking for trouble. It would be easier to set it up to only allow timekeeping functions from the Win 2K machines than to attempt to safegard the Win98 machines.

pcgeek11

This is a "bottom line" situation; even if it requires purchasing some bit of outside software it's still going to be cheaper than upgrading all the 98 workstations to 2k.

To reiterate: the solution is not "upgrade to 2k". There is nothing you can possibly say that will convince me, or more accurately my boss, that upgrading to 2k is prefferable to finding a way to prevent clock changes on the existing systems.

 

[doan]

Originally posted by: yukichigai

Originally posted by: pcgeek11

Originally posted by: yukichigai
The Timecard software is actually on a 2k server, and run on the 2k server via network share. (It's really quite bizzare) It doesn't matter what the time on the server says, it pays attention the system times on the individual workstations. It'd be nice if we could upgrade them all to 2k+, but we can't.

I guess It makes it quite convenient for the employees to just come in whenever they want change the time on the PC clock in and then set it back to the correct time. I wouldn't allow a windows 98 machine on my business network especially for a timecard machine. Wide open and asking for trouble. It would be easier to set it up to only allow timekeeping functions from the Win 2K machines than to attempt to safegard the Win98 machines.

pcgeek11

This is a "bottom line" situation; even if it requires purchasing some bit of outside software it's still going to be cheaper than upgrading all the 98 workstations to 2k.

To reiterate: the solution is not "upgrade to 2k". There is nothing you can possibly say that will convince me, or more accurately my boss, that upgrading to 2k is prefferable to finding a way to prevent clock changes on the existing systems.

Your only choice is to resort to registry hacking. Dissable the clock on the task bar, dissable the date and time control panel, password the BIOS, etc...

 

[bsobel]

Originally posted by: yukichigai
We're having a problem with users changing the time on the system clocks on the Win98 machines. Why is this a problem? Because the electronic timecard software uses the system time to determine when you clock in/out. Yeah, dumb, I know. Anyway, I've prevented users from changing the system time on all the 2k+ machines, but I can't figure out how to do it on the 98 machines. Does anybody know how?

You won't like the answer, but short of changing the user shell to something that strictly controls what they can run (and even there a knowledgable person could work around it easily) it just can't be done. The 9x line is not a secure operating system, no amount of glue will turn it into one.

 

[nweaver]

fire the people doing this, as they are not honest. or upgrade to 2K

 

[pcgeek11]

Originally posted by: bsobel

Originally posted by: yukichigai
We're having a problem with users changing the time on the system clocks on the Win98 machines. Why is this a problem? Because the electronic timecard software uses the system time to determine when you clock in/out. Yeah, dumb, I know. Anyway, I've prevented users from changing the system time on all the 2k+ machines, but I can't figure out how to do it on the 98 machines. Does anybody know how?

You won't like the answer, but short of changing the user shell to something that strictly controls what they can run (and even there a knowledgable person could work around it easily) it just can't be done. The 9x line is not a secure operating system, no amount of glue will turn it into one.

nweaver and bsobel are 100 % correct. Windows 98 wasn't designed with security in mind as they are simply INSECURE. Even a secure OS can be hacked if the person has access to the physical machine, there is Nothing you can do. You cannot polish a turd!
I would go the way nweaver suggested fire the bastid, as it is obvious that they are dishonest.... It is the only way, set an example.

pcgeek11

 

[loup garou]

Originally posted by: yukichigai

Originally posted by: pcgeek11

Originally posted by: yukichigai
We're having a problem with users changing the time on the system clocks on the Win98 machines. Why is this a problem? Because the electronic timecard software uses the system time to determine when you clock in/out. Yeah, dumb, I know. Anyway, I've prevented users from changing the system time on all the 2k+ machines, but I can't figure out how to do it on the 98 machines. Does anybody know how?

I don't think you can on windows 98 as it is not permissions based etc. Anybody can do anything pretty much. Why don't you use W2k for the timeclock software, much better anyway.

pcgeek11

The Timecard software is actually on a 2k server, and run on the 2k server via network share. (It's really quite bizzare) It doesn't matter what the time on the server says, it pays attention the system times on the individual workstations. It'd be nice if we could upgrade them all to 2k+, but we can't.

ADP eTime?
Have a Terminal Server at your disposal?

 

[yukichigai]

Originally posted by: pcgeek11
nweaver and bsobel are 100 % correct. Windows 98 wasn't designed with security in mind as they are simply INSECURE. Even a secure OS can be hacked if the person has access to the physical machine, there is Nothing you can do. You cannot polish a turd!
I would go the way nweaver suggested fire the bastid, as it is obvious that they are dishonest.... It is the only way, set an example.

pcgeek11

It's a shared computer. 5+ guys log in on the same computer, so we don't know who it is. Yet. I installed some monitoring stuff to keep an eye on it.

Even if it's "insecure", it doesn't have to be very complex. These aren't computer-savvy folks using the system.

But meh, I think I'll just leave the monitoring stuff on there, figure out who it is and watch the boss fire his ass. Should provide at least 20 minutes of entertainment next week.

 

[yukichigai]

Originally posted by: werk
ADP eTime?
Have a Terminal Server at your disposal?

My response has two main parts:

1) What?

2) Huh?

Did I mention this is my first net admin job?

 

[pcgeek11]

yukichigai

But meh, I think I'll just leave the monitoring stuff on there, figure out who it is and watch the boss fire his ass. Should provide at least 20 minutes of entertainment next week.

I love this response! Sorry I couldn't help you more! I hope you catch the b@stard red handed.

pcgeek11

 

[loup garou]

Originally posted by: yukichigai

Originally posted by: werk
ADP eTime?
Have a Terminal Server at your disposal?

My response has two main parts:

1) What?

2) Huh?

Did I mention this is my first net admin job?

I thought maybe the software you were using for schedule management was ADP eTime. I have a client who uses it, it runs in a similar configuration (off a network share).

A Terminal Server would solve your problem. It's going to be a bit complicated to set up if you don't even know what TS is.

Basically, the app will run multiple instances on the server. The win98 machines will connect over RDP and the time in the app will be the time that is on that terminal server. The best part is you can be really cruel and remove all other software off their computer that isn't necessary and just leave them with the RDP connection as punishment, if that's all they're supposed to be doing anyways.

If you already have a 2000 server, you could install TS off the 200 disc and use that if you have licenses...somebody remind me...were TS licenses included with the server CALs? I think they used to be. That way it wouldn't be any added expense.

 

[OdiN]

You could take away the mose and keyboard.

 

[LiLithTecH]

Are you forcing the user to log in (disable Cancel & ESC key)?

 

[Leros]

Can you have one time clock computer for the whole place?

 

[SoundTheSurrender]

Take a Picture of the desktop as is, than turn it to your background. Now hide the start menu to the background shows the start menu.