Lansweeper keeps losing AssetNames after upgrading to v12.5.3.0

[EricWatanabe]

Hello Lansweeper Community!

We are having trouble after upgrading to Lansweeper v12.5.3.0 (on-premise) and I would appreciate your help. 

Some of our assets are losing the AssetName and as a fallback, Lansweper is using the local IP as the AssetName. This mainly happens whenever we do a manual rescan of the asset. 

Affected OS's:
- Linux, Windows ans macOS

We have already tried:
- Installing different LsAgent versions (both v10.4.2.1 and v12.3.0.1)
- Reinstalling the whole OS 
- Manually installing LsAgent (using the installer)

We haven't tried rolling back the whole lansweeper server but it could be a available option. 

[Obi_1_Cinobi · Accepted solution]

Hello there!

If you need further technical assistance, please raise a support case: https://www.lansweeper.com/contact/contact-support/

If you need technical support and have issues with accessing the Support Portal, please use this URL instead: https://www.lansweeper.com/contact/contact-support-case/

[Mister_Nobody]

Do you have PTR records in your DNS for these assets? 

[EricWatanabe]

The Linux machines in question are not joined to the domain, so they don't register themselves in DNS and therefore do not have associated PTR (reverse DNS) records. 
Is relying on PTR records the only reliable method Lansweeper uses to gather asset names? Or is there an alternative approach you'd recommend for identifying these assets more accurately?

I thought LsAgent would be sufficient for this.