Skip to content
Increase WMI Default Memory Allocation for ConfigMgr Server

Increase WMI Default Memory Allocation for ConfigMgr Server

Written By Anoop C Nair
Last Updated July 22, 2024
Posted In SCCM
SHARE

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.

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..

Written by

Anoop C Nair is Workplace Technology solution architect with 25+ years of experience in global enterprise organizations such as JP Morgan, Capgemini, etc. Microsoft Certified Trainer. Microsoft MVP from 2015 onwards for consecutive 11+ years! He also conducts Intune and modern workplace tech training for enterprise organizations. He is Blogger, Speaker, and Founder of HTMD Community and HTMD Conference. His main focus is on Device Management technologies like Intune, Windows, Cloud PC. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security.

Discussion · 8 comments

  1. When I update WMI quota it set it correctly. But my customer is reporting that it gets set back to defaults upon reboot. Any clues?

    1. May be, you missed to click some buttons like “SAVE”, “OK” or “Apply”? If that is NOT the case then check the event logs to get some clue.

  2. 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

Join the discussion

Your email address will not be published. Required fields are marked *

Related guides

Intune

Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws

Key Takeaways Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws! In the July 2026 Patch, Microsoft introduced new features designed to improve the overall Windows experience. The update adds enhancements to Windows Update for more flexible update management and introduces Point-in-Time Restore, providing an additional recovery option for […]

AC Anoop C Nair 9 min read
Intune

2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws

Key Takeaways 2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws! The June 2026 Windows 11 Patch Tuesday update brings several improvements to File Explorer. It adds support for additional archive formats, including UU, CPIO, XAR, and NuGet Packages (NUPKG). The update also preserves View and Sort preferences in […]

AC Anoop C Nair 10 min read
Intune

2026 May KB5089549 KB5087420 Windows 11 Patch | 0 Zero Day Vulnerabilities and 120 Flaws

Key Takeaways The Windows 11 May 2026 Patch KB5089549 KB5087420 Update brings important security fixes, performance improvements, and reliability enhancements across the operating system. The update introduces new features such as Xbox Mode for gaming, File Explorer improvements, enhanced input and sharing experiences, better taskbar and Windows Hello reliability, and additional enterprise management capabilities for […]

AC Anoop C Nair 8 min read
SCCM

ConfigMgr 2603 Introduces New Early Update Enrollment Process

Key Takeaways In this post we are discussing the ConfigMgr 2603 Introduces New Early Update Enrollment Process. Microsoft has officially released Configuration Manager version 2603 to the Early Update Ring, giving organizations an opportunity to test upcoming improvements before the global production rollout. The release is targeted at enterprises running ConfigMgr version 2409 or later […]

AC Anoop C Nair 3 min read