Rescan Asset takes 5+ minutes after updating to 10.2.4.0

[jdansacket]

We recently upgraded our Lansweeper server from the previous version to the most current. We've noticed that when we use the Rescan Asset feature it now takes anywhere from 5 to 6 minutes for the scan to complete. It doesn't matter if the system is physical or virtual. We are a small office in 1 building. Nothing has changed from a networking perspective. Our Lansweeper server uses a dedicated SQL server which is in good health. Prior to the upgrade a Rescan Asset action would take less than 1 minute. I have a ticket open with Lansweeper support but it seems they've headed down a rabbit trail based on what they are asking me to do. Everything else works fine, it's just surprising. Both servers have been rebooted. I'm wondering if the update did something to the database that would cause the issue. Both servers have plenty or resources. Curious if anyone else has noticed this.

[jdansacket]

We will run maintenance on the SQL database and see if things change, it is in Simple mode so there are no log files to truncate.

[Obi_1_Cinobi]

Hello there!

We've not seen additional support cases that complain about the rescanning feature taking much longer in the latest version. But we have located your support case, and we have escalated it to a senior support engineer. They will analyze the ongoing case and reach out to you as soon as possible.

Even if your SQL Server is in good health, we would highly recommend going through all the steps in this KB article when facing any kind of performance issues: https://www.lansweeper.com/knowledgebase/clearing-tables-to-free-up-space-and-improve-performance/

• In addition to cleaning up your database, this KB article will rebuild all indexes which can make all the difference.

[jdansacket · Accepted solution]

We performed the suggested maintenance, that did not help. However, it was still good to go through that process....so thank you for the suggestion! The solution was to stop scanning Certificates, our scan time for a single system went from 6+ minutes to less than 45 seconds. I don't know what changed from the previous version to the latest....as it never took that long before. However, the problem is resolved as we have no need to perform certificate scans.

[DovT]

We've also had EXACTLY the same issue since upgrading to 10.2.x (we're now on 10.3.0.0), scanning assets, even on the same subnet as the scan (and database) server, takes forever, whereas before if would take less than a minute. Our scanning queue is clear when we trigger a manual scan (or after a package deployment), and the SQL server has excellent performance, it's only the scanning which takes forever. Pardon the ignorance, but how do you disable the certificate scanning? We'd like to try that as a solution as well.
@Lansweeper, if anyone is reading this, we also had a case open about this issue, ref:_00D1tqhAh._5006NN4iFi:ref

[Obi_1_Cinobi]

Hello there!

You can control which items are scanned and how often in the Scanning\Scanned Item Interval section of the Lansweeper web console. This is explained here: https://community.lansweeper.com/t5/scanning-your-network/managing-how-often-specific-data-is-scanne...

However, as you have already updated to Lansweeper version 10.3, there are some things you need to be aware of:

In Lansweeper version 10.3, you will already see some changes to the Scanning\Scanned Item Interval page. These changes were made to prepare for a new LsAgent client and Lansweeper version that has the following new feature:

• Configuration option to scan items with LsAgent only, with your scanning server only, or both. 

We currently do not have an ETA for this LsAgent client (and Lansweeper version), but in the meantime, you can find the current meaning of the new drop-down values here:

• LsAgent Only: the item is disabled for scanning.
• Scan Server And LsAgent: the item will be scanned by both.

As soon as the new LsAgent client and Lansweeper version are released, the following KB article will be updated to explain the new feature: https://community.lansweeper.com/t5/scanning-your-network/managing-how-often-specific-data-is-scanne...

Additionally, there is also a bug in Lansweeper version 10.3 (bug ID LAN-14483), where disabled scan items are still scanned when performing a manual rescan. We have no ETA for a fix at this time.