Share via

ConfigMgr (SCCM) How to Increase WMI Default Memory Allocation

  • Article

WMI is an integral part of ConfigMgr (SCCM). Many SCCM issues could be directly linked with WMI.

One such issue is when the following error is received:  “The ConfigMgr Provider reported an error connecting to the ConfigMgr site database server”.

This could be because the server doesn't have enough WMI memory to handle all the processes.

Updated Post @ http://anoopcnair.com/2011/05/06/configmgr-sccm-how-to-increase-wmi-default-memory-allocation/

For More details on __ProviderHostQuotaConfiguration

The solution is to increase the WMI default memory. See, the below steps to complete this task.

1) Run “wbemtest” on cmd prompt
2) Connect to the “root” namespace (not “root\default”, just “root”)
3) Select Open Instance, and specify “__ProviderHostQuotaConfiguration=@”
4) Check “Local Only” for easier readability and you will see the threshold values
5) Change the MemoryPerHost value to something greater – eg. Double it (256 MB)
6) Save Property
7) Save Object
8) Exit

 Sample VB Script Code:

Dim locator: Set locator = CreateObject(“WbemScripting.SWbemLocator”)
Dim wmi: Set wmi = locator.ConnectServer(“”, “root”)
Dim quota: Set quota = wmi.Get(“__providerhostquotaconfiguration=@”)
quota.MemoryPerHost = 384*1024*1024
quota.put_()
Wscript.Echo(quota.MemoryPerHost)

It’s always better to restart the box.

NOTE - There are lot of hotfixes available to fix the WMI related issues. See, the details Suggested hotfixes for WMI related issue on Windows platforms