New capability - Track your hard-to-reach assets using IT Agent, the future of LsAgent

[Gilian]

Hi everyone!

Lansweeper is delighted to announce the availability of its new IT Agent in your Lansweeper Site. Track your hard-to-reach assets using the IT Agent which tracks the details of a single computer running Windows, Linux, or Apple MacOS and sends these directly to your Lansweeper Site.

How to access IT Agent in your Lansweeper Site

1. Open a browser and navigate to https://app.lansweeper.com.
2. Choose the Lansweeper Site to which you want to link the IT Agent Discovery. 
3. Go to Scanning > Discovery systems > Download installers/packages > IT Agent Discovery

A brief explanation

• Learn how to install/deploy IT Agent here.

• After a successful installation, the IT Agent(s) will be shown in your Lansweeper Site in Scanning > Discovery systems.

• To see the asset data, you can open Inventory > All assets (and you can use the search/advanced filter on the top right to filter on the specific assets/installation where IT Agent is running)

Product comparison

Lansweeper IT Agent vs LsAgent vs Network Discovery

Topic	Lansweeper IT Agent (Portable)	Lansweeper LsAgent	Lansweeper Network Discovery
Summary	Newest generation local tracking of any IT device running Windows, Linux or macOS device (including guest virtual machines and connected monitors)	Older generation local tracking of any IT device running Windows, Linux or macOS device (including guest virtual machines and connected monitors)	Discover all IT assets in your network. OT discovery will be added to the same installer/package later on
Asset reach	By default, local tracking only, no other network devices are discovered. This can be changed, but we recommend using Network Discovery for discovering network devices instead	Local tracking only, no other network devices are discovered. To discover network devices in combination with LsAgent, we recommend using Lansweeper On-Premise	Tracks both the machine running Network Discovery and discovers IT (and later OT) assets remotely
Asset data	Expanded default IT discovery data set (extra data like user info on macOS)	Default IT discovery data set	Expanded default IT (and later OT) discovery data set (extra data like user info on macOS)
Credentials	No credentials required for local tracking (runs as local system or similar elevated user by default). Credentials are optional for remote discovery but we advise to use Network Discovery for discovering network devices instead.	No credentials required for local tracking (runs as local system or similar elevated user by default).	Requires credentials to get all asset details remotely. Can recognize assets without credential though
Network access	Syncs with Lansweeper Site directly To sync with your Lansweeper Site, HTTP2 proxy is supported Check Install IT Agent Discovery - Lansweeper Community for connection requirements Send results to Network Discovery hub or to a file on a network drive for later import into Lansweeper Site. See Set up and run Lansweeper IT Agent Discovery Portable	Does not sync with Lansweeper Site directly HTTP2 proxy is not supported Requires a scan server to connect to (from a Lansweeper On-Premise installation). Can also connect first to Lansweeper LsAgent Relay server, see this link. Can save results to a file for import into Lansweeper On-Premise via scan server	Requires specific ports to be open on the assets to discover. See Ports scanned or used by Lansweeper To sync with your Lansweeper Site, HTTP2 proxy is supported
Auto update	Auto update on Windows, Linux and macOS	Auto update on Windows. Linux and macOS require manual updates	Auto update on Windows, Linux and macOS
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 (Windows) and .NET 6.0 (Linux, macOS)	Built on .NET 8.0 with a reduced vulnerability risk in comparison to .NET FW 4.8

Kind regards,

Gilian De Raes
Product Manager | Lansweeper

[Lee-TG]

I can confirm this behavior still exists with the latest IT Agent. A second issue, much larger problem, is the records do not merge. Everything can be the same (MAC, Serial, Hostname), only difference is the "Installation" and "Scan Server". This has been a real problem for us.

Besides the thousands of duplicates that need to be removed, we're no longer able to get the AD Scan information on the IT Agent records. 

Please fix this!

[Mercedes_O]

Thank you all for the incredible insights and contributions to this thread. With over 100 replies since it started, we’re closing it to new comments to keep things organized.

 If you have additional questions or new topics to discuss, please start a new topic here https://community.lansweeper.com/t5/product-discussions/bd-p/ProductConversations

We appreciate your engagement and look forward to seeing you in future discussions!