→ Having trouble accessing our new support portal or creating a ticket? Please notify our team here

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
degett
Engaged Sweeper II
Hi guys,

I have a report that flags any changes made to the hard drives. It flags whenever an add or a remove is triggered

I am using the tblFloppyHist in order to do this.

Unfortunately i am getting a lot of triggers for no reasons. please see an examble in the the below image link:

http://imgur.com/vuRtPsl

is there a reason i am seeing these false positives? im 99.99% sure the users aren't unplugging the drives. does it happen when the pc is physically turned off? maybe that would cause it to flag.

Any help would be greatly appreciated.

Thanks
1 ACCEPTED SOLUTION
Susan_A
Lansweeper Alumni
A colleague of yours appears to have asked us a very similar question via email back in March. Below is a copy of the reply we sent back then.
An entry is only added to tblFloppyHist if there is a change in one or more fields of tblFloppy. Possible explanations we can think of for the behavior you're seeing:
  • Your report is built incorrectly. This seems unlikely.
  • There was a change in a field that you're not displaying in your report output. We recommend displaying *all* tblFloppyHist fields in your report.
  • You have multiple scanning servers scanning the same machine and not all of them are on the same Lansweeper release. We added some fields to the tblFloppy table at one point. If you have two scanning servers scanning a client machine, one old and one new, the new one will scan the new fields while the old one won't. This would cause "changes" to be detected that didn't actually occur on the client machine. Please double-check that all Lansweeper component numbers listed under Configuration\Your License are 5.3.0.34. If they aren't, please update all servers to Lansweeper release 5.3.0.34 by following the instructions in this knowledge base article and verify whether incorrect drive changes are reported again in the future.

If the information above doesn't explain the issue, could you provide us with the following to help us troubleshoot:
  • Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on the Lansweeper server that scanned the problem client machines.
  • Screenshot of the Configuration\Your License section of the Lansweeper web console.
  • Output of the debug report below, in Excel format. Instructions for adding this report to your Lansweeper installation can be found here.

Select Top 1000000 tblAssets.AssetID As ID,
tblAssets.AssetUnique As [Unique],
tblAssets.Assettype,
tblAssets.Firstseen,
tblAssets.Lastseen,
tblAssets.Lasttried,
tblAssets.Lasttriggered,
tblAssets.LastScheduled,
tblAssets.LastActiveScan,
tblAssets.LastIPScan,
tblAssets.LastLsPush,
tblAssets.lastWorkgroupScan,
tblAssets.LastSaved,
tblAssets.Scanserver,
tblAssets.ServiceVersion,
tblAssets.LsPushVersion,
tblFloppyHist.bytespersector,
tblFloppyHist.InterfaceType,
tblFloppyHist.Manufacturer,
tblFloppyHist.Model,
tblFloppyHist.Name,
tblFloppyHist.Partitions,
tblFloppyHist.Sectorspertrack,
tblFloppyHist.Size,
tblFloppyHist.Totalcylinders,
tblFloppyHist.Totalheads,
tblFloppyHist.Totalsectors,
tblFloppyHist.Totaltracks,
tblFloppyHist.TracksperCylinder,
tblFloppyHist.Lastchanged,
tblFloppyHist.Action
From tblAssets
Inner Join tblFloppyHist On tblAssets.AssetID = tblFloppyHist.AssetID
Order By tblFloppyHist.Lastchanged Desc

View solution in original post

4 REPLIES 4
Nick_VDB
Champion Sweeper III
We deleted the zip file as this contained your errorlog which can contain information that must not be shared publicly. We would recommend that you send a new ticket to support@lansweeper.com with the files and a reference to this forum post.

Files:

  • Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on the Lansweeper server that scanned the problem client machines.
  • Screenshot of the Configuration\Your License section of the Lansweeper web console.
  • Output of the debug report below, in Excel format. Instructions for adding this report to your Lansweeper installation can be found here.



Select Top 1000000 tblAssets.AssetID As ID,
tblAssets.AssetUnique As [Unique],
tblAssets.Assettype,
tblAssets.Firstseen,
tblAssets.Lastseen,
tblAssets.Lasttried,
tblAssets.Lasttriggered,
tblAssets.LastScheduled,
tblAssets.LastActiveScan,
tblAssets.LastIPScan,
tblAssets.LastLsPush,
tblAssets.lastWorkgroupScan,
tblAssets.LastSaved,
tblAssets.Scanserver,
tblAssets.ServiceVersion,
tblAssets.LsPushVersion,
tblFloppyHist.bytespersector,
tblFloppyHist.InterfaceType,
tblFloppyHist.Manufacturer,
tblFloppyHist.Model,
tblFloppyHist.Name,
tblFloppyHist.Partitions,
tblFloppyHist.Sectorspertrack,
tblFloppyHist.Size,
tblFloppyHist.Totalcylinders,
tblFloppyHist.Totalheads,
tblFloppyHist.Totalsectors,
tblFloppyHist.Totaltracks,
tblFloppyHist.TracksperCylinder,
tblFloppyHist.Lastchanged,
tblFloppyHist.Action
From tblAssets
Inner Join tblFloppyHist On tblAssets.AssetID = tblFloppyHist.AssetID
Order By tblFloppyHist.Lastchanged Desc
degett
Engaged Sweeper II
Bump. this is still an issue
degett
Engaged Sweeper II
Hi Susan,

I apologize for the long delay in response. I did not even notice there was a reply 🙂

the issue still persists and i have all the info you requested. i will attach them to the post
Susan_A
Lansweeper Alumni
A colleague of yours appears to have asked us a very similar question via email back in March. Below is a copy of the reply we sent back then.
An entry is only added to tblFloppyHist if there is a change in one or more fields of tblFloppy. Possible explanations we can think of for the behavior you're seeing:
  • Your report is built incorrectly. This seems unlikely.
  • There was a change in a field that you're not displaying in your report output. We recommend displaying *all* tblFloppyHist fields in your report.
  • You have multiple scanning servers scanning the same machine and not all of them are on the same Lansweeper release. We added some fields to the tblFloppy table at one point. If you have two scanning servers scanning a client machine, one old and one new, the new one will scan the new fields while the old one won't. This would cause "changes" to be detected that didn't actually occur on the client machine. Please double-check that all Lansweeper component numbers listed under Configuration\Your License are 5.3.0.34. If they aren't, please update all servers to Lansweeper release 5.3.0.34 by following the instructions in this knowledge base article and verify whether incorrect drive changes are reported again in the future.

If the information above doesn't explain the issue, could you provide us with the following to help us troubleshoot:
  • Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on the Lansweeper server that scanned the problem client machines.
  • Screenshot of the Configuration\Your License section of the Lansweeper web console.
  • Output of the debug report below, in Excel format. Instructions for adding this report to your Lansweeper installation can be found here.

Select Top 1000000 tblAssets.AssetID As ID,
tblAssets.AssetUnique As [Unique],
tblAssets.Assettype,
tblAssets.Firstseen,
tblAssets.Lastseen,
tblAssets.Lasttried,
tblAssets.Lasttriggered,
tblAssets.LastScheduled,
tblAssets.LastActiveScan,
tblAssets.LastIPScan,
tblAssets.LastLsPush,
tblAssets.lastWorkgroupScan,
tblAssets.LastSaved,
tblAssets.Scanserver,
tblAssets.ServiceVersion,
tblAssets.LsPushVersion,
tblFloppyHist.bytespersector,
tblFloppyHist.InterfaceType,
tblFloppyHist.Manufacturer,
tblFloppyHist.Model,
tblFloppyHist.Name,
tblFloppyHist.Partitions,
tblFloppyHist.Sectorspertrack,
tblFloppyHist.Size,
tblFloppyHist.Totalcylinders,
tblFloppyHist.Totalheads,
tblFloppyHist.Totalsectors,
tblFloppyHist.Totaltracks,
tblFloppyHist.TracksperCylinder,
tblFloppyHist.Lastchanged,
tblFloppyHist.Action
From tblAssets
Inner Join tblFloppyHist On tblAssets.AssetID = tblFloppyHist.AssetID
Order By tblFloppyHist.Lastchanged Desc