- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2019 11:16 PM
Solved! Go to Solution.
- Labels:
-
General Discussion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2019 05:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2019 05:33 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2019 05:50 PM
JacobH wrote:
sorry was talking things out loud in the forum so people can be informed and check themselves... and maybe have people use the forums more. if everything is handled in a support ticket to support, we don't know the cause/resolution.
That's fine, feel free to continue to discuss it. I just want to make sure people know that they can let our support team take a look at it. I don't want people to browse around for hours to try and find an answer if there isn't one yet.
FYI, another cause can be when you have a single VM on two hosts. Usually this means one of them won't have a MAC address. This is what happened in Caleb's case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-07-2019 06:35 PM
Esben.D wrote:
That's fine, feel free to continue to discuss it. I just want to make sure people know that they can let our support team take a look at it. I don't want people to browse around for hours to try and find an answer if there isn't one yet.
FYI, another cause can be when you have a single VM on two hosts. Usually this means one of them won't have a MAC address. This is what happened in Caleb's case.
To clarify, we had two separate issues.
1. The original issue of duplicate assets with same MAC address,and
2. The scenario where a single VM is on two different ESXi hosts.
I understand the second scenario, however the first is problem needs to be resolved.
We ended up deleting the duplicate assets and re-scanning. That seemed to help somewhat, although I'm not sure it has been resolved yet. I need to send in some additional logs to support for further troubleshooting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2019 05:28 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2019 05:13 PM
The only reasons I can think of why there would be a vmware guest asset (provided the MAC merge issue is fixed)... is:
The MAC reported by ESX is different than the successfully scannned asset
or
The VM is offline or powered off
or
You can't successfully scan the asset, so then you have a miscategorized asset (with no MAC), and the vm asset both.
Am I missing a scenario?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2019 05:06 PM
But, again, they're not merging in our environment and it's a really big deal. Disabling the scanning of the VDI is not the route I want to take.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2019 03:13 PM
SELECT Top 1000000
tblAssets.AssetID,
tblAssets.AssetName,
tblAssets.AssetType,
tblAssets.Mac,
tblAssets.IPaddress
FROM
tblAssets
WHERE
tblAssets.Mac <> ''
AND (SELECT Count(*) FROM tblAssets AS a WHERE a.Mac = tblAssets.Mac) > 1
ORDER BY
tblAssets.Mac
What you're looking for is the same MAC for AssetType 70, and AssetType -1 (VMWare Guest, Windows Guest)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2019 03:10 PM
I just did:
SELECT Top 1000000
tblAssets.AssetID,
tblAssets.AssetName,
tblAssets.AssetType,
tblAssets.Mac,
tblAssets.IPaddress
FROM
tblAssets
WHERE
tblassets.assetname like '%EXAMPLE%'
and I got
3290 EXAMPLE 70 00:50:56:86:D5:D8 192.168.108.128
4139 EXAMPLE -1 00:50:56:86:D5:D8 192.168.108.128
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2019 03:05 PM
I have the same issue - but it's on some but not all VM's.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-29-2019 10:43 PM
Best I can tell is that Lansweeper identifies a unique asset when the Windows asset is scanned, as well as when the asset is scanned via the ESXi host and vCenter.