Software that shows which user is logged into which machine - pulls from AD

[Svarcy]

Hey guys,

does anyone know of a piece of software that will pull the list of stations and users from AD and then give you a run down of which user is logged into which machine? Not after anything fancy just something that goes:

Station Example: User Example:
PC-01 Name-01

My school previously ran an RM network which had a feature like this in the management console, we now run a vanilla Win XP, Server 2008 R2 network and would like a small bit of a software we can pull up when needed for this.

Cheers

[glennda]

I use Webman's Login Tracker. Uses a Script to report to the DB at login and log off.

Then has a nice web interface which can be viewed either per machine or per user.

[FN-GM]

You might be able to do something with this - Check who is logged into a machine - Blogs - EduGeek.net

[Svarcy]

FN-GM. Thanks for that, so simple! We have decided to go with that one for the time being, I may get one of my senior colleagues to have a look at Glenndas post as it is abit above me at the moment. Thanks for both of your input though.

[penfold]

I use Webman's Login Tracker. Uses a Script to report to the DB at login and log off.

Then has a nice web interface which can be viewed either per machine or per user.

Sorry to drag up an old thread, but I've just set this up but I want to restrict access to the web interface to IT staff only. How do I go about setting it so only staff can view the webpage?

[glennda]

Sorry to drag up an old thread, but I've just set this up but I want to restrict access to the web interface to IT staff only. How do I go about setting it so only staff can view the webpage?

what are you using IIS or Apache windows or linux?

[penfold]

We already had Xampp running Apache & MySQL on Windows 2008R2 so I just added it onto that.

[TheScarfedOne]

The login tracker in HAP will do this...Home Access Plus+

Shameless plug for @nickbro

[sted]

is this any use it adds the computer name a user last logged on to their office field in ad (obviously you need to delegate users permissions to change this attribute)

Const ADS_PROPERTY_CLEAR = 1

Set objSysInfo = CreateObject("ADSystemInfo")
Set objNetwork = CreateObject("WScript.Network")
strCompName = LCase(objNetwork.ComputerName)
strUserDN = objSysInfo.userName
Set objUser = GetObject("LDAP://" & strUserDN)	' Bind to the user object in Active Directory with the LDAP provider.

objUser.Put "physicalDeliveryOfficeName", (strCompName)	'...add the computer name to Active Directory profile...
objUser.SetInfo										' ...and save the changes.

lastpc.jpg

[glennda]

We already had Xampp running Apache & MySQL on Windows 2008R2 so I just added it onto that.

Ok you can either make a basic .htaccess file which limits the access to the website via IP address - or username, then just give everyone that needs access to it static addresses.

Limit certain ip to access website with .htaccess - Techie Corner

[penfold]

I've now got this setup but am just finding one thing which is slightly annoying. The log shows that some staff are logged on for a number of days and I'm assuming this is because staff are leaving their machines logged on but because we have an automated shutdown which forces the machine to power off at night the logoff script doesn't run. If I add the logoff script to the computer shutdown would this solve the problem, or would that cause errors?

Edit: This is actually showing for all users, meaning first thing in the morning you can see lots of people logged on even though it may only say 6 people logged in today.

[penfold]

Just to bump this thread, it looks like the reason this isn't running properly is due to some group policy issue. If I put a computer in 1 OU it works fine (as it has for students) if I put it in to another (staff OU) for some reason it doensn't pull the OU details through and when you logoff it doesn't register. I've looked at the group policies pulling through on the client and I can't see any difference.

Any ideas where to start looking?

[penfold]

OK, just an update in case anyone else falls to this. It turns out it was the field lenght of the OU's in the logon tracker database. It was set to 20, but the OU name where the problem was was longer. I have increased the value and now it works fine.

[speckytecky]

Hi @Savrcy - good to see you getting answers that you thank for in following posts. I'm reckoning @FN-GM and @Glenda would be well happy if you happened to hit the thanks button under their answers as well if you haven't noticed it.

FN-GM. Thanks for that, so simple! We have decided to go with that one for the time being, I may get one of my senior colleagues to have a look at Glenndas post as it is abit above me at the moment. Thanks for both of your input though.