→ Celebrate SysAdmin Day 2024 with Lansweeper Enter our Giveaway here

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Jonnym
Engaged Sweeper II
We are having an issue where in the LsAgent category we have over 100 entries for - No asset linked

How can I start to troubleshoot this as it only seems to be growing in terms of entries and I am concerned that these may be machines trying to report in and they cannot for whatever reason.
1 ACCEPTED SOLUTION
Bruce_B
Lansweeper Alumni
These are orphaned LsAgent records, meaning that the rows do not have a corresponding asset in the main asset table, tblAssets and only have a record in tblLsAgentAsset (null AssetID). This can be the result of an automatic merge through Windows rename detection, or an LsAgent reinstall on the clients (generating a new GUID for these clients). Ordinarily this shouldn't be a cause for concern.

You should be able to delete these records safely.

View solution in original post

5 REPLIES 5
StillGoing
Engaged Sweeper III

I recently opened a support ticket regarding this issue. Here's the long response from support. Note that this response doesn't address duplicate entries (e.g. multiple tblLsAgentAsset entries referencing the same AssetID), which is also a problem. I'm still working through that one.



We understand the importance of keeping your LsAgent data clean and organized, and it sounds like you've encountered some challenges with orphaned assets and duplicates.

We have two options to help you address this:

Option 1: Manual Uninstallation of Orphaned LsAgent Assets
This approach is ideal if you want to target specific devices that you're confident are no longer needed. Here's how to proceed:

  1. Locate Orphaned Assets: You can identify these assets by looking for entries with no AssetID in the tblLsAgentAssets table. You can use the query (Select from tblLsAgentAsset where AssetID is NULL) to view them.
  2. Uninstall LsAgent from Orphaned Devices: Navigate to Scanning > LsAgent Scanning in the Lansweeper web console. Tick the boxes next to the unwanted LsAgent assets and select "Delete". This will send a command to those devices to uninstall the agent, provided they can still communicate with the scanning server.

Option 2: Database Cleanup of Orphaned LsAgent Assets
This method allows you to directly delete orphaned entries from the database. It's a good option for bulk cleanup but proceed with caution as any mistakes could affect valid assets. Here's what to do:

Important: Before proceeding, it's crucial to back up your Lansweeper installation as a safety measure. You can find instructions on how to do this here: https://community.lansweeper.com/t5/lansweeper-maintenance/back-up-your-installation/ta-p/64309

  1. Identify Orphaned Assets: Use the same query (Select from tblLsAgentAsset where AssetID is NULL) to view assets with no associated AssetID.
  2. Delete Orphaned Entries: Once you have a backup, you can run the following query to delete these entries: delete from tblLsAgentAssets where AssetID is NULL

Additional Considerations:

We recommend choosing the option that best suits your comfort level and the specific situation. If you have any questions or need further clarification on either approach, please don't hesitate to ask. We're happy to assist you further.

Excellent, thank you for sharing the answer with the rest of the community @StillGoing 

Bruce_B
Lansweeper Alumni
These are orphaned LsAgent records, meaning that the rows do not have a corresponding asset in the main asset table, tblAssets and only have a record in tblLsAgentAsset (null AssetID). This can be the result of an automatic merge through Windows rename detection, or an LsAgent reinstall on the clients (generating a new GUID for these clients). Ordinarily this shouldn't be a cause for concern.

You should be able to delete these records safely.

But does anyone know what should be done in this case

tdtoga
Engaged Sweeper
Hi Jonnym,

Have you found out what this issue is? i am facing the same problem right now.

cheers.