Software Update: Lansweeper 7.0.100.5

To map the devices in your network, you can use Lansweeper. This program installs itself on a Windows server with IIS and a sql database, and is able to inventory the software and hardware present in the network without having to install a client program on each computer. All information can then be consulted via a web interface. Lansweeper is available as freeware for small environments and for larger environments you will have to pay. The developer has released version 7.0.100.5 with the following changes:

Version 7.0.100.5, LsPush 6.0.100.32, LsAgent 7.0.100.1, SQL 162

• Added: LAN-1451 Added a built-in package for deploying LsAgent on Windows computers under Deployment\Installer Packages
• Added: LAN-1228 Added options for testing custom SNMP OID scanning to the Devicetester tool
• Added: LAN-1273 Citrix credentials can now be submitted in the Devicetester tool for testing Citrix XenServer scanning
• Added: LAN-1272 vCenter credentials can now be submitted in the Devicetester tool for testing vCenter scanning
• Changed: LAN-1341 LsAgent installations now connect to alias relay.lansweeper.com when contacting the relay server
• Fixed: LAN-1312 Browsing to the LsAgent page under the listen port of a scanning server crashes the Lansweeper Server service
• Fixed: LAN-1332 Due to the use of custom password boxes throughout the web console, password manager tools fail to save or auto complete Lansweeper passwords
• Fixed: LAN-1484 Excessive entries added to the credential delegation group policies of scanning servers by the Lansweeper Server service
• Fixed: LAN-1286 Exporting data to Universal Inventory using LsExport fails, with a “column name is not valid” error
• Fixed: LAN-1395 If connecting to the relay server fails, due to an Internet access issue for instance, the Scanning\Cloud Relay Configuration page keeps showing a connection attempt and never throws an error
• Fixed: LAN-1583 If disabling the relay server fails, due to a firewall issue for instance, the Lansweeper Server service never stops processing the attempt and other service functions like deployments fail to run
• Fixed: LAN-1269 It is theoretically possible for users without the Access Configuration permission to submit a Lansweeper license key in the web console
• Fixed: LAN-1673 Newer chassis types are missing from the TsysChassisTypes database table, causing chassis display issues for Windows computers
• Fixed: LAN-1310 Several executables in Program Files (x86)\Lansweeper subfolders are not digitally signed
• Fixed: LAN-1365 Software license keys found on Windows computers are sometimes incorrectly scanned by the LsAgent scanning agent
• Fixed: LAN-1579 The ifconfig command used while scanning Linux computers is called as root when it doesn’t need to be
• Added: LAN-1305 The PowerShell Data tab of Exchange Servers now indicates when Exchange data was last scanned and a wait time for PowerShell is now available under the Scanning\Scanned Item Interval menu
• Fixed: LAN-1345 The Scanned OIDs tab for listing custom SNMP data is displayed on webpages of assets that don’t have SNMP enabled
• Fixed: LAN-1294 The start IP address of auto filled IP ranges in the First Run Wizard is sometimes higher than the end IP
• Fixed: LAN-1394 The tblLsAgentRelayConfig database table that stores relay server settings is visible in the report builder when it should be hidden from view
• Fixed: LAN-1348 The vCenter datastores report found in the Reports menu has no results even when there are scanned datastores
• Fixed: LAN-1670 Typo in the word “synchronization” under Scanning\Cloud Relay Configuration when using multiple scanning servers
• Fixed: LAN-1317 Unclear error message when submitting an invalid relay authentication key in the LsAgent installer
• Fixed: LAN-1405 Unhandled exception errors can occur when attempting to move the Lansweeper database from SQL Compact to SQL Server using the CompactToServer tool
• Fixed: LAN-1710 Unwanted evaluation message in the first screen of the LsAgent installer
• Fixed: LAN-1230 VMware guests sometimes fail to be cleaned up by enabled asset cleanup options found under Configuration\Server Options
• Fixed: LAN-1300 “VMware” is inconsistently capitalized throughout the web console
• Fixed: LAN-1321 When attempting to add an asset to a relation or location map, the asset list fails to load
• Fixed: LAN-1393 When attempting to delete the scanning server that is used for cloud relay synchronization, the deletion silently fails without a warning message
• Fixed: LAN-1639 When scanning ESX or vCenter servers with shared datastores, no vCenter data is returned and a “multiplicity constraint violated” error is logged in Program Files (x86)\Lansweeper\Service\Errorlog.txt on the Lansweeper server
• Fixed: LAN-1287 When using a Lansweeper license limited in number of assets and reaching the licensed asset limit, users without the Access Configuration permission also see the warning popup even though they shouldn’t
• Fixed: LAN-1675 When using certain Lansweeper licenses and updating to Lansweeper 7.0, some previously scanned ESX/VMware server data is hidden from view
• Fixed: LAN-1406 Windows OS build and version number are not scanned when using the LsAgent scanning agent
• Fixed: LAN-1293 Word wrap issue in scanning errors displayed in the Summary tab of asset webpages