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 Network Discovery	Lansweeper IT Agent Discovery	Lansweeper IT Agent Portable Discovery
Summary	Discover all IT (and later OT) assets in your network	Get all details of the computers you know that have IT Agent Discovery installed and running as a background service or daemon.	Planned, not available yet. Get all details of the computers on which you run IT Agent as a foreground application. Ideal to be included in a logon script
Asset reach	Tracks both the machine running Network Discovery and discovers IT (and later OT) assets remotely	Local computer tracking where the IT Agent Discovery is running	Local computer tracking where the IT Agent Discovery is running
Credentials	Requires credentials to get all asset details remotely	Does not require credentials	Does not require credentials
Network access	Requires specific ports to be open on the assets to discover. See Ports scanned or used by Lansweeper	Few connectivity requirements. See Install IT Agent	An encryption key from a Lansweeper Network Discovery - Hub component. Either direct access to the hub or a location to store the discovery result file in, for later import.

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

[Artichoke]

Could the Change Log please be updated? The last update was "March 28th, 2023" for "0.15.8 Network Discovery Windows, Linux, macOS". The current version for download is labeled "0.16.1" and I have "0.17.3" reporting for some of my Windows Agents.

Thanks.Peet

[Gilian]

Hi @Artichoke ,

Thanks for mentioning. We've also noticed there are some issues with the changelog and versioning of IT Agent. This will be updated soon. Last version is indeed 0.17.3 using https://download.lansweeper.com/stable/windows/it-agent-discovery/latest. We'll update the download page too

[Artichoke]

What am I missing? 

I've deployed both the macOS and Windows Client on two separate tenants. In both tenants, I can see "DISCOVERY SOURCES -> Agent-Based -> *agent names with 'Up' status". But in neither case do I have any information collected by the agent. (it's been more than 24hrs).  

In one tenant, I have three agents that are all on computers that do not have scan credentials on the local LS server. All information those records have is from the incomplete network scan. 

In the other tenant, I have two records, both Windows. One has not been scanned, the other has been, but the scan is incomplete by virtue of being firewalled. The asset that has not been scanned, *does not* appear in the inventory.

I know this is preview software, but I must be missing something.

[Gilian]

Hi @Artichoke ,

Thanks for sharing this feedback. I'd like to start by analysing if the scans were actually being delivered to your LS Site from your IT Agent. 

Can you share the following via preview@lansweeper.com:

- Site ID on the tenant where you have this issue? (Configuration > Site Settings > Site ID)

- logs of those IT Agents. You can find them here

• Windows:
  • "C:\Program Files\Lansweeper IT Agent Discovery\sensor\logs\Lansweeper.IT.Sensor.log"
  • "C:\Program Files\Lansweeper IT Agent Discovery\sensor\logs\Lansweeper.Discovery.Hub.log"
• Linux:
  • "/opt/lansweeper-it-agent/sensor/logs/Lansweeper.IT.Sensor.log"
  • "/opt/lansweeper-it-agent/hub/logs/Lansweeper.Discovery.Hub.log"
• macOS:
  • "/Application Support/Lansweeper IT Agent Discovery/hub/logs/Lansweeper.IT.Sensor.log"
  • "/Application Support/Lansweeper IT Agent Discovery/sensors/IT/logs/Lansweeper.Discovery.log"

[ryf]

Is there a timeline or roadmap for when we can expect the cloud token for IT Ageny Discovery to last more than 24 hours? My environment is a mix of SCCM and Intune, it is not feasible to try to update the package every single day to ensure all devices receive the agent. This also makes it impossible to include the agent as a mandatory application during the provisioning process due to the limited lifetime of the cloud token.

Considering this delay, I've now had my license for a month and have not been able to reach more than 50% of my environment because of this oversight.

[Gilian]

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.

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

[ninjalee]

Is there any update on the duplicate asset using the IT Agent?

[Gilian]

@ninjalee 

Meanwhile the bug has been resolved and you should see IT Agent assets also in inventory > duplicate conflicts so you can manually merge them. The automatic merging using the reconciliation engine is still being worked on and should result in unique assets starting Q4 this year.