login tracking question
Hi,
We would like to track the number of times a work station is logged onto and have that data saved in some format (excel?) that would be easy to crunch some numbers from. Currently we have students walk through our computer labs and count people using computers each hour but this isn't really good data because some people sit in there and study, not use the workstation. These are XP boxes. We would like the package to count the number of logins, not necessarily record who logged in, but it would be nice to track how long they stay logged in. It will help us make hardware purchase decisions. Is anyone doing anything like this?
Thanks,
Rick
We would like to track the number of times a work station is logged onto and have that data saved in some format (excel?) that would be easy to crunch some numbers from. Currently we have students walk through our computer labs and count people using computers each hour but this isn't really good data because some people sit in there and study, not use the workstation. These are XP boxes. We would like the package to count the number of logins, not necessarily record who logged in, but it would be nice to track how long they stay logged in. It will help us make hardware purchase decisions. Is anyone doing anything like this?
Thanks,
Rick
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
mrtap
20 years ago
You can use either group policy or local machine policy to set the computers to "Audit logon events". This information will then be recorded in the Event Log which you can view and export manually (locally or remotely) from eventvwr.exe. If sure also be possible to this programatically.
For more information refer to http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/518.asp
For more information refer to http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/518.asp
Posted by:
sean_c_roberts
20 years ago
For a more manual approach, you can write a little exe (in Wise or whatever) which can do a number of things to track logins...
1) Post to an http server on your intranet and have a web app intercept and parse them,
2) Write a litte text file to a shared network location - and you can just as easily use Wise to write a harvesting app.
To ensure unique filenames, I usually name the files with a combination of PCName and MAC Address (which you can get using Wise, too).
In my opinion, sometimes it's better to avoid large enterprise tools because they carry some serious overhead or have complications.
1) Post to an http server on your intranet and have a web app intercept and parse them,
2) Write a litte text file to a shared network location - and you can just as easily use Wise to write a harvesting app.
To ensure unique filenames, I usually name the files with a combination of PCName and MAC Address (which you can get using Wise, too).
In my opinion, sometimes it's better to avoid large enterprise tools because they carry some serious overhead or have complications.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.