My buddy Carl wrote a simple, but amazing powershell script to make WMI more Enterprise-friendly. What does that mean? It means that WMI may not start soon enough for some Enterprise engines such as SCCM or GPO or other tools that query WMI. Especially as we consider the logon/boot experience.

So Carl engineered this little script:

1
2
3
4
5
6
7



$oWMI=get-wmiobject -Namespace root -Class __ProviderHostQuotaConfiguration
$oWMI.MemoryPerHost=768*1024*1024
$oWMI.MemoryAllHosts=2048*1024*1024
$oWMI.put()

Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\Winmgmt -Name 'Group' -Value 'COM Infrastructure'
winmgmt /standalonehost

 

This script increases the memory allocated for the WMI engine and breaks WMI into its own SVCHOST (something support has often recommended for some time) as well as change the ordering so WMI starts a bit early.

Read all about it here!

And for more primer information on why the settings do what they do, you might want to check out this post.