VirtualMetric Hyper-V Monitoring, Hyper-V Reporting


Cozumpark Bilisim Portali
Fixing WMI issues on Windows Server 2012 Hyper-V Cluster
Posted in Windows Powershell, Windows Server | 2 Comments | 4,919 views | 20/07/2014 23:31

You may get following issues due to WMI problem:


Reboot is only way to fix it but at least you can prevent future issues:

1. Go to Start -> Run and type wbemtest.exe
2. Click Connect
3. In the namespace text box type “root” (without quotes).
4. Click Connect
5. Click Enum Instances
6. In the Class Info dialog box enter Superclass Name as “__ProviderHostQuotaConfiguration” (without quotes) and press OK.
(Note: the Superclass name includes a double underscore at the front.)
7. In the Query Result window, double-click “__ProviderHostQuotaConfiguration=@”
8. In the Object Editor window, double-click HandlesPerHost
9. In the Value dialog, type in 8192
10. Click Save Property
11. Click Save Object
12. Under properties find the property “MemoryPerHost” or any other ones you need to modify and double click it
13. Change the value from 512 MB which is 536870912 to 1GB which is 1073741824
14. Click Save Property
15. Click Save Object
16. Close Wbemtest
17. Restart the computer

Thanks to Shaon Shan for sharing this solution.

Comments (2)


August 1st, 2014

have you tried this?:

Oel Graae

March 21st, 2017

Here is some powershell I wrote to do the above.
#(Get-CimClass -Namespace root -ClassName __ProviderHostQuotaConfiguration).CimClassProperties
$Changes = Get-CimInstance -ClassName __ProviderHostQuotaConfiguration -Namespace ROOT -ComputerName $serverlist
ForEach ($Change in $Changes) {$Change.HandlesPerHost = 8192;$Change.MemoryPerHost = 1073741824;Set-CimInstance -InputObject $change}
Get-CimInstance -ClassName __ProviderHostQuotaConfiguration -Namespace ROOT -ComputerName $serverlist | Select-Object PSComputerName,HandlesPerHost,MemoryPerHost

Leave a Reply