cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Gilian
Product Team
Product Team

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

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 

Few connectivity requirements. See 

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

100 REPLIES 100
brian_blater
Engaged Sweeper II

First and foremost I'm flabbergasted on the support Lansweeper provides for the IT Agent. The excuse is always in preview and unsupported. Go to this group. You would think being in preview ("beta") that they would want to know of any potential issues, but no. Ok, rant over.

I have linked our on prem server to the Cloud and installing the IT Agent on our machines with Intune and Jamf. The install is actually going quite well. However, I'm not sure how IT Agent assets function in the new cloud version. I know they do not show up in the on prem assets for now.

One of the questions I have... we have over 500 assets in Lansweeper. Most of those are now macs using the IT Agent. I have some IP Locations setup (they were setup in Classic) and machines are not being assigned to those locations.

From the looks of it, only machines from Classic with LsAgent are in these locations, but that is only like 50 or so. We are missing a bunch.

Is this a manual process? I've got machines in several offices and all over the world (some connecting over VPN) and would like to be able to look at an asset and know where it last connected. Is this even possible?

Hi @brian_blater

Thanks for raising this. We certainly want to know about potential issues as this improves the quality of our preview features for all users. Our current process is: GA features are covered by our global support team while Preview features are covered by the product/development team using this community and preview@lansweeper.com.

 

IP locations are used to give your IP ranges and VLANs a unique name, grouping the included assets based on their IP address. IP locations are specific to any LS On Premise installation and do not include IT Agent/Network/Cloud Discovery assets (yet). If you also use these discovery systems, you can create a new custom report in Reports > Create new report. When you use the fields and filter below you can create a report for each relevant IP range.Untitled1.png

 

 

Fields:

/*
specifications - The fields to include or exclude
*/
 
{
  "assetName": 1,
  "ipAddress": 1,
  "asServer.asServerId": 1,
  "lastSeen": 1,
  "lastTried": 1,
  "lastLsAgent": 1,
  "installKey": 1
}
 
Filters:
{
"$or": [
{
"$and": [
{
"ipAddress": {
"$exists": true,
"$nin": [
"",
null
]
}
},
{
"ipAddress": {
"$startWith": "10.37.0"
}
}
]
}
]
}
 

 

brian_blater
Engaged Sweeper II

Ok, I can do a report then to get the information I'm looking for in this way. However, it makes me wonder what the purpose of an IP Location in Lansweeper then? I may be misunderstanding what it is used for.

@brian_blater 

IP locations give you the option to address a filter of IP ranges with a chosen displayname. This is fully functional for LS On Prem but not yet ready for Network/IT Agent/Cloud Discovery. For this to work, IP locations should no longer require an "installation" property which they still do at the moment. We plan to solve this so IP locations are fully managed at the inventory side in your LS Site, across all assets, regardless of where/how they were added to your inventory.

brian_blater
Engaged Sweeper II

Ok. For now I will rely on the Reports until the IP Locations work with IT Agent. thx

eputz
Engaged Sweeper III

We only use the ITAgent with our site and have no additional discovery methods configured so are a bit confused why we're seeing instances of Ring doorbells, CCTV cameras and smart TVs appearing in our inventory when we're currently only interested in assets that have the IT Agent installed?

Hi @eputz 

Thanks for sharing. In https://app.lansweeper.com can you go to scanning > Discovery groups?

Next, can you ensure your IT Agents are member of the group "Default Group IT Agent" and not "Default Group"?

"Default group" has network visibility enabled by default, whereas "Default Group IT Agent" only focuses on the device where the IT Agent is running (workstations/servers on Windows/Linux/macOS)

After correcting the group membership, you can remove the assets from the other asset types from your inventory and they should not be re-added after a next discovery from your IT Agents.

eputz
Engaged Sweeper III

Thanks I'll take a look. Going forward how do we ensure that our ongoing ITAgent installs are not ending up in that Default group as we don't want to have to keep manually managing group memberships?

@eputz this was resolved during the current preview phase. All new IT Agents are now joining "Default IT Agent" Group by default. You can change their membership manually in your LS Site to give them different settings like their auto update behavior.