IT Agent Discovery frequently asked questions

Linking codes support 3 expiration options: 1 day, 1 month, or 3 months. To create one:

1. In your site, go to Discovery > Systems, and select Link discovery system.
2. Select Create new code, choose an expiration period, and select Apply.
3. Select Copy code, and paste it into the installer.

• IT Agent can send discovery results directly to your Lansweeper Site, so you don't need an on-premises scanning server.
• Like LsAgent, IT Agent auto-updates on Windows. It also auto-updates on Linux and macOS, which LsAgent doesn't support.
• IT Agent gathers additional data from devices, such as user information on macOS, and maps it to your Lansweeper Site for broader visibility.
• IT Agent supports silent installation on Windows, like LsAgent, and also on Linux and macOS.
• IT Agent runs on .NET 8 across all platforms, which carries less vulnerability risk than LsAgent for Windows, which uses .NET Framework 4.8.
• You can trigger an on-demand scan for IT Agent using the Lansweeper Data API. LsAgent scans must be force-started manually.

If the installer exits during the pre-installation phase, no files or changes are left behind. If it exits during installation, it rolls back and removes anything it added.

• 0: the installer finished without issues.
• 20-39: issues with the OS, installer, or an existing installation (pre-installation).
• 40-59: issues with user input (pre-installation).
• 60-79: issues during installation (installation is rolled back).
• 80-99: warnings during installation (installation is kept).

Exit code	Description
0	The installer finished successfully.
20	Another installation is already in progress. Finish that installation before starting a new one.
21	The installer is running on an unsupported operating system. Update your OS if possible.
22	The existing installation is newer than the version you're installing. The installer closes.
40	You must accept the terms of use to continue. Use the accepteula parameter.
41	A valid linking code is required to continue. Use the cloudtoken parameter.
42	A valid proxy configuration is required. Use both the proxyserver and proxyport parameters, or neither.
43	A valid proxy port is required. Use the proxyport parameter correctly.
44	No module was selected to install. The installer closes.
60	PowerShell script execution isn't enabled on this computer. Allow PowerShell script execution and try again.
61	A link to your Lansweeper Site couldn't be made. IT Agent only.
62	A required component service couldn't be started.
80	The installation succeeded, but a link to your Lansweeper Site couldn't be made. Network Discovery only.

On macOS, the PKG installer only returns 0 (success) or 1 (general error). For the specific exit code, check /tmp/Lansweeper-IT-Agent-Discovery_exitcode.log, which contains the exit code as an integer.

The installer bundles all core next-generation discovery components, which makes it larger than a typical agent installer. We're evaluating ways to reduce the size for mass deployments over metered connections, such as stripping components that aren't needed for local computer scanning.

IT Agent scans the computer it's installed on once every 24 hours by default. To change this frequency, create or edit a discovery action. See Define when IT Agent Discovery runs.

Yes. Use the Lansweeper Data API to request a scan on demand. See Perform actions in the developer documentation.

No. You can link as many IT Agent installations to a single Lansweeper Site as you need.

Yes:

1. Open Services on the Windows device.
2. Double-click the Lansweeper IT Agent Discovery Hub, Sensor, or Update service.
3. Go to the Log On tab.
4. Select This account and enter the service account.

The account needs local administrator rights on the device to retrieve all asset details. A least-privileged account also works, but it won't return the full set of asset details.

Lansweeper's reconciliation engine handles this automatically. If the same physical device is discovered by IT Agent, Network Discovery, Cloud Discovery, or Lansweeper Classic within the same Lansweeper Site, the engine matches the records using stable identifiers like MAC address or serial number, and merges them into a single asset. You don't need to configure exclusions or resolve duplicates manually.

See Understand the reconciliation engine for how matching works and what to do if you spot a duplicate that wasn't merged.

Though we don't recommend it, you can disable auto-updates on a device by running the following on the machine running IT Agent:

sc config "Lansweeper IT Agent Discovery Update service" start= disabled
sc stop "Lansweeper IT Agent Discovery Update service"

To manage or pause auto-updates for specific systems instead, use groups:

1. In your Lansweeper Site, go to Discovery > Groups.
2. Select the group your IT Agents belong to.
3. Turn off Enable scheduled updates.

See Update IT Agent Discovery for the full group configuration options.

Pausing updates through a group stops scheduled updates from applying, but update files are still downloaded. To block downloads entirely, block outbound access to Lansweeper's download servers. Run nslookup download.lansweeper.com to find the current IP addresses, then block them with a firewall rule, for example on Windows:

netsh advfirewall firewall add rule name="Block auto-update Lansweeper" dir=out action=block remoteip=<ip-address> enable=yes

This still allows access to your Lansweeper Platform gateway, which IT Agent needs for data sync. Your Lansweeper Site requires a minimum IT Agent version to stay in sync, so re-enable auto-updates as soon as you can.

Deleting the IT Agent Discovery system from your Lansweeper Site also triggers a local uninstall on all devices connected to it. To delete it:

1. In your Lansweeper Site, go to Discovery > Systems.
2. Select the IT Agent Discovery system.
3. Select Delete > Delete system.

See Uninstall IT Agent Discovery for the full uninstall options, including how to remove the agent locally on Windows, Linux, and macOS.

No. Scan exclusions apply to Network Discovery actions, which scan a defined range of targets. IT Agent only collects data about the device it's installed on, so there's no target list to exclude from.

If you don't want a specific device reported through IT Agent, remove that IT Agent installation from Discovery > Systems, or uninstall the agent from the device. See Uninstall IT Agent Discovery.

Computers, servers, and other assets that IT Agent Discovery finds count toward your licensed asset limit. Once you reach that limit, scanning of new and existing assets may stop until you delete assets or upgrade your subscription.

Check your current usage under Site settings > Subscription plan. See Manage your licensed asset limit for the full breakdown of what counts.

Yes. .NET 8 is a dependency for IT Agent on Windows, Linux, and macOS. The installer handles this automatically as a self-contained package, so you don't need to install .NET separately.

• Check Lansweeper's status page for the Discovery data pipeline.
• Confirm the IT Agent service is running: open Services on Windows, Activity Monitor on macOS, or run sudo ps -aux | less on Linux.
• Confirm the device can reach the discovery gateway APIs for your region. See IT Agent Discovery requirements for the exact URLs.
• If the results still don't appear, contact Lansweeper Support with the device name and the checks you've already run.

Yes, IT Agent updates automatically through your Linux package manager, such as apt or yum. To manage or automate these updates yourself, refer to your package manager's documentation.

The linking code is only used during installation to associate the agent with your Lansweeper Site. Once it expires, the agent keeps sending data to your site as expected, so you don't need to replace it.