Issue
A stock PC was manually added in Lansweeper with asset type = Computer, including serial number and model information. After the device was connected to the network and a network scan was run, Lansweeper created a new Windows asset instead of merging it with the manually created computer asset.
This occurs even though Windows Renaming Detection is enabled and configured to merge assets when the model and serial number match.
Cause
The assets do not merge because Windows Renaming Detection only applies to assets with the asset type Windows.
Manually created assets with asset type Computer are treated as a different asset class and therefore cannot be merged with scanned Windows assets, regardless of matching serial number or model.
Lansweeper uniquely identifies Windows assets using a specific asset key, which is derived from Windows system data:
<NetBIOS domain or workgroup name>\<NetBIOS computer name>\1
Since manually created Computer assets do not have this Windows-specific asset key, Lansweeper does not consider them eligible for Windows Renaming Detection.
Solution
When manually adding stock computers, ensure that the asset type matches the operating system that will be detected during scanning.
-
For Windows devices, the asset type must be set to Windows
-
Do not use the generic Computer asset type for Windows systems you expect to be merged with scanned assets
If a Windows device was already added as asset type Computer, it must be corrected (or recreated) with asset type Windows to allow proper merging when the device is scanned.
Related Articles
