HELP! Followup after extension in Configuration.mof

I'm working on the configuration.mof and sms_def.mof to collect the purchase date information from client machine registry. Yet, instruction in my hand says that the new reports will collect the purchase date from corresponding view in the SCCM SQL Server Database. But how can the SQL Server view come out from nowhere while I just adjust only those two mof file and add new registry key value on the client machine?  Hints imply that I should reboot the client machine several times. Will that work?

view gets created after you extend your inventory and when the first client does as full inventory with the added changes

But already my Configuration.mof & sms_def.mof both have got extended. What should I do to get the first client "do as full inventory with the added changes"? Do you mean the registry changes?

it doesn't need a full; a delta (normal inventory) will work just fine.

Since it's been a few days, the view is probably already there.  I'm sure some box somewhere has run an inventory, and has the regkey so it had something to say.

If not, the view isn't there; pick any random computer.  Check it's registry, confirm the regkey exists with a value.  Interactively, monitor inventoryagent.log (%windir%\system32\ccm\logs), probably using trace32.exe from the toolkit.

While monitoring the log, invoke a Hardware inventory.  Watch for the line of select <yourvalue> from <yourwin32Whatever>.  If the very next line is NOT "does not exist out", then that computer successfully had something to say.  Wait a few minutes, and go check for the view.

fyi, view names are based on what you put in your custom "SMS Group Name" section of the mof edit.
 
question: what does your mof edit look like?  Did you create it using Mark Cochrane's regkeytomof? or did you follow the wiki?  Regkey mof edits can come in two flavors... ones like add-remove programs style which is for subkeys with common values, or the one I suspect you want, which is specific regkeys.  If you made the wrong kind, that might be messing you up.

Take a look at inventory Manager dudeworks.com. Save tons of headaches.

Hey there,
we also have the problem, that nothing happens after we made a change in the sms_def.mov. I was searching for the view sKissinger said, which is generated when you make a change in the sms_def.mof (and the configuration.mof, for sure ;) )
Did you meant a view within the SMS SQL DB or just the view in the Resource Explorer??
We cannot find a new entry anywhere.

Rgds
rob

Did you perform a hardware inventory on a client? is the syntax correct? you check by running mofcomp -check and the mof file.

Looks like there are two people in this thread, smith2010, and robbster. 

Smith2010: are you golden? or not?  If not, post your sms_def.mof/configuration.mof edits here (not the full files, just the stuff you added).  One of us might find the issue, or help you know what the view will be called at least.

Robbster: what type of mof edit did you do?  regkeys? wmi only?  just changed false to true or true to false on existing classes or attributes in the default sms_def.mof?  If you added custom stuff, and you don't see the views created yet in your database, like for smith2010, post your edits (not everything, just the new stuff) here, and one of us will see if we can spot something.

Hello sKissinger,

we did a change in the Mof for regkeys.
In the log we can see that the server performs the wanted actions.
But there is no view and nothing to see in the Resourceexplorer. I hope you can help. Added the custom stuff as txt.

Attachment(s)

mof.txt (8.92 KB) - downloaded 61 times

I have had this issue back sms 2003 and sometimes updating statistics helped solve it. I would do it on off hours if you have huge database. Here is a link with syntax to help:
http://www.myitforum.com/articles/18/view.asp?id=12496

robbster:
for the landriver, in sms_def.mof, and the bottom section of configuration.mof, you reference DriverDate.  But in the top section of configuration.mof (for landriver) you don't have DriverDate there.  Just like happened to me once:  http://myitforum.com/cs2/blogs/skissinger/archive/2008/08/25/hardware-inventory-action-missing-on-configmgr-client.aspx

Make sure you have driverDate in the top part of Configuration.mof for that section.

Same thing for WlanDriver--DriverDate is missing in the top part of Configuration.mof, but you have a regkey location in configuration.mof, and in sms_def.mof you are asking for driverdate.

It looks like biometric driver section and hpcdriver section correctly have driverdate in configuration.mof.  So cleanup those 2 sections I mentioned, save configuration.mof (now that it is corrected).  Do a couple of policy refreshes on clients, and about 5-10 minutes later, exit the control panel applet, go back into it, and you should see Hinv again.

If you don't, maybe I missed something.  But those two driverdate are certainly going to cause a problem since they are missing.

Hi,

Thanks for your answers.
But I think I have not described the problem correctly.
We see that these classes are defined correctly. That means we see actually the defined classes in the SMS Client Inventory.
The problem now is, that the views in the database are not generated and that there are no new categorys in the Resource Explorer, like LAN-Driver or the other ones. We made policy updates and everything, but it does not work out.
I hope you understand what I mean.

Greetings
Rob

Did you update the statistics on the database and restarting sms executive service? On the link posted above it has the command to this on the entire database

Hello,

we finally got it.
We ran the sp_updatestats procedure, with the code of cp07451, but there were no big changes.
Then we decided to start from scratch with the standard SMS_DEF.mof and Configuration.mof and tried the steps sKissinger mentioned at first with one change. After that everything worked fine.

Thanks for your help guys.

Regards
Rob