lah
New Member.
2313 views

Can't create local product -. EXE file not listed

Hello there.

I'm having trouble with the listing of all EXE files on a machine and add it as a Local Product.

The inventory is configured to collect .exe from all folders, except some exceptions, like here. The list of excluded folders was configured by the previous admin.

We have a machine that shows a Product (Matrix Multimedia Ltd. Flowcode V5 for dsPIC_PIC24 5.5) in its inventory. Proof.

But... when I go to reports, software files and try to find the .EXE file associated with the app, it does not show up anywhere. Here is the report definition and result, where you can see the the file is not listed. As can you see here and here, it should be showing in "c:\program files (x86)" somewhere.

It's annoying, to say the least, as it's not working as expected. Or are my expectations wrong? Anyway, this is not the main problem.

The problem is that I want to tracka previous version, Flowcode V4, that is not recognized by ZENworks. So my only option is to create a Local Software Product. And I can't do that: the .EXE for the Flowcode V4 is nowhere to be found.

Any ideas?
0 Likes
1 Reply
BMcDowell1 Absent Member.
Absent Member.

Re: Can't create local product -. EXE file not listed

I believe what you're seeing here is the product working correctly. If a software product is recognized by ZENworks inventory, then the executable associated with the product is not listed in the software files data. Indeed, the discovery of a product in a particular folder should exclude any executables found in that folder from the software files scan. Effectively, the business rule for this case is "We found the product, so the executable itself is not relevant." The main reason to report an executable is for the creation of a local product, which you would not want to do in the case for the product discovered by inventory. So that covers your V5 situation.

As for V4, unless that version cohabits with V5 the executable should appear in the listings. Some manual inspection of a device known to have the V4 software installed is in order. You might also try modifying your report definition to not search for particular devices, but instead search for the relevant VRB Company.

As a side note, the list of "Skip Directories" appears to be the default list that ships with the product. Scanning into this list will generate false positives due to the way that Microsoft saves copies of executables all over the place, bumping up against the way ZENworks recognition works. I'd have to see the bottom of the Skip list to determine if anything has been added by one of your administrators.

Bruce McDowell Technical Services Consultant, McDowell Consulting LLC bruce@consultbruce.com
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.