keep a list of whos logged in to which pc

[dhnriverside]

Hi guys

I'm trying to create an updated list of which of my AD users are logged onto
each computer - there's about 29 computers and we use hotdesking!

I'm using Windows Integrated Authentication, so I know who the user is, and
I obviously know the Workstation name they are on.

My theory is that I could put something in Session_Start to store the
User/Workstation in a database, and I could put something in Session_End to
remove that record.

Any thoughts on any possible problems with that? Also, how can I guarantee
Session_End is fired when the user closes the browser?

Cheers

Dan

[S. Justin Gengo]

dhnriverside,

That sounds like a fine plan.

Session is a timed event. The default session timeout is 20 minutes so your
session end event will fire 20 minutes after a user no longer makes contact
with the app by requesting a page / posting a page. You may change the
default session timeout.

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche
"dhnriverside" <da*@musoswire.com> wrote in message
news:73**********************************@microsof t.com...

Hi guys

I'm trying to create an updated list of which of my AD users are logged
onto
each computer - there's about 29 computers and we use hotdesking!

I'm using Windows Integrated Authentication, so I know who the user is,
and
I obviously know the Workstation name they are on.

My theory is that I could put something in Session_Start to store the
User/Workstation in a database, and I could put something in Session_End
to
remove that record.

Any thoughts on any possible problems with that? Also, how can I guarantee
Session_End is fired when the user closes the browser?

Cheers

Dan

[Norman Yuan]

Excuse me for my ignorant: I do not see how a computer user's loggin on to
his workstation could have something to do with your ASP.NET app's
Session_Start, if he does not start IE (or other browser) and go to your
ASP.NET app. Unless you have some login script running on each station that
send request to your ASP.NET app whenver a user logs on.

So, it is just very simple to write a loggon script to catch user logon
time, user name, computer name and save the infomation to database. This
script can be enforced by AD/Windows Group Policy, so that no user can
bypass it.

Then in you ASP.NET, you only need a very simple page to browse the user
logon data from the database.

"dhnriverside" <da*@musoswire.com> wrote in message
news:73**********************************@microsof t.com...

Hi guys

I'm trying to create an updated list of which of my AD users are logged
onto
each computer - there's about 29 computers and we use hotdesking!

I'm using Windows Integrated Authentication, so I know who the user is,
and
I obviously know the Workstation name they are on.

My theory is that I could put something in Session_Start to store the
User/Workstation in a database, and I could put something in Session_End
to
remove that record.

Any thoughts on any possible problems with that? Also, how can I guarantee
Session_End is fired when the user closes the browser?

Cheers

Dan