LANDESK doesn't return this information, only what is executed locally and exists locally. Part of this is that the inventory scanner doesn't scan network locations so it has nowhere to link usage data to. The only way (I know of) to get around this with LANDESK is to wrap the launch of the executable with another executable that is on the machine and configured to run the network version of the app (as stay resident while it is running it. You wouldn't actually report on the network app, you would report on the local app used to launch the network app. It's a bit of a fudge but possible.
Alternatively, if the application is a unique executable name then our plug-in, State Management, may help to provide the information you need. It won't update LANDESK data about this, again because it doesn't have anything there to update but it can give you total launches and concurrent usage information.
Mark McGinn
MarXtar Ltd/MarXtar Corporation
http://landeskone.marxtar.co.uk
LANDESK One Development Partner
The One-Stop Shop for LANDESK Enhancements
