Lansweeper 10.6.2

Fixed: LAN-13095 If the Lansweeper server has an older OS than the Windows machines it’s running deployments on, the deployments can fail with the following preliminary checks error: “Task Registering Error. The current version of the native library (1.4) does not support the original or minimum version of the .NET Framework NGEN v4.0.30319 task (1.x/1.x).”

Added: LAN-12485 An extended display scanning option is now available under Configuration\General to retrieve additional data for a wide variety of common monitor models
Added: LAN-9933 Lansweeper can now perform custom file scanning for Linux computers, like it already could for Windows computers
Added: LAN-8207 Lansweeper can now scan users from Azure Active Directory, using a new type of scanning target
Added: LAN-8616 Lansweeper now scans users, user groups and user logon information of Linux computers, like it already did for Windows computers
Added: LAN-9816 Lansweeper now supports using the LDAPS protocol for scanning and otherwise connecting to on-premises Active Directory domains
Changed: LAN-9840 If you relink a Lansweeper installation with Cloud whose old data is still present in Cloud, you now get a warning and option to delete the old data first
Changed: LAN-11061 Improved and expanded the network information scanned for Linux computers
Changed: LAN-9293 Improved and expanded the operating system information scanned for Linux computers
Changed: LAN-9295 Improved and expanded the processor information scanned for Linux computers
Changed: LAN-9294 Improved and expanded the software information scanned for Linux computers, retrieving data from additional commands and directories
Changed: LAN-9889 Improved and expanded volume information scanned for Linux computers
Changed: LAN-9526 Improved the way password profile info is displayed on Microsoft 365 user pages
Changed: LAN-10795 In installations with multiple scan servers, it is now possible to select a scan server from the Microsoft Cloud Service credential creation popup
Changed: LAN-4597 Removed the report “Software: List of software by computer” from the Reports menu, if not previously modified by users of the Lansweeper installation, as it is a duplicate of “Windows: Installed software by computer”
Changed: LAN-9296 Replaced old, deprecated commands used for scanning Linux computers with more modern ones, only using the old ones as a fallback now
Changed: LAN-11122 Some Active Directory scanning options that were previously spread out over the Scanning\Scanning Targets and Configuration\Server Options menus are now centralized in a single section of the Scanning\Scanning Targets menu
Changed: LAN-8538 SSH and SSH certificate credentials are now grouped under one “SSH” scanning credential type
Changed: LAN-11223 The “Active Directory Domain scanning options” previously found in a separate section under the Scanning\Scanning Targets menu are now configurable per Active Directory Domain target
Changed: LAN-11332 The Lansweeper terms of use are no longer hard coded into the installer for review, but dynamically linked from the Lansweeper website
Changed: LAN-12511 There is now a button directly in the upper right corner of the web console’s menu bar for linking a Lansweeper installation with Cloud, a button that takes you to the Configuration\Link With Cloud Site menu
Changed: LAN-12732 Visual overhaul of the information seen in the Configuration\Link With Cloud Site menu
Changed: LAN-10795 When creating a new Microsoft 365 or Intune scanning target, it is now possible to add a credential directly from within the target creation popup
Changed: LAN-10795 When editing a Microsoft 365 or Intune scanning target, an option to edit the linked credential is now available from within the target popup
Fixed: LAN-3045 A single VMware guest’s asset name not being retrievable causes the entire scan of the guest’s ESXi or vCenter server to fail
Fixed: LAN-11364 Automated cleanups of Windows assets can fail due to the following underlying error: “The DELETE statement conflicted with the REFERENCE constraint FK_tblWindowsClusterNode_tblAssets”
Fixed: LAN-12502 Citrix XenServer hosts can fail to properly scan, with the following error occurring in the background: “Sequence contains no elements”
Fixed: LAN-4942 Configuring the Display drop-down menu in the upper right corner of reports to show All results can cause the drop-down to disappear
Fixed: LAN-12658 Deployments that contain a registry condition for a (Default) registry value fail with the following error when run: “Preliminary checks unexpectedly failed”
Fixed: LAN-12625 Deployments with an After Scanning schedule only ever run once on an asset, even if multiple scans are performed
Fixed: LAN-3869 Display issue in several scan server menus in the web console when there are lots of scan servers
Fixed: LAN-12611 Duplicate printer entries in the Config\Devices\Printer tab of Windows computer webpages
Fixed: LAN-7720 Editing Mode is incorrectly labeled as Mass Edit Assets mode when hovering over the Assets menu
Fixed: LAN-12395 Error in the Scanning\Asset Radar Logs menu when the Lansweeper database is hosted under SQL Server 2008 or 2008 R2
Fixed: LAN-11046 Faulty input validation prevents help desk email accounts with Microsoft Graph as the outgoing but not the incoming protocol from being saved
Fixed: LAN-4297 If a performance scan of a Windows computer fails with an underlying “invalid query” error due to WMI corruption, that error is not displayed on the asset page, making the cause of the issue unclear
Fixed: LAN-4479 If Exchange scanning fails over HTTPS due to a timeout, Lansweeper does not try HTTP as it should
Fixed: LAN-4299 If Hyper-V logs were previously scanned for a guest and that guest is then removed from the Hyper-V host, the guest erroneously remains listed on the host’s Lansweeper webpage, even after a rescan
Fixed: LAN-12691 In a Cloud-linked installation with multiple scan servers, the Change Sync Server button doesn’t work, triggering a prerequisite check popup whose checks never complete
Fixed: LAN-4820 In Lansweeper installations with many scan servers, inability to view all server tabs in the Scanning\Asset Radar Logs menu
Fixed: LAN-4818 In Lansweeper installations with multiple scan servers, server tabs under Scanning\Compatibility & Settings are squished against the menu bar
Fixed: LAN-4930 Inability to change the Asset Radar mode after the initial Lansweeper installation, unless another compatibility check is performed first
Fixed: LAN-10169 Inability to sort the Ping column in the Assets menu
Fixed: LAN-4592 Incorrect database documentation for the tblLsAgentGroup.Status field
Fixed: LAN-12578 Incorrect saving of data in the tblSystemDriverPnpEntity and tblPrinterDriverDevice database tables used for linking system drivers and PnP drivers, printers and printer drivers
Fixed: LAN-12402 Intune and Microsoft 365 scanning can fail when using a proxy server for Internet access, even with valid proxy settings
Fixed: LAN-5094 Lack of input validation error when attempting to import a scanning credential file that contains a malformed SSH certificate key
Fixed: LAN-5035 Lack of input validation error when saving an SNMPv1/v2 scanning credential without selecting an SNMP version
Fixed: LAN-11485 Lansweeper fails to scan warranty information of Dell monitors
Fixed: LAN-9221 Linking a Lansweeper installation with Cloud can fail if the local database files are stored in a root directory
Fixed: LAN-7719 Out-of-date asset type list in the asset import template
Fixed: LAN-11124 Minor language issue in the description of the FILES item under Scanning\Scanned Item Interval
Fixed: LAN-12499 Missing Target description under the Scanning\Scanning Targets menu for AWS targets where all regions are selected
Fixed: LAN-10946 Multiple scanning credentials can be mapped to the exact same Windows computer, which should not be allowed
Fixed: LAN-5420 Performance scanning fails to take scanning exclusions into account that were set up for Linux computers
Fixed: LAN-4106 Some columns in the Assets menu don’t sort correctly when clicked
Fixed: LAN-5381 Some large values retrieved during disk scanning of Mac computers are not properly written to the Lansweeper database, due to the corresponding database fields being too small
Fixed: LAN-12042 The Asset Group, Asset Type and Report scanning targets erroneously update the Last IP Range Scan date of Windows computers that are not reachable, preventing those computers from being cleaned up by asset cleanup options
Fixed: LAN-12408 The auto-update feature doesn’t work when using a proxy server to connect to the Internet, even if the correct proxy settings are submitted under Configuration\Server Options in the Lansweeper web console
Fixed: LAN-5557 The built-in report “Users: AD password expired” erroneously includes users whose password is set to never expire
Fixed: LAN-5537 The “Computer: Duplicate SID” report has a confusing title, as it lists duplicate local user SIDs and not duplicate computer SIDs
Fixed: LAN-5096 The Lansweeper installer does not prevent users from installing just the scanning service or web console under LocalDB when a LocalDB database is not present, allowing users to set up incomplete and broken installations
Fixed: LAN-4496 The Password Required field in the Audit tab of Active Directory user pages displays incorrect data, even though the data was correctly scanned
Fixed: LAN-10144 The Previous and Next buttons in the Credential Mapping section of the Scanning\Scanning Credentials menu don’t always work
Fixed: LAN-10992 The Save Log button in the Devicetester tool is grayed out and non-functional even after completing a scan test
Fixed: LAN-12575 Using the Deploy Package option in certain reports doesn’t result in deployments actually running
Fixed: LAN-11377 Values entered into ticket custom fields of the Time type are sometimes not applied as submitted
Fixed: LAN-5174 Volume size label incorrectly set to “MB” instead of “GB” for AWS instances
Fixed: LAN-4729 When an email alert in Excel format is set up and triggered for a report that contains Active Directory user images, the following error occurs: “Type Byte is not supported”
Fixed: LAN-4758 When attempting to delete an asset group that is still linked to a performance scanning target, the following web server error is generated instead of the target automatically being deleted: “The DELETE statement conflicted with the REFERENCE constraint FK_tsysPerformanceCounterTarget_tblAssetGroups”
Fixed: LAN-7694 When deleting a knowledge base article, the article count of the knowledge base category does not immediately update
Fixed: LAN-4799 When editing a location map and scrolling to the right, assets on the map can move over parts of the user interface
Fixed: LAN-4805 When submitting % as a wildcard for software version in the software license compliance module, the module fails to include in its count software installations with an empty software version
Fixed: LAN-9737 Windows autorun items with very long Command values are not properly scanned or saved to the database, due to the underlying database field being too small

LsPush 8.4.100.1, LsAgent Windows 9.1.0.8, SQL 450 (17 Feb 2022)
Added: LAN-10165 A new option under Windows rename detection, disabled by default, to have Windows computers merge based just on a common model and serial number, without comparing the MAC addresses
Changed: LAN-2162 Added a Next Execution column to the deployment configuration section of Deployment\Scheduled Deployments, so it is clear when a deployment will run next
Changed: LAN-2114 Added paging to the Deployment\Installer Packages menu to improve page load times when there are lots of deployment packages to display
Changed: LAN-2114 For clarity’s sake, renamed some of the menus and labels in the Deployment section of the web console
Changed: LAN-10427 For licensing situations that still had it, removed the limit on the number of scan servers a Lansweeper installation can have
Changed: LAN-10556 If a scan server is receiving too many LsAgent or LsPush scans for timely processing, an error notification with recommendations is now shown in the web console
Changed: LAN-10034 If an initial push to Cloud fails, a button is now available to manually trigger another push attempt
Changed: LAN-10034 If an initial push to Cloud fails, the push is now automatically retried once after 15 minutes, instead of once after 1 hour
Changed: LAN-11639 Improved the info popup seen in the Lansweeper installer when installing a secondary scan server
Changed: LAN-2499 It is now possible to scan multiple AWS accounts with overlapping regions, by creating a scanning target for each account
Changed: LAN-11702 Made the look of the Rescan button in asset overviews and reports consistent with the Rescan button on individual asset pages
Changed: LAN-9397 SCCM scanning now respects scanning exclusions configured under Scanning\Scanning Targets and does not add excluded assets to the Lansweeper database
Changed: LAN-10646 Updated the built-in lists of: iOS codes and names, Windows OS codes and names
Fixed: LAN-9399 A deployment configuration with a weekly schedule doesn’t run for the rest of the current week if it is manually triggered once
Fixed: LAN-5439 An initial push to Cloud can fail with the following error: “Could not create backup of the SQL database. Error executing xp_create_subdir”
Fixed: LAN-11899 Asset Radar sometimes scans and shows an incorrect IPv4 subnet mask value for assets, e.g. ffff:ffff:ffff:ffff::
Fixed: LAN-10955 Certain values retrieved during Azure and Intune scanning are trimmed and not fully written to the database, due to the database fields being too small
Fixed: LAN-11342 Cross-site scripting (XSS) issue
Fixed: LAN-11346 Cross-site scripting (XSS) issue
Fixed: LAN-11939 Cross-site scripting (XSS) issue
Fixed: LAN-2154 Deployments and email alerts using an Every 1st Of The Month schedule don’t execute as planned
Fixed: LAN-8863 Exchange server data can fail to scan due to an issue in the part of the Exchange identification procedure that looks for domain controllers
Fixed: LAN-11609 Help desk mailing can start failing when attempting to import an email with a very long (reply) subject
Fixed: LAN-11624 If a Windows computer and the user logged into it are in different domains, LsAgent incorrectly identifies the domain of the logged on user
Fixed: LAN-10530 If an agentless scan is performed of a Windows computer whose Print Spooler service is stopped or disabled, a “generic failure” error is generated on the machine’s asset page
Fixed: LAN-5072 If during the execution of a deployment a referenced file cannot be accessed in the package share, e.g. because the file is blocked by Windows, this can cause the deployment to fail with an unclear object reference error and future deployments on the client machine to get stuck
Fixed: LAN-11952 If the package share username of a deployment contains a dot, the username is incorrectly displayed in the deployment logs
Fixed: LAN-11930 In Lansweeper installations linked with Cloud, slight inaccuracies in disk data displayed for Windows computers in Cloud
Fixed: LAN-7376 In some cases, e.g. after the resolution of a database connection issue, the following error is thrown when attempting to log into the web console: “404 Error: This page cannot be found”
Fixed: LAN-11769 In very large Lansweeper installations with lots of assets, performance issues can occur in certain areas of the web console due to inefficient querying of the assets’ IP locations
Fixed: LAN-10007 Inability to view or deselect previously selected days in the edit popup of a Monthly deployment schedule
Fixed: LAN-11194 Inability to view or enable a scan server’s network interfaces in the Asset Radar configuration, if one of the server’s interfaces has multiple IP addresses
Fixed: LAN-11531 Intune scanning can fail with the following error: “Error saving Intune container: Unrecognized GUID format”
Fixed: LAN-11770 Long text values in fields in the Summary tab of asset pages do not always wrap correctly, causing display issues
Fixed: LAN-11849 LsAgent fails to fully scan macOS Big Sur
Fixed: LAN-11324 LsAgent fails to scan the memory of macOS computers with an Apple M1 chip
Fixed: LAN-11239 Memory issue when opening multiple instances of the Lansweeper report builder at the same time
Fixed: LAN-11649 Notifications regarding the deprecation of old Intune and Office 365 scanning targets do not automatically disappear after the removal of the deprecated targets
Fixed: LAN-9389 Optical disc drives of Linux computers are not always detected during scanning
Fixed: LAN-11508 “Region is not valid” error while scanning the ap-northeast-3 AWS region aka Asia Pacific (Osaka), due to Amazon changing the region from a local region to a standard region
Fixed: LAN-4961 Running a deployment on a dynamic group also results in deployment attempts against non-Windows assets in the group, which it shouldn’t
Fixed: LAN-11831 Running a deployment on a filtered list of assets from multiple scan servers can result in deployment attempts against assets that are in the asset list but not part of the filtered result
Fixed: LAN-803 Running deployments on a Windows computer and then deleting the computer’s asset results in orphaned deployment log entries with an empty asset name
Fixed: LAN-5159 Running multiple deployments on different sets of assets in the Assets menu can result in deployment attempts against incorrect, previously selected assets
Fixed: LAN-11852 Scanning a Windows computer using multiple scanning methods or agents can result in incomplete memory information being returned
Fixed: LAN-11938 SQL injection issue
Fixed: LAN-11940 SQL injection issue
Fixed: LAN-11941 SQL injection issue
Fixed: LAN-11587 The Edit Built-in Admin Password button is not always visible in the ResetWebUserRoles.exe tool for installations that have the built-in admin enabled
Fixed: LAN-11857 The Force HTTPS option is visible under Configuration\Website Settings when using the IIS web server, even though that setting only applies to IIS Express and does nothing for IIS
Fixed: LAN-11884 The HTTP title of assets is displayed multiple times and in an incorrect way on individual asset pages
Fixed: LAN-11616 The Lansweeper web console does not always automatically open after completing a Lansweeper installation
Fixed: LAN-5120 The Last Execution time is not filled in under Deployment\Scheduled Deployments for deployment configurations with an After Scanning schedule
Fixed: LAN-11345 The LsAgent scanning agent for Windows still scans files and registry keys that are disabled for scanning, which it shouldn’t
Fixed: LAN-11535 The OS information of SCCM assets isn’t always displayed in asset reports and overviews even though the data was scanned
Fixed: LAN-621 Triggering deployments on multiple asset pages within a short time frame can result in duplicate deployments on those assets
Fixed: LAN-3345 Unclear object reference error thrown by a deployment in the deployment log if Lansweeper is unable to copy the latest deployment executable to the client machine, e.g. due to a firewall issue
Fixed: LAN-8130 Unnecessary technical details are displayed in some web console validation messages
Fixed: LAN-11933 When accessing the web console over HTTP and then over HTTPS, the following web server error can occur: “Subquery returned more than 1 value”
Fixed: LAN-11663 When clicking the link to the troubleshooting guide in the Scan Issues section of an asset, the page erroneously opens in the current web browser tab instead of a new tab
Fixed: LAN-4439 When creating a deployment configuration, disabling the linked deployment package and then editing the configuration, another package is erroneously preselected in the popup window
Fixed: LAN-11178 When creating a scanning credential from within a popup for mapping credentials, not all of the listed credential types are compatible with the selected mapping type
Fixed: LAN-2162 When editing a schedule linked to a deployment configuration, the deployment triggers right away and outside of the configured schedule
Fixed: LAN-11927 When linking a Lansweeper installation with Cloud, the installations is erroneously marked as Down in Cloud until the initial push is fully complete
Fixed: LAN-11558 When logging out of the web console and then trying to log back in with a new user for the first time, the following error is generated: “You have been logged out”
Fixed: LAN-11619 When scanning a Windows computer both with and without a scanning agent, the credential info listed next to Last Successful Scan and Last Scan Attempt in the computer’s Scan Time tab is not always correct
Fixed: LAN-11588 When scanning Windows computers with LsAgent over the relay server and making changes to certain scan settings like file and registry scanning, those changes are not always synced to the agents
Fixed: LAN-11556 When submitting invalid settings during the creation of an Intune v2 or Office 365 v2 scanning target, and then correcting those settings, an error is thrown indicating that the scanning target name is already in use
Fixed: LAN-9034 When using a SQL Server database hosted on Linux and linking the Lansweeper installation with Cloud, the Cloud prerequisite checks get stuck instead of throwing an error about Linux databases being unsupported
Fixed: LAN-11650 When using IIS Express and changing the Force HTTPS setting, the web console does not indicate that a web service restart is required for the change to take effect

Changed: LAN-11378 If a custom install folder is chosen that does not already end in “LansweeperAgent”, LsAgent now automatically installs to a "LansweeperAgent" subfolder in the specified directory
Changed: LAN-7424 Improved the startup process of the LsAgent service on Windows computers, to ensure the service automatically retries the startup in case of a temporary failure
Fixed: LAN-11888 If a Windows computer and the user logged into it are in different domains, LsAgent incorrectly identifies the logged on user
Fixed: LAN-10237 If the name of a software installed on a Windows computer contains the \0 termination character, the software name is scanned incorrectly by LsAgent
Fixed: LAN-11882 Issue with unauthorized First Run Wizard access under certain scenarios
Fixed: LAN-10915 LsAgent can fail to scan the OS build and release info of a Windows computer, throwing an “unexpected exception” in the background and causing the rest of the scan to fail as well
Fixed: LAN-10679 LsAgent does not correctly identify the memory type of Windows computers with DDR4 memory
Fixed: LAN-10678 LsAgent for Windows fails to scan user-specific software, causing incorrect software history entries to be generated when scanning with both LsAgent and agentless scanning
Fixed: LAN-10678 Software names are sometimes inconsistently scanned by LsAgent for Windows and agentless Windows scanning, causing incorrect software history entries to be generated
Fixed: LAN-10926 When performing a new LsAgent install on a supported Windows OS that does not yet have the required .NET Framework 4.8, the LsAgent installer fails to automatically download and install .NET 4.8, stating that no Internet access is available even when it is
Fixed: LAN-10975 When running the LsAgent installer on Windows Server 2012, the OS is erroneously reported as being unsupported
Fixed: LAN-10890 When scanning logged on users of a Windows computer, LsAgent incorrectly detects the user domain of local users as “workgroup” instead of the name of the machine
Fixed: LAN-10923 When uninstalling LsAgent from a Windows computer, some files are left behind in the LsAgent installation folder

Fixed: LAN-11396 Authorization bypass issue, allowing unauthorized users to create shared dashboard tabs
Fixed: LAN-11682 Authorization rules configured for the Lansweeper web console in IIS are erroneously removed after a Lansweeper update
Fixed: LAN-11482 Azure scanning can fail with the following DbUpdateException error: “Number 515: Cannot insert the value NULL into column ‘AddressPrefix’, table ‘lansweeperdb.dbo.tblAzureSubnet’; column does not allow nulls. INSERT fails”
Fixed: LAN-11394 Cross-site scripting (XSS) issue related to the creation of dashboard tabs
Fixed: LAN-11395 Cross-site scripting (XSS) issue related to user edits
Fixed: LAN-11653 Duplicate user entries can occur in the Exchange tab of Exchange server asset pages
Fixed: LAN-11357 If in a Lansweeper installation with multiple scan servers the help desk mail server is down, duplicate error notifications are generated for the mail server, sometimes mentioning an incorrect server name
Fixed: LAN-11357 If multiple scan servers in a Lansweeper installation are down, the related error notifications erroneously list the same server name for all servers
Fixed: LAN-11589 In some cases when using Microsoft Graph as the email protocol, processing of help desk emails can start failing due to the following underlying error: “There is already an open DataReader associated with this Command which must be closed first”
Fixed: LAN-11324 LsAgent fails to scan the memory of macOS computers with an Apple M1 chip
Fixed: LAN-5556 LsAgent for Linux and Mac erroneously creates a new log file every day and fails to clean up old LsAgent log files
Fixed: LAN-11653 “Missing username” errors can occur on the webpages of Exchange users whose Active Directory data hasn’t been scanned
Fixed: LAN-10304 Office 365 v2 scanning can time out during the retrieval of user groups, resulting in an object reference error during the subsequent retrieval of organization info and a failure of the entire scan
Fixed: LAN-11347 Remote code execution issue related to ticket template files
Fixed: LAN-5710 Starting the LsAgent service on Linux using /etc/init.d/LansweeperAgentService can result in the service crashing, due to the sudo process being aborted prematurely
Fixed: LAN-10789 The Config and Software tabs of an Apple Mac asset are sometimes hidden even though scanned data is available
Fixed: LAN-11068 The following error can occur during the initial scan of an SCCM scanning target: “Attaching an entity of type Lansweeper.Service.Domain.Asset failed because another entity of the same type already has the same primary key value”
Fixed: LAN-11611 The Lansweeper scanning service fails to stop in case of a database connectivity issue, even though the service log indicates the service is being stopped
Fixed: LAN-8186 The libicu package is erroneously deemed a dependency for installing LsAgent on Linux, causing LsAgent not to work properly on machines that don’t have this package installed
Fixed: LAN-11685 The processor type of macOS computers with an Apple M1 chip is scanned as “unknown” by LsAgent
Fixed: LAN-5712 When using a custom install directory for LsAgent on Linux, the LsAgent service fails to start
Fixed: LAN-11699 When using the IIS Express web server with the built-in Lansweeper certificate and accessing the web console on Windows 11 or Windows Server 2022, the console fails to open under its HTTPS port

Changed: LAN-11474 Revised the text and visual layout of the credential info banner seen in the Assets menu after completion of the First Run Wizard
Changed: LAN-11391 The credential info banner seen in the Assets menu after completing the First Run Wizard is now shown below the “scanning your network” banner
Changed: LAN-11391 The credential info banner seen in the Assets menu after completing the First Run Wizard now only disappears when manually dismissed
Changed: LAN-11300 The Scanning\Asset Radar Logs page now also lists data retrieved through Credential-free Device Recognition (CDR), if this is the most accurate data available for a device
Fixed: LAN-11525 Hitting the Enter key in the web console login screen does not work for logging in with the built-in admin account, even when correct built-in admin details have been submitted
Fixed: LAN-11610 Incorrect serial numbers are shown in the Summary tab of VMware asset pages, even though correct serials are scanned
Fixed: LAN-11323 The OS version of recent 32-bit Windows 10 builds is incorrectly scanned
Fixed: LAN-10854 The processor type of macOS computers with an Apple M1 chip is scanned as “unknown” by agentless scanning
Fixed: LAN-11586 Web consoles that are configured for integrated authentication, and that therefore cannot be logged into with the built-in admin, still erroneously show warning notifications regarding the use of the built-in admin
Fixed: LAN-11359 When completing the First Run Wizard on a smaller screen, the credential info banner in the Assets menu overlaps with the asset list

LsPush 8.4.100.1, LsAgent Windows 8.4.100.149, SQL 400 (18 Nov 2021)
Added: LAN-10006 For each Windows computer’s last successful scan, last scan attempt and last manual rescan, Lansweeper now shows a list of used credential names in the Scan Time tab of the asset page
Added: LAN-8791 For security reasons, a warning notification is now shown in the upper right corner of the console if the built-in admin is still enabled for web console login
Added: LAN-8790 For security reasons, a warning notification is now shown in the upper right corner of the console if the web console’s being accessed over HTTP
Added: LAN-8795 It is now possible to configure a username and password for the built-in admin. New installations are required to do this through the First Run Wizard and updated installations can optionally do this using the ResetWebUserRoles.exe tool.
Changed: LAN-11032 As part of the Asset Radar scanning feature, Lansweeper now installs Npcap 1.55 instead of 1.31
Changed: LAN-9206 Credential-free Device Recognition (CDR) now periodically updates properties that it previously filled in for an asset, if more accurate asset information is now available through CDR
Changed: LAN-8867 Credential-free Device Recognition (CDR) now returns data more quickly for assets detected after the initial Lansweeper installation
Changed: LAN-8125 For security reasons, disabled password auto-complete functionality in several password input fields in the web console
Changed: LAN-8793 For security reasons, it is no longer possible to automatically log into the web console with the built-in admin by accessing the /login.aspx?admin=1 URL
Changed: LAN-8796 For security reasons, it is no longer possible to load the Lansweeper.com website in the iFrame dashboard widget
Changed: LAN-8787 If a custom username and password are configured for the built-in admin, those details must now be submitted in the web console login screen in order to log in with the admin
Changed: LAN-9821 Improved the error message that is thrown when attempting to run asset or user actions in an unsupported or misconfigured web browser
Changed: LAN-11052 Improved the mechanism that detects whether a Windows computer is a desktop or a server during remote, credential-free scanning
Changed: LAN-9870 Lansweeper now stores two LsAgent scan dates per asset, one for the last LsAgent scan sent directly to the scan server and one for the last LsAgent scan sent to the cloud relay server
Changed: LAN-8792 Made several textual improvements in the ResetWebUserRoles.exe tool
Changed: LAN-9873 Made visual improvements to the display of scan items in the Scan Time tab of individual asset pages
Changed: LAN-8788 Performed an overhaul of the Configuration\Website Settings menu, making the page more visually consistent and adding more website info and knowledge base links
Changed: LAN-9822 Rebranded the Lansweeper Chrome extension to “Lansweeper Chromium extension”, as the same extension works for other Chromium-based web browsers as well
Changed: LAN-9866 Relabeled, repositioned and regrouped various fields in the Summary and Scan Time tabs of individual asset pages for clarity’s sake. Also added tooltips where necessary.
Changed: LAN-11238 Rephrased some of the text in the unlock screen of the First Run Wizard, to make it more explanatory
Changed: LAN-9868 Repositioned the Rescan button on individual asset pages, to make it more prominent
Changed: LAN-9882 Revised the error message that is thrown when attempting to access the Lansweeper web console in Internet Explorer, which is an unsupported web browser
Changed: LAN-9466 Scan issues that prevent some of an asset’s data from being retrieved are now visualized differently in asset overviews, reports and on asset pages. They are also more accurately referred to as “issues” rather than “errors”.
Changed: LAN-8866 The First Run Wizard seen after a new Lansweeper installation no longer requests immediate submission of scanning credentials, instead relying on Credential-free Device Recognition (CDR) to gather basic asset details
Changed: LAN-9292 The first Windows user to log into the web console is no longer given full admin rights to the console. Instead, a first Windows user to give admin rights to can be chosen through the First Run Wizard.
Changed: LAN-10787 To align with Microsoft’s own branding, local Active Directory is now referred to in the Lansweeper web console as “on-premises Active Directory”
Changed: LAN-8867 When completing the First Run Wizard after their initial Lansweeper installation, users are now directed to the Assets menu to view data, instead of to the web console dashboard. The Assets menu now also includes an info banner regarding the use of scanning credentials for further data enrichment.
Changed: LAN-9882 Windows Internet Explorer 11 is no longer a supported web browser. Access to the Lansweeper web console is now fully blocked when using IE11.
Fixed: LAN-7609 Active Directory user account enumeration issue related to the display of user images in the web console login screen
Fixed: LAN-10302 Display issue in the vCenter Overview widget when certain vCenter field values are not filled in
Fixed: LAN-8787 Duplicate login history entries in tblLoginLog when logging into the web console with the built-in admin
Fixed: LAN-4933 Duplicate network interfaces are sometimes shown in a scan server’s Asset Radar configuration
Fixed: LAN-2113 If a file not found or other type of issue occurs when running an action, the Lansweeper Chrome extension crashes instead of showing an informative error message
Fixed: LAN-9470 Importing large values into an asset custom field of the Numeric type can fail
Fixed: LAN-8796 Incorrect spelling of the word “iFrame” in several locations in the web console
Fixed: LAN-11204 Last Full Sync Date and Last Minor Sync Date in the Cloud configuration menu are displayed in UTC when they should be displayed in the time zone of the Lansweeper database server
Fixed: LAN-10793 Merging help desk tickets can fail with “INSERT statement conflict” or “no row at position 0” errors
Fixed: LAN-11119 Password hash mismatch notifications sometimes appear when there is no actual mismatch
Fixed: LAN-5194 Related help desk tickets, computer logon history and other user details are sometimes missing from a user’s Lansweeper webpage, e.g. if the user’s Active Directory details haven’t been scanned
Fixed: LAN-10825 Some error handling messages in the First Run Wizard are incorrectly positioned, overlapping with the wizard’s progress bar
Fixed: LAN-9159 SQL injection issue related to AssetActions.aspx, an issue found by Jake Dunn of Division 5
Fixed: LAN-9160 SQL injection issue related to HelpdeskEmailActions.aspx, an issue found by Jake Dunn of Division 5
Fixed: LAN-10731 The Created, CreatedBy, LastChanged and ChangedBy columns are missing from the Reports\View All Reports page
Fixed: LAN-10302 The following DbUpdateException error can occur during vCenter scanning, resulting in an incomplete vCenter asset: “Number 515: Cannot insert the value NULL into column ‘Mac’, table ‘lansweeperdb.dbo.tblAssetMacAddress’; column does not allow nulls. INSERT fails”
Fixed: LAN-10479 The following error can occur during vCenter scanning, resulting in an incomplete vCenter asset: “The operation failed: The relationship could not be changed because one or more of the foreign-key properties is non-nullable”
Fixed: LAN-10436 The MIB Importer fails to import MIB files that have multiple definitions in them
Fixed: LAN-11009 Unnecessary whitespace and column header layout issues in the Software tab of Windows computer webpages
Fixed: LAN-11178 When creating a scanning credential from within a popup for mapping credentials, not all of the listed credential types are compatible with the selected mapping type
Fixed: LAN-11286 When triggering the Asset Radar compatibility check from the web console, it fails to automatically install the Npcap driver if not already present

Fixed: LAN-11341 When linking an installation that has multiple scan servers with Cloud, servers not configured as sync server erroneously attempt to sync data with Cloud as well
Fixed: LAN-11349 Windows Server 2022 machines are sometimes erroneously identified as Windows Server 2020

Добавлено: LAN-9210 Если установка Lansweeper связана с облачным сайтом, теперь можно редактировать параметры сканирования как из облака, так и из локальной веб-консоли
Добавлено: LAN-8820 Появилась возможность использовать многофакторную аутентификацию (MFA) при связывании установки Lansweeper с Cloud
Добавлено: LAN-8442 Уведомления в правом верхнем углу веб-консоли для ситуаций, когда возникает проблема с синхронизацией с Cloud, например, когда сервер синхронизации не работает
Изменено: LAN-10572 Добавлена ссылка на базу знаний в раздел "Отслеживание гарантий" раздела "Конфигурация\Параметры сервера".
Изменения: LAN-10463 Внесено несколько изменений в программное обеспечение для корректного прекращения использования старых целей сканирования v1 Intune и Office 365
Изменения: LAN-10413 Проведен ребрендинг платформы данных об ИТ-активах на "Cloud", что привело к изменению названий некоторых кнопок, опций и меню.
Изменения: LAN-8562 Пересмотрены некоторые сообщения о состоянии синхронизации в меню конфигурации Cloud
Изменения: LAN-8442 Пересмотрено визуальное расположение информационных сообщений, предупреждений и уведомлений об ошибках в правом верхнем углу веб-консоли.
Изменено: LAN-10555 Обновлен putty.exe в Program Files (x86)\Lansweeper\Actions до версии 0.76
Исправлено: LAN-10318 Если пакет автообновления не устанавливается из-за повреждения файла и загружается повторно, кнопка Install Updates остается серой и не может быть нажата
Исправлено: LAN-5544 Если не удается связаться с доменом пользователей, опция очистки для удаления пользователей, не найденных в Active Directory, может занять много времени и привести к высокой загрузке процессора на сервере Lansweeper
Исправлено: LAN-10947 В новых установках Lansweeper страницы активов компьютеров Windows, просканированных с помощью актуальной версии LsPush, неверно указывают, что используется устаревший агент
Исправлено: LAN-10552 Длинные номера версий LsAgent не могут быть просмотрены полностью в разделе Сканирование\LsAgent Scanning
Исправлено: LAN-5232 Ошибки сканирования, возникающие при сканировании журнала Hyper-V или кластера Windows, не всегда отображаются на веб-странице Lansweeper соответствующего актива
Исправлено: LAN-10811 Несколько опций очистки активов в разделе Configuration\Server Options не функционируют, например, "Permanently delete assets not seen in the last XX days".
Исправлено: LAN-10789 Вкладки Config и Software актива Apple Mac иногда скрыты, хотя данные сканирования доступны
Исправлено: LAN-10407 Всплывающее окно "Доступна новая версия Lansweeper" все еще появляется в некоторых случаях после того, как установка Lansweeper была обновлена функцией автоматического обновления
Исправлено: LAN-10919 Инструмент ResetWebUserRoles.exe при открытии или при нажатии кнопки Enable Built-in Administrator выбрасывает следующую ошибку: "Недопустимое имя столбца AdminPassword. Неверное имя столбца AdminUserName".

Fixed: LAN-10199 Creating or deleting certain items in the web console, e.g. an asset group, can cause the sync with the IT Asset Data Platform to start failing

Added: LAN-8053 An auto-update feature is now available under Configuration\Server Options that can be enabled to automatically keep Lansweeper scan servers up-to-date
Changed: LAN-4287 Help desk email and email alerts now support Modern Authentication and Microsoft Graph for Office 365 mailing, as Microsoft is deprecating Basic Authentication
Changed: LAN-5375 Intune and Office 365 data can now be scanned with a new v2 scanning target that uses Modern Authentication and Microsoft Graph, as Microsoft is deprecating Basic Authentication
Changed: LAN-8706 Optimized the way IT Asset Data Platform setting changes are read from the Lansweeper database, to reduce the amount of database querying
Fixed: LAN-3580 A SQL Server instance that is removed from a Windows computer fails to be removed from the computer’s asset page in Lansweeper after a rescan
Fixed: LAN-3220 Active Directory User/Group Path scans of large OUs can take several days to complete
Fixed: LAN-4490 Character encoding issue in schedule names under Deployment\Scheduled Deployments
Fixed: LAN-1663 Character encoding issue in the popup you see when hovering over a user in the web console
Fixed: LAN-8083 If a Linux computer has a software installed with left or right quotation marks in its software properties, Lansweeper fails to scan the computer’s full software inventory
Fixed: LAN-8511 If the FQDN field of an asset is empty and the asset is edited, the field is sometimes filled with a blank string, which causes incorrect results in certain reports
Fixed: LAN-8248 Lansweeper fails to scan software info of Arch Linux distributions
Fixed: LAN-4137 OS information of non-Windows assets is not displayed on the Assets\LsAgent Assets page
Fixed: LAN-8751 Path traversal issue related to certain Lansweeper configuration pages
Fixed: LAN-8784 Software scanning inconsistencies between LsPush and agentless scanning, causing incorrect software history entries to be generated
Fixed: LAN-4680 The help desk ticket API fails to process ticket requests whose ticket description includes line breaks or other formatting
Fixed: LAN-9291 The Lansweeper scanning service is stuck in the Starting state when updating from a version older than 8.0 to the latest Lansweeper release
Fixed: LAN-5020 The list of available action parameters under Configuration\Asset Pages in the web console does not mention the {mac} parameter though this parameter is functionally available
Fixed: LAN-2305 The unique identifier of a Windows computer is sometimes erroneously set to the computer’s IP address instead of its domain\name combination, resulting in duplicate assets for the same machine
Fixed: LAN-5649 The unique identifier of manually created monitor and other types of assets is incorrectly formed sometimes