That value is straight from the OS - so yeah, only updated when someone "actually logs in".
Not overly useful.
If you schedule to run an inventory scan every day for instance, you can use the "last hardware / software scan" date/times as a general "finger in the wind" ... so if a device hasn't checked in the last 180 days, chances are that it's not been powered on / stolen / collecting dust somewhere.
What is it you're trying to do exactly - as "computer usage" is a bit of a nebulous matter. If you just want to ensure that a device is "on" and "connected to the network", a daily inventory (or vulnerability) scan may be enough for you.
If you're trying for more specific things, it'd help having more information.
SLM is certainly useful to monitor usage of specific pieces of software that you care about (usually to answer the questions -- "who has software X" and "who actually USES software X" ... so as to be able to reclaim unneeded expensive software licenses).
We are in the process of purchasing new computers and want to narrow down what to focus on.
Our computers wake up every evening, so while the last scanned date will help find computers with problems, it doesn't show us if the computers are being used. As a basic indicator of usage, I think the last time a user logged in to a computer will be enough.
I was worried that there may be other times that the value is updated, such as when a task runs as a specified user instead of the system account. I tested this yesterday and can confirm that the value was not updated in this scenario.
As far as SLM, I thought if we started monitoring common applications such as web browsers and MS Office, we would have a better idea of actual usage. I haven't really looked at SLM yet, so I'm not sure if there are any limitations to this.
That all sounds reasonable.
The only thing I'm surprised at is devices being powered up in the evening (usually that happens in the morning - so as to have power saved over night). But there may well be reasons for that .
Well - sounds like you've got a clear enough path ahead of you for now.
Let us know if you need more help / get stuck anywhere .
As for learning SLM -- the relevant community section -- Software License Monitoring -- should have a bunch of stuff / guides for you when you get to cross that bridge.
Would it be feasible to use SLM to track winlogon.exe? That could basically tell you how long and how frequently a system is logged into...
If you'd like more data in this area, take a look at our State Management plug-in module. This tracks the state of devices, users etc. and can help with this type of analysis.
MarXtar Ltd/MarXtar Corporation
Ivanti One Development Partner
Try MarXtar State Management for Ivanti to Better Understand and Manage your Assets