Error 'Get-WmiObject : Invalid class "Msvm_ImageManagementService"'

Question

Recently I've been getting this error, and I have no idea what triggered it. The documentation I found regarding this class is minimal and I'm not sure what I need to check or where to look in order to understand it and fix it.

System:

Windows Server 2012 R2 Datacenter Preview Build 9431
PowerShell Version 4.0 32bit and 64bit

Output:

PS > Get-WmiObject -Class "Msvm_ImageManagementService" -Namespace "root\virtualization"

Get-WmiObject : Invalid class "Msvm_ImageManagementService"
At line:1 char:1
+ Get-WmiObject -Class "Msvm_ImageManagementService" -Namespace "root\virtualizati ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidType: (:) [Get-WmiObject], ManagementException
    + FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.Commands.GetWmiObjectCommand

@magicandre1981, So this class is not available/supported in 2012R2? Also made an edit to the question. — slybloty, Sep 26 '13 at 14:21
HyperV? I believe 2012 / Win 8 has some dedicated HyperV cmdlets... — Austin T French, Sep 26 '13 at 20:37
@AthomSfere, how can I find this out? It seems that way, but I just can't find any specific documentation. — slybloty, Sep 26 '13 at 20:41
Starting point at least http://technet.microsoft.com/en-us/library/hh846767.aspx — Austin T French, Sep 26 '13 at 21:01
@AthomSfere Unfortunately I haven't been able to find any helpful information. — slybloty, Oct 03 '13 at 17:41
What information are you trying to get get? http://technet.microsoft.com/en-us/library/hh848559.aspx has the commands which likely require PowerShell 3 — Austin T French, Oct 03 '13 at 18:01
@AthomSfere First I'd like to find out if this class is still supported under 2012R2. If so, why am I getting the error of invalid class, and how to fix it. I have PSVersion 4.0 — slybloty, Oct 03 '13 at 18:30
PS 4 should be OK, but with end of support it is possible even if it is there the WMI classes are slightly different thus through the errors. My personal experience / preference is to use the most precise tool available tool, and avoid WMI whenever possible. — Austin T French, Oct 03 '13 at 20:14
do you run it under correct PS version (64bit vs 82) I had similar and this was the case — cpoDesign, Oct 07 '13 at 09:41
@slybloty can you run it under 32bit instead? (just to humor me) had issues that it was mistargeting — cpoDesign, Oct 07 '13 at 19:44
@slybloty have you installed powershelll for HyperV, http://pshyperv.codeplex.com/SourceControl/latest#install.cmd — cpoDesign, Oct 08 '13 at 08:08

score 13 · Accepted Answer · answered Nov 05 '13 at 16:39

13

The class is still there, it now resides in a different namespace. It's in the namespace "root\virtualization\v2". It's also worth noting that the class has changed, previously used methods may not exist anymore.

answered Nov 05 '13 at 16:39

Dan Barber

146
1
3

Error 'Get-WmiObject : Invalid class "Msvm_ImageManagementService"'

1 Answers1