LANDesk does not track this information and it would have to be scripted. Depending on the amount and activity of the user(s) this would be a lot of information. Active Directory you could use eventcombMT.exe or if you want a starting query for the local logins http://www.droppedpackets.org/inventory-and-slm/logonhist/ The source code shows how to scrape the security logs.
One of my customers uses actions.ini and miniscan.exe's custom data flag to send an update for login. Logout is such a rare activity for most shops that it's hardly worth tracking.
I guess it is all about how they want to use the information. I read it as they want a historical record of all logon/logoffs. Some may want actual usage of the machine - primary owner, etc... There are many types of logons http://www.windowsecurity.com/articles/Logon-Types.html
Actions.ini is a neat trick.
Thanks for all the help guys .. This was actually for a flexi time program to record staff hours
I know not the best idea but they dont want to spend any money on this one ; )
I found a different solution using some PHP and a small client
1 of 1 people found this helpful
LANDesk Doesn't track when per se. If this is an absolute must, perhaps you can have a batch file in the run key of the registry that executes (silently) and records the date time and login name.
it would be simple:
echo logon %date% %time% %username% >>c:\myfile.ini
you could then use a tool like regtoinv to add the contents of myfile.ini to the LANDesk inventory scan data. Thats how I would do it~ you can even push out the registry changes and regtoinv via a custjob script.
Oh - forgot to mention -- you can have the same type of script run at logoff via group policy except it would say logoff instead of logon