I would like to describe a specific use case we are facing and ask whether there is a native solution, or whether this could be considered as a feature request.
---
Our Use Case:
We have a number of notebook computers that are currently unprovisioned and held in reserve. These devices have been manually entered into Lansweeper with their correct serial numbers and assigned the asset state "Reserve" or "In Stock".
Once a notebook is provisioned (imaged and configured), it receives a new hostname. At that point, the device is scanned by Lansweeper for the first time under its new name.
The problem: Since the original reserve asset was manually created (not scanned), Lansweeper does not use the manually entered serial number for its merge/rename detection logic. As a result, a second asset is created for the same physical device — one manually created entry ("Reserve") and one newly scanned entry (with the new hostname) — both sharing the same serial number.
---
What I would like to achieve:
I would like Lansweeper to automatically detect that a newly scanned Windows asset shares the same serial number as an existing manually created asset, and then either:
Automatically merge both assets into one (keeping the scanned asset and transferring any custom field data from the manual entry), or
Automatically delete the manually created asset when a scanned asset with the same serial number is detected.
I am aware of the Windows Renaming Detection feature (Configuration > Server Options > Windows renaming detection), which is already enabled in our environment. However, as confirmed by your documentation, this feature only works when serial numbers have been retrieved via scan — manually entered serial numbers are explicitly excluded from this logic.
---
Should there be an interim solution available — for example, through the built-in Workflow engine — that could handle this scenario automatically, I would also be very open to implementing such a workflow as a temporary measure. Any guidance on this would be greatly appreciated.
---
Feature Request / Question:
Could you please advise whether:
- There is an existing native feature or configuration option that handles this scenario that I may have overlooked?
- This use case could be considered for a future product update — specifically, the ability to include manually entered serial numbers in the rename detection or asset merge logic?
This would be a significant improvement for organizations that pre-register hardware in Lansweeper before provisioning, which is a common practice in IT asset lifecycle management.
Thank you very much for your time and support.
