The only possibility that you might have is to build an LDMS query that includes a column in the output for the "install date" of a particular software.
Look for "Software" - "Add or Remove Programs" - "Program" - "Install Date"
You'll want this in the column output.
You'll probably want to use "Software" - "Add or Remove Programs" - "Program" - "Name" = "Name of the software here for the query itself.
Beyond this, LANDesk installed items do not necessarily include any sort of date as to when it was installed, which means even in the above method, you won't be able to tell the difference between when the software was installed via LANDesk and when it was installed manually, though based on the date range you might be able to deduce that the installs were done through a LANDesk scheduled task based on when it was used.
If you keep your scheduled Tasks, you can see all Tasks on a Client, by right clicking inside the Landesk Console and checking under Scheduled Tasks and Polices.
Otherwise, a good Idea, is to mark every Software Installation by setting a Special Registry Key or writing a Dummy File, so you can
read out this as Custom Data and make a Report on this.
Hope this is helpful for you.
Since were throwing out suggestions of ways to have the information for future purposes, I'd recommend using custom definition patch for each software package installation. This way you gain the data points of a patch which includes several date values including an installation date. These are built-in values, so no need to create customization in the package to tatoo a device with a value that then requires a modification to the inventory template, or a custom definition to look for that value. This is a big move to take on though, since its a significant change to building packages. We made this move many years ago, and from what i'm hearing it sounding more and more like LANDesk is going to merge the software distribution side and the patch manager side into a single thing some time in the future. We'll see!
Maybe this is possible if the application stores the installation source in the registry or file. For example, I recall Office and other apps having a registry key that would tell the original installation source. You could then use a custom definition to see if this value(s) exists. Custom definitions have been great for identifying and/or changing small values or files like this.
Having this entry to identify whether or not an applicaton was installed via LANDesk would be an excellent built-in feature.(A great ER) Here at our University most of our students come in person to have software installed but also have the option to use the Software Portal. I can look at the Scheduled Task to see how many have taken advantage of installing Office, etc via LANDesk but this is not accurate at all for me. Reason being is that not all installations are successful and the student decides to come in and get software installed.
I just created an ER for this.