Lansweeper Review: IT Asset Discovery and Inventory

How this review was prepared: This is a research-based comparison of published vendor documentation and attributed third-party feedback. Toollers has not documented hands-on use of this product. Confirm current features, terms and pricing with the vendor before buying.

Lansweeper review: the problem it addresses

An organization may have computers in offices, VMs in a data center, cloud resources, remote employees, network switches and industrial devices with different owners and inventories. If there is no reliable central list, operations teams struggle to find an asset before a change, identify the owner of a vulnerable application or estimate hardware replacement costs. Lansweeper focuses on discovering those resources and keeping facts about them in a normalized inventory.

The Lansweeper listing on Toollers categorizes the product as IT asset management software. Its feature set spans discovery, inventory, lifecycle and vulnerability context, reporting and integrations. I am evaluating what the vendor documents and how that maps to typical ITAM workflows. I have not connected Lansweeper to a network, compared scanner results against a complete estate or measured its effect on incident resolution.

The critical distinction is between finding a device and completely understanding it. A passive network sensor might see traffic and infer that a machine exists, while credentialed active discovery can collect richer configuration and software information. An endpoint agent can reach a laptop that rarely appears on a company network. A cloud connector may discover resources invisible to a local network scan. Coverage comes from combining methods and maintaining the permissions to use them.

Active network discovery: identify what can be scanned

Lansweeper describes network discovery of servers, workstations, printers, routers and other devices. Active approaches use defined targets, protocols and authorized access to collect information. An infrastructure administrator may obtain operating-system versions, installed software, network interfaces, hardware identifiers and configuration attributes when devices respond appropriately.

Credentialed scanning offers deeper information, but it requires planning. A high-privilege shared credential increases risk; an incorrectly targeted or overly aggressive scan can disrupt a sensitive segment. A responsible trial starts with a small allowed IP range, documented scan accounts and scheduling that respects operational windows. The organization should check exactly what permissions are necessary for Windows, Linux, network gear and any specialized devices.

A discovery tool cannot collect what it cannot reach. Network segmentation, offline endpoints, disabled protocols, local firewalls and incorrect secrets can leave gaps. Lansweeper may report fewer assets than a procurement list not because devices are absent but because the collection topology is incomplete. A useful result includes a list of unknown or unreachable targets for investigation.

Passive discovery and credential-free recognition

The current vendor discovery page explains sensors that observe traffic, identifying devices as they communicate without contacting each device through a full active scan. It distinguishes detected assets from those recognized through fingerprinting and those fully profiled with credentials. This distinction is particularly useful in IoT or industrial networks, where scanning every device aggressively may be undesirable.

Passive visibility is not magic: a device that never produces traffic on the observed span may be missed, and metadata inferred from traffic may be incomplete or ambiguous. A switch mirror, sensor placement or other monitoring topology must be designed by network owners. For a hospital or factory, the security and operational teams should approve the passive collection location and any supplemental active probes.

I would verify both new-device detection and confidence in classification during a pilot. Put a known test device on a monitored segment, observe when it appears, check its manufacturer and model, and note what the system cannot determine. A responsible inventory retains uncertainty instead of silently filling gaps with unverified labels.

Coverage is more than a device count

A count of 4,000 assets can conceal serious blind spots if the estate actually contains 5,000 devices or if hundreds are known only as unknown network nodes. Compare Lansweeper’s output with DHCP, switching, hypervisor, cloud and purchasing records, then classify findings as confirmed, duplicate, stale or unresolved.

The vendor describes IP range coverage and asset recognition states. Use those to understand where the network has not been fully observed. This is more actionable than treating a large asset total as proof that the environment has complete visibility.

Remote endpoints and the IT Agent

Traditional network discovery has difficulty with work-from-home laptops that rarely reconnect to a company segment. Lansweeper’s IT Agent can collect inventory directly from authorized endpoints, including supported Windows, macOS and Linux devices, so the platform can continue receiving relevant facts even when traditional reachability is limited.

That approach introduces software deployment and maintenance work. An endpoint team must install the agent through an approved management process, handle version updates, monitor failures and remove the agent when a device leaves the organization. The inventory owner should know which devices use agents and which are scanned over the network to avoid duplicate records or inconsistent freshness expectations.

A good pilot includes a laptop that stays off the VPN for several days. Check whether inventory updates when expected, whether asset identity reconciles with the same laptop’s earlier network scan and what information is unavailable because of local OS permissions. This is a concrete test of remote estate coverage, not an assumption based on an agent feature badge.

Cloud and virtual infrastructure discovery

Lansweeper supports cloud discovery through connectors to providers such as AWS, Azure and Google Cloud, subject to product and account configuration. It can collect information about eligible workloads and related technology resources through supported APIs. Virtual environments and cloud resources can be highly dynamic, so an accurate inventory needs more than a once-a-month spreadsheet export.

The administrator should grant read access as narrowly as possible, document which accounts and subscriptions are in scope, and test reconciliation across regions. Some resources appear only as components of another billable asset. The subscription definition counts distinct managed workloads differently from sub-resources such as attached disks or network interfaces, so cloud inventory design has both technical and pricing effects.

Cloud discovery is not cloud security posture management by default. An asset list helps identify what exists; separate controls may be needed to assess misconfigurations, network exposure or exploitability. Confirm which Lansweeper fields are sourced from a connector and when they were last synchronized.

OT and IoT discovery in sensitive environments

The vendor specifically describes OT and IoT discovery capabilities for industrial and segmented environments. Asset identification can help operations teams document devices that cannot run ordinary endpoint agents, including some controllers and specialized networked equipment. Passive sensing and careful network placement may be preferable to active interrogation of fragile production equipment.

A maintenance department should not simply reuse corporate IT scanning credentials and settings in an industrial control segment. Work with the plant network and safety teams to decide which protocols, collection locations and scan frequencies are approved. Confirm how a device is classified when passive observation has incomplete data, and whether unsupported device types appear as unknown rather than absent.

The value of the inventory is stronger when it includes owner, location, service dependency and lifecycle information. These may need human validation or enrichment from another source. Asset discovery can supply evidence for a risk review, but does not authorize changes to production controllers.

Normalization, duplicate records and asset relationships

Lansweeper’s inventory aims to reconcile observations from different sources into one asset record. The official discovery page describes matching identifiers including serial number, MAC address and hostname while avoiding reliance on a changing IP address alone. That is useful when a laptop moves between networks or a device is observed by both an agent and a network sensor.

Reconciliation errors remain possible. A reused hostname, missing serial number, reconfigured NIC or ephemeral VM can cause ambiguity. An administrator should inspect duplicates and stale records rather than assume the platform has perfect identity resolution. Establish rules for record ownership, retirement and confidence; log manual merges or corrections where the product supports them.

Relationship diagrams can help visualize connections and virtual infrastructure, but a diagram inferred from inventory is only as trustworthy as its sources. Service owners should validate relationships before using them to approve a high-risk maintenance change. Where the company already has a CMDB, decide which system is authoritative for hardware facts, business services and application ownership.

Vulnerability and lifecycle insights: useful, with limits

Pro and Enterprise include vulnerability and lifecycle insights under the current pricing plan. That can help identify software or hardware reaching end of support and surface relevant published vulnerability data associated with installed products. Security teams may use those signals to prioritize manual review or request a patch from their existing tools.

A match between a product version and a public advisory does not prove that an asset is exploitable in its actual configuration. Conversely, missing insight is not proof of safety. The team should verify patch level, compensating controls, actual software use and asset criticality through established security tools and owners. Lansweeper should feed prioritization, not replace a vulnerability scanner or patch deployment solution.

For lifecycle decisions, enrich the technical end-of-support date with business owner, replacement cost, application dependencies and maintenance window. If those fields are incomplete, the inventory may identify old software without providing enough context to approve retirement. The operational workflow still needs people.

Reporting, service desk links and APIs

The platform lists dashboards, a report builder, exports and an integration marketplace. For an IT asset owner, a useful report may identify unassigned laptops or machines with old operating systems. A procurement department may need warranty and model information. A service desk may want a ticket to show the asset’s technical attributes when a user reports a failure.

Starter includes service-desk ticket enrichment, while Pro opens the full marketplace app library according to the current plan comparison. Enterprise adds full API and webhook access; the table describes Starter and Pro API use as proof-of-concept limited. An organization intending to run a production data pipeline should obtain written clarification rather than assuming that every integrations menu option grants unrestricted automation.

A good integration pilot should define the source of truth. If Lansweeper discovers a hostname while the CMDB holds an asset owner, decide which field wins and what happens after a device is retired. Otherwise, automated synchronization can copy inaccurate information faster than manual processes.

Security and administrative permissions

An asset inventory contains sensitive details about network devices, operating systems and software exposure. Lansweeper’s feature grid lists SSO, MFA, advanced permissions and asset scopes. The security team should determine who can view full asset information, export datasets, change discovery credentials and create integrations. A universal read-only role may still reveal data that should be restricted to certain business units.

Avoid storing broad domain administrator credentials where a narrower scanning account will work. Review supported authentication methods and how secrets are rotated. Collectors should be deployed in authorized network segments with documented access paths; cloud API permissions should be limited to required resources. The right technical setup depends on the organization’s network and identity architecture.

These controls are prerequisites for a safe inventory, but a website feature list does not constitute a security audit. Obtain current contract/security documentation and test administrative role enforcement in a nonproduction environment if regulatory requirements apply.

Pricing, fit and editorial limitations

The Free tier supports a 14-day full-access trial followed by up to 100 assets. Starter begins at $245 per month equivalent, about $2,940 annually for 2,000 included assets; Pro starts at $449, about $5,388 annually, with expansion toward 9,000 assets. Enterprise begins at 10,000 and requires a custom annual quote. All plans list unlimited users, so assets and functionality, not ordinary seat count, determine the initial purchase.

These rates make Lansweeper a substantial purchase for a small company that only needs a manual sign-out ledger. They may be more reasonable for an organization where discovery is difficult, inventory quality affects security operations or several teams need a common asset record. Measure the time currently spent reconciling devices and the cost of unidentified assets rather than evaluating only the first-year subscription.

Toollers’ current Lansweeper editorial rating is 4.1/5 and is marked research-based. It has not been established through an independent estate scan or production configuration. This review preserves the limitations: no measured recall/precision for discovery, no verified network performance impact and no independent vulnerability validation.

A reproducible Lansweeper evaluation plan

Create a known test set: ten Windows laptops, three Linux machines, two network devices, a pair of VMs and one approved cloud resource, or a smaller equivalent. Record each device’s true hardware ID, software state and ownership in a protected baseline. Configure Lansweeper only for authorized discovery routes and approved credentials. Compare detected devices, recognized types and fully profiled records against this baseline.

Measure what is missing and why. Did a laptop report through the agent when off-network? Was a switch identified only through passive traffic? Did cloud inventory import a resource from the correct account? Are duplicates reconciled when the same VM is observed twice? An asset known to be present but missing from the platform should be recorded as a false negative in that test, not ignored because the dashboard looks complete.

Then apply a limited privilege role and attempt an export from an unauthorized user. Create a service-desk enrichment test and verify source attribution and refresh timing. Finally, calculate the actual billable asset count, including manually created resources, and request the correct yearly band. These results will show whether Lansweeper fits your architecture more convincingly than a broad product description.

Lansweeper review FAQs

Continue reading about Lansweeper

• Lansweeper Pricing: Free, Starter, Pro and Enterprise
• 7 Best Lansweeper Alternatives for IT Asset Management