
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-24-2019 09:07 AM
Hi,
Since upgrading to version 7.1.100.16 on 18th April, I've noticed that changes -/+ on the "History" tab on assets is getting showing all software as being removed (-) and then a (+) appears once a re-scan is done, and is throwing my reports off, until a re-scan is done.
My settings for history is 45days, so not sure why it's showing a mass (-) in the history tab daily for assets?
In scanned interval config, "Software" is set to 0 and the history box is checked, not sure if this is why? But never noticed an issue before the upgrade.
Ideas?
Thanks,
Since upgrading to version 7.1.100.16 on 18th April, I've noticed that changes -/+ on the "History" tab on assets is getting showing all software as being removed (-) and then a (+) appears once a re-scan is done, and is throwing my reports off, until a re-scan is done.
My settings for history is 45days, so not sure why it's showing a mass (-) in the history tab daily for assets?
In scanned interval config, "Software" is set to 0 and the history box is checked, not sure if this is why? But never noticed an issue before the upgrade.
Ideas?
Thanks,
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-24-2019 01:46 PM
This sounds like it will be most likely a result of the LsAgent issue. At the moment LsAgent has an issue scanning MSI packages.
If you are scanning the asset with both direct scanning and LsAgent, then LsAgent will be removing the MSI packages (due to the bug) and direct scanning will add them again.
In those cases it's best to disable LsAgent scanning until it has been fixed.
If you are scanning the asset with both direct scanning and LsAgent, then LsAgent will be removing the MSI packages (due to the bug) and direct scanning will add them again.
In those cases it's best to disable LsAgent scanning until it has been fixed.
1 REPLY 1

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-24-2019 01:46 PM
This sounds like it will be most likely a result of the LsAgent issue. At the moment LsAgent has an issue scanning MSI packages.
If you are scanning the asset with both direct scanning and LsAgent, then LsAgent will be removing the MSI packages (due to the bug) and direct scanning will add them again.
In those cases it's best to disable LsAgent scanning until it has been fixed.
If you are scanning the asset with both direct scanning and LsAgent, then LsAgent will be removing the MSI packages (due to the bug) and direct scanning will add them again.
In those cases it's best to disable LsAgent scanning until it has been fixed.
