Understanding “No Asset Linked” Entries in LsAgent Assets

[Obi_1_Cinobi]

Question

Under Assets > LsAgent Assets, there are a large number of entries showing “No asset linked.” What do these entries represent, why do they occur, and can they be safely deleted? Some of these entries also appear to be assigned to LsAgent groups.

Answer

An entry marked “No asset linked” indicates that Lansweeper has lost the association between an existing LsAgent record and its corresponding Lansweeper asset.

Why does this happen?

This situation most commonly occurs in the following scenarios:

• The asset was manually deleted from the Assets menu.
• The device was reimaged or otherwise changed in a way that altered its unique identifier, preventing Lansweeper from matching the LsAgent record to the original asset during synchronization.

In these cases, the LsAgent record still exists in the database, but it is no longer linked to a valid asset record.

Will Lansweeper fix this automatically?

If the LsAgent entry is still enabled, and the device is still active with a running LsAgent service, Lansweeper will attempt to resolve the issue automatically:

• During the next successful LsAgent scan, Lansweeper may recreate the asset or re-establish the link using the device’s unique identification data.

If the device is no longer active, decommissioned, or no longer relevant, the orphaned LsAgent record will remain unless it is manually removed.

Is it safe to delete “No asset linked” entries?

Yes. If you are confident that:

• The device is no longer in use, or
• You do not expect the LsAgent on that device to report back again,

then it is safe to delete these “No asset linked” entries from Assets > LsAgent Assets.

Why do these entries still appear in LsAgent groups?

LsAgent groups may continue to display these entries because grouping is based on the LsAgent record itself, not the linked asset. As long as the orphaned LsAgent record exists in the database, it can still appear in group listings.

Once you delete the “No asset linked” entries from Assets > LsAgent Assets, they will also be removed from the associated LsAgent groups.

---

Bulk cleanup using SQL (optional)

If you are dealing with thousands of orphaned entries, manual cleanup may be impractical. In that case, you can remove them directly from the database using the following SQL statement:

DELETE FROM tblLsAgentAsset
WHERE AssetID IS NULL

Important precautions

• Always take a full database backup before proceeding.

• Test the change carefully in a non-production environment if possible.

Backup instructions are available here:
https://www.lansweeper.com/knowledgebase/backing-up-your-installation/

Steps to run the script safely

1. Stop the following services:

   • Lansweeper Server service (on all scanning servers)
   • Web server service on the Lansweeper web server:
     • World Wide Web Publishing Service (IIS) or
     • IIS Express, depending on your setup

2. Run the SQL statement using one of the following:

   • The DatabaseMaintenance tool in the Lansweeper installation’s Tools folder, or
   • SQL Server Management Studio

3. Restart all previously stopped services.