Problem with Hyper-V based virtual machines

[rmeleiro]

First of all. let me congratulate you on the superb enhancements made to Lansweeper 4. That said, I've found a problem with all my virtual servers running on Hyper-V (both Windows 2008 and Windows 2008 R2 hosts).
The reported memory for any of those virtual machines is always 64MB (image attached). Any hint?
Regards
Rui Meleiro

[rmeleiro]

Hi. Just popped in to say that the problem I reported is now solved. All Windows 2008 and Windows 2008 R2 Virtual machines are now reporting the right amount of memory. As it happened to all of them somewhere along the line, I'm guessing that one of the recent Windows updates solved the problem.
Regards
Rui Meleiro

[PaulWegs]

What I have now found is that when Windows Server 2008 R2 Hyper-V is used as the virtual host server, the guest virtual machines report the correct RAM.

[Hemoco]

PaulWegs wrote:
What I have now found is that when Windows Server 2008 R2 Hyper-V is used as the virtual host server, the guest virtual machines report the correct RAM.

It's clearly a bug in other hyper-v versions, only I haven't been able to find a patch for it.
Vmware does not have this problem.

[PaulWegs]

It seems as though this problem is not limited to Hyper-V, as it has been around for a long time. The following link will take you to a post which has an explanation behind the problem.

http://blogs.msdn.com/b/virtual_pc_guy/archive/2004/12/02/273639.aspx

Can Lansweeper record the total RAM as reported based on the "TotalPhysicalMemory" property of ComputerSystem? At least for Virtual Machines?

[Hemoco]

PaulWegs wrote:

Can Lansweeper record the total RAM as reported based on the "TotalPhysicalMemory" property of ComputerSystem? At least for Virtual Machines?

Previous version used TotalPhysicalMemory but this was not correct in 90% of the computers because TotalPhysicalMemory shows the memory available to the OS, not the actual memory installed.
If the computer had 512 MB you could have results going from 480 to 512

[Hemoco]

Wmi is reporting the wrong data.
16777216 bytes = 16 MB

I looked on the Microsoft support site but couldn't find a patch for it.

[Ponchohobono]

Here's mine:

BankLabel Capacity Caption CreationClassName DataWidth Description DeviceLocator FormFactor HotSwappable InstallDate InterleaveDataDepth InterleavePosition Manufacturer MemoryType Model Name OtherIdentifyingInfo PartNumber PositionInRow PoweredOn Removable Replaceable SerialNumber SKU Speed Status Tag TotalWidth TypeDetail Version
BANK0 16777216 Physical Memory Win32_PhysicalMemory 72 Physical Memory DIMM1 8 1 0 17 Physical Memory 1 Physical Memory 0 64 128
BANK1 16777216 Physical Memory Win32_PhysicalMemory 72 Physical Memory DIMM2 8 1 0 17 Physical Memory 1 Physical Memory 1 64 128
BANK1 16777216 Physical Memory Win32_PhysicalMemory 72 Physical Memory DIMM2 8 1 0 17 Physical Memory 1 Physical Memory 2 64 128
BANK1 16777216 Physical Memory Win32_PhysicalMemory 72 Physical Memory DIMM2 8 1 0 17 Physical Memory 1 Physical Memory 3 64 128

[rmeleiro]

Amended the previous post. From where I stand, it still looks inconclusive 🙂 Let me know if you need additional info.

[Hemoco]

I'm sorry, I actually needed "wmic path win32_physicalmemory"