Changelog

If you use SQL LocalDB 2014, this release will update your database. Before updating to the newest version, make sure to back up your installation.

• Added: LAN-16013 Added an additional “Unwanted” status to the software authorization list.
  
• Changed: LAN-16111 Improved the processing of Windows LsAgent scan files.
• Changed: LAN-16167 Improved the stability of VMware scanning, and added functionality to remember successful credentials for each server.
• Changed: LAN-16464 Corrected a typo in the database naming for “web40repwokrstationOOW60days”.
  
• Fixed: LAN-12860 For some assets, an error occurred while saving drivers.
• Fixed: LAN-14109 AWS information was removed from an asset when an agentless scan couldn’t perform a full scan on that AWS asset.
• Fixed: LAN-14936 Manually inputting a serial number longer than 100 characters when editing an asset caused changes to revert.
• Fixed: LAN-15303 The categories section in the knowledgebase was missing a vertical scrollbar.
• Fixed: LAN-15935 A dashboard widget layout included an unnecessary blank space.
• Fixed: LAN-16096 VMware servers in vCenter could be identified as printers.
• Fixed: LAN-16131 Software information could be deleted if a software scan could not be completed due to network issues.
• Fixed: LAN-16142 Large AD group names could cause errors.
• Fixed: LAN-16177 The “Not latest build” reports did not take long-term support into account.
• Fixed: LAN-16188 Deployments could fail when the target computer was located on another domain.
• Fixed: LAN-16286 The Status column would disappear when scrolling on the LsAgents Assets page.
• Fixed: LAN-16315 Software scans on Linux systems were incomplete when they encountered executables located in the /usr/local/bin directory.
• Fixed: LAN-16337 Airwatch data could wrongly be deleted by certain cleanup options.
• Fixed: LAN-16399 The cleanup of old asset changelogs could result in a timeout exception.
• Fixed: LAN-16413 Filtering on custom fields in the helpdesk was not functioning correctly.
• Fixed: LAN-16460 LsAgent scans on Linux could fail if no SNMP data was found.
• Fixed: LAN-16472 When a report contained a column with the name “title”, assets could not be rescanned or exported.
• Fixed: LAN-16484 Azure Entra scans could error out when trying to save the data.
• Fixed: LAN-16489 Asset duplicates were created when the service could not find the Netbios name.
• Fixed: LAN-16490 Duplicate assets were created after running SCCM scans.
• Fixed: LAN-16519 A security issue was resolved.
• Fixed: LAN-16520 A security issue was resolved.
• Fixed: LAN-16521 A security issue was resolved.
• Fixed: LAN-16523 Software information could be lost during the LsAgent import process.
• Fixed: LAN-16562 Scanning VMware Workspace ONE UEM platforms could fail if some fields weren’t filled in on the platform.
• Fixed: LAN-16566 LsPush scans would remove the Encryptable volume data on import.
• Fixed: LAN-16568 Linux scans could not be completed if the sudo command was unavailable due to security settings.
• Fixed: LAN-16569 The “Brocade ICX7750” device was not correctly recognized as a switch.
• Fixed: LAN-16588 An error occurred when scanning Windows serial numbers.
• Fixed: LAN-16612 The Assets tab in the LsAgent Groups Configuration view was not updated correctly.
• Fixed: LAN-16638 Software data inconsistencies occurred between LsAgent and agentless scans.
• Fixed: LAN-16651 Windows Computer scans failed with the “No potentially correct credentials” error.

• Added: LAN-10459 Added a “Scan time” tab for non-Windows, Linux, and macOS assets on the asset details page.
• Added: LAN-14625 Added extra SHA variants to support SNMPv3 authentication.
• Added: LAN-15705 Added non-http2 proxy support to sync with the cloud.
• Added: LAN-15754 View and manage your OT assets in Lansweeper On-premises. For more information, see Link OT hub with Lansweeper Classic.
  
• Changed: LAN-14778 Increased size of tblSNMPinfo.ifIPaddress so that data is no longer truncated.
• Changed: LAN-14815 Upgraded the scanning service to .Net Core 6.
• Changed: LAN-14935 Extended proxy support for cloud sync.
• Changed: LAN-15267 Updated the Integrations link in the web console to redirect to the proper location.
• Changed: LAN-15450 Renamed “Azure AD” to “Microsoft Entra ID” in the web console.
  
• Fixed: LAN-10429 Multiple Azure scanning targets were shown as “Azure” on the scanning credentials page.
• Fixed: LAN-14430 Updated the link for “Download more packages” to accurately point to the page containing deployment packages.
• Fixed: LAN-14702 Compatibility Check for Asset Radar did not remove data about deleted network adapters.
• Fixed: LAN-14831 The tblSoftware.InstallLocation field was missing in the database documentation.
• Fixed: LAN-15284 When an ESXi server was scanned with only a vCenter credential, the IP address of the ESXi server was lost.
• Fixed: LAN-15300 CurrentUser software was sometimes incorrectly scanned.
• Fixed: LAN-15342 A duplicate of an asset would sometimes be created when simultaneously scanned via multiple IP addresses.
• Fixed: LAN-15407 In rare cases, software gets added and removed after every scan.
• Fixed: LAN-15422 Some firewalls were misidentified as routers.
• Fixed: LAN-15423 Some printers were incorrectly identified as switches.
• Fixed: LAN-15460 Certain Windows build numbers were not shown correctly.
• Fixed: LAN-15467 The Software History table would rarely grow out of proportion when Microsoft Store apps were scanned.
• Fixed: LAN-15612 Registry keys were not scanned for Windows 11 assets if they contained “Internet Explorer”.
• Fixed: LAN-15672 In rare cases, the Last Successful Scan value did not update due to an uncaught error that showed up during software scans.
• Fixed: LAN-15698 Installed software was sometimes not saved when scanning Mac devices using LsAgent.

• Added: LAN-14294 Added the option to enable TLS 1.2 during a Lansweeper installation update.
• Added: LAN-14537 Added a notification to the web console to notify users about the new LAPS integration.
• Added: LAN-14559 Enabled Lansweeper Cloud prerequisite checks to run in the background every 12 hours and reduced the number of required checks.
• Changed: LAN-14844 In the First Run Wizard, users can select and install Lansweeper Classic.
• Changed: LAN-15120 The license key character limit is expanded to support more partner licenses.
• Fixed: LAN-14246 An error occurs when Airwatch organization groups are scanned and saved.
• Fixed: LAN-14483 When a scan item was disabled with the “Lsagent only” option, the item was still scanned on a manual rescan.
• Fixed: LAN-14586 When AD groups were added under Website Settings, an error occurred.
• Fixed: LAN-14731 Links in the Dell manufacturer support page did not work.
• Fixed: LAN-14740 On a system with multiple network cards scanned with SNMP, the wrong MAC address was sometimes chosen as the primary MAC address.
• Fixed: LAN-14763 Some users received the “Instance is read-only” error when opening reports.
• Fixed: LAN-14776 A security issue was resolved.
• Fixed: LAN-14963 The scan server failed to import the LsAgent scan file.
• Fixed: LAN-14968 Scan errors occurred when scanning most Windows Server assets.
• Fixed: LAN-14976 Certificates were not updated correctly for LsAgent scans.
• Fixed: LAN-14977 All software was listed as updated scanning.
• Fixed: LAN-15022 For certain software items, the CatalogSoftwareId could not be updated and an error occurred.
• Fixed: LAN-15110 When FIPS was enabled, a web server error sometimes occurred.
• Fixed: LAN-15234 In the First Run Wizard, “Cloud site” did not link to Lansweeper Cloud.

• Added: LAN-10734 Added support for credential management in the Lansweeper Cloud environment.
• Added: LAN-14104 Enabled Extended Protection for Exchange EWS mailing.
• Added: LAN-14208 Added support for the Cloud-first installer.
• Added: LAN-14226 Added sections to the web console that link to Cloud features.
• Added: LAN-14359 Added the option to auto enable TLS 1.2 if the Cloud prerequisite check fails.
• Changed: LAN-14311 The rights of the “View assets” role have been reworked.
• Changed: LAN-14473 Software normalization takes place before syncing to Cloud.
• Fixed: LAN-12644 Outgoing mails in the helpdesk could give errors when using MS Graph credentials.
• Fixed: LAN-13287 SSL Decryption was not supported.
• Fixed: LAN-13408 A deadlock could occur if assets that were not completely scanned yet were deleted.
• Fixed: LAN-14005 Assets could be duplicated if they were managed by multiple SCCM servers.
• Fixed: LAN-14011 Configuring MSGraph strictly for outgoing mails in the helpdesk gave errors.
• Fixed: LAN-14016 Duplicate entries were shown in deployment logs.
• Fixed: LAN-14203 Mails in the helpdesk with large attachments could not be sent using MS Graph credentials.
• Fixed: LAN-14240 The “Software” and “Version” columns in the Reports section were not working as expected.
• Fixed: LAN-14244 The “Last successful scan” field was updated even though the asset did not exist or was offline.
• Fixed: LAN-14257 Toner information for Xerox B210 printers was not fetched.
• Fixed: LAN-14263 Forwarded mails were cut off in the helpdesk when using MS Graph credentials.
• Fixed: LAN-14278 AD information was not always added to offline assets.
• Fixed: LAN-14313 The “Printerstatus” column was too short to contain certain printer messages.
• Fixed: LAN-14317 Changes to agent options were not applied in the old layout.
• Fixed: LAN-14319 Autocomplete has been disabled in the reports search field.
• Fixed: LAN-14342 A number of issues following a Fing OID import into SNMP OID lookup have been fixed.
• Fixed: LAN-14355 Certain characters were replaced by code after translation in the helpdesk.
• Fixed: LAN-14378 Mail settings could not be saved in the helpdesk due to the encrypted client secret being too long.
• Fixed: LAN-14389 Sending an empty message in the helpdesk would break the interface.
• Fixed: LAN-14435 The sync server internet access check failed when connecting via a proxy.
• Fixed: LAN-14484 Exchange Mailboxes were not correctly scanned.
• Fixed: LAN-14497 Object reference errors could occur when opening a local user page.
• Fixed: LAN-14512 IP Locations that were in use could not be deleted after a Cloud link had been established.

• Added: LAN-14069 We now include the MudUrl when sending DHCP packets for CDR (Credential-free Device Recognition), for better analysis and correct detection. 
• Added: LAN-11174 Added the GatherLogs tool that can be found in the file system under Tools/Gatherlogs.exe. This tool automatically gathers all of the relevant logs and system information into a Zip file which can be provided to Lansweeper support for troubleshooting purposes.
• Added: LAN-12848 vMotion-related properties are now extracted during the scan of a VMware cluster. These new properties are visible on the asset page of the VMware cluster. They include info on high availability enablement, DRS enablement, default virtual machine behavior, and the number of virtual machine movements.
• Added: LAN-13144 The system will now extract vMotion-related properties during the scan of a VMware host. These new properties are visible on the asset page of the VMware host. They include info on CPUs, cores, the power state of guests and hyper-threading enablement.
• Added: LAN-13208 Added a new report “VMware: vMotion overview” that shows the newly scanned properties of VMware environments.
• Added: LAN-13714 New functionalities in Lansweeper Cloud, such as “Vulnerability insights” and “Normalized Software”, were added to certain reports and in the Authorization menu of the Software module.
• Added: LAN-13855 CDR (Credential-free Device Recognition) is now applied to asset data with the Windows asset type as well.
• Added: LAN-13994 In the User Cleanup options, the option to cleanup groups detected in on-premise Active Directory and Azure Active Directory was added. The option allows the automatic cleanup of groups that haven’t been found in the most recent scan of the Active Directory environment.
• Added: LAN-13899 Added a frequent check to see if the LsAgent relay access has been overridden by another installation.
• Added: LAN-14291 Extended SQL server scanning with SQL Server 2022
• Added: LAN-14210 Changed the text of label “Security” to “Maintenance information” label on the Asset details page.

• Changed: LAN-13799 Improved the status and description of errors when linking with Lansweeper Cloud.
• Changed: LAN-14041 Moved the general search bar to the left side of the screen.
• Changed: LAN-14042 The sub-menus for reports are improved visually and functionally by reworking the hover functionality and the search bar.
• Changed: LAN-4075 An asset imported or added through the Lansweeper web console will have its MAC address corrected when it is retrieved during regular scanning. This behavior was introduced to avoid faulty merge behavior where two unrelated assets would be merged.
• Changed: LAN-11205 Rephrased the warning message for a scan server without an internet connection when changing the dedicated scanning server to track warranty information.
• Changed: LAN-11897 Visualization of Asset Radar network interfaces with multiple IP addresses has been altered. Network interfaces can only be enabled or disabled in their entirety and not per linked IP address.
• Changed: LAN-12983 Sorting on mailbox size in the Exchange mailbox data on Exchange server asset pages will no longer sort numbers alphabetically, but numerically.
• Changed: LAN-13485 Some icons in popups in the Lansweeper web console have been reworked: the icon for the installation status to the cloud, the icon for unassigned tickets, the icon for notifications and the icon for events.
• Changed: LAN-13976 Updated the built-in list of OIDs used for SNMP lookup.
• Changed: LAN-14030 When editing the Website access on the website settings page, the groups can now be sorted and filtered in their various fields.
• Changed: LAN-14062 When performing CDR (Credential-free Device Recognition), the properties of assets with an unknown asset type are now also filled and corrected with data from CDR.
• Changed: LAN-14063 Some reports on historical data have been expanded to show all 3 possible values for history entries (i.e. add, delete, and update).
• Changed: LAN-13997 The menu item “API” found in the menu “Community” is renamed to “Cloud API”.

• Fixed: LAN-13550 Scanned Linux assets are merged with existing assets based on the IP address first which can lead to incorrect merged assets.
• Fixed: LAN-13843 During Windows computer scanning, the main IP of an asset is not always being updated if the newly acquired IP is a public IP.
• Fixed: LAN-13971 Unable to insert an image in a note or description in a helpdesk ticket through an image browser.
• Fixed: LAN-11147 It is no longer possible to use the Show header, Show footer or Show message buttons under Configuration\Website Settings as the results are not saved.
• Fixed: LAN-13161 When using deployments, excessive errors can be logged when there is no exception to the flow.
• Fixed: LAN-13260 The netBIOS name of Active Directory scanning targets is used to generate assets rather than the scanned NetBIOS name. This can potentially lead to duplicate assets.
• Fixed: LAN-13299 Disabling the Linux scan items, configured under Scanning\Scanned Item Interval, has no impact during LsAgent scan file imports.
• Fixed: LAN-13300 When disabling scan items for Linux under Scanning\Scanned Item Interval, the actual items are not marked as disabled for scanning in the corresponding asset information pages.
• Fixed: LAN-13301 After every update, the manually changed authorization rules in IIS for the Lansweeper web console are reverted.
• Fixed: LAN-13592 Scanning of Hard Disk Partition information on Linux systems doesn’t parse correctly when the Linux distribution is in another language.
• Fixed: LAN-13694 After editing and saving a scanned Azure Resource Group in the Lansweeper web console the unique identifier gets shortened.
• Fixed: LAN-13747 The cleanup option “Scan users that are disabled in on-premises Active Directory” behaves incorrectly as another option overrides the value.
• Fixed: LAN-13816 The uptime field is no longer present on asset summary pages.
• Fixed: LAN-13891 Sorting on LsAgent version in Assets\LsAgent Assets is unable to retrieve the correct data.
• Fixed: LAN-13932 Unable to process a scanned certificate when the issuer of the certificate is empty.
• Fixed: LAN-13952 The “Import from AD” button under Configuration\Asset Groups is not functional. The selected IP ranges are not imported.
• Fixed: LAN-13956 Incorrect user domain for the last logged on user for Windows assets scanned via LsAgent that have their Azure environment scanned separately.
• Fixed: LAN-13958 Incorrect main MAC address displayed for Windows assets with multiple IP addresses. The MAC address linked to the IP address of the scanned network interface should be displayed.
• Fixed: LAN-13959 The asset page of a scanned SCCM Server is broken when the SCCM scan of the asset fails.
• Fixed: LAN-13962 Incorrect domain information retrieved for an ESXi host during vCenter scan.
• Fixed: LAN-13978 Unable to retrieve OWA information for Exchange mailboxes. When certain information is not found, it is erroneously displayed as “No” instead of being omitted.
• Fixed: LAN-13980 A deployment does not start from a dynamic group when the group is created by applying a filter on the last successful scan.
• Fixed: LAN-14000 Disabled LsAgent groups are not shown in the dropdown that allows moving assets to an LsAgent group.
• Fixed: LAN-14015 The Information icon in the Configuration tab of LsAgent groups under Scanning\LsAgent Scanning is out of proportion.
• Fixed: LAN-14100 When creating multiple AWS scanning targets, a separate credential needs to be created and mapped for each scanning target. Reusing a created credential is not possible.
• Fixed: LAN-12494 The built-in admin for the helpdesk and knowledge base is shown a dialogue to enter the email address on the second login.
• Fixed: LAN-12851 SCCM managed device shows the wrong SCCM server when the asset moves to a new SCCM server.
• Fixed: LAN-12993 During SSDP discovery of an IP range scan, excessive errors are logged.
• Fixed: LAN-13169 When linking to Lansweeper Cloud, the prerequisite checks don’t react correctly when the Lansweeper database is hosted in an Azure SQL-managed instance.
• Fixed: LAN-13463 Mass edits of assets for custom fields of type Date do not persist in the database.
• Fixed: LAN-13575 Error when performing a certificate scan for the first time. Subsequent scans do not show this issue.
• Fixed: LAN-13685 After scanning Linux Solaris, an error is shown on the asset detail page of those assets.
• Fixed: LAN-13720 Built-in report: “Windows: Last scanned Windows update by computer” does not return the last update.
• Fixed: LAN-13898 The field LastseenCredentials of an asset is filled with the first tried SNMP credential when it isn’t scanned successfully via a protocol requiring credentials.
• Fixed: LAN-14018 In the new menu layout, custom names with international characters are displayed in the wrong encoding resulting in unreadable names.
• Fixed: LAN-14110 The asset location on a location map is sometimes shown in front of the left-side menu.
• Fixed: LAN-13631 When in print mode, the menu covers multiple rows of the table of interfaces on the switch asset pages, making it seem like data is missing.
• Fixed: LAN-14397 Some random assets are often not synced to Lansweeper Cloud.
• Fixed: LAN-14116 During custom file scanning of Linux system, an error is often shown instead of the type of the scanned item.
• Fixed: LAN-14128 Warranty for Dynabook devices isn’t being fetched.
• Fixed: LAN-14220 Asset Radar is overloading the SQL server with queries.
• Fixed: LAN-14213 Displaying ChromeOS devices result in webserver errors.
• Fixed: LAN-14165 OU relations not shown on user pages.
• Fixed: LAN-14131 VMware scanning – VMware vMotion report shows ESXi cluster while the asset isn’t shown in the related ESXi cluster report.
• Fixed: LAN-14052 Custom OID scanning returns null values while devicetester.exe does return values for the same OIDs.
• Fixed: LAN-14204 Deployments don’t execute after being delayed because of another deployment on the same machine.

• Changed: LAN-10499 To facilitate accurate device identification, added close to 18,000 new entries to the SNMP OID lookup list under Configuration\Asset Mapping
• Fixed: LAN-14051 Scanning servers query the database too frequently to check for configuration changes.
• Fixed: LAN-13957 Model “HP Printer” erroneously detected during OID lookup instead of more specific models.
• Fixed: LAN-13402 Older CentOS and Red Hat Enterprise Linux are not properly recognized as operating systems when performing a Linux scan.
• Fixed: LAN-13380 Large memory consumption and slow performance of the processing and persistence of the scan results of any Linux scan.

• Added: LAN-11934 Cloud-linked Lansweeper installations can now see brand, model and OS lifecycle information on individual asset pages in Cloud
• Added: LAN-11999 It is now possible to configure per LsAgent group under Scanning\LsAgent Scanning whether automatic LsAgent client updates are enabled. The default setting is “enabled” for all groups, both in new and updated Lansweeper installations.
• Added: LAN-12468 Lansweeper now also scans the install location of Microsoft Store apps, if Store apps are enabled for scanning, and saves it in the tblSoftware.InstallLocation database field
• Added: LAN-13246 Lansweeper now scans some additional properties of applications installed on Mac computers, including app path, and saves them in the tblMacApplications database table
• Changed: LAN-13094 Added a software type column to the Software\Windows Software menu
• Changed: LAN-13056 Added more indexes to the Lansweeper database to improve performance in certain areas
• Changed: LAN-12391 If an OID lookup entry exists under Configuration\Asset Mapping for an asset scanned via SNMP, the model from that lookup entry is now used as the scanned asset model, taking precedence over any model info pulled from the device itself
• Changed: LAN-11999 LsAgent version info is now displayed in the Configuration tab of LsAgent groups under Scanning\LsAgent Scanning
• Changed: LAN-11999 LsAgent version info is now displayed on the Assets\LsAgent Assets page
• Changed: LAN-11891 Made minor cosmetic improvements to the popups for creating Azure AD, Intune and Microsoft 365 scanning targets
• Changed: LAN-13224 Performed a visual redesign of the top and left menus of the Lansweeper web console, giving these menus a more modern look and feel. A setting is available under Configuration\Website Settings to switch between the old and new UI.
• Changed: LAN-12985 Scanned serial numbers are now taken into account by the non-Windows asset merge logic. If two non-Windows devices share a MAC address but have different scanned serials, these devices no longer merge.
• Changed: LAN-13235 Updated messaging throughout the web console to reflect that two-factor authentication and an app password are required now to use Gmail as a mail server for the help desk or alerts
• Changed: LAN-12595 When installing or updating Lansweeper under the SQL LocalDB database server, LocalDB is now based on the more recent SQL Server 2014 Express SP3, build 12.3.6433.1
• Changed: LAN-11744 When re-enabling a previously disabled scanned item interval, the refresh setting is now reverted to its previously configured value, instead of a default value of 5
• Fixed: LAN-13117 Azure AD scanning can fail due to a DbUpdateException error related to postal code information
• Fixed: LAN-13128 Character encoding issue in LsAgent, causing some scanned values with special characters in them (groups, users, software names etc.) to be scanned as empty strings
• Fixed: LAN-12576 Character encoding issue in the Switch Scanning info text under Configuration\Server Options
• Fixed: LAN-12650 Distinct AirWatch devices that share a MAC address aren’t correctly uniquely identified, resulting in AirWatch data being linked to incorrect assets
• Fixed: LAN-13127 Doing an export to Excel from the Assets menu results in a file without the .xlsx file extension
• Fixed: LAN-13120 Duplicate rows in the built-in reports “Software: Changes in the last 24 hours” and “Software: Changes in the last 7 days”
• Fixed: LAN-13316 Errors related to the built-in reports “Chart: Display number of display ports” and “Chart: Display number of HDMI” when the Lansweeper database is hosted in SQL Server 2008 or SQL Server 2008 R2
• Fixed: LAN-13173 Even with Asset Radar set to Enabled, assets found in Asset Radar logs aren’t always scanned or scanned assets aren’t always linked to the correct Asset Radar log entries
• Fixed: LAN-13101 Fujitsu warranty scanning is non-functional due to changes in the manufacturer’s website
• Fixed: LAN-13141 If an initial push to Cloud repeatedly fails, database backups used for previous push attempts aren’t always cleaned up, taking up unnecessary disk space
• Fixed: LAN-10219 If a Windows computer’s graphics card memory exceeds 4GB, Lansweeper is unable to correctly identify the memory amount
• Fixed: LAN-13175 Importing a non-Windows asset with a MAC address but no IP address can result in asset duplication when subsequently scanning the device
• Fixed: LAN-12727 Incorrect amount of memory scanned for Citrix XenServer assets
• Fixed: LAN-12868 Incorrect display of line breaks as HTML in asset comments in the Summary tab of individual asset pages
• Fixed: LAN-12976 In some situations, e.g. when certain firewall rules are in place, IP scans can get stuck in the IP queue after being sent to the Windows computer queue
• Fixed: LAN-13401 Issue scanning CPU and RAM info of some Unix distributions
• Fixed: LAN-13003 Issue scanning network interface info of some Unix distributions
• Fixed: LAN-12925 Issue scanning OS info of Linux Mint machines
• Fixed: LAN-12413 Issue scanning OS release info of some Unix distributions
• Fixed: LAN-12831 Issue with broken images in help desk ticket templates
• Fixed: LAN-11851 On smaller screens, the confirmation popup when deleting a user under Configuration\User Access & Roles appears partially off-screen
• Fixed: LAN-13132 Pinging assets from the Assets menu, sorting the Ping column and then exporting asset data results in the following web server error: “Invalid column name Custom. ORDER BY items must appear in the select list if SELECT DISTINCT is specified”
• Fixed: LAN-12794 Scheduled tasks used for running deployments are not always automatically cleaned up on the client machine after the completion of the deployment
• Fixed: LAN-13166 Several issues scanning enhanced key usage information of Windows computer certificates
• Fixed: LAN-13028 Several issues with the display of intended purposes in the Config\Windows\Certificates tab of Windows computer webpages, also resulting in multiple lines being shown for a single certificate
• Fixed: LAN-11845 Several layout issues on individual asset pages when no results are available for certain scanned pieces of data
• Fixed: LAN-12766 Some large values retrieved during Linux, ESXi and Windows certificate scanning are not properly written to the Lansweeper database, due to the corresponding database fields being too small
• Fixed: LAN-12866 Sorting the Scan Issues column in the Assets menu and then exporting asset data results in the following web server error: “ORDER BY items must appear in the select list if SELECT DISTINCT is specified”
• Fixed: LAN-12541 SQL injection issue, found by Matt M of Dark Nebula Security
• Fixed: LAN-13140 The button for manually retrying a failed initial push isn’t always available, despite being mentioned in the failure message
• Fixed: LAN-13124 The following DbUpdateException error can occur during Windows certificate scanning: “Number 515: Cannot insert the value NULL into column Subject, table lansweeperdb.dbo.tblCertificates; column does not allow nulls. INSERT fails”
• Fixed: LAN-13123 The following DbUpdateException error can occur during Windows certificate scanning: “Number 2627: Violation of UNIQUE KEY constraint UQ_tblCertificateLocations. Cannot insert duplicate key in object dbo.tblCertificateLocations”
• Fixed: LAN-12415 The following error can occur when attempting to add an alert for a report: “Error while saving: String was not recognized as a valid Boolean”
• Fixed: LAN-12808 The following error can occur while scanning system drivers of Windows computers: “Error getting unique key in sql server via SELECT SystemDriverUniID FROM tblSystemDriversUni”
• Fixed: LAN-12414 The following error can occur while scanning unbundled software of a Unix machine: “maxdepth is not a valid option”
• Fixed: LAN-12921 The Lansweeper database backup used for the initial push to Cloud sometimes remains mounted after a failed push
• Fixed: LAN-13049 The Last Full Sync date under Configuration\Link With Cloud Site does not take the configured web console date format into account
• Fixed: LAN-11922 The Scan Time tab on individual asset pages is not highlighted when selected
• Fixed: LAN-13162 Unbundled software of Linux computers is incorrectly detected when there are executables present directly in the /opt directory of the client machine
• Fixed: LAN-12859 Using complex JOIN clauses in a report can cause the report builder to get stuck loading or to throw object reference errors
• Fixed: LAN-13415 “Value cannot be null” error when attempting to import a file under Scanning\OID Scanning Targets
• Fixed: LAN-13214 When disabling the Windows driver, certificate or Microsoft Store app item intervals and then scanning client machines with LsAgent, data is still erroneously imported for the disabled items
• Fixed: LAN-12703 When replacing a Lansweeper scan server with another server in the same subnet, Asset Radar logs erroneously remain associated with the old server
• Fixed: LAN-7464 When scanning an asset both directly with agentless scanning and with an Azure scanning target, duplicate assets are generated
• Fixed: LAN-13194 When unsyncing individual assets from Cloud in a Cloud-linked installation, those assets are sometimes erroneously synced with Cloud again
• Fixed: LAN-12418 Windows Internet Explorer 11 is sometimes shown as installed software on machines that don’t have this web browser installed
• Fixed: LAN-12807 Windows printer driver scanning can fail with the following DbUpdateException error: “Number 242: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value”