ConfigMgr slow to display collection members but queries are normal

Morrissey, Evan 301 Reputation points
2021-03-10T21:05:13.707+00:00

Recently upgraded to ConfigMgr CB2010. Full disclosure I made a stupid mistake where I forgot to re-enable our SQL backup jobs after the upgrade. So, of course, a couple days later everything ground to stop when the disks ran our of space. That may not be related, but, just in case... That was resolved easy enough, run a backup, shrink the logs, fix replication.

So currently ConfigMgr seems to work fine except when you try to open a collection. It can take a minute or two for a small (fewer than 10) collection, but takes absolutely forever (10+ minutes) for a larger (200+) collection. What's odd is that queries run fine, and collections update their membership just fine. In fact EVERYTHING seems to work fine except display members. Unfortunately this hard to research as every result is about collections slow to update membership which is not the problem.

This affects all users, and the problem occurs even when using PowerShell to retrieve devices

My hierarchy is a CAS with a single PRImary site (used to have more if you're wonder why there's a CAS). If the console is connected to the PRI then this problem disappears. If the console is connected to the CAS the collections are slow to display members.

Any help would be appreciated as this is driving me crazy!

Microsoft Configuration Manager
Accepted answer
  1. Morrissey, Evan 301 Reputation points
    2021-03-13T16:42:18.3+00:00
    2 people found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Fiona Yan-MSFT 2,311 Reputation points
    2021-03-12T07:57:17.157+00:00

    @Morrissey, Evan

    Thank you for posting in Microsoft Q&A forum.

    What's odd is that queries run fine.

    Could we know which query do we use? WMI, SQL or Powershell?

    It can take a minute or two for a small (fewer than 10) collection, but takes absolutely forever (10+ minutes) for a larger (200+) collection.

    Could we know how many collections and the mount of "Incremental Update" collection in our SCCM environment? Based on my understanding, It's best to limit the number of incrementally updated collections to 200. Maybe it will cause the slow connection if we use over 200.
    For more details, please refer to this microsoft article:
    https://learn.microsoft.com/en-us/mem/configmgr/core/clients/manage/collections/best-practices-for-collections#bkmk_incremental

    Have a nice weekend!

    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.