We are using SCCM 2012 for delploying MS patches on Client machines after successful deployment of MS patches WMI repository size is keep getting increase. Due to this we are facing the system performance issue. Please suggest how we can resolve this issue.
Also make sure that there are no expired updates in any deployment/software update group.
I've "heard" that running ADRs too frequently (which in turn triggers update compliance evaluation on targeted systems) also causes WMI bloat along with simply targeting way too many, non-applicable updates at clients.
So, for your ADRS (if you are using any), how often are you running them?
And, do you have your update groups broken down for targeting so Win7 clients aren't targeted with Server updates for example?
We are using SCCM 2012 for delploying MS patches on Client machines: excellent, you are using the right tool.
WMI repository size is keep getting increase: The WMI repository should pretty much take care of itself in 99.9% of cases. WMI repository size really shouldn't be a concern under normal operations. It is natural for it to grow.
Due to this we are facing the system performance issue: This statement is likely a bit of a reach. I very much doubt that WMI repository size has anything to do with system performance issues.
What are your client machines? As a ballpark, WMI repository size should be under 100 Mb. This is not a hard ceiling.
Please specify what kind of performance issues you are having.
Thanks,
Nick.
I know this is an old post, but we're facing the exact same issue. As soon as the SCCM client is deployed, the wmi repository grows from less than 30MB to over 1GB in the matter of hours. After this the wmi repository becomes inconsistent at some point and users start to get problems with extremely slow login, black screen at logon etc.
If I then remove the client and reset the wmi repository the problem is gone.
We're running Windows 7 SP1 and automatic updates.
What version of ConfigMgr 2012 are you running?
Are you using software updates and do you have updates targeted to all systems or are you filtering them somehow?
Have you deployed the hotfix from KB2775511?