Increase WMI Default Memory Allocation for ConfigMgr Server

WMI is an integral part of ConfigMgr (SCCM). Let’s see How to increase – WMI Default Memory Allocation for ConfigMgr Servers.

Many SCCM issues could be directly linked with WMI. One example is SCCM console connectivity issues, such as “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 (old win2k3 servers).

Index
Increase WMI Default Memory Allocation
Solution | FIX – Increase WMI Default Memory Allocation
Script
Increase WMI Default Memory Allocation for ConfigMgr Server – Table 1

Increase WMI Default Memory Allocation

WMI Explorer Architecture -Increase WMI Default Memory Allocation
Increase WMI Default Memory Allocation for ConfigMgr Server -Fig.1

For More details on __ProviderHostQuotaConfiguration

Patch My PC

Solution | FIX – Increase WMI Default Memory Allocation

The solution is to increase the WMI default memory. See the below steps to achieve the same.

NOTE! Please try this in a LAB environment. I don’t think it’s recommended to change the WMI memory configuration directly on the production servers. To be on the safer side, take a snapshot of the servers before the change.

Adaptiva

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 – e.g. Double it (256 MB)
6) Save Property
7) Save Object
8) Exit

Script

Also, see the 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 after applying this change.

Resources

We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.

Author

Anoop C Nair has been Microsoft MVP from 2015 onwards for 10 consecutive years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is also a Blogger, Speaker, and leader of the Local User Group Community. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc..

8 thoughts on “Increase WMI Default Memory Allocation for ConfigMgr Server”

  1. I have found increasing the handlesperhost to 8192 fixed the memory issue for me with larger Task Sequences.
    I did have memoryallhosts = 2GB, memoryperhost = 1GB

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.