Lansweeper 10.4.2.4

What's new in this version:

Added:
- Added a new cleanup option to delete unused data for Windows assets that are no longer in the inventory
- Added a new section in the Scan Test Tool to fetch registry data using WMI

Changed:
- A message will display when the installer is ran on systems with unsupported database servers
- The volume of LsAgent scan file sizes can be reduced by disabling scan items
- A message will display when the installer is ran on unsupported operating systems
- Selecting the OT assets menu in the web console will redirect to the cloud OT assets page for linked OT installations
- The default scanning schedules have been spread out to lower peak network traffic
- The Microsoft 365 scan and mail tester can test non-default environments
- More details are provided when cloud prerequisite checks fail
- Background checks will automatically run every 30 minutes across multiple servers when cloud prerequisite checks fail

Fixed:
- LsAgent scans returned an incorrect user domain if the user was logged in using a Remote Desktop session
- The Lansweeper service sometimes used excessive memory
- Linux software was not scanned correctly when using LsAgent
- LsAgent scans would incorrectly update tblAssets.ScanServer, leading to failed deployments
- The scanning queue would appear stuck when scanning certificates due to a stopped Remote Registry service on the scanning target
- Reports using the alias “at” could not be edited in the report builder
- When creating or editing Dynamic Groups that were filtered by IP location, the “Like” operator acted as an “Equal to” operator
- When Lansweeper’s console default language was not set to English, translation errors occurred
- Some queries used too much CPU
- Linux assets were overwritten by other Linux assets if they shared the same IP address
- The Edit credential screen used the “Login” field instead of the “Username” field
- A security issue was resolved
- A security issue was resolved
- A security issue was resolved