Lansweeper
Key Info:
Lansweeper is an IT asset intelligence platform that discovers and inventories technology assets across an organisation. It brings device, software, network and cloud information into a shared inventory so IT teams can investigate estate changes, ownership and exposure with more complete context.
Details
Discovery and inventory coverage
Lansweeper is designed to collect asset information from connected environments and present it as an inventory. Coverage is the primary evaluation question: identify the networks, endpoints, cloud accounts, directories and systems that must be included, then measure what is discovered, what remains unknown and how duplicates are resolved. Test a newly connected device, a removed device and a deliberately incomplete credential scope.
Operational context
Asset records can be used for hardware, software, configuration and relationship investigation. Reports and dashboards help teams identify gaps, changes and items needing attention. The value of these outputs depends on asset identity and refresh rules, not just the number of collected records. Review timestamps, source attribution, conflict handling and retention before using the inventory for compliance or purchasing decisions.
Evaluation boundaries
Lansweeper can support IT asset management work, but it is not automatically the system of record for finance, service management or endpoint control. Establish how it connects to ticketing, security and configuration processes, who resolves exceptions and how corrected data is fed back. Validate roles, API scope, integration failure alerts, permissions, exports and the operational cost of maintaining discovery coverage.
Evaluation record
Document the approved asset scope, identity rules, required fields, operational owners, source systems, retention, integration boundaries, test exceptions and acceptance measures. Keep fields for pricing, customer size, languages, operating systems and apps blank unless a current official source maps them precisely to the BBS field. Run a time-boxed pilot with a representative asset sample, named data stewards and a written exception log. Compare user actions, audit trail and reports against the present process. At the end, decide whether the product can support the required control model, what configuration or integration work remains, and which measurable result would justify a full rollout. Keep the pilot evidence in a decision record that another administrator can replay, including sample source files, permission settings, expected reports, failure handling, sign-off owners and the plan for migration, training and post-launch review.