Well - you'd have to add ".ini" as a scan-extension, but overall I don't think SLM would be a good way to do it.
Personally, I'd write a little script (VB or whatever your poison is) and run that at login. This little script's purpose is to find this INI-file and identify its version (based on stuff you feed it) ... the results (i.e. "MyScreensaver version 10.5" or whatever) could then be simply fed into inventory via custom data ... nicely automated, and VERY easy to query against (since it's custom data, it would thus be a normal field you could build queries on).
This might work better for you?
LANDesk EMEA Technical Lead
Paul raises some good points. Screensavers are basically exes with a scr extension. So if you right click on the scr files you will see that it has a version tab. So if you really want to track the version of the screen saver file, one option could be to include .scr in your ldappl and then use slm to track. I have not tried this but it should work in theory. Also there should not be that many scr files on a machine (could be wrong) so it should not bloat the db too much.
If it is only the .ini file you are interested in then try using the Configuration Files section of the ldappl3.template file:
; Configuration files
; Ommission of the drive letter works on all local hard drives. There can be
; 4 CfgFilesx lines and more items per line.
Uncomment one of these lines and add the path to the .ini file you want to collect. Then the inventory of the machine will have an entry similar to the screenshot.
This will let you see the file size etc, plus it will also keep a copy in the DB so you can browse the contents (but not search it via a query).
Mark Star - MarXtar LANDesk Enhancement
Home of Power State Notifier & Wake-On-WAN for LANDesk
config file.bmp 45.7 K