No idea if this the best forum or not, but I'm curious how does Windows Security handle situations where a user logs into the network and then has their machine crash where the user does not explicitly log out. Is the user still shown as logged in? Is there something on the network side that detects that the machine is no longer on the network and then shows the person as not logged in?David H

Hello Are we talking about an Active Directory Domain Network?Isaac Oben MCITP:EA, MCSE

Yes.David H

Hi, May I know your concern? If the machine is not accessible, the network sessions such as RDP session and SMB session will be disconnected after a period of time. This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

We're building a ASP.NET based telephone directory. Since the users will need to update their own information, we're tying their contact information to their Windows User Id. This will allow them to access their information by simply clicking on a link. It occurred to us that this would provide an ideal platform for identifying which PC and IP address the user is logged into. The idea is to run a logon script that updates the database given that the script can obtain their Windows ID, machine name, and IP address. A logoff script would then delete the record. The catch though is figuring how to deal with situations where the user did not explicity log off like when they just turn off the machine. We're using a SQL Server DB for the directory because we need much more flexibility than Active Directory provides and so that we can tie it into several other projects.David H