Network Discovery Changelog

[#1]

December 10, 2025 — v4.9.4

✨ Features

• Added support for MAC address block sizes (MA-L, MA-M, MA-S) during OT device recognition. [ACME-40732]
• Added UEFI and Secure Boot detection capabilities for Windows devices. [ACME-35756]

🔃 Changes

• SNMP-OT recognition now only uses public communities, reducing unnecessary fallback calls and device load. [ACME-37438]
• Improved SNMP-based OT device mapping. [ACME-40728]
• Unified Siemens device data scanned across multiple protocols. [ACME-41777]

🐛 Fixes

• Fixed an issue where Debian packages failed to install on the latest Debian 13 distribution. [ACME-44055]
• Fixed an issue where configuration changes could cancel ongoing scans. [ACME-40267]
• Fixed an issue where scan exclusions set in a discovery action were not applied. [ACME-40559]

December 4, 2025 — v4.8.11

✨ Features

• Added support for PowerShell Constrained Language Mode. [ACME-40292]

🔃 Changes

• Improved Hub result processing to increase throughput and unblock the scanning queue. [ACME-42839]

🐛 Fixes

• Fixed an issue where installation via PowerShell script failed because embedded scripts were not signed. [ACME-40292]
• Fixed an issue where the installer incorrectly detected that linking to a site was successful. [ACME-42362]
• Fixed an issue where the configured limit for concurrent scans was not respected. [ACME-42991]
• Fixed an issue where deep EtherNet/IP scanning could fail when a device had already been discovered. [ACME-44885]

September 30, 2025 — v4.8.6

✨ Features

• Added support for OT devices from the vendor Janitza when scanning using the Modbus protocol. [ACME-31543]
• Introduced Telnet protocol support to the OT sensor for compatible DeltaV devices. [ACME-40138]

🔃Changes

• Improved passive scanning device detection for more accurate asset discovery. [ACME-37125]
• Refreshed the design of the linking and linking error pages to enhance user experience. [ACME-38644]
• Updated Npcap to version 1.83 for improved network capture performance and stability. [ACME-39990]

🐛 Fixes

• Corrected device name mapping for S7-1200 and S7-1500 series devices; manufacturer names now translate correctly. [ACME-39672]
• Resolved a security issue to enhance overall scanning safety. [ACME-39078]
• Fixed an issue where ARP scanning during OT discovery could cause devices to appear as down. [ACME-40490]
• Addressed a parsing issue where the serial number of Siemens devices was incorrectly captured when using the SNMP protocol. [ACME-40621]

July 28, 2025 — v4.7.3

✨ Features

• Added registry key mapping to enable Network and IT Agent Discovery scanning of Windows devices for UEFI and Secure Boot capability. [ACME-35878]
• DNS names can now be used for rescans in the Hub. [ACME-35187]

🔃 Changes

• The Discovery queue UI has been reworked to show more action details, with added filtering and grouping options. [ACME-33517]

🐛 Fixes

• The IP address of a local scan would sometimes not update correctly. [ACME-34511]
• SNMP scans in Network Discovery could fail with the error “Could not execute a deep SNMP scan” due to missing OIDs for TotalMemory and ProcessorArchitecture. [ACME-34844]
• When linking to cloud, the page could refresh, resulting in errors in the logs. [ACME-35587]
• The ModuleStartIndex of a bus configuration could be displayed incorrectly in the UI due to a mapping issue. [ACME-37326]
• Windows user logons were generating duplicate entries. [ACME-36189]

June 25, 2025 — v4.6.3

✨ Features

• Users can now add LAPS as a credential type when configuring scanning through the Hub interface. [ACME-20231]
• Added UEFI and Secure Boot capabilities on Windows devices. [ACME-35756]

🐛 Fixes

• Improved scan queue processing reliability. [ACME-30810]
• Improved reliability of the installation process and link-to-cloud process. [ACME-35380]

June 2, 2025 — v4.5.5

🐛 Fixes

• Exceptions thrown by converters during Active Directory scans were not being properly handled. [ACME-34479]

May 22, 2025 — v4.5.3

🐛 Fixes

• Exceptions thrown by converters during Active Directory scans were not being properly handled. [ACME-34479]
• The auto-update could be triggered before the new files were fully downloaded. [ACME-34785]

May 14, 2025 — v4.5.2

✨ Features

• Frictionless Cloud-First Trial install flow for Windows and macOS. [ACME-28350]
• Added support for the HART-IP protocol. [ACME-31982]

🔃 Changes

• SNMP parsing has been improved for OT devices from the vendor Fisher Rosemount. [ACME-33970]
• Improved Siemens data parsing during scanning with the SNMP protocol. [ACME-32585]

🐛 Fixes

• SNMPv3 scans were not possible with certain combinations of authentication digest and privacy protocol. [ACME-34446]
• Error when executing warranty scan. [ACME-32237]
• Forbidden errors when syncing data. [ACME-34510]
• The MAC address “00:00:00:00:00:00” was not ignored when scanning with SNMP-OT. [ACME-33197]

April 17, 2025 — v4.4.2

✨ Features

• Added the HID VertX protocol to scan HID VertX and HID EDGE access control systems. [ACME-22618]
• Added the ABB protocol. [ACME-28757]
• Scan options for IT Agent Portable have been improved. [ACME-26448]
• Added printers when scanning Active Directory for devices. [ACME-27739]
• Extended expiration time options for linking codes. [ACME-28217]
• Improved visibility of sensor issues. [ACME-29971]

🐛 Fixes

• MAC addresses starting with 00:00:0C:07:AC were incorrectly filtered out. [ACME-27874]
• Improved handling of unknown WMI errors. [ACME-32431]
• Improved Moxa device detection. [ACME-32836]
• AD user scans would stop and throw errors when scanning users that had a thumbnail photo. [ACME-33230]
• Display all sensors in Discover Now page when having more than 15 sensors. [ACME-33350]

March 6, 2025 — v4.3.5

✨ Features

• Added Citrix scanning functionality via Discover Now. [ACME-26773]
• Start an ESXi and vCenter credentials from LS Site. [ACME-22344]

🔃 Changes

• Expanded the status code information for controller-type devices from the vendor Rockwell in the EtherNet/IP protocol. [ACME-27931]

🐛 Fixes

• Fixed multi-region environment parameters for the Hub. [ACME-30876]
• Proxy settings were not always taken into account. [ACME-30557]
• OT scan targets that were not linked to a sensor could sometimes fail to be deleted. [ACME-30174]
• Reworked the validation of the linking token so the skipcloudlinking value is taken into account. [ACME-30077]
• The recognition flow during an advanced OT scan was executed for every selected protocol instead of just once per IP address. [ACME-29781]

February 10, 2025 — v4.2.5

🐛 Fixes

• Some scanning actions were not performed consistently due to the scanning configuration not being properly retrieved. [ACME-30175]
• The macOS PKG installer would fail to install successfully. [ACME-30521]
• Reusing an existing schedule for multiple sensors did not work correctly. [ACME-30188]

January 28, 2025 — v4.2.4

✨ Features

• Enhanced logging and improved handling for the RSA key identifier. [ACME-28594]
• Added IT devices to the data transfer for air-gapped installations. [ACME-27337]
• An Active Directory domain scan will automatically start when a new sensor registers on the Hub for the first time. [ACME-26664]
• Do an active CDR Scan on first run. [ACME-26658]
• SCCM deepscan — it is now possible to add manual credentials to scan the devices that are found through the SCCM scan in Discover Now. [ACME-26492]
• When users order their credentials on LS Sites, the order will be followed when executing a scan by clicking “Scan Now.” [ACME-26204]
• Added an HTML request fallback to the MOXA protocol for fetching basic information. [ACME-23604]

🐛 Fixes

• Installer configuration files downloaded from Lansweeper Sites did not point to the stable release channel by default. [ACME-28902]
• The RPM repository signature was not correctly signed, preventing warnings for customers with GPG checks enabled. [ACME-28457]
• On the scan target page, sorting by sensor name without a linked sensor would crash the page. [ACME-28441]
• DCP messages in the Profinet protocol were not always consumed. [ACME-27994]
• Notifications from Lansweeper Sites were not properly handled and were sometimes processed out of order. [ACME-27863]
• An infinite loop could occur in CDP scanning. [ACME-27849]
• An error was thrown when importing an OT scan target with an invalid IP address. [ACME-27682]
• A null reference error could occur when mapping Active Directory users. [ACME-27658]