1 ACCEPTED SOLUTION
Hello there!
This sounds like a merging issue.
In general, when Lansweeper or LsAgent scans your assets (or when an asset is created manually), a unique identifier is created based on the scanned/submitted information. For non-Windows assets, this unique identifier is the MAC address of the asset (if Lansweeper was able to scan this information or if this information was provided). If the MAC address is not available, the IP address will be used instead.
When saving the scanned information in the database, Lansweeper will first check if this unique identifier already exists. If this is the case, the existing asset will be updated, and if not, the new asset will be added.
With this in mind, if a (newly) scanned asset (or one of the linked components) shares one (or more) MAC address(es) with another asset, the scanned asset will have the same identifier and will as such merge or update the existing asset. When an asset is merged into another asset, this should be listed in the Comments tab of the asset that still exists. Please note that there has to be an exact match, Lansweeper doesn't assume similar MAC addresses to be the same.
In some scenarios, the default merging logic can be quite aggressive.
We’ve expanded the existing merge logic in version 9.2 and added an additional check on the serial number. This means the new logic will check on both the scanned MAC addresses and the scanned serial numbers to determine if non-Windows assets need to be merged. If two devices share MAC addresses, but Lansweeper detected different serial numbers during the scan, then they will no longer merge. Please note that manual serial number edits will not be taken into account for the new merge logic. Only serial numbers that were detected during scans are used.
The new merge logic is not enabled by default (yet) as we're still gathering feedback from customers.
However, you can enable the new merging logic as follows:
- First, ensure that your Lansweeper installation is up to date.
- Before updating, create a backup of your installation, just to be safe.
- Go to Program Files (x86)\Lansweeper\Tools on your Lansweeper server and run ConfigEditor.exe.
- In the Service tab, click Add under AppSettings.
- Enter NonWindowsDuplicatesNewMerge with a value of 1 and hit Add.
- Hit Save configs and restart service and confirm by hitting Yes in the window that pops up.
- Rescan the IP range(s) containing the non-Windows assets that were merging.
- Check if asset pages were created for the devices in the scanned range(s) that were previously being merged into other devices.
Hello there!
This sounds like a merging issue.
In general, when Lansweeper or LsAgent scans your assets (or when an asset is created manually), a unique identifier is created based on the scanned/submitted information. For non-Windows assets, this unique identifier is the MAC address of the asset (if Lansweeper was able to scan this information or if this information was provided). If the MAC address is not available, the IP address will be used instead.
When saving the scanned information in the database, Lansweeper will first check if this unique identifier already exists. If this is the case, the existing asset will be updated, and if not, the new asset will be added.
With this in mind, if a (newly) scanned asset (or one of the linked components) shares one (or more) MAC address(es) with another asset, the scanned asset will have the same identifier and will as such merge or update the existing asset. When an asset is merged into another asset, this should be listed in the Comments tab of the asset that still exists. Please note that there has to be an exact match, Lansweeper doesn't assume similar MAC addresses to be the same.
In some scenarios, the default merging logic can be quite aggressive.
We’ve expanded the existing merge logic in version 9.2 and added an additional check on the serial number. This means the new logic will check on both the scanned MAC addresses and the scanned serial numbers to determine if non-Windows assets need to be merged. If two devices share MAC addresses, but Lansweeper detected different serial numbers during the scan, then they will no longer merge. Please note that manual serial number edits will not be taken into account for the new merge logic. Only serial numbers that were detected during scans are used.
The new merge logic is not enabled by default (yet) as we're still gathering feedback from customers.
However, you can enable the new merging logic as follows:
- First, ensure that your Lansweeper installation is up to date.
- Before updating, create a backup of your installation, just to be safe.
- Go to Program Files (x86)\Lansweeper\Tools on your Lansweeper server and run ConfigEditor.exe.
- In the Service tab, click Add under AppSettings.
- Enter NonWindowsDuplicatesNewMerge with a value of 1 and hit Add.
- Hit Save configs and restart service and confirm by hitting Yes in the window that pops up.
- Rescan the IP range(s) containing the non-Windows assets that were merging.
- Check if asset pages were created for the devices in the scanned range(s) that were previously being merged into other devices.
Hello there!
This sounds like a merging issue.
In general, when Lansweeper or LsAgent scans your assets (or when an asset is created manually), a unique identifier is created based on the scanned/submitted information. For non-Windows assets, this unique identifier is the MAC address of the asset (if Lansweeper was able to scan this information or if this information was provided). If the MAC address is not available, the IP address will be used instead. More information on this unique identifier can be found in the following knowledgebase article: https://www.lansweeper.com/knowledgebase/how-lansweeper-uniquely-identifies-assets/
When saving the scanned information in the database, Lansweeper will first check if this unique identifier already exists. If this is the case, the existing asset will be updated, and if not, the new asset will be added.
With this in mind, if a (newly) scanned asset (or one of the linked components) shares one (or more) MAC address(es) with another asset, the scanned asset will have the same identifier and will as such merge or update the existing asset. When an asset is merged into another asset, this should be listed in the Comments tab of the asset that still exists. Please note that there has to be an exact match, Lansweeper doesn't assume similar MAC addresses to be the same.
In some scenarios, our default merging logic is a bit too aggressive. We’ve expanded the existing merge logic in version 9.2 and added an additional check on the serial number. This means the new logic will check on both the scanned MAC addresses and the scanned serial numbers to determine if non-Windows assets need to be merged. If two devices share MAC addresses, but Lansweeper detected different serial numbers during the scan, then they will no longer merge. Please note that manual serial number edits will not be taken into account for the new merge logic. Only serial numbers that were detected during scans are used.
The new merge logic is not enabled by default (yet) as we're still gathering feedback from customers.
However, you can however enable it as follows:
- First, make sure that your Lansweeper installation is up to date: https://www.lansweeper.com/knowledgebase/updating-your-installation/
- Before updating, create a backup of your installation, just to be safe: https://www.lansweeper.com/knowledgebase/backing-up-your-installation/
- Go to Program Files (x86)\Lansweeper\Tools on your Lansweeper server and run ConfigEditor.exe
- In the Service tab, click Add under AppSettings.
- Enter NonWindowsDuplicatesNewMerge with a value of 1 and hit Add.
- Hit Save configs and restart service and confirm by hitting Yes in the window that pops up.
- Rescan the IP range(s) containing the non-Windows assets that were merging.
- Check if asset pages were now created for the devices in the scanned range(s) that were previously being merged into other devices.
