Re: Force Logoff if Inactive (idle time)
From: Harry Paratestes (harryp_at_newz-grp-reader.com)
Date: Sat, 15 Nov 2003 14:41:15 -1000
Think I'm getting warm.....
"Harry Paratestes" <firstname.lastname@example.org> wrote in message
> Thanks for feedback.
> Just now I checked out the Scheduled Task Wizard on W2K client. I believe
> could do what you're suggesting, but the missing piece to the puzzle is
> 'inactivity timer'. Did a little more research on this and it dawned on
> that there MUST be an internal clock/process/service/daemon running on W2K
> that determines inactivity. No surprise here, screensaver and Power
> functions [Control Panel/Power Options] obviously are triggered by some
> keypad or mouse activity timer. Terminal services on W2K Server has
> inactivity function too (bounces users if not activitely using TS).
> If anyone has insight on the process/service/daemon that determines
> and/or mouse inactivity on W2K and how to exploit it, any guidance or
> will be much appreciated.
> HP sends
> "Torgeir Bakken (MVP)" <Torgeir.Bakkenemail@example.com> wrote in message
> > Harry Paratestes wrote:
> > Hi
> > You can't do this detection from the DC, it will have no idea about if
> > workstations are idle or not, you need to do this on the local computer.
> > I don't know of any way with a script to determine idle time, but the
> > Steve suggested should work, creating a Scheduled Tasks on every
> > kicks in after x minutes of idle time and runs a logoff script/program.
> > --
> > torgeir
> > Microsoft MVP Scripting and WMI, Porsgrunn Norway
> > Administration scripting examples and an ONLINE version of the 1328 page
> > Scripting Guide: http://www.microsoft.com/technet/scriptcenter
> > > Thanks, read something similar on a bulletin board after my ng post.
> > > "scheduling" of the logoff was kind of the first thought we had. We
> > > up just having to go with that. In a perfect world, we'd like an
> > > trigger" where logoff only occurs if certain condition exists (i.e.
> > > inactivity after X# of hours/minutes). I've found off-the-shelf
> > > that can do exactly this, so I'm thinking it can be done, not to
> > > IT budget is a joke and the thought of buying these products is OOQ.
> Out of
> > > frustration, we're moving away from GPO or ResKit tools and towards
> > > script-writing. We're thinking to implement the LOGOFF.EXE tool, but
> > > sure what mechanism is available to determine 'idle time' on the
> > > workstation. And when inactivity condition = TRUE, how does the DC
> > > the LOGOFF.EXE on the workstation / luser account?
> >"Steven L Umbach" <firstname.lastname@example.org> wrote in message
> > You might look at using Scheduled Tasks to run logoff.exe or
> > after a certain period of idle time - up to 999 minutes though I don't
> > of a good way offhand to implement it on a large number of
> > Steve
> > "Harry Paratestes" <email@example.com> wrote in message
> > news:firstname.lastname@example.org...
> > >
> > > Anyone know of tool/script/CMD that will automagically log
> > > off lusers after timeout has expired? Situation we have
> > > is lusers habitually locking their workstations and never
> > > logging off. Most recently, we've found out that a couple
> > > lusers from a remote office are currently on-travel and
> > > left their workstations powered on with screens locked.
> > >
> > > We have password locked screensaver implemented to kick
> > > off after 15 minutes of inactivity. We'd like ability to
> > > subsequently force logoffs after 24-36 hours of inactivity
> > > (weekends, business travel, etc.). We do NOT want to
> > > change our current screensaver set up (i.e. don't want to
> > > use Winexit.scr or something similar).
> > >
> > > I looked at Winexit.scr and also for a GPO security
> > > setting. No luck on GPO and Winexit didn't seem to do
> > > what I wanted. Don't want to implement the "working
> > > hours" GPO either which would log off or lockout lusers
> > > during certain hours of the day (we occassionally have
> > > shift work, also some lusers travel to various timezones).
> > >
> > > Summary: Luser locks workstation or password-protected
> > > screensaver kicks in. If no activity for 24hrs, luser
> > > gets bounced (and/or system reboots).
> > >
> > > Any tips? Is this even feasible?
> > >
> > > HP sends
> > >
> > >
> > >