Custom Hardware Inventory - NON DEFAULT namespaces

[sencee]

Hello again.

Looking for some more insight into the wonderful world of SMS Custom Inventory.

I have a class in a namespace other than cimv2.

The Namespace is fully accessable and the class is there, and the providers is kicking out the properties in WMI. All is good. All is great.

Im wanting to refence this in my SMS Hardware Inventory.

Lets call the namespace root\MyNameSpace and the Class MyClass and the properties MyProp1 -> MyProp3

I need to edit the def and schm mof files....

HOW DO I DO IT.

I have been using the following syntax in the SMS_DEF.mof

This was provided to me from an old developer, so I cant say why it is done this way, but it seems to match the scenarios laid out in other sources that I have read.

===sms_def.mof ALTERED for AditionalNamespace===

#pragma namespace("\\\\.\\root\cimv2")

[union, ViewSources{"SELECT * FROM MyClass"};,
ViewSpaces{"\\\\.\\root\\MyNameSpace"}, Dynamic : ToInstance,
provider("MS_VIEW_INSTANCE_PROVIDER")]

class MyClass
{
[PropertySources("MyProp1"), key] Unit16 MyProp1;
[PropertySources("MyProp2")] boolean MyProp2;
[PropertySources("MyProp3")] string MyProp3;
};



#pragma namespace ("\\\\.\\root\\cimv2\\SMS")

[SMS_Report(TRUE),
SMS_Group_Name("MyClass"),
ResID(5200), ResDLL("mydll.dll"),
SMS_CLASS_ID("MySMS|MY_CLASS|1.0")]

class MyClass : SMS_CLASS_TEMPLATE
{
[SMS_Report(TRUE), key]
unit16 MyProp1;

[SMS_Report(TRUE)]
boolean MyProp2;

[SMS_Report(TRUE)]
string MyProp3;
};
============END OF MODIFICATION==================

Im confused about all the different namespaces that are mentioned in this alteration.

What I BELEIVE, is that the first bit creates the view instance that links the MyClass in MyNameSpace into the stanrad SMS namespace where it stores all classes that are to be inventoried, and the second instance, is just the same as a normal additional class that is now referenced from the default view provider.

Anyone shed any light on this.

I have inserted this code exactly as it appears in the modificaton that i have been given, just replaced the names of the propriatory classes, NS and props, so there may be even syntax errors, that I haven't spotted, even, missing colons; as I have never used the namespace cross referencing before.

When the new policy is to be recreated. It just spits it into HINVARCHIVE and replaces it with the stock SMS one. (Mof file that is)

if you would prefer to email any comments, then njcotton@uclan.ac.uk.

Please point out anything, I dont mind looking like fool for something stupid.

Big Regards in advance
NC.
Any light will help