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!