Symantec Management Platform (Notification Server)

Hi guys,

I am trying to build an automtic removal process for software which is not used for a certain amout of days.

I have found some queries on connect (for example the one here) which I was trying out but it seemed like they do not match what i can see in the Software View. For example here in can see that none of the computers have an Install Date.

But running the query mentioned above I do get the Install Date.

For the Visio Standard 2003 it looks different. Here I have many which have an install Date but not all.

So my question is which Tables are queried in this Software View. Is it "inv_addremoveprogram" and "vammonthlysummary"? Once I know that I can go and check if the inventory is missing for example if it is related inv_addremoveprogram. Or maybe it is some configuration error with the usage tracking... 

If it is only a problem of the "Software View" I would not be concerned and would go ahead with automatic removal process but if I cannot trust the Inventory / Metering it will be difficult to have an automated removal process. I do not want users complaining that they have lost the programs which they use daily.

Stefan

'Install Date' comes from the Inv_InstalledSoftware table, which is populated when software inventory is run.  If that column is blank in the database then there is no way for the UI to show anything.

'Last Used' comes from vAMMonthlySummary.

Thanks for the hint. I was looking now in the Inv_InstalledSoftware table and I could find many empty values. Now the question is why is the field not populated even if the InstallFlag is = 1.

Does anyone know if these issues with differences between Add Remove Programs and Software Discovery have been fixed? Or does it still apply that these invenory issues will be fixed in 7.5?

@Andrew: Is the following scheduled task somehow involved int the population?

NS.Nightly schedule to associate Software component to software product.{a48d3b11-5169-464b-9773-6c0f476e7748}

Because that task seems to fail every night.

The NS.Nightly schedule is a backup to the default mapping process.  When a software component is discovered via Inventory, it is sent to the NS.  If it is a component that already exists, then it simply merges.  If it is a new component, then the NS automatically does a reverse-lookup using Software Product SQL definitions (in the Inv_SoftwareProductFilter table) and will associate that component to that product if it meets the filter criteria.  On occassion, a component will slip through the cracks so this nightly schedule finds any components that should be associated to a product and associates them.  If that task is failing to run, then it is likely you have a few components that should be associated to a software product but are not.