Lansweeper

What's new in this version:

Added:
- Added an option for LsAgent groups to configure exclusive LsAgent asset scanning. These assets will not be scanned by agentless or credential-free scanning methods
- Added a new section to the server options to allow more control over unique records cleanup
- Improved Cisco model specifications
- Added more keyboard data for Windows assets, such as the “Layout name” and “Layout variant” fields and a link for more information
- Added the layout name and layout variant fields to the Windows asset summary page

Changed:
- Updated “AirWatch” to “VMware Workspace One UEM (AirWatch)” in the console
- The size of log files included in the GatherLogs tool has been decreased
- Old authorized or unauthorized software unique records will only be cleaned up if no action has been assigned to the software
- Removed unnecessary and duplicate CSRF checks, and improved logging for failed CSRF checks
- Improved the AD data cleanup functionality and added the option to throttle the volume of requests
- The loading speed of the helpdesk tab has been improved by optimizing the custom filter query
- Memory usage of the Lansweeper service has been improved by implementing more efficient disposal of objects created by WMI

Fixed:
- An excessive number of “The LDAP Server is unavailable” error messages were being displayed on the Server Log page
- Deleting an ESXi host left stale entries in the tblVmwareGuest table
- An error occurred when setting the authentication mode to mixed during installation
- HP Laserjet printers were misidentified as Switches
- The same antivirus software could be displayed multiple times in the Software > Antivirus section of Windows computer asset pages
- The Windows Computer (eventlog only) scanning target was not functioning as expected
- An error occurred when attempting to scan vCenter targets
- The Edit Ticket menu in the helpdesk displayed incomplete information due to misaligned dropdown lists
- It was not possible to select an item from a dropdown list in the helpdesk using a keystroke
- Creating a knowledgebase article in the helpdesk from a ticket resulted in an error
- An issue sometimes occurred for installations with multiple scan servers where upgradescript 900 failed to create tblOTModule due to a deadlock on tblAssets
- When an incorrect username or password was used to connect to a VMware instance, an error message incorrectly appeared in the Windows Event Viewer
- Cloud sync did not work correctly when a proxy that required authentication was used
- Microsoft Entra ID scans sometimes failed, throwing an “Object reference not set to an instance of an object” error
- Comments on assets could not be edited
- The Windows computer scanning target was blocked for computers in a workgroup. Domain mapping was not used for computer scanning targets
- The IP location was missing for ESXi host and VMware guest assets following a rescan
- Assets without an IP address were not cleaned up
- A print spooler error was shown even when the PRINTERDRIVERS scan item was not enabled
- An error occurred when adding a scanning exclusion without selecting an exclusion reason
- Event filter widgets were displayed incorrectly
- The Status and Version of the VM tools were no longer retrieved when scanning ESXi or vCenter servers
- The Last successful scan field did not display the credential used for the scan
- The scanning service could send an excessive number of queries to the domain controllers
- Foreign key constraint errors could occur when deleting assets scanned through Microsoft Entra ID
- Cleanup options would wrongly delete asset radar records, even when brought in by another scanning server
- The “Assets: All licensed assets in Lansweeper” report showed a different number of assets compared to the number on the license page
- LsAgent scans didn’t pick up certain registry keys