Re: possible to log when a domain user locks workstation?



In particular look for type 7 logons. My experience however is that an event
seems to be recorded when the user unlocks the computer but not when they
lock it. Be sure to test it out to see what the results are. You may want to
implement a policy that users are required to logoff of their computers at
the end of a day with a reminder that lack to do so could result in
discipline and/or loss of data if you are forced to logoff users that just
lock their computers.

Steve

http://www.windowsecurity.com/articles/Logon-Types.html --- Windows logon
types

Logon Type 7 - Unlock
Hopefully the workstations on your network automatically start a password
protected screen saver when a user leaves their computer so that unattended
workstations are protected from malicious use. When a user returns to their
workstation and unlocks the console, Windows treats this as a logon and logs
the appropriate Logon/Logoff event but in this case the logon type will be
7 - identifying the event as a workstation unlock attempt. Failed logons
with logon type 7 indicate either a user entering the wrong password or a
malicious user trying to unlock the computer by guessing the password.


"Reluctant Sys-Admin" <ReluctantSysAdmin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:4E6E8682-1167-4F8E-A23C-B298AE644271@xxxxxxxxxxxxxxxx
Thanks Adam! I'll give it a try.

"Adam" wrote:

Reluctant Sys-Admin wrote:
I have a 2003 Server domain controller and XP workstations. I am
trying to
audit when domain users log on and off the domain for the day, however,
certain users are not logging off but simply locking the workstation at
the
end of the day and unlocking it the next day. These events do not
appear in
the security events log on the domain controller. Is there any way to
log
when a user locks a workstation either on the domain controller OR on
the
local machine?

Yes -- use group policy to enable logon/logoff success auditing on the
XP workstations.

Basically locking and unlocking a machine doesn't touch the network so
the domain controller will never know -- instead you have to gather
together the audit logs from the workstations.



.



Relevant Pages

  • Re: Unable to Logon
    ... The users cannot logon from their own workstations. ... >It's probably a Domain Controller. ... administrators can ...
    (microsoft.public.win2000.active_directory)
  • local policy of this system does not permit you to logon interacti
    ... I just installed a win 2k3 server as domain controller. ... joining the workstations to the domain, but when they try to logon as a user ...
    (microsoft.public.security)
  • RE: Event ID 529
    ... The source is clear - workstations that are not part of my ... SBS2003 domain share the same local network (it's a shared local network in ... This kind of issue may be caused by Application logon such as while Outlook ... is connecting to Exchange Server, or this is an automated dictionary attack ...
    (microsoft.public.windows.server.sbs)
  • Re: How do manage your workstations?
    ... For the most part these functions require a local administrator rights. ... Therefore I have to logoff the regular user, then I logon as local administrator so I can update programs or add-in devices. ... However, if there are hundreds of workstations involved, it’s really time consuming! ... Maybe there is remote installation system that push program updates to the workstation and that system logons on as domain admin. ...
    (microsoft.public.windowsxp.general)
  • Re: "Lock workstations" after certain idle time. Is it advisable to do it from server side
    ... > business needs, ... > to mitigate the risk of unauthorized access. ... > unlocked terminal or even a logon prompt without a warning can be ... >> workstations idle for a certain period of time. ...
    (microsoft.public.win2000.active_directory)