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

[Gilian]

@eputz 

Our development team has corrected the incorrect asset type "mobile" for Windows 10 Education devices. During a next scan, your assets should receive the Windows asset type once again.

[eputz]

@Gilian  - Hi Gilian , we're still seeing Windows Computers being incorrectly classed as mobile devices. Do you need any further information from us to troubleshoot as we have 340+ incorrectly showing as Asset Type - Mobile? 

[avillarreal]

By the way... In the case of Windows Business it's considering as a Server, not as Workstations:

Thanks!

[Gilian]

@avillarreal thanks for sharing. I'll report this to our development team to correct the type in case of Windows Business.

Edit: where are you seeing "Server" in your Lansweeper site?

[avillarreal]

Hello @Gilian ,

On the assets screen:

It shown as 466 servers. 

Thanks!

[Gilian]

@avillarreal I'll report this as a bug as it affects all LS Sites. Thanks for mentioning

[Gilian]

@eputz , +2K devices using IT Agent? That's great news! We did notice a solid increase in the number of IT Agents lately and now we know why ;-). 

Seems like a bug as the asset type shouldn't be changed if IT Agent detected a "Windows" device. I already contacted our development teams so we can have this resolved. Thanks to auto update they would be automatically set to Windows.

For any other asset type, you could resolve this manually using inventory > assets > selecting multiple assets > clicking the bulk edit button on the top > setting the new asset type and clicking the lock icon (to never overwrite this value), but you can't do this for the Windows asset type.

[avillarreal]

Did someone face and error about the IT Agent get a "Forbidden" code on the installations? I'm getting this error and I can't find the root cause, the TLS 1.2 is enabled, direct connection to the server works, it previously works on a few clients and now they don't appear online even that they were connected once and after that there is no activity and I can't make it work again, restart services or the entire computer don't solve the issue.

-------------------
Something went wrong while creating the installation.
System.InvalidOperationException: Result is in status failed. Value is not set. Having: Error with Message='ConfigApiClient Request linking/CreateInstallationAndLink failed with status code Forbidden'
at FluentResults.Result`1.ThrowIfFailed()
at FluentResults.Result`1.get_Value()
at Lansweeper.Discovery.Hub.Application.Linking.Cloud.AutolinkToCloudConsumer..MoveNext()

[Gilian]

@avillarreal 

This is a bug in the IT Agent which we've already fixed but is still being tested as we speak. Expect to have release with a fix available in your LS Site (Scanning > Discovery sources > Download) soon.

Meanwhile you could try this:

* Remove any cloudtoken.txt file from your IT Agent installation directory

* Restart the IT Agent installer (with a new linking code from your LS Site > Scanning > Discovery Sources > Link Discovery source)

[ryf]

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

WHAT?!