Share via

System Center Configuration manager CB custom hardware inventory not being shown in Resource Explorer

ChanChun Ting Andrew 1 Reputation point
2020-10-05T06:06:43.86+00:00

followed a few resources online to create the custom hardware class, collecting Monitor Details (such as Serial no. etc.) and a specific folder size.

I can find the newly created SQL table in the CM database, but the corresponding Views were not created and thus these two hardware inventory were not shown in resources explorer

I can confirm that the boxes are checked in the Client Settings

I can also confirmed that the clients parsed the new hardware class during inventory from the logs

Please help, thanks

Andrew

Microsoft Configuration Manager
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Fiona Yan-MSFT 2,311 Reputation points
    2020-10-05T10:34:41.06+00:00

    @ChanChun Ting Andrew

    Thank you for posting in Microsoft Q&A forum.

    As you mentioned, the SQL table and view display are not the same, at this situation, could we try to restart the sms_executive service and then we refresh our state to see if there is any change?

    Have a nice day!

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Sherry Kissinger 4,041 Reputation points
    2020-10-09T16:53:51.59+00:00

    what exact steps did you do for Monitor details, and specific folder size, via inventory? Where is that info stored, when you look interactively on a client? wmi, or regkeys?

    There are three paths, really, for adding to inventory.
    Path 1:
    if everything you want is already in WMI. This is the easiest; you just browse in default client settings, inventory, and add that class. (if you are using WMIMonitorID, a wmi class that already exists, then that might work for that; but you don't say what you are using)
    Path 2:
    If what you want are registry keys. Then you need to modify configuration.mof, and either import, or browse wmi (after configuration.mof is processed by that client).
    Path 3:
    If what you want is "the results of a custom script, where that script dumped the results into a custom WMI class or custom registry keys"; then it's multiple things, depending upon what that script did. The first step is to ensure that custom script ran at all on a client. Did it run, and populate wmi or regkeys? If the values are there now on a client, did you modify configuration.mof (if it was regkeys)?

    0 comments