Experiencing high resource usage cpu/memory?

[ErikT]

We're currently investigating reports of high resource usage (cpu/memory) on the scanning server and the scanned assets. First results show these are mostly caused by driver scanning, exchange scanning, or Microsoft Store app Scanning.

Symptoms
You are experiencing a performance issue on your Lansweeper server.

Solution
For any performance issues, we generally recommend first to:

• Always update to the latest version by following the steps in this article
  
• Run a manual database cleanup to improve performance as described in this article.

If the issue persists, follow the below steps to disable the scan items that can potentially cause the issue.

Go to Scanning\Scanned Item Interval:

• Disable the SYSTEMDRIVERS item
  
  
  
• Disable the EXCHANGE item
  
  
  
• Disable SOFTWAREMSSTOREAPPS item
  From Lansweeper version 10, scanning Microsoft Store apps is not enabled by default. To battle the performance issues, double-check if the Store App item is disabled as well.
  
  

After the items are disabled:

• Clear the scanning queue via Scanning\Scanning Queue
  
• Restart the Lansweeper Server service to sever any ongoing connections

[ErikT]

We've just released Lansweeper version 10.0.1.0. This release contains improvements and fixes for some of the above-mentioned experiences with performance issues.

System driver scanning of Windows computers is now disabled by default. The WMI (Windows Management Instrumentation) class containing the driver data can be heavy to read and cause performance issues on the client machine or during scanning. When enabling system driver scanning of Windows computers, a warning is now given regarding the possible impact on performance. (LAN-12947 & LAN-13038)

Scanning a Windows computer’s Microsoft Store apps could take a long time and impact the overall scanning performance. The Microsoft Store app scan item has been improved to reduce the impact on the overall scanning performance. (LAN-12931)