Hello @justanotherbod
This is a GREAT question. The challenge to answering this is first to understand that Lansweeper isn't a "monitoring tool". I say that because in order to fully know, real-time, who's using a computer, the asset must be scanned upon login -- via GPO's, login script, or local auto-runs, etc.
Therefore, to be 100% certain who's using which asset will require a few changes to the frequency and method of scanning that asset. You may want to consider some options.
LsPush is a comman line tool that is often recommended for this type of scanning upon login. Here's a KB that talks about LsPush: LsPush fallback scanning - Lansweeper Community. I'd also recommend searching our KB's for "LsPush".
Another work around can be found in ProTip #54. Jacob explains ways that you can use LsAgent to scan during login. To clarify, LsAgent is only designed to scan based off a schedule that's configured within the Web Console. But Jacob gives some ideas around manually making LsAgent run during login.
I don't think this answers your immediate question. But I hope it brings some clarity and work arounds to get the up-to-date and as real-time data as possible.
Let us know how it goes. Best wishes.
Tim
Tim N.
Lansweeper Employee