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 sources > 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 sources

• When you keep that page open, it auto refreshes and the total assets will change from 0 to a higher number (usually 1 but can be higher if monitors are connected to the asset). To see the asset data you can click on the “Total assets” number and open the specific asset details. Some data might still be missing we’re continuously mapping and expanding our global data model.

• Logs can be found here by default:
  • Installer:
    • "C:\Users\%USERNAME%\AppData\Local\Temp\Lansweeper_IT_Agent_Discovery_installer.log"
      "C:\Users\%USERNAME%\AppData\Local\Temp\Lansweeper_IT_Agent_Discovery_uninstaller.log"
    • "C:\Users\%USERNAME%\AppData\Local\Temp\Lansweeper.IT.Hub.log"
  • Modules:
    • "C:\Program Files\Lansweeper IT Agent Discovery\sensor\logs\Lansweeper.IT.Sensor.log"
    • "C:\Program Files\Lansweeper IT Agent Discovery\sensor\logs\Lansweeper.IT.Hub.log"

FAQs

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.

Can I use a single command to deploy IT Agent to multiple computers over an extended period of time?	Yes, we've extended the linking code duration so you can 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.
When should I use IT Agent over LsAgent?	-IT Agent can send the discovery results directly to your Lansweeper Site (without the need of an LS scan server on prem) -IT Agent auto-updates itself on Windows (like LsAgent) but also on Linux and macOS -IT Agent gathers extra data on the devices (such as user info on macOS) which will be mapped in your Lansweeper Site and made visible. -IT Agent can be installed silently on Windows (like LsAgent) but also on Linux and macOS -IT Agent for Windows was built on .NET 6.0 which has a reduced vulnerability risk in comparison to LsAgent for Windows (built on .NET FW 4.8) -IT Agent can be instructed to scan its asset(s) on demand using the Lansweeper Cloud API. To this with LsAgent, you'd have to force start a scan (see https://community.lansweeper.com/t5/quick-tech-solutions/force-start-an-lsagent-scan/ba-p/71844)
During the installer I get the message: “There has been an error. Could not start Lansweeper IT Agent Discovery Hub Service. The application will exit now.” How can I solve it?	If you receive this message during the installation, you can follow this procedure to resolve it: Press Windows + R to open Run Type regedit to open the Registry Editor. Navigate to the location below or copy-paste the location in the navigation bar. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control Now the Control registry folder is selected. Move to the right side and create a new DWORD (32-bit) Value called ServicesPipeTimeout Now in the Edit Value window, change the Base to Decimal. Enter a value of 600000 in the Value Data field. Click on OK to save the changes. Exit the Registry Editor and restart your system. (You need to restart, otherwise, the change doesn’t work.) After restarting, run the IT Agent installer again. We’ve noticed this on machines being a bit slower but haven’t figured out the root cause yet (slow hard disk, low memory, low CPU,…)
What are the installer return codes and possible error messages?	When the installer terminates with an exit code during the pre-installation phase, it ensures that no actions have been executed, with no files or changes left behind. In the event the installer terminates during the installation, a rollback will occur, and no files or changes will be left behind. The ranges are the following: 0 (zero) will be returned when the installer finished as expected, without issues. 20-39 range: issues regarding OS, installer or current installation (pre-installation) 40-59 range: issues regarding user input (pre-installation) 60-79 range: issues during installation (removing the installation) 80-99 range: warnings during installation (keeping the installation) Exit code Description Position Exit code Description Position 0 The installer finished with success. 20-39 Issues regarding OS, installer or current installation Pre-installation 20 Another installation is already in progress. Please finish that installation before starting a new one. 21 This installer is being run on an unsupported operating system. Please update your OS if possible. 22 The existing installation is newer than the version you want to install. Installer will be closed. 40-59 Issues regarding user input Pre-installation 40 You must accept the terms of use before continuing with the installation. Please use the accepteula parameter for this. 41 A valid linking code to your Lansweeper Site is required to continue. Please use the cloudtoken parameter for this. 42 A valid proxy configuration is required to continue with the installation. Please use both the proxyserver and proxyport parameters (or none). 43 A valid proxy port is required to continue with the installation. Please use the proxyport parameter correctly. 44 No module was selected to be installed. Installer will be closed. 60-79 Issues during the installation (installation will be rolled back) Installation 60 PowerShell script execution is not enabled on your computer, make sure your computer is configured to allow PowerShell script execution. 61 A link to your Lansweeper Site could not be made. (IT Agent only) 62 A required component service could not be started. 80-99 Warnings during installation (installation will be kept) Installation 80 The installation succeeded but a link your Lansweeper Site could not be made. (Network Discovery only) Note: When using the MacOS PKG, the installer command only returns 0 (success) or 1 (general error). To get the specific exit code (from the list above), this extra log file is available : /tmp/Lansweeper-IT-Agent-Discovery_exitcode.log. This file only contains the specific exit code (integer value).
Why is the size of the IT Agent installer rather big?	Currently, the IT Agent installer has all the core next-generation discovery components, resulting in a bigger installer. To cater to mass deployments, over metered connections, we're looking to decrease this size by stripping redundant parts and keeping only those required for local computer scanning.
What is the scan frequency of the IT Agent?	The IT Agent does a daily scan of the computer it’s installed on. You can change this frequency of 24h in your Lansweeper Site > Scanning > Discovery actions. See https://community.lansweeper.com/t5/cloud/configure-it-agent-discovery/ta-p/72780
Can I force the IT Agent to do an ad hoc rescan of the asset(s), now?	IT Agent does a rescan every 24 hours by default. You can also force a scan using the API, see https://docs.lansweeper.com/docs/api/actions#request-the-scan
How many IT Agent installations can I link to my Lansweeper Site?	As many as you like, there's no limit.
Can I use another service account to run the IT Agent services(s) instead of Local System?	Yes, you can. Go to Windows > Services > double click on either Lansweeper IT Agent Discovery Hub/Sensor/Update Service(s), go to tab "Log On", Choose "This account" and fill in the new service account. This account needs to be a local administrator on the machine running IT Agent (in order to retrieve all asset details). You can also use a least privileged account instead (see link) but it won't be able to get all asset details as mentioned in the link.
Why am I not seeing all asset data (yet)?	We’re remapping all data to a universal data model. As we’re doing this in phases, you’ll only see certain data sections available on the asset page of assets discovered by IT Agent. Currently, these sections are available: HW Operating System Software Monitor And this list is continuously being extended.
How do I solve duplicate issues?	You can resolve duplicate assets by opening Scanning › Discovery sources and unlinking the IT Agent installation(s), and removing all related data.
Can I disable the auto-update behavior?	Auto update is enabled by default in an 8-hour time window varying between 08:00 am and 06:00 pm (18:00). Though not recommended, you can still disable the auto-update behavior after installation by running the following command on the machine running IT Agent: sc config "Lansweeper IT Agent Discovery Update service" start= disabled sc stop "Lansweeper IT Agent Discovery Update service" Be aware that your Lansweeper Site does require a minimum version of your IT Agent(s) to keep syncing so it's advised to re-enable the auto-update behavior when you can to ensure correct inventory data.
Can I unlink the IT Agent installation from my Lansweeper Site?	Yes, you can by going to Scanning › Discovery sources > choosing the IT Agent and clicking “UNLINK” in the top right. After confirming with your site name, the data of the assets it discovered will no longer be added to your inventory. Remark: After unlinking, IT Agent is still scanning and trying to send its data to your Lansweeper Site. To avoid this from happening, we recommend you uninstall the IT Agent on the machine it was installed on. We’re looking to automate this process so you don’t have to manually uninstall IT Agents you no longer want to track. When doing an auto uninstall of the IT Agent on Linux, it won't delete the new user and group added as its required to correctly remove the other data. You can still cleanup this user and group manually.
If I uninstall IT Agent on the asset, could you also unlink the installation in your Lansweeper Site?	We like to promote centralized management from within your Lansweeper Site. When you decide to unlink the IT Agent installation, we plan on auto-uninstalling IT Agent to keep a clean system. If you still do a manual uninstall on the machine itself, we could go for a global option in your Lansweeper Site that auto-archives installations of type IT Agent and/or IT and keeps/deletes data (ls-to-do). Currently, unlinking from your Lansweeper Site means the asset data is also removed but we plan on offering you the option to choose whether or not to keep the data when unlinking the IT Agent from your Lansweeper Site (ls-to-do)

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]

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.

[jsutherland125]

We are trying to deploy the IT agent via Intune to our assets in the field. It seems that the token expires in 24 hours and after that installations fail. Is this expected behavior? If so, is there a method to deploy this agent?

Edit: I see this is expected (it obviously tells you that when getting the token), however, is there a preferred method to use to deploy the agent via Intune or any other deployment service that relies on device check-in that may not occur in the same day?

[avillarreal]

As the last that @Gilian comment on earlier post, the developer team is working on a way to achieve this, there are many as you and me that are waiting for that to complete... The only option that I found that could help you is to target computers specific that doesn't have the client already installed and change it every day... Seems a lot of work... Yeap... But probably until it gets addressed on a later release is the only option.

[Gilian]

@avillarreal and @jsutherland125 ,

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.

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

[CloudFire]

Hi @Gilian, could you give us a feedback?

Thanks!