[THIN] Re: OT: Locked accounts...identification

I struggle with this every time I change my password.  I've had some success
using the psloggedon utility from sysinternal.com.  It's a free utility that
will tell whose logged onto a machine locally and/or through resources, but
you can restrict it to just local.  If you just run it with a username, it
will scan all machines it finds on the network to see if the user is logged
on.  You can redirect the results to a file and review later (so psloggedon
uname > output.txt).  That works pretty good, but only works for one user at
a time.  If you need to check for multiple users and have a bunch of
machines, it can take quite some time.  What I've typically done is taken a
list of all my machines (use "net view" and then clean it up in Excel) and
then put together a batch to call psloggedon with a -l switch on each
machine on the network.  So, the batch contains a bunch of "psloggedon -l
\\compname <file:///\\compname> " commands.  Run that batch, redirect the
output to a file, and then search the output file in the morning for all the
users you're having problems with.

 

It's kind of awkward, but it works.  The utility is available at
www.sysinternals.com <http://www.sysinternals.com/> , or if you need it, let
me know off list.  Good luck

 

 

-----Original Message-----
From: Claus, Brian [mailto:BClaus@xxxxxxxxxxxxx] 
Sent: Wednesday, July 30, 2003 3:57 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] OT: Locked accounts...identification

 

We have a few users who keep complaining about their accounts getting locked
out.  Is there a utility that can be used to find out the computername or IP
address of where a user is logged in on the domain or how many times they
are logged in?

 

My thinking is that he logged in on a warehouse PC, then logged in on his
own PC and then changed his password.  Since the warehouse PC is still
logged in under the old name, could this be causing the locking of his
account?

 

Any help would be GREATLY appreciated on this one.

Other related posts: