Re: Email on user login/unlock


<requeth@xxxxxxxxx> wrote in message
news:681c5cf8-20ee-4542-84f8-50a41ef4071d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hey,

I want to have a script fire off an email when a user logs in to one
of my servers, or when they unlock their session. I can do the email
part easy enough, but do any of you have ideas of how to identify when
someone does an interactive login and/or unlock?

I can do vbscript, batch, and I can figure out most other things. I
have a mixed windows 2000/2003 environment.

Your best bet to detect when someone logs in is to use a domain-wide logon
script.

Your only bet on the unlock is to run something as a service or perpetual
scheduled task on each workstation, however, I have no idea how that script
or program would be able to detect when the user unlocked the workstation.
Note that when the user enters their domain password to unlock the
workstation, that is strictly a local operation that does not do any
transaction with the domain controller.

How many users do you have. how often do you expect them to logon, and what
will you do when you receive these emails? A more common method for tracking
user logons (but not unlocks) is to have your logon script write info to a
logfile on a server giving the date, time, workstation, and user. You can
then examine that logfile at any time to get a picture of who has logged in
recently.

/Al


.

Relevant Pages

  • Re: bad logon attempts against the Unlock dialog box dont count
    ... Are you trying to unlock the machine with a different user than who has ... Can you please send precise steps to reproduce the problem? ... > a server or workstation using Ctrl+Alt+Delete, bad logon attempts against ...
    (microsoft.public.win2000.security)
  • Re: windows 2000 lock workstation auditing
    ... No events are logged when a workstation is locked. ... You see a logon and logoff event at unlock, ... then destroy the resultant, unneeded logon session. ...
    (microsoft.public.win2000.security)
  • User cant log on (weird)
    ... One user keeps experiencing the following--he locks his workstation ... and then can't unlock it. ... code 0x18 which indicates logon failed due to wrong username or password. ... But user has correct username in logon box and is typing password correctly. ...
    (microsoft.public.windows.server.active_directory)
  • Re: More than one vbs file
    ... > which are needed at each logon (based on the user name, group memberships, ... > the OU he is in, the workstation he is using, etc), then it will be more ... > sub include ... If there is a need to have a different script ...
    (microsoft.public.scripting.vbscript)
  • Re: More than one vbs file
    ... >> which are needed at each logon (based on the user name, ... >> the OU he is in, the workstation he is using, etc), then it will be more ... If there is a need to have a different script ... The reasons we're moving to vbs is that the users won't have to download the ...
    (microsoft.public.scripting.vbscript)