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.

Introduction

Many SCCM issues could be directly linked with WMI. One of them could be SCCM console connectivity issues like “The ConfigMgr Provider reported an error connecting to the ConfigMgr site database server.”

Update: I have never tested this for Task Sequence export-related topic 🙂 18th March 2020.

Patch My PC

This could be because the server doesn’t have enough WMI memory to handle all the processes (old win2k3 servers).

WMI Explorer Architecture -Increase WMI Default Memory Allocation
Increase WMI Default Memory Allocation- WMI Architecture

For More details on __ProviderHostQuotaConfiguration

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. Take a snapshot of the servers before the change to be on the safer side.

1) Run “wbemtest” on cmd prompt
2) Connect to the “root” namespace (not “root\default”, just “root”)
3) Select Open Instance, and specify “[email protected]
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("[email protected]")
quota.MemoryPerHost = 384*1024*1024
quota.put_()
Wscript.Echo(quota.MemoryPerHost)

It’s always better to restart the box after applying this change.

Resources

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, 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.