Mindomo Desktop (64-bit) 歷史版本列表 Page20

更新時間：2022-02-25
更新細節：

更新時間：2022-02-23
更新細節：

更新時間：2022-02-21
更新細節：

更新時間：2022-02-18
更新細節：

更新時間：2022-02-18
更新細節：

What's new in this version:

Fixed:
- LAN-12487 “Incorrect syntax” error on the ScanningScanning Targets page when the Lansweeper database is hosted in SQL Server 2008 or SQL Server 2008 R2
- LAN-12467 The Startup Type of the Lansweeper Server service is not correctly set to Automatic (Delayed Start) after a Lansweeper update

更新時間：2022-02-17
更新細節：

What's new in this version:

- Improved the Microsoft Word Format (.docx) export: better look and feel, added options to select what content to be exported, added functionality to generate a Table of Contents, and added functionality to export images and icons from topics, comments, and notes.
- Faster loading time and interaction on large diagrams

更新時間：2022-02-17
更新細節：

What's new in this version:

- 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 DeploymentScheduled Deployments, so it is clear when a deployment will run next
- LAN-2114 Added paging to the DeploymentInstaller Packages menu to improve page load times when there are lots of deployment packages to display
- LAN-2114 For clarity’s sake, renamed some of the menus and labels in the Deployment section of the web console
- LAN-10427 For licensing situations that still had it, removed the limit on the number of scan servers a Lansweeper installation can have
- 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
- LAN-10034 If an initial push to Cloud fails, a button is now available to manually trigger another push attempt
- 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
- LAN-11639 Improved the info popup seen in the Lansweeper installer when installing a secondary scan server
- LAN-2499 It is now possible to scan multiple AWS accounts with overlapping regions, by creating a scanning target for each account
- LAN-11702 Made the look of the Rescan button in asset overviews and reports consistent with the Rescan button on individual asset pages
- LAN-9397 SCCM scanning now respects scanning exclusions configured under ScanningScanning Targets and does not add excluded assets to the Lansweeper database
- 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
- 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”
- LAN-11899 Asset Radar sometimes scans and shows an incorrect IPv4 subnet mask value for assets, e.g. ffff:ffff:ffff:ffff::
- 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
- LAN-11342 Cross-site scripting (XSS) issue
- LAN-11346 Cross-site scripting (XSS) issue
- LAN-11939 Cross-site scripting (XSS) issue
- LAN-2154 Deployments and email alerts using an Every 1st Of The Month schedule don’t execute as planned
- 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
- LAN-11609 Help desk mailing can start failing when attempting to import an email with a very long (reply) subject
- 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
- 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
- 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
- LAN-11952 If the package share username of a deployment contains a dot, the username is incorrectly displayed in the deployment logs
- LAN-11930 In Lansweeper installations linked with Cloud, slight inaccuracies in disk data displayed for Windows computers in Cloud
- 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”
- 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
- LAN-10007 Inability to view or deselect previously selected days in the edit popup of a Monthly deployment schedule
- 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
- LAN-11531 Intune scanning can fail with the following error: “Error saving Intune container: Unrecognized GUID format”
- LAN-11770 Long text values in fields in the Summary tab of asset pages do not always wrap correctly, causing display issues
- LAN-11849 LsAgent fails to fully scan macOS Big Sur
- LAN-11324 LsAgent fails to scan the memory of macOS computers with an Apple M1 chip
- LAN-11239 Memory issue when opening multiple instances of the Lansweeper report builder at the same time
- 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
- LAN-9389 Optical disc drives of Linux computers are not always detected during scanning
- 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
- 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
- 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
- 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
- LAN-5159 Running multiple deployments on different sets of assets in the Assets menu can result in deployment attempts against incorrect, previously selected assets
- LAN-11852 Scanning a Windows computer using multiple scanning methods or agents can result in incomplete memory information being returned
- LAN-11938 SQL injection issue
- LAN-11940 SQL injection issue
- LAN-11941 SQL injection issue
- 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
- LAN-11857 The Force HTTPS option is visible under ConfigurationWebsite Settings when using the IIS web server, even though that setting only applies to IIS Express and does nothing for IIS
- LAN-11884 The HTTP title of assets is displayed multiple times and in an incorrect way on individual asset pages
- LAN-11616 The Lansweeper web console does not always automatically open after completing a Lansweeper installation
- LAN-5120 The Last Execution time is not filled in under DeploymentScheduled Deployments for deployment configurations with an After Scanning schedule
- LAN-11345 The LsAgent scanning agent for Windows still scans files and registry keys that are disabled for scanning, which it shouldn’t
- LAN-11535 The OS information of SCCM assets isn’t always displayed in asset reports and overviews even though the data was scanned
- LAN-621 Triggering deployments on multiple asset pages within a short time frame can result in duplicate deployments on those assets
- 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
- LAN-8130 Unnecessary technical details are displayed in some web console validation messages
- 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”
- 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
- 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
- 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
- LAN-2162 When editing a schedule linked to a deployment configuration, the deployment triggers right away and outside of the configured schedule
- 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
- 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”
- 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
- 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
- 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
- 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
- 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

更新時間：2022-02-14
更新細節：

What's new in this version:

Fixed:
- Double compare fails in LVS
- CIF writer generates unreadable file with invalid cell or layer names
- Enhanced timeout in package manager on large file download
- Backup file generation fails with relative paths
- Heal option for tiled XOR
- Bug changing PCell parameters of multiple cell instance
- Crash in debug mode when placing a "slow cell"
- Loss of selection when clicking at wrong position To make this problem less annoying, the capture range was increased when clicking at already selected items for "Move".
- New top cell appearing after load
Enhancement: #996 Refresh function to trigger update from within library
- Wrong display of negative extensions of paths
- scale and grids were wrong in case of oversampling

更新時間：2022-02-03
更新細節：

What's new in this version:

- Fixed: LAN-12017 If a Windows computer’s LsAgent client installation is auto-updated through the relay server, the LsAgent.ini file of the installation can become corrupt and subsequent LsAgent scans of the client machine can fail

更新時間：2022-01-26
更新細節：

What's new in this version:

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
- 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-4483 An LsAgent scan of a Windows computer fails if one of the computer’s Hyper-V or cluster log messages contains quotes
- LAN-11888 If a Windows computer and the user logged into it are in different domains, LsAgent incorrectly identifies the logged on user
- LAN-10237 If the name of a software installed on a Windows computer contains the termination character, the software name is scanned incorrectly by LsAgent
- LAN-11882 Issue with unauthorized First Run Wizard access under certain scenarios
- 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
- LAN-10679 LsAgent does not correctly identify the memory type of Windows computers with DDR4 memory
- 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
- LAN-10678 Software names are sometimes inconsistently scanned by LsAgent for Windows and agentless Windows scanning, causing incorrect software history entries to be generated
- 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
- LAN-10975 When running the LsAgent installer on Windows Server 2012, the OS is erroneously reported as being unsupported
- 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
- LAN-10923 When uninstalling LsAgent from a Windows computer, some files are left behind in the LsAgent installation folder