SCCM/MECM 2207 Hardware Inventory - Length of time to update Server

Matt Pierce 1 Reputation point
2022-11-03T13:23:35.603+00:00

Howdy. I have a SCCM/MECM 2207 hot-patched Primary Site server configured and working normally.

My question is related to the time frame in which a client updates the server with its hardware inventory. More so, how long before the Device listed in the Configuration Manager Console is updated with this information and shows the date and time under the Hardware Scan heading.

When I manually run a hardware inventory scan, this seems to take a very long time, not in minutes. All the logs on the client device and server show success. I know the device has been updated because if I open Resource Explorer, under Hardware everything is listed. But the device inside the CM Console still is blank under the Hardware Scan heading.

I am assuming that due to this not showing is why when I client on the Collections tab, the device isn't showing being a member of certain device collections based on Operating System. This is also problematic as I have Windows Updates associated to Device Collections that have included OS Device Collections on them for deploying Windows updates.

So, can anyone help me to understand if there is a way I can speed this process up? Again, this is a new server setup, with less than 20 computers active on it currently. I'd appreciate any assistance.

Matt

Microsoft Security | Intune | Configuration Manager | Updates
Microsoft Security | Intune | Configuration Manager | Other
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Sherry Kissinger 5,526 Reputation points
    2022-11-04T15:16:14.537+00:00

    fyi, quick SQL to find collection with incremental checkbox checked. If the ID starts with "SMS" then it's an internal/default collection, and you can leave incremental checked on. It's the other, not-SMS default ones you would want to really evaluate how desperately you need incremental to be enabled.

    Select c.SiteID as 'CollectionID', c.CollectionName,
    case when c.CollectionType=1 then 'User or UserGroup'
    when c.CollectionType=2 then 'System'
    when c.CollectionType=0 then 'Custom'
    else cast(c.CollectionType as varchar)
    end as 'CollectionType'
    ,c.MemberCount
    from v_collections c
    where c.RefreshType in (4,6)

    1 person found this answer helpful.
    0 comments No comments

  2. Garth Jones 1,666 Reputation points MVP
    2022-11-03T13:25:47.733+00:00

    In generally, it should take less than 5 minutes to be update within the db. Use this article to see where the slow down is.
    https://www.recastsoftware.com/resources/updated-troubleshoot-configmgr-hardware-inventory-issues/

    0 comments No comments

  3. Garth Jones 1,666 Reputation points MVP
    2022-11-03T13:29:45.767+00:00

    I missed that you are talking about within the console node, that take ~24 hours to update. It is NOT meant to be real time.

    As for the collection, that could be many reasons but most likely due to how often the collection membership is refreshed. However you Say OS. EXACTLY which of the several locations are you using for OS details? I'm asking as it MIGHT not even be HW inventory that collects those details e.g heartbeat discovery.


  4. Garth Jones 1,666 Reputation points MVP
    2022-11-03T17:40:21.367+00:00

    Most things within the console used cashed results for performance reasons. If you are looking for troubleshooting then resource explorer is always uptodate.
    How often are you doing HW inv? What about Heartbeat discovery? In both cases, I recommend these be set to daily. https://askgarth.com/blog/inventory-cycle-version-numbers/

    I have not looked that their scripts but my guess is they use heartbeat discovery data. I personally don't add collections for the sake of having collections. I only add them when I need them. Why because this adds overhead to your site server and can slow down everything.

    If the data is based on Heartbeat discovery, triggering HW inv. will do nothing to make it fast. You need to trigger heartbeat discovery. Don't forget that the collection membership need to run too before the collection will update. And you will need to do all collections aka limiting collections too.

    To echo the infamous words or Jason Sandys there is no such thing as Best Practices. And he is right, there is only the things what work for you.

    BTW I'm assuming DC = Device collections.

    I 100% agree with Sherry Collections are NOT for reporting. SQL (Reporting) is for reporting.
    There is even a built-in report for OS details. Have you looked at them?

    I'm curious, what setting will you have different between Windows 10 versions? as it clearly sound like you are using collections for reporting and it will slow down your environment if you are not careful.

    Although it is not until May, I would ask to go to https://mmsmoa.com/ this is the place to learn more about ConfigMgr for Experts (like @Sherry Kissinger ) :-)


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.