In ZENworks Asset Management (or Asset Inventory that is included in the ZENworks 7 suite) you can collect info about data files on workstations.
A great example would be if you ran Lotus Notes, and wanted to know what databases were stored on the local machines. (What is nice about the Notes example is that it uses files that end in .NSF.)
Here is how you do it.
Use the Manager (It is called just Manager), the Win32 app on the Collection Server and look at the production Collection Option set.
On the third tab, you can enable collecting info about files. Unselect .EXE, since ZAM uses fingerprints that are more efficient at recognizing the installed applications than simply looking at file names.
Then in the file extension field, enter the extensions, semi-colon separated. The docs say to use something like NSF; NTF; etc... But it turns out it won't work with a space. So NSF;NTF; would be the syntax to use.
The limitation to this is that once ZAM finds an application via fingerprints in a directory, it will stop looking in the directory. But it will continue looking in subdirectories.
In the Lotus Notes example this works well, as the Notes.exe is usually in \lotus\notes and the NSF files are usually in the \lotus\notes\data directory.
When you want to report on it, you can create a custom report in the web client, that looks for File Extension = NSF, and since, by default, Notes installs have many default databases on the local workstation (Bookmark.nsf, names.nsf, etc), you can also add a filter line that says File name "is not in list" and when you use the picker tool, (after an inventory has run at least once with the scan for NSF enabled) it will show all the found file names, and you can select them all to exclude.
If you have any questions you may contact Geoffrey at geoffcTAKETHISOUT@TAKETHISOUTyorku.ca
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.