Custom Inventory Problem.

[sencee]

Im trying to create a customised SMS_DEV.mof and SMS_SCHM.mof. I have adjusted the files to include the required details that weren't being reported, and brought in some new classes. At first everytime I ran SMS, the adjusted SMS_DEV.mof reverted back to the installed version, the one held in the setup files. I realised this was due to a syntax error, which I fixed. When I run SMS now, my custom mof files are eexecuted, however, there is no difference in the inventory reported. I have had a look to the database, and without precisely knowing what I should expect to find, see no change.

Any help would be much appreciated.

Regards
NC

 

[sencee]

I have sorted "some" of this out.

I have 3 classes, A, B and C in the MOF and Schema Files.

In the SQL_InventoryClass, which just lists the whole class name asto what to include, A, B and C show up. Great.
In the individual class tables A and C exists (A_DATA, A_HIST + C_DATA, C_HIST), with the select query correct in each as to which properties of said class to include. there are no entries for CLASS_B in the database, except in the InventoryClass class definitions.

I have had a look in the ClientSide inventory and actions ogs, and the CLASS_B commands are being processed, and suprise suprise, only A and C are appearing in the resource manager.

Is there anyway of seeing the MOF file that is being held on the client? In full, or logged format (full preferably, as I hate logs...too much junk)

Regards

 

[sencee]

I beleive the main problem that I had with this is that the CLASS_B contain
ed a Unit64 property. I left property comemented out, therefore the class wa
s added to the InventoryClass, however the table for the class properies was
not, because the class was not complete. (Even thouh it would have been set
to false, the call to the instantiation of the mof file is correct with cor
rect syntax and headers, and the properties of the class to be reported are
then checked and added to the DataItems table, it is only when they all want
to link round to the CLASS_B table, that there is a problem, because CLASS_
B table was not created for the lack of a complete class.

I hope that makes sence. Im not very good at explaining things like that.

In the InventoryClass table in the DB, it was shown, however there was no in
stance of a properties table for the class on its self. I beleive that when
I fixed this problem, using the transform mechanism SMS builds in (SMS_UNIT)
, it should have fixed the problem, but because the first point of call, whi
ch is the class defining (somewhat like a #include, or #using) table Invento
ryClass, already contains the CLASS_B reference, it isn't bothering to carr
y on, as it assumes that it is all correct.

As far as I was aware, the WMI was a repository that has nothing to do with
SMS, as far as configuration is concerned, as it only holds the system data,
and doesn't contain details of what to report back to SMS.

I have had a look at PolicySpy, and can't see how it would help my problem,
as I don't know what I expect to see, or not see, the instantiations are the
re, and the policy that is taken dirrectly from the MOF, but that doesn't he
lp me see how far it has got.


Im am 95% sure thatI have just confused the hell out of you.

Any help would be much appreciated..even setting me straight on some of the
"statements" I have just made regarding how and why things work, I must exc
use myself if they are wrong, as these are just my theories of why the probl
em is persisting.

Regards in advance.
NC

 

[sencee]

BTW - I have had a look at the InventoryAgent log and it says that a number 32/39 completed sucessfully, yet no sign of any of my classes failing.

I looked at the dataldr.log and the only one that is changed in there is the CLASS_C which is the one that is showing. There is no mention of any of the other classes. The only mif file that is left is the .bad.mif's in AUTH\dataldr\badmifs\ and that is a MS one.

I have changed the mof file, chaning some of my properties from false to true, (of my classes only) one extra from each class, and the CLASS_C one has been updated everywhere, RE, LOGS, DB InventoryClassProperies and DB CLASSinstance.

The other two classes, changes have been reflected in the InventoryAgent.log, but nowhere else.

ARRRHHHHH!!!!!