
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-23-2016 03:12 PM
Lansweeper reading 1GB instead of 2GB memory. Also memory modules size is invalid as LANsweper reading 2x512MB memory modules instead of 2x1GB modules.
LANsweeper version 5.3.0.33
Asset is accessible, and was rescanned several times. Remote connection using msinfo32 showing properly 2GB on this computer.
Also in LANsweeper-Asset-Config-OS there are TotalVirtualMemorysize: 2097024 (proper)
LANsweeper version 5.3.0.33
Asset is accessible, and was rescanned several times. Remote connection using msinfo32 showing properly 2GB on this computer.
Also in LANsweeper-Asset-Config-OS there are TotalVirtualMemorysize: 2097024 (proper)
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2016 02:24 PM
Memory information is pulled from WMI (Windows Management Instrumentation), a management framework built into Windows operating systems. Most likely WMI itself returns incorrect data, which is something we can do very little about.
You can run the command below in cmd.exe on the problem computer and open the resulting WMImemoryinfo.txt file to see the information stored by WMI.
wmic path Win32_PhysicalMemory >WMImemoryinfo.txt
If the output of this command differs from the exact total amount of memory in the computer, there is most likely nothing we can do because Lansweeper retrieves the data as stored in WMI. You can try to repair the WMI on your computer. However, we are not sure whether this will resolve the problem.
You can run the command below in cmd.exe on the problem computer and open the resulting WMImemoryinfo.txt file to see the information stored by WMI.
wmic path Win32_PhysicalMemory >WMImemoryinfo.txt
If the output of this command differs from the exact total amount of memory in the computer, there is most likely nothing we can do because Lansweeper retrieves the data as stored in WMI. You can try to repair the WMI on your computer. However, we are not sure whether this will resolve the problem.
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-28-2016 11:50 PM
A BIOS update has fixed some similar issues for us in the past, it is also worth a try.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2016 02:24 PM
Memory information is pulled from WMI (Windows Management Instrumentation), a management framework built into Windows operating systems. Most likely WMI itself returns incorrect data, which is something we can do very little about.
You can run the command below in cmd.exe on the problem computer and open the resulting WMImemoryinfo.txt file to see the information stored by WMI.
wmic path Win32_PhysicalMemory >WMImemoryinfo.txt
If the output of this command differs from the exact total amount of memory in the computer, there is most likely nothing we can do because Lansweeper retrieves the data as stored in WMI. You can try to repair the WMI on your computer. However, we are not sure whether this will resolve the problem.
You can run the command below in cmd.exe on the problem computer and open the resulting WMImemoryinfo.txt file to see the information stored by WMI.
wmic path Win32_PhysicalMemory >WMImemoryinfo.txt
If the output of this command differs from the exact total amount of memory in the computer, there is most likely nothing we can do because Lansweeper retrieves the data as stored in WMI. You can try to repair the WMI on your computer. However, we are not sure whether this will resolve the problem.
