Determine whether a computer is locked out (versus actually being in-use)?
Posted on 2010-01-07
Hey experts -
Is there any way to figure out if a machine has been locked out (or possibly even when screen saver is in use)? I frequently remote to workstations and use PsTools such as PsExec to deploy stuff to the machines, but the fact that I have to do this during business hours makes it a bit harder for me. I currently use psloggedon to determine if a user is logged on a machine, but it doesn't tell whether the user is actually ON the machine and currently using it or whether the user has decided to lock his machine and go out to lunch.
My current method is to:
1) use psloggedon to determine if a user is logged on, and WHEN the user logged on
2) call or email the user to request them to log off so i can patch/troubleshoot their workstation
The problem with this method is my organization has not been proactive in updating the phone roster.. so a majority of users don't even have phone numbers listed in the GAL or they have OLD numbers listed in the GAL. When i attempt to email them, most of the time they are slow to respond or don't respond at all. In addition to this, we have a good number of users who NEVER log off their machine, but lock their machine.. so my current "logon/logoff script" which records the last username/time for each computer in AD is not as accurate as it could be.
So some entries might say the user was logged on since 3 weeks ago on a particular machine even though they haven't logged on since 2 weeks ago (when they left for vacation but never logged off their machine). So what I resort to is either booting them off and hope they don't complain. What would be nice is a way to figure out when the user has locked their workstation, so I can make an executive decision and assume they left for the day and kick them off so I can do my job.
Are there any commands (i.e. pstools or sysinternals tools) or even vbscripts or batch files that can grab the status of the machine (remotely) and report it back?
And yes, yes I know that I could make some policy changes to force users to log off their machines and automatically kick them off after a certain period of inactiviy.. but that's a question for another day. That would be something that'd take some time bc I'd have to move that up the chain, and I'd rather find a quick solution now to get my work done now. >_<!