Lansweeper Classic scans most assets without installing anything on them. LsAgent is the optional alternative: a lightweight, cross-platform program that collects an inventory from the computer it's installed on and sends it back to your installation.
LsAgent sends that data either directly to your scanning server or through the Lansweeper relay server in the cloud. Relay data travels over HTTPS, is stored encrypted, and is deleted once a scanning server retrieves it. Because of the relay, LsAgent can scan computers outside your network and over the internet.
If you use Lansweeper Platform, the IT Agent Discovery scanning agent may suit you better than LsAgent. See What is IT Agent Discovery to compare.
Before you install
- Verify the computer has .NET Framework 4.8 or higher. LsAgent needs it to run. For the full list of supported Windows versions, see LsAgent installation requirements.
- Decide how data reaches your installation. A direct connection needs your scanning server name and listen port. A relay connection needs the Cloud Relay Authentication Key, and only works once relay access is enabled. You can configure both, in which case LsAgent tries the direct connection first.
- Download LsAgent, or take the installer from
Program Files (x86)\Lansweeper\Clienton your Lansweeper server.
Enable relay access
Skip this section if you're scanning the computer over your own network and won't use the relay.
-
Verify outbound traffic is allowed on your Lansweeper scanning server. The scanning server must be able to open an outbound connection to port 443 of
lsagentrelay.lansweeper.com, the cloud relay server hosted by Lansweeper in Microsoft Azure. If LsAgent can't send data directly to a scanning server, it sends it to the relay, where the scanning server collects it. -
In the Lansweeper Classic web console, go to Scanning > Relay Configuration and enable access to the relay server. The access check can take a few dozen seconds. If you have multiple scanning servers, you can choose which one collects relay data.
-
Copy the Cloud Relay Authentication Key shown on the page. You enter it in the LsAgent installer later.
You can only switch on the LsAgent relay configuration from the Lansweeper Classic web console. If you can't get into the console yet, see Access the web console.
Install LsAgent
-
Run the LsAgent installer on your Windows client machine and select Next.
-
Choose an installation directory and select Next.
-
Enter your connection details. Fill in one or both:
- Scanning server name or IP, and its listen port. With these filled in, LsAgent first tries to send scanned data straight to your scanning server's listen port. The listen port is 9524 by default, and you'll find it under Configuration > Server Options in the web console.
- Cloud Relay Authentication Key. With this filled in, LsAgent sends scanned data to the relay server for your scanning server to collect.
If you fill in both, LsAgent tries the scanning server first and falls back to the relay.
-
Select Next, then Finish to complete the installation.
The client machine is scanned automatically, once per day by default. Find it in the web console by searching for the computer's name in the search bar. The machine's Scan Time tab shows that it was scanned with LsAgent.
When an LsAgent scan is imported, Lansweeper performs an Active Directory lookup using the credentials associated with the domain's NetBIOS name.
Change the scanning schedule
Go to Scanning > LsAgent Scanning in the web console. Here you can group machines scanned with LsAgent, set a schedule per group, and enable, disable, or delete LsAgent installations.
LsAgent uses the same schedules as deployment packages, so the link for creating a new schedule takes you to a deployment configuration page.
The minimum scan interval for LsAgent is 1 hour. Choose a more frequent schedule and your LsAgent installations silently fall back to 1 hour.
Add fallback scanning servers
If you have multiple scanning servers, link additional servers to your LsAgent group on the same page. When an LsAgent installation can't reach one scanning server, it tries another. If none of the linked servers can be reached and you supplied the relay key during installation, the data goes to the relay instead.