Speedify

What's new in this version:

- Changed: The links in the Reports and Community menus of the web console to download more reports now point to the Lansweeper report library instead of the report section of the Lansweeper forum

Fixed:
- Assets scanned with the LsAgent scanning agent are not always listed in the AssetsLsAgent Assets section of the web console
- Duplicate assets are sometimes generated for devices scanned closely following the completion of the First Run Wizard
- LAN-8597 Network info of Linux computers can fail to scan with the following error: “StartIndex cannot be less than zero”
- Object reference errors can occur on the webpages of Exchange users
- Saving scanned data of a large Office 365 environment to the Lansweeper database can take a long time
- Scan servers incorrectly handle software data sent by LsAgent installations on Linux computers, causing the software data not to be scanned
- The following object reference error can occur when scanning the shares of a Windows computer: “Error getting unique key in sql server via SELECT shareuniqueid FROM tblsharesuni”
- The “scanning your network” banner seen in the Assets menu after completing the First Run Wizard sometimes stays on screen longer than it should
- The Scan Time tab of a client machine scanned with LsAgent over the cloud relay server incorrectly indicates that a direct-to-server LsAgent scan occurred
- When scanning a Windows computer multiple times with the LsAgent or LsPush scanning agent, duplicate entries are generated for user-specific software found on the machine
- When scanning client machines with LsAgent over the cloud relay server, the LsAgent scan dates and versions in the ScanningLsAgent Scanning section of the web console are either blank or incorrect