1 of 1 people found this helpful
Short answer is, in one way or another, yes, but....
It's going to depend on the file extension of the active X file, as to whether the inventory scanner is going to pick this up automatically with a software scan, or if you'd have to modify the template file in some way to get it to be included in the inventory. So question on that is what is the file extension? OCX or something else?
An alternative way to "detect" a file would be to create a custom definition in the patch manager side of the product. You could set up a detection logic that you know would never actually occur, like version = 1000.0 or something crazy that just wont ever be true. This would cause every device to "detect" regardless of what the file's actual version is, and if you set it up to detect on a file version, then it will provide the "REASON" for detection and that would show the actual version of the file.
Ideally, the inventory scanner is the better approach as it can actually gather more information about the file than just its version, where the specific custom def is only going to get the one detail, but it all depends on the file's type on whether or not the inventory scanner will work with it.
The file extension is .DLL, i will look in this way then.
Thx for your answer.
It looks like by default "SCANEXTENSIONS" in the LDappl3.template file on the core under the ldlogon folder is set to only scan for .EXE, but they have a commented out line that shows that it can be set up to scan for other things like .DLL, so you could modify this, and then publish this (dont forget this step if you make the edit). Its going to cause all the devices to have to download the ldappl3 delta file and update the template on their next inventory scan on all the devices which i don't care for myself, as this is a change that can cause some issues, or at least it did for us back in the day with 8.7. With 9 sp2, hopefully those problems don't happen anymore, but you could look at doing it that way also. If you did make this change, you would then be able to use a query like for example:
"Computer"."Software"."Package"."path" LIKE "whateverthefilenameis.DLL"
You could use "Name" instead of "Path" if you preferred and change it to the = operator, but I like the "Path" myself, since you might want to narrow which specific DLL it looks at by adding some or all of the file's location. You could put the folder its in, plus its file name, and that would narrow it down, just in case the file might exist in multiple places, which might cause some false positives.
As a result of all this, you'd gain the access to the rest of the values that are under:
Version of course, all the usage information, and a few of the goodies that show up in file properties basically.
Ok i will test it this afternoon.
Thx for this idea.