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

[eputz]

@Gilian - Hi Gilian, any update on:

• the linking code expiration works
• asset types incorrectly identified as 'mobile' instead of windows (still have 350 showing as mobile)

Thanks for your help.

Ebe

[Gilian]

Hi @eputz ,
Our development/security team is still working on the extended duration of the linking code.
Can you rescan and recheck the asset types of the "mobile" devices? They should now report back as Windows devices according to our development team.

[eputz]

Hi @Gilian , apologies if I'm missing something but I thought the IT Agent default behaviour is to undertake a scan every 24 hours or is there a different scan I'd be initiating?

[eputz]

@Gilian  - following up on the rescan, I can't bulk select devices to initiate this but going back to the default scan interval,  if I export the LANSweeper Site data and filter on last scan date, worryingly of approx. 2800 devices - most of which were installed prior to March 2024, only 140  of them have a last scanning date withing March 2024 and at least 1000+ would have been in use during March so is the scanning date in cloud console supposed to be updating? If so does this mean that most of our IT Agent installs are no longer talking  to LANSweeper? The only changes we've been making  is to regularly update the linking code due to the 24 hour timeouts.

[jsutherland125]

We are trying to deploy the IT agent via Intune to our assets in the field. It seems that the token expires in 24 hours and after that installations fail. Is this expected behavior? If so, is there a method to deploy this agent?

Edit: I see this is expected (it obviously tells you that when getting the token), however, is there a preferred method to use to deploy the agent via Intune or any other deployment service that relies on device check-in that may not occur in the same day?

[avillarreal]

As the last that @Gilian comment on earlier post, the developer team is working on a way to achieve this, there are many as you and me that are waiting for that to complete... The only option that I found that could help you is to target computers specific that doesn't have the client already installed and change it every day... Seems a lot of work... Yeap... But probably until it gets addressed on a later release is the only option.

[ninjalee]

How do you resolve duplicates? We have the IT Agent installed on all our machines and Server Scan running. We want to keep the asset scanned by the IT Agent. Is it possible to merge the assets?

[Gilian]

@ninjalee 

These should show up in inventory > duplicate conflicts so you can manually merge them in bulk. However there seems to be a bug so the IT Agent assets are no longer included here. I created an internal issue so we can resolve this. As soon as it's fixed, you'll be able to merge the assets. Later on, once the reconciliation engine's ready, this will be done automatically based on your preferences set in your Lansweeper Site.

[CloudFire]

Hi @Gilian, could you give us a feedback?

Thanks!

[Gilian]

Hi @CloudFire 
We released a new version 0.15.7 today which you can download here:

https://download.lansweeper.com/stable/windows/it-agent-discovery/latest,
https://download.lansweeper.com/stable/MAC/it-agent-discovery-dmg/latest,
https://download.lansweeper.com/stable/MAC/it-agent-discovery-pkg/latest

These should already resolve most scenarios but our team is still working out on resolving the last ones for which a new patch version will be made available soon.

[eputz]

@Gilian My Windows computer downloaded the 0.15.7 version yesterday lunchtime but following restarts appears to have not updated the running version which is still 0.15.2 - should it have auto-updated in light of the download? 

[eputz]

@Gilian - following up on Tuesday we can report that we're now seeing ITAgents auto-update to 0.15.7 and now hoping that scan dates and scan information will start updating in our cloud site soon.

[Gilian]

@eputz thanks for sharing. Meanwhile the team is working on a newer patch version which will contain a fix for the last scenarios where the data isn't being refreshed. Hopefully 0.15.7 does already cover yours and keeps updating the asset data. Otherwise could you let us know and share a log file ("C:\Program Files\Lansweeper IT Agent Discovery\sensor\logs\Lansweeper.IT.Hub.log") of your IT agent to preview@lansweeper.com ?

[ryf]

The installation fails and it cleans itself, so there is no cloudtoken.txt to remove

I have attempted what you suggested (new linking code). What other suggestions do you have, or do you have a timeline for this fix? This has more or less rendered our license unusable as what good is this app if we cannot deploy it?

[ryf]

Ignore my other comment, I see the linking code has a lifetime of 24hours. 

WHAT?!