How can I prevent a user from changing the system date and time in Windows XP SP3?
Hi,
I'm using Windows XP SP3.
It's running a third party(VC++) application that uses the system date and time.
It has no internet access.
It seems that some of the staff are changing the system date and time, and thereby affecting the date and time, The third party application will not run properly.
is there a way to prevent from changing the system date and time ? Pls help me.
Re: How can I prevent a user from changing the system date and time in Windows XP SP3
If it's a domain computer, then just edit the user's group policy.
If this is some sort of timeclock machine for calculating important things like work hours...then not having an internet connection is a very unintelligent setup! You should always be checking the time from a central server.
If the post was helpful...Rate it! Remember to use [code] or [php] tags.
Re: How can I prevent a user from changing the system date and time in Windows XP SP3
As long as the users run as admins you can't prevent them from doing anything.
You might use an alternative solution like:
- Refusing to run if the system clock has been set back since last run.
- Call GetTickCount now and then, accumulate and limiting the total time the app has been runned.
Remember though that all software protection schemes are breakable, no matter what effort you put into it.
Last edited by S_M_A; April 16th, 2012 at 12:57 AM.
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
- Brian W. Kernighan
Re: How can I prevent a user from changing the system date and time in Windows XP SP3
I haven't tried to tamper with any of MS trial packs so I don't know how hard it is to bypass. Anyway, most users tend to want to have a proper time in their machines. Pretty much everything gets awfully confusing when file time stamps can't be trusted anymore.
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
- Brian W. Kernighan
Bookmarks