New preview 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, now in Preview. 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 Network Discovery vs Lansweeper IT Agent (Portable) Discovery

Topic	Lansweeper IT Agent	Lansweeper LsAgent
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)
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
Asset data	Expanded default IT discovery data set (extra data like user info on macOS)	Default IT discovery data set
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).
Network access	Syncs with Lansweeper Site directly To sync with your Lansweeper Site, HTTP2 proxy is supported Check Install Network Discovery - Lansweeper Community for connection requirements Not available yet: Send results to Network Discovery hub or to a file on a network drive for later import into Lansweeper Site	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
Auto update	Auto update on Windows, Linux and macOS	Auto update on Windows. Linux and macOS require manual updates
Vulnerability risks	Built on .NET 8.0	Built on .NET FW 4.8 (Windows) and .NET 6.0 (Linux, macOS)

Request for feedback

It's time for us to let you try and test this new feature. We hope this first version will give you an easy-to-deploy agent-based discovery.

Finally, we're all ears! Your feedback is valuable, and we'd love to hear it.

Feel free to share in the comments or share your logs and screenshots privately to preview@lansweeper.com

Kind regards,

Gilian De Raes
Product Manager | Lansweeper

[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?

[Gilian]

@ryf 

We've extended the linking code duration so you can now choose how long a single linking code should remain valid (1 day, 1 month, 3 months, ...)

Go to Scanning > Discovery sources > Link discovery source. Select Create new code, set an expiration and select Copy code.

[SimonJuulLarsen]

Another issue is that devices with IT-asset installed results in a lot of notifications when they go offline / come online again.

It would be nice if these messages could be supressed/ignored/excluded.

[Gilian]

Hi @SimonJuulLarsen ,

Thanks for mentioning. We're going to exclude the IT Agents from those system notifications so we only focus on scan servers there.

[SimonJuulLarsen]

When planning for remote / push installation of the IT Agent, it doesn't make sense that the Cloud Linking Code is only valid for 24 hours.

That means you have to update your deployment script every day.

Please consider the option of creating Linking Codes with a customized expiry date for this purpose.

Also, when the installer fails because of an expired linking code, no usable return codes / error messages are sent back.

[Gilian]

@SimonJuulLarsen 

We've extended the linking code duration so you can now choose how long a single linking code should remain valid (1 day, 1 month, 3 months, ...)

Go to Scanning > Discovery sources > Link discovery source. Select Create new code, set an expiration and select Copy code.

[Gilian]

Hi @SimonJuulLarsen , we are indeed adding the option to set an expiration timing of your personal choice for the linking code to your Lansweeper Site. Our development team is currently reviewing their solution so it keeps ensuring a secure way to have new data entering your Lansweeper Site. We expect to have this solution implemented soon. Until then, a linking code expires every 24h.

The installer does return specific exit codes and error messages which I now added above, in the FAQ section of the original post.

[MilesFromHome]

Any chance we could get a walk-through for Intune Deployment like this article specifically for IT Agent? I followed similar steps with IT Agent, and i must be missing something with the install command or somewhere else along the line.

[Gilian]

Thanks for the suggestion. I'll ask my colleague Esben if he can make a similar article for IT Agent.
The install command should be the one mentioned in method 2:

1. Lansweeper-IT-agent-discovery-X.X.X-windows-x64-installer.exe --mode unattended --accepteula 1 --path "C:\Program Files\Lansweeper IT Agent Discovery" --cloudtoken cloudtokenvalue

[ndeering]

I'm also having trouble trying to get the IT Agent deployed via Intune, I've tried used the script section in Intune, also trying to package the app as WIN32 app to no success. The error when trying to do it via WIN32 app is pointing to an error in the install command. "The system cannot find the file specified. (0x80070002)"

My Install command for the WIN32 app is the one you pasted above, (with my details and version.)