Link to home
Start Free TrialLog in
Avatar of cprietom
cprietomFlag for Spain

asked on

I want to know on which computers a user is logged on

I think the subject of this question is self-explanatory.

There are two options:

1. I am REALLY stupid.

2. Windows does not have an easy way of knowing where in
the domain computers a user is logged on.

What I need it for?.
When I started administering this university Windows 2000
environment, I created a temporary account called "student" that the users could use if they had problems with their own accounts. Now I don't need that account but I DO know that some students still use it instead of their own one. So, before disabling the account I would like to know who are those users.

Any idea of how to make it?
I've tried usrstat but it just tells me the last time the users logged on anywhere and, what I want to know, is on which computers the user student is logged on at a specified time.
Avatar of jkr
jkr
Flag of Germany image

Add a logon script to that account that informs you about users logging on under this 'student' account.
www.goverlan.com has a routine that queries all domain controllers about a given user. It is not free, but they have a fully functional trial version.
ASKER CERTIFIED SOLUTION
Avatar of NEOsporin
NEOsporin

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of MSGeek
MSGeek

to add to jkr's advice, have the script use the net send command to notify you what workstation they are on.  The destination would be easy and there is  a variable for the workstation name.

Another evil way to deal with this would be to send a long series of beeps in the logon script.  This would alert those around the user, if the computing areas are monitored they can let you know who got zapped.
Avatar of cprietom

ASKER

Great,  http://www.controtex.com/NTAdmin.htm was exactly the tool I was looking for,

thanks a lot
I like the NTAmin.htm answer as well.  I looked at PSLoggedon and it looked like it might present a problem across different broadcast domains.