2000 and XP, but I want to do more than that will let me.Kawaii said:Which version of Windows are you using? Most versions have a Power Management part of the control panel.
There is a who? I can't seem to find anything about it. Does it work like the unix 'who'?Kawaii said:Which version of Windows are you using? Most versions have a Power Management part of the control panel.
Edit: There is a 'who', ie the user logged in atm. Which person is logged in determines a shitload of settings, so thoretically the 'check who is using it' could work... Firewalls and stuff are a whole different matter, oc.
Errm, well technnically it isn't really a 'who', but i think you should be able to determine which account is logged in. I have no idea if there is such a program, but it should be doable.... (determine it remotely, oc)Mirlyn said:There is a who? I can't seem to find anything about it. Does it work like the unix 'who'?
Mirlyn said:2000 and XP, but I want to do more than that will let me.Physically turn the machine off after an hour of inactivity. I can turn the machines off remotely now, but I can't tell if anyone is logged in or if someone is, how long they've been idle.
Mirlyn said:Getting closer....got it to work by doing some scheduling.
Now I need to figure out how to do it via command-line.
Tried...but "at" doesn't have a switch for idle. It seems to only accept 24-hour time values.rrfield said:Is it possible to use "at" commands instead of the windows scheduler for this specific case?
rrfield