
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-21-2016 03:32 PM
After I updated to version 6019 it seems the chip set maker is being reported as manufacturer instead of the PC manufacturer. This isn't happening for all of my machines but it is for a good number of them.
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
‎05-08-2016 08:29 PM
FYI for everyone: Lansweeper pulls the manufacturer of Windows computers from the win32_computersystem WMI (Windows Management Instrumentation) class on the computer itself.
I can't confirm this as we haven't received a win32_computersystem output of a problem computer from one of the users in this forum topic, but I assume the information is stored incorrectly in WMI itself. This is not something we can resolve. You can manually override scanned manufacturers though, e.g. by hitting the Edit Asset button on individual asset pages or clicking the Assets link at the top of the web console and using one of the mass editing options on the left.
I can't confirm this as we haven't received a win32_computersystem output of a problem computer from one of the users in this forum topic, but I assume the information is stored incorrectly in WMI itself. This is not something we can resolve. You can manually override scanned manufacturers though, e.g. by hitting the Edit Asset button on individual asset pages or clicking the Assets link at the top of the web console and using one of the mass editing options on the left.
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-08-2016 08:29 PM
FYI for everyone: Lansweeper pulls the manufacturer of Windows computers from the win32_computersystem WMI (Windows Management Instrumentation) class on the computer itself.
I can't confirm this as we haven't received a win32_computersystem output of a problem computer from one of the users in this forum topic, but I assume the information is stored incorrectly in WMI itself. This is not something we can resolve. You can manually override scanned manufacturers though, e.g. by hitting the Edit Asset button on individual asset pages or clicking the Assets link at the top of the web console and using one of the mass editing options on the left.
I can't confirm this as we haven't received a win32_computersystem output of a problem computer from one of the users in this forum topic, but I assume the information is stored incorrectly in WMI itself. This is not something we can resolve. You can manually override scanned manufacturers though, e.g. by hitting the Edit Asset button on individual asset pages or clicking the Assets link at the top of the web console and using one of the mass editing options on the left.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2016 11:56 PM
I don't think this is a known issue. Could you contact support@lansweeper.com and provide the following:
- Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on your Lansweeper server.
- Screenshots of one problem client machine's Lansweeper webpage. Show us the following tabs: Summary, Scan Time, Errors (if it exists).
- Lansweepertest.txt file generated by the command below, run locally on the same problem client machine.
wmic path win32_computersystem >lansweepertest.txt

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-25-2016 08:56 PM
I am seeing something very similar but I think it's basing it on the Network Adapter manufacturer. For instance, we are a dell shop and a majority of our VPN users are using the Cisco VPN client which creates the Cisco VPN client adapter.
I figured this out due to the fact that the systems we are seeing this happen to are on our VPN subnets.
I figured this out due to the fact that the systems we are seeing this happen to are on our VPN subnets.
