Lansweeper includes several agentless scanning methods to scan the assets in your network. You can scan the Linux, Unix, Mac and Windows computers, VMware servers and other devices in your network without installing any Lansweeper software on the machines you're scanning. Optionally, you can scan your computers with a scanning agent instead.
LsAgent is a scanning agent introduced in Lansweeper 7.0. It is a cross-platform, lightweight program that you can install on Windows, Linux and Mac computers and that automatically collects an inventory from the computer it's installed on. LsAgent sends scanned data back to your Lansweeper installation, either directly or through our relay server in the cloud. Data is securely sent to the relay server over HTTPS, stored in an encrypted format and deleted once a scanning server has retrieved it. Thanks to the relay server connectivity, LsAgent can even scan computers outside of your network and over the Internet.
To install LsAgent on a Linux computer and subsequently have LsAgent scan the machine, do the following:
- Make sure your Linux OS supports .NET Core 3.1 as described in this article.
- If you will be scanning the Linux computer over the Internet, make sure outbound traffic is allowed on your Lansweeper scanning server. Specifically, the scanning server must be able to make an outbound connection to port 443 of lsagentrelay.lansweeper.com, our cloud relay server, to retrieve data scanned by LsAgent. The relay server is a server hosted in Azure (Microsoft cloud environment) by us, Lansweeper. If LsAgent cannot send data directly to a Lansweeper scanning server, it will send the data to the relay instead, where the scanning server can collect it.
- If you will be scanning the Linux computer over the Internet, enable access to the Lansweeper relay server under Scanning\Cloud Relay Configuration in the Lansweeper web console. The relay access check may take a couple dozen seconds. If you have multiple scanning servers, you can configure which one collects relay data.
- Copy the relay authentication key seen on the page, as you will need to submit this in the LsAgent installer later.
- Download the LsAgent installer for Linux through this download page.
- Run the LsAgent installer on your Linux client machine and hit Next. You may need to tick Allow Executing File As Program in the installer's properties in order to do this.
- Optionally, choose a different installation directory. Hit Next.
- Submit one or both of the following:- Your scanning server name or IP and its listen port. You can see your listen port (9524 by default) listed in the Configuration\Server Options section of the web console. If you fill in these fields, LsAgent will first try to send scanned data directly to the listen port of your scanning server.- The relay authentication key you copied earlier, from the Scanning\Cloud Relay Configuration section of the Lansweeper web console. If you fill in this field, LsAgent will send scanned data to the Lansweeper relay server, where your scanning server can collect it. If you submit both your scanning server and relay authentication key, LsAgent will first try to send data directly to the scanning server and, if that fails, to the relay server. Data is securely sent to the relay server over HTTPS, stored in an encrypted format and deleted once a scanning server has retrieved it.
- Hit Next and Finish when the installation process has completed.
- LsAgent has now been installed. The client machine will automatically be scanned by LsAgent, by default once per day. Data will be sent to the scanning server and, if that fails, to the relay server, where the scanning server can retrieve it. You can find the client machine in the Lansweeper web console like any other Linux client machine, e.g. by performing a search for the computer's name through the search bar.
- Optionally, change the machine's scanning schedule in the Scanning\LsAgent Scanning section of the Lansweeper web console. Here, you can divide machines scanned with LsAgent into groups, configure a scanning schedule for each group and enable/disable/delete LsAgent installations. Keep in mind that the minimum scan interval for LsAgent is 1 hour. If you choose a more frequent schedule, your LsAgent installations will silently default to an interval of 1 hour. LsAgent uses the same schedules as deployment packages, so the link for creating a new schedule takes you to a deployment configuration page.
- Optionally, if you have multiple scanning servers, link additional servers to your LsAgent group on the same page. If an LsAgent installation then attempts to send scanned data to a scanning server and that server cannot be reached, another server is tried. If all linked scanning servers cannot be reached and if you submitted your relay key during LsAgent installation, scanned data is sent to the relay instead.