Hyper-V WMI values incorrect for the ResourceType property of Msvm_ResourceAllocationSettingData

When enumerating Hyper-V resources using WMI with the Msvm_ResourceAllocationSettingData class I couldn't find any physical disks by using the appropriate resource type. I however find the physical and synthetic disks listed with a resource type of 17.

The documentation for both Msvm_ResourceAllocationSettingData and Msvm_ResourceAllocationSettingData  (v2) reports that ResourceType 17 is actually a serial port.

Running the same query against both the V1 and V2 namespaces on the same server reports differing results. This would suggest that either there is a bug in the code or the enum values have changes or the documentation is incorrect.

If anyone else has noticed this issue please let me know. I've commented on the MSDN page.






Comments

  1. TCarruthers18 June 2013 at 12:39

    Did you find a workaround for this issue? Also seeing the same problem.

    ReplyDelete
  2. David Homer19 June 2013 at 02:13

    No, I haven't seen any feedback from Microsoft on the MSDN pages either. I think we are going to just have to code around this depending on which namespace we are connected to. It's a bit nasty.

    Dave

    ReplyDelete
    Replies
    1. TCarruthers19 June 2013 at 08:49

      With Windows 2012 R2, the v2 virtualization is all we can use, so coding around it is even a bit harder. I'm opening a Microsoft support case against Windows 2012 R2 for my company.

      Delete
    2. TCarruthers24 June 2013 at 12:52

      Microsoft responded to use: the Msvm_StorageAllocationSettingData class documented at http://msdn.microsoft.com/en-us/library/hh859775(v=vs.85).aspx. This is associated to the Msvm_VirtualSystemSettingData object representing the VM’s configuration in the same way as other CIM_ResourceAllocationSettingData-derived classes are, i.e. through the Msvm_VirtualSystemSettingDataComponent association.

      They also noted that the documentation for this class is also lacking, "does not correctly list the ResourceType and ResourceSubType values for virtual hard disks. For VHDs, ResourceType is 31 (Logical Disk) and ResourceSubType is “Microsoft:Hyper-V:Virtual Hard Disk”."

      Microsoft said they would open a bug to update the MSDN documentation.

      Delete

Post a Comment

Popular posts from this blog

Windows Server 2016, 2019, 2022, Windows 10 and Windows 11: Date and time "Some settings are managed by your organization".

Image
When you're using the new "Modern" date and time settings in Windows Server 2016, 2019, 2022, Windows 10 and Windows 11 you may find that you can't set the correct date and time and the value "Some settings are managed by your organization". - While you're here - Why not check out our Windows Server Documentation and Audit Tool? The simplest way around this is to go back to the proper control panel using Start, Run, "Control.exe" and searching for "Set the date".  Within here you can set the date and time manually as required If you try and click the Change time zone button you may again get access denied... To resolve this open an elevated command prompt by right clicking the command prompt and selecting Run as Administrator  From there run the command rundll32.exe shell32.dll,Control_RunDLL timedate.cpl This will open the Data and Time control panel app elevated as an Administrator.
Read more

TFTPD32 or TFTPD64 reports Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions.

Image
When you start the trivial FTP (TFTP) server application TFTPD32 or TDTPD64 you may see the following error Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions. This can be because another application is using this port. The easiest way to check if (and which) application is using the port is as administrator run an elevated command prompt and enter netstat -anb > ports.txt Then open ports.txt in Notepad and search for :69, you'll quickly be able to see the process using the required port - While you're here - Why not check out our Windows Server Documentation and Audit Tool?
Read more

Windows Server 2019 desktop icons such as My Computer, Windows cannot access the specified device, path, or file.

Image
In Windows Server 2019 you may notice that the desktop icons such as My Computer are missing, however when you goto Personalization > Themes > Desktop icon settings You see the error Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. The quickest way to resolve this is to ignore the modern UI and desk.cpl ,5 From here you can easily add the My Computer icon - While you're here - Why not check out our Windows Server Documentation and Audit Tool?
Read more