huggy59
Active Member
No, the AT scheduler wouldn't give you the ability to stop the shutdown once it started, but you could kill the scheduled shutdown before it starts if you were using the PC.
Then again, if you use different user accounts, you can set a local or domain-level (or AD) security profile so that it enforces account or system usages times... I'm not sure you can force a shutdown this way, though. And it would depend on the OS as to how granular this would be.
Either hook into a screensaver timeout, or use the power management to shut the machine down or go into sleep mode after so many minutes of inactivity. Or use a scheduler that shuts it down at a specific time.
No one solution is going to cover every scenario, though. Maybe the real solution is to teach the kids to do it right or suffer the consequences.
Here are some possibilities:
The one I use: http://www.splinterware.com/products/wincron.htm - lots of good features, including sending keystrokes to running programs, checking if a program is already running, etc.
The one already in XP: http://www.iopus.com/guides/winscheduler.htm
Then again, if you use different user accounts, you can set a local or domain-level (or AD) security profile so that it enforces account or system usages times... I'm not sure you can force a shutdown this way, though. And it would depend on the OS as to how granular this would be.
Either hook into a screensaver timeout, or use the power management to shut the machine down or go into sleep mode after so many minutes of inactivity. Or use a scheduler that shuts it down at a specific time.
No one solution is going to cover every scenario, though. Maybe the real solution is to teach the kids to do it right or suffer the consequences.
Here are some possibilities:
The one I use: http://www.splinterware.com/products/wincron.htm - lots of good features, including sending keystrokes to running programs, checking if a program is already running, etc.
The one already in XP: http://www.iopus.com/guides/winscheduler.htm