Some known assets is shown as new assets within the modified new devices report

[Timbo]

Hi.

I do hope someone here can help me, as we now need to get an email report on all new detected hardware on our moitored networks, but for some reason I get 2-3 emails with same data, and sometimes the "new" assets is old and known assets, but they simply just show up.

This makes the report useless, as monitoring team only need to act on new hardware/assets, and not already known hardware.

I've been looking around in the community, and found several articles stating issue from 7.1.x versions, but none from our current version 12.4.0.1. I am not sure how old the Lansweeper installation and database is, but some of the known assets I have seen, is no older than 12-18 months.

 The email report is launched every 15 minutes, and for some reason I now get the same newly discovered (old and known) item in 3 emails at 15 m, 30 m and 45 m, before it stops telling me this is a new device. The same goes for new devices that is correctly detected.

Then at some point, I get a "new" known asset indicated as new, even if also known for a couple of years.

So all in all, thje report is not giving the correct details.

In my email report I have requested that it uses the following - with a few other details, but all based on the Report: Device: New devices found in the last 24 hours.

Where tblAssets.Firstseen > GetDate() - 0.1249998 And tblAssetCustom.State = 1

Original line contained " GetDate () -1 " - somewhere I found that I should use "0.0416666" but then I had the data in 4 or 5 emails.

I would like to

1. Only get new devices/assets in 1 email sent everry 15 minutes, unless empty (last part is working)

2. Only get devices in 1 e-mail - not in 2 or 3 emails in a row.

[Jacob_H]

wow - i didn't know you could do GetDate in that format lol. Like David said, yeah put in the ticket and do the gatherlog thingie -  but...  i'm curious... in the report, put the assetID field in again but name it something else so it shows up on the actual email/report...   like this:   tblassets.assetid AS [blablabla]  -  i'm really curious as to if the asset is indeed the same asset with the same assetID or if its some other assetID.  Could you share the entire SQL report just to make sure something else isn't weird in it?

[Timbo]

Hi Jacob

I will give it a try, and see if this changes anything.

Here is my script - changed the subnet that I do not want results for

Select Top (1000000) tsysAssetTypes.AssetTypeIcon10 As icon,
  tblAssets.AssetID As Name,
  tblAssets.AssetName,
  tblAssets.Domain,
  tblAssets.Username,
  tblAssets.Userdomain,
  tsysAssetTypes.AssetTypename As Type,
  tblAssets.IPAddress,
  tblAssets.Description,
  tblAssetCustom.Manufacturer,
  tblAssetCustom.Model,
  tblAssetCustom.Location,
  tsysIPLocations.IPLocation,
  tblAssets.Firstseen As [Created at],
  tblAssets.Lastseen As [Last successful scan],
  indirect.lastIndirectScan As [Last indirect scan]
From tblAssetCustom
  Inner Join tblAssets On tblAssetCustom.AssetID = tblAssets.AssetID
  Inner Join tsysAssetTypes On tblAssets.Assettype = tsysAssetTypes.AssetType
  Left Outer Join tsysIPLocations On tsysIPLocations.LocationID =
      tblAssets.LocationID
  Left Join (Select Max(tblIndirectScan.LastChanged) As lastIndirectScan,
      tblIndirectScan.AssetId
    From tblIndirectScan
    Group By tblIndirectScan.AssetId) indirect On tblAssets.AssetID =
      indirect.AssetId
Where tblAssets.IPAddress Not Like '<IPrange>.%' And tblAssets.Firstseen >
  GetDate() - 0.0416666 And tblAssetCustom.State = 1 And tblAssets.Assettype <>
  -1 And tblAssets.Assettype <> 66
Order By tblAssets.AssetName

 If this do not resolve my issue, I will put in a ticket as suggested, but it will take me a couple of days to investigate.

[DavidPK]

We would like to take a closer look at the issue you have documented.

Our tech support team should be able to assist you with this.  Please open a ticket in our support portal.

Make sure to add screenshots and the GatherLogs output file so our SME's can start investigating the issue straight away. 

Using the GatherLogs tool.