cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Hi everyone!

Lansweeper is delighted to announce the availability of its new Network Discovery in your Lansweeper Site. Discover more details of your assets remotely with Network Discovery, now available on Windows, Linux and macOS with auto update on all platforms.

 

How to access Network Discovery in your Lansweeper Site

A brief explanation

  • Learn how to install/deploy Network Discovery here.

  • If you chose to link your Network Discovery with your Lansweeper Site, it will be shown in Scanning > Discovery systems.

  • To see the assets your Network Discovery brought in, you can check Inventory > All assets. You can also use Inventory > Installations > %Name of the Network Discovery Hub% to filter on the assets of a specific installation. Some data might still be missing we’re continuously mapping and expanding our global data model.

Product comparison

Lansweeper Network Discovery vs Lansweeper On-premises

Topic Network Discovery Lansweeper On-premises

Summary

Discover all IT and OT assets in your network and access them in a cloud based inventory in your Lansweeper Site.

Discover all IT assets in your network and access them in an on- premises based inventory, with an optional extended cloud based inventory in your Lansweeper Site.

Asset reach

Tracks both the machine running Network Discovery and discovers IT and OT assets remotely

Tracks both the machine running Network Discovery and discovers IT assets remotely

Asset data

Expanded default IT (and later OT) discovery data set (extra data like user info on macOS)

Default IT discovery data set

Asset inventory

Located in Cloud via Lansweeper Site (mandatory).
Discovery results are stored in a cache in the hub which sends these to your Lansweeper Site where they are converted into inventory assets.

Located in on-premises and optionally via Lansweeper Site.
Inventory assets are saved in an on-premises SQL database, optionally synced by the sync server to your Lansweeper Site for cloud based access.

Credentials

Requires credentials to get all asset details remotely. Can recognize assets without credential though

Requires credentials to get all asset details remotely. Can recognize assets without credential though

Network access

Auto update

Yes, on Windows, Linux and macOS

No, manual update

Vulnerability risks

Built on .NET 8.0 with a reduced vulnerability risk in comparison to .NET FW 4.8

Built on .NET FW 4.8 with a higher vulnerability risk in comparison to .NET 8.0

Depending on your situation and your needs, you may want to install a specific discovery system, or perhaps a combination of multiple discovery systems.
For a full comparison of their capabilities, check out Comparing Lansweeper Sites and Lansweeper On-premises, which provides more information to aid you in your decision.

Lansweeper Network Discovery vs Lansweeper IT Agent (Portable) Discovery

Topic

Summary

Discover all IT (and later OT) assets in your network

Get all details of the computers you know that have IT Agent Discovery installed and running as a background service or daemon.

Planned, not available yet. Get all details of the computers on which you run IT Agent as a foreground application. Ideal to be included in a logon script

Asset reach

Tracks both the machine running Network Discovery and discovers IT (and later OT) assets remotely

Local computer tracking where the IT Agent Discovery is running

Local computer tracking where the IT Agent Discovery is running

Credentials

Requires credentials to get all asset details remotely

Does not require credentials

Does not require credentials

Network access

Requires specific ports to be open on the assets to discover. See 

Few connectivity requirements. See 

A connection to a Lansweeper Network Discovery - Hub component or a location to store the discovery result file in, for later import.

 

Lansweeper Network Discovery architecture

2025-02-10-Deployment-Architecture-Diagram-01.png

 

Lansweeper Network Discovery components

Component

Deployment Type

Description

Deployment Notes

Owner

Location

Hub

  • Lansweeper Discovery (Cloud-Native)

The Main Component of Lansweeper discovery is the Hub, Which is the central point of communication with the data collector (IT Sensor) and the Lansweeper Data Platform. This follows the standard hub-and-spoke architecture pattern.

Contains

  • Data Storage Cache: A local temporary storage service to enable data transfer

  • Local Web Console: A primary management console that can be enabled to aid debugging.

A single hub can support multiple IT/OT Scanners; however, to cover a full enterprise-level network, multiple hubs may be required.

Supported OS

  • Windows

  • Mac

  • Linux

Typical Hosting

  • Server (virtual or physical)

Client Deployed

Client Network

IT Sensor

  • Lansweeper Discovery (Cloud-Native)

The Lansweeper agentless discovery collection element, the IT Sensor(s) collects asset data and sends it to the Hub - this follows the std Hub and Spoke architecture pattern.

The IT Sensor is a lightweight ‘spoke’ component, and many may be deployed across the network, directed back at a single hub server.

Supported OS

  • Windows

  • Mac

  • Linux

Typical Hosting

  • Server (virtual or physical)

Client Deployed

Client Network

OT Sensor

  • Lansweeper Discovery (Cloud-Native)

IT Sensor' OT sibling, the OT Scanner(s), collects asset data and sends it to the Hub—this follows the standard hub-and-spoke architecture pattern.

The OT Sensor is a lightweight ‘spoke’ component, and many may be deployed across the network, directed back at a single hub server.

Supported OS

  • Windows

  • Linux

Typical Hosting

  • Server (virtual or physical)

Client Deployed

Client Network

IT Agent

  • Lansweeper Discovery (Cloud-Native)

Miniature version of the full agentless Discovery

Contains.

  • Hub

  • IT Scanner

  • Local Cache: A local temporary storage service to enable data transfer

  • Web Console: A basic management console that can be enabled to aid debugging.

Designed to be deployed to end-user devices for clients with restrictions on agentless scanning or who have many mobile/home workers.

Supported OS

  • Windows

  • Mac

  • Linux

Typical Hosting

  • End User Devices

Client Deployed

Client Location Dependant

Kind regards,

Gilian De Raes
Product Manager | Lansweeper

 
11 Comments

About the author

Product Team
54 99 6

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now