Missing Software and version #

Question

Okay, how would you all handle this:
In ZEN 7, we had JUST MSI And add/remove programs setup for software inventory. It actually did pretty good (example, it found a bunch of ESRI ArcGIS stuff).
It would show ALL the SDK (ie, there's an SDK for C++, one for VB, etc.)
It would also show the complete version and build number (ie: 9.2.134.21)
Now we are using ZAM 7.5 (in addition to ZEN, but eventually will cutover to ZCM)
Anyway, ZAM 7.5 seems even more limited in its software inventory.
It doesn't find any of the SDK's (I've had to submit multiple fingerprint wizards in the past for missing software).
It also doesn't report build numbers, just versions like 9.2
Sooo, what's the best way to handle this?
The missing stuff I'm either going to have to add more fingerprints (very time consuming as I have to go visit the PC's with the software to run the utility) or add local product (in which case I've gotta get the people to send me the .exe and whatnot). Either way, stinks, IMO.
And how should I handle the missing version information? It's in the windows registry at the least, but I'm not sure about the actual VBR info in the file. Do I submit an SR, enhancement request, run the wizard?
Version info is very important for us because it signifies the product patch levels (ie, it doesn't say like: Hi I'm ArcView 9.2 SP3, but rather, I'm 9.2.somethingsomethingsomethng)

Answer 1

Recognition in ZAM - and ZCM - has been, over time, focused more towards business applications than development applications. In that environment, recognition out to the build number is viewed as less relevant; accordingly, most fingerprints tend to report at the "N.N" or "N.N.N" level. The recognition technology is quite capable of reporting out to "N.N.N.N" and indeed that level of granularity is utilized when requested and appropriate. (We pickup the build from the VRB.) Further, when specified, "promotion" fingerprints will automatically discover versions with new build numbers in them and create new products on-the-fly. This type of fingerprint must, however, be engineered by Novell.
Generally, the recognition team has placed less emphasis on SDKs. We tend to make decisions towards products that will have impact on the majority of customers. But, as you've mentioned, we respond to requests for signatures.
From the software local products perspective, if you are gathering "software file" (the ZAM name) or "file scan" (ZCM) data, you shouldn't need to have files sent to you to create a local product. In ZAM 7.5 you can create a local product from the Software Files report in the web console fairly efficiently. It works even better in the ZENworks Control Center of ZCM 10. On a project earlier this year, at a customer site where there is a lot of internal application development and a strong commitment to populating the VRB on every update, we created over 150 local products - with different product names and versions - in about a minute.