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

[eputz]

@Gilian - Hi Gilian, we're also seeing issues with AV being incorrectly marked as disabled - example in screenshot below

[Gilian]

Hi @eputz , thanks for sharing the screenshot.

I've added it to the issue where our development team is already investigating the similar antivirus issue for Cisco Secure Endpoint

[eputz]

Thanks @Gilian  - any update on the Asset Type being incorrectly identified as 'Mobile' rather than Windows? e.g. do we need to be using a newer installer package and if so what will happen for existing deployments as the number of devices classified as Mobile is still growing rather than reducing?

[Gilian]

@eputz Not yet, investigations are ongoing.

edit: meanwhile the asset type of remaining Windows assets (mostly from brand Asus) have also been corrected. Can you do a rescan and see if the type has been corrected? The last scan attempt and last succesful dates should be updated (so we know the new asset type could be applied)

[avillarreal]

Hello @Gilian,

Is there a way to "relink" a computer that was removed from the scanning targets? or do I need to do a reinstall and remove the asset from the console?? 

It happens to me that on my test computer I install/uninstall several times the client... but it was added several times on the scanning targets page, so I delete them, but it didn't appear again after a reinstall... Any idea?

[Gilian]

@avillarreal ,

@avillarreal In Scanning > Discovery sources, you'll see a row for each time you install the client/IT Agent.
If you remove the source, the asset will still remain in your inventory.
During this preview phase, you could remove the asset(s) from your inventory, reinstall the IT Agent client and see a new record in Scanning > Discovery sources and in Inventory > Assets

Once the reconciliation engine is more finalized, these multiple asset records in your inventory will be merged into 1 and you'll see which of the sources brought in the data at what time.

The assets from deleted sources, can be found in your inventory, having the "unlinked" icon in the first columns

[avillarreal]

The weird thing is that it doesn't appear on the scanning targets... But on the computer (even after I manually delete the assets and check that there wasn't on the scanning agents was marked as if there was another installation there:

Let me know if you need any information about it.

[Gilian]

@avillarreal IT Agents are visible in Scanning > Discovery sources, not in scanning targets. The instruction when the scanning should happen is configured in Scanning > Discovery actions

[avillarreal]

@Gilian Correct, but it's not shown at that part either... It appears on the inventory, but not on the discovery sources... But from yesterday until now is still not shown... The number of current sources wasn't changed from yesterday...

I just try a resync and no luck either 😞 

[Gilian]

@avillarreal 
As it's from a test machine, could you try:

* Removing all related assets of MXRA-PF3DWCG6
* Removing all discovery sources of MXRA-PF3DWCG6
* Generating a new discovery source linking code (scanning > discovery sources > link discovery source)
* Downloading the IT Agent installer (scanning > discovery sources > download installer)
* Uninstalling IT Agent on MXRA-PF3DWCG6
* Installing IT Agent on MXRA-PF3DWCG6 using the new linking code

[avillarreal]

Already did all those steps... But seems it's leaving something behind... I remove the client... and I can't remove the discovery sources as they are not shown there... remove the entire asset... I clear the registry from the computer too install the client using a fresh code... and registers again... but it still shows that it was added on December... even that it wasn't found before I try to add it back.

[avillarreal]

Hello @Gilian,

After a few days the computer on the "Discovery sources" appeared and I was able to remove it and clear everything from the computer and add it back with a fresh code... But I saw something that I don't understand why is marked that way:

Its setting the computer on de default group but with the "Network Visibility Disabled" and still waiting if after a few hours gets refreshed everything on that computer...

Any suggestions? 

Thanks!

[Gilian]

@avillarreal 

Groups is still in the works. All IT Agents belong to the same "Default Group" for now. The secondary "Default Group (Network Visibility Disabled)" should remain behind the scenes and will be hidden soon. Once we have groups finished, you'll be able to choose to which group your IT Agent belongs to (to configure for instance the maintenance window or proxy settings in bulk). We're currently investigating an issue with the refresh of the data

[CloudFire]

Hi,
I've installed the IT Agent on several MacOS and Windows devices, but the date of the last scan attempt on all of those is when the agent was installed. Does the 24h rescan really work? I've also edited the default rescan time to "every 4h", but nothing has changed. 
I know that I can force it using APIs, but I can't implement them right now. 

Thanks!