TRY NOW

Changelog

  • 11.2.0.3, LsPush 8.4.100.1, LsAgent Windows 11.1.10.0, SQL 950

    25/04/2024
    • Added: LAN-15897 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: LAN-15929 Added a new section to the server options to allow more control over unique records cleanup.
    • Added: LAN-16060 Improved Cisco model specifications.
    • Added: LAN-16112 Added more keyboard data for Windows assets, such as the “Layout name” and “Layout variant” fields and a link for more information.
    • Added: LAN-16164 Added the layout name and layout variant fields to the Windows asset summary page.
    • Changed: LAN-15453 Updated “AirWatch” to “VMware Workspace One UEM (AirWatch)” in the console.
    • Changed: LAN-15898 The size of log files included in the GatherLogs tool has been decreased.
    • Changed: LAN-15929 Old authorized or unauthorized software unique records will only be cleaned up if no action has been assigned to the software.
    • Changed: LAN-15979 Removed unnecessary and duplicate CSRF checks, and improved logging for failed CSRF checks.
    • Changed: LAN-16076 Improved the AD data cleanup functionality and added the option to throttle the volume of requests.
    • Changed: LAN-16116 The loading speed of the helpdesk tab has been improved by optimizing the custom filter query.
    • Changed: LAN-16148 Memory usage of the Lansweeper service has been improved by implementing more efficient disposal of objects created by WMI.
    • Fixed: LAN-5052 An excessive number of “The LDAP Server is unavailable” error messages were being displayed on the Server Log page.
    • Fixed: LAN-10056 Deleting an ESXi host left stale entries in the tblVmwareGuest table.
    • Fixed: LAN-10303 An error occurred when setting the authentication mode to mixed during installation.
    • Fixed: LAN-14444 HP Laserjet printers were misidentified as Switches.
    • Fixed: LAN-15428 The same antivirus software could be displayed multiple times in the Software > Antivirus section of Windows computer asset pages.
    • Fixed: LAN-15798 The Windows Computer (eventlog only) scanning target was not functioning as expected.
    • Fixed: LAN-15891 An error occurred when attempting to scan vCenter targets.
    • Fixed: LAN-15920 The Edit Ticket menu in the helpdesk displayed incomplete information due to misaligned dropdown lists.
    • Fixed: LAN-15922 It was not possible to select an item from a dropdown list in the helpdesk using a keystroke.
    • Fixed: LAN-15939 Creating a knowledgebase article in the helpdesk from a ticket resulted in an error.
    • Fixed: LAN-15951 An issue sometimes occurred for installations with multiple scan servers where upgradescript 900 failed to create tblOTModule due to a deadlock on tblAssets.
    • Fixed: LAN-15953 When an incorrect username or password was used to connect to a VMware instance, an error message incorrectly appeared in the Windows Event Viewer.
    • Fixed: LAN-15980 Cloud sync did not work correctly when a proxy that required authentication was used.
    • Fixed: LAN-15987 Microsoft Entra ID scans sometimes failed, throwing an “Object reference not set to an instance of an object” error.
    • Fixed: LAN-15993 Comments on assets could not be edited.
    • Fixed: LAN-16009 The Windows computer scanning target was blocked for computers in a workgroup. Domain mapping was not used for computer scanning targets.
    • Fixed: LAN-16054 The IP location was missing for ESXi host and VMware guest assets following a rescan.
    • Fixed: LAN-16055 Assets without an IP address were not cleaned up.
    • Fixed: LAN-16058 A print spooler error was shown even when the PRINTERDRIVERS scan item was not enabled.
    • Fixed: LAN-16059 An error occurred when adding a scanning exclusion without selecting an exclusion reason.
    • Fixed: LAN-16070 Event filter widgets were displayed incorrectly.
    • Fixed: LAN-16066 The Status and Version of the VM tools were no longer retrieved when scanning ESXi or vCenter servers.
    • Fixed: LAN-16073 The Last successful scan field did not display the credential used for the scan.
    • Fixed: LAN-16076 The scanning service could send an excessive number of queries to the domain controllers.
    • Fixed: LAN-16077 Foreign key constraint errors could occur when deleting assets scanned through Microsoft Entra ID.
    • Fixed: LAN-16108 Cleanup options would wrongly delete asset radar records, even when brought in by another scanning server.
    • Fixed: LAN-16124 The “Assets: All licensed assets in Lansweeper” report showed a different number of assets compared to the number on the license page.
    • Fixed: LAN-16200 LsAgent scans didn’t pick up certain registry keys.

  • OT – 3.7.0

    10/04/2024
    • Added: ACME-16858 Added PCOM protocol for discovering devices for the manufacturer Unitronics
    • Added: ACME-17097 Added the capability to export OT scan targets.
    • Added: ACME-17100 Added the ability to bulk delete scan targets.
    • Added: ACME-17107 Added basic encoding to the initiate request for the IEC-61850 protocol.
    • Added: ACME-17656 The Controller Name is added when available for Rockwell devices while scanning with EtherNet/IP protocol.
    • Changed: ACME-17099 Memory usage has been improved in several protocols when parsing data.
    • Changed: ACME-17104 Adjusted the EtherNet/IP protocol to retrieve multiple IP addresses and MAC addresses on different communication interfaces, likewise improving coverage.
    • Fixed: ACME-14839 The info field in the version info menu would randomly switch between “Up to date” and “Update in progress” while an update was in progress.
    • Fixed: ACME-16590 Fixed the firmware parsing for Micrologix devices
    • Fixed: ACME-17106 Modified cancelling a scan in the Network Discovery Hub when scanning an OT protocol, as some protocols did not completely stop when the scan was cancelled.

  • 11.1.10.5, LsPush 8.4.100.1, LsAgent Windows 11.1.10.0, SQL 910

    28/03/2024
    • Changed: LAN-16228 The saving and merging logic for assets with Azure data has been improved.
    • Fixed: LAN-16055 Assets without an IP address were not cleaned up.
    • Fixed: LAN-16108 Cleanup options would wrongly delete asset radar records, even when brought in by another scanning server.
    • Fixed: LAN-16212 LsAgent could stall when attempting to fetch Windows Cluster logs if there was no cluster.
    • Fixed: LAN-16276 Performance scanning would throw WMI errors.
    • Fixed: LAN-16228 Azure information was sometimes removed after scans.

  • OT – 3.6.1

    18/03/2024
    • Added: ACME-17091 Expanded the SOPAS protocol for the vendor SICK AG with CoLa-A/B and the newer CoLa-2 protocol.
    • Added: ACME-17092 Improved the scanning logic for the Modbus protocol to be able to find devices from the manufacturer WAGO Kontakttechnik GmbH.
    • Changed: ACME-17103 Npcap has been updated to the latest OEM.
    • Fixed: ACME-14735 The Npcap installation could fail due to an invalid thumbprint.
    • Fixed: ACME-14816 Hub errors flooded the Application event log, causing it to rapidly wrap and unnecessarily consume system resources.

  • 11.1.9.1, LsPush 8.4.100.1, LsAgent Windows 10.4.2.0, SQL 910

    14/03/2024
    • Fixed: LAN-14404 Intune scanning failed to save data to the database.
    • Fixed: LAN-16031 Fixed an error that caused Intune scans to fail, and further implemented enhancements to optimize Intune scanning.
    • Fixed: LAN-16136 Certain asset information in vCenter assets would not be shown following a scan.
    • Fixed: LAN-16161 In rare cases, the scan server went down, concurring with resource leaks.

  • 11.1.8.0, LsPush 8.4.100.1, LsAgent Windows 10.4.2.0, SQL 910

    07/03/2024
    • Fixed: LAN-16155 The Purchased and Warranty fields within Lifecycle information could display inaccurate information.
    • Fixed: LAN-16157 Cisco VOIP phones were not correctly scanned.

  • 11.1.7.1, LsPush 8.4.100.1, LsAgent Windows 10.4.2.0, SQL 910

    15/02/2024
    • Changed: LAN-16101 Improvements have been made to the processing of incoming LsAgent files, specifically when saving Windows certificates.
    • Fixed: LAN-15989 Active Directory scans failed when passwords contained “@” or “¤.“
    • Fixed: LAN-16014 Microsoft 365 FallbackToV1 scanning failed if PowerShell 7.1 or higher is installed on the Lansweeper scanning server.
    • Fixed: LAN-16039 The startup process of the scanning service could be delayed due to email account errors in the helpdesk.
    • Fixed: LAN-16077 Foreign key constraint errors could occur when deleting assets scanned through Microsoft Entra ID.

  • …