We went with a simplified approach to the report, looking at how many connections and filtering it to those with a count greater than 1. This gave us a quick scale of the problem machines. In our case we learned the vast majority were Dell laptops.
To help resolve the issue we're using Lansweeper to deploy a configuration update to our Dell laptops using the automatic "After Scanning" schedule and a target SQL report that filters to the specific models where we can make corrections. The deployment checks for, and if needed installs, the Dell CCTK BIOS utility and then updates the BIOS to prevent simultaneous LAN and WiFi connections by default. In cases where there is a specific need this can be overridden.
Select Top 1000000 tblAssets.AssetUnique,
tblAssets.AssetID,
tblNetwork.DNSHostname As [Computer Name],
tblAssets.Username,
Count(tblNetwork.IPAddress) As [Active IP Addresses],
tblAssetCustom.Model,
tblAssets.Lastseen,
tblADComputers.OU
From tblAssets
Inner Join tblNetwork On tblAssets.AssetID = tblNetwork.AssetID
Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID
Inner Join tblADComputers On tblAssets.AssetID = tblADComputers.AssetID
Where tblNetwork.DHCPenabled = 1 And tblNetwork.IPAddress Not Like '192.168' And
tblAssetCustom.State = 1
Group By tblAssets.AssetUnique,
tblAssets.AssetID,
tblNetwork.DNSHostname,
tblAssets.Username,
tblAssetCustom.Model,
tblAssets.Lastseen,
tblADComputers.OU
Having Count(tblNetwork.IPAddress) > 1
Order By tblAssets.AssetID