Om de apparaten in je netwerk in kaart te brengen, kun je gebruikmaken van Lansweeper. Dit programma werkt op een Windows-machine en is in staat om de aanwezige software en hardware te inventariseren in het netwerk, zonder dat daarvoor op elke computer een clientprogramma moet worden geïnstalleerd. Alle informatie is vervolgens via een webinterface te raadplegen. Lansweeper is beschikbaar als freeware voor kleine omgevingen, maar voor grotere omgevingen zal betaald moeten worden. Vanaf versie 10.4 wordt standaard de cloudversie geïnstalleerd. Wil je een lokale installatie, dan kun je deze instructies volgen. In de afgelopen paar versies zijn de volgende veranderingen en verbeteringen aangebracht:
Lansweeper 12.0.0.10, LsPush 8.4.100.1, LsAgent Windows 11.4.1.2, SQL 1010Lansweeper 11.4.1.9, LsPush 8.4.100.1, LsAgent Windows 11.4.1.2, SQL 1010
- Changed: LAN-16709 The Lansweeper Scanning service has been upgraded to .NET Core 8.
- Fixed: LAN-15279 Office365V2 scanning would randomly fail without an error.
Lansweeper 11.4.1.4, LsPush 8.4.100.1, LsAgent Windows 11.1.10.0, SQL 1010
- Fixed: LAN-16840 A security issue was fixed.
Lansweeper 11.4.1.2, LsPush 8.4.100.1, LsAgent Windows 11.1.10.0, SQL 1010
- Fixed: ACME-22672 Asset lifecycle information was missing for new installations.
- Fixed: LAN-16759 The helpdesk mail connection would fail when app.lansweeper.com was blocked.
Lansweeper 11.4.0.4, LsPush 8.4.100.1, LsAgent Windows 11.1.10.0, SQL 1000
- Changed: LAN-16712 The “OS: Not latest Build” reports will no longer show extended support data.
- Fixed: LAN-16721 Deployments and helpdesk mailing would fail if app.lansweeper.com was blocked.
- Fixed: LAN-16730 Updates to triggers on tsysasservers would throw errors.
- 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.
:fill(white):strip_exif()/i/2002730316.jpeg?f=thumbmedium)
/u/1957000/crop66602807e34a1_cropped.png?f=community){kind=small}
:strip_icc():strip_exif()/u/12330/dnangel_70.jpg?f=community){kind=small}