Lansweeper Reporting Old Assets as New

[Jpatterson]

Contents of errorlog.txt

2019-09-14 20:25:13,980 [SCAN_10.40.195.11] INFO Error updating or inserting last scan DNS redirected to 1205-DC02 but expected computer 1205-DC02.something.local
at LansweeperService.ComputerScanning.CheckWMIInitialAccessOK(Asset #=q7m_xSQK3jbu3ZYpxRFPpEA==)
at LansweeperService.ComputerScanning.CheckWMIAccessIP(Asset #=q7m_xSQK3jbu3ZYpxRFPpEA==, Func`2 #=qJSGaJ8d9O64iMDIMrqj1ew==)
2019-09-15 12:00:25,077 [SCAN_10.40.1.19] INFO Error updating or inserting last scan DNS redirected to AS-APPS but expected computer AS-APPS.something.local
at LansweeperService.ComputerScanning.CheckWMIInitialAccessOK(Asset #=q7m_xSQK3jbu3ZYpxRFPpEA==)
at LansweeperService.ComputerScanning.CheckWMIAccessIP(Asset #=q7m_xSQK3jbu3ZYpxRFPpEA==, Func`2 #=qJSGaJ8d9O64iMDIMrqj1ew==)

Thanks-

[Jpatterson]

Yes, updated to 7.2.100.23 a few days ago when this started. We use the canned report:

Computer: New computers found in the last 5 minutes

and set up an email alert.

Thanks for your time-

[Esben_D]

Could you check which report is being used for the alert? Maybe the update changed something in the report.

As long as the assets' first seen date has not changed, it not a "scanning" issue, but a reporting issue.

If it is a custom report you can also post it here and I can take a look at it.

Lastly, you can update to the latest version 7.2.100.23 from here: https://www.lansweeper.com/update-lansweeper/

[Jpatterson]

Yes, we have an email alert setup that warns us each our if there are new assets added to the network. Typically we only get one alert when creating new virtual machines. For some reason we get an email every hour with just this one asset as-apps.

Thanks-

[Esben_D]

Is it being displayed in a specific report for new devices or has the first seen changed?

The one time I saw this error, the problem just ended up being a mistake in a report the person was using. You can always contact support and send them the errorlog and screenshots.

[Jpatterson]

The machine is a server that has been in lansweeper since 2017.

[Esben_D]

The only case I've seen like this ended up not being a simple mistake in the way the data was reported on.

How did you determine that old machines are being reported as new?