Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Custom Inventory is not being placed in the 7.1 SP2 database and there are NO errors!

Created: 04 Dec 2012 • Updated: 04 Dec 2012 | 1 comment
QuietLeni's picture

Dear All,

I am doing some VBScript Custom Inventory on SMP 7.1 SP2 and I am trying to get some registry entry values in a database.

The problem is that the script works - I have tested this in a command line and does not error when I run it in the Task Server. I have intercepted the NSE and it is sent when executed in the Task Server (although I am not sure that it is being received).

I once saw the data being populated in the database and I cleared it down.

However, when I run the Task Again, it just does not re-show up in the database. Does SMP check the hash of the previous dataclass for a computer and not bother to re-populate the database again? This did not happen in NS 6.0 - in that, you could just run it over and over and over!

EDIT: I have been since, reading this article again:

https://www-secure.symantec.com/connect/articles/event-queues-itms-71-sp2

and I have noticed a paragraph that I did not see before:

There was a small change made to the messaging resource to ensure that it doesn't load and save a resource if the resource key information has not changed. Before SP2, on an average software inventory NSE, it was causing hundreds of items to load or be saved per NSE which was adding seconds of processing time per NSE for the large software inventory NSEs.

Now, here is the question - is this paragraph saying that it IGNORES data classes that have been repeatedly sent with the same data?

Kindest regards,

QuietLeni

Comments 1 CommentJump to latest comment

QuietLeni's picture

Dear All,

This is an interesting issue - the NSE was being generated by the computer and it was getting to the NS, but then beig discarded.

When I found the NSE on the local PC, I noticed that there was a space at the end of one of the values. When I changed the inventory script to remove the space, then the NSE was received by the NS and it got to the database. It was not the space at fault, but it was the fact that the NSE was not changed in second and subsequent identical inventory values, so the hash on the dataclass for the endpoint inventory in the database did not change and therefore Altiris ignored the update. Normally, this would not be a problem, as the data does not get deleted (like in testing).

Hope that this helps someone else.

Kindest regards,

QuietLeni

What is the point of an Asset Management Solution that needs excessive management? Let me help you.