Lansweeper Installation Prerequisites

Get Started with Lansweeper

Contact us for a demo, product resources, and formal quotation.

Lansweeper scans Linux, Unix, Mac, and Windows computers, VMware servers, and other network devices, but must be installed on a Windows computer. Lansweeper installation requirements can be found below.

Architecture

• 32-bit or 64-bit
• Virtual or physical
• You can install the Lansweeper software on either a virtual or physical computer.
• RAM
• 8 GB Minimum required

Operating system

You can install the Lansweeper software on non-Home, non-Core and non-Starter editions of any of the operating systems listed below. A Windows Server OS is recommended for networks of more than 1,000 assets, though not strictly required.

• Windows 10 21H2 (LTSC) or higher, with the exception of:
  • Windows 10 1809 (LTSC)
  • Windows 10 1607 (LTSB)
  • Windows 10 1507 (RTM) (LTSB)
• Windows 11
• Windows Server 2016 (End of mainstream support; extended support available until January 12, 2027)
• Windows Server 2019 (End of mainstream support; extended support available until January 9th, 2029)
• Windows Server 2022
• Windows Server 2025

Disk space

Lansweeper data, reports and settings are stored in a database. Your database is hosted in either the Microsoft SQL LocalDB, Microsoft SQL Server or (deprecated) Microsoft SQL Compact database server.

The size of your database can vary greatly depending on how much data you’re scanning and how much history you’re keeping. However, as a general rule, we recommend reserving 1 GB of disk space per 1000 Windows computers. Non-Windows machines have less of an impact on database size.

Database server

The database servers below are supported for hosting the Lansweeper database. Only SQL Server versions installed on a Microsoft Windows operating system are supported.

• Microsoft SQL LocalDB
• Microsoft SQL Server 2016, any edition (Express, Standard, Enterprise…) including Cumulative Update 11 or higher
• Microsoft SQL Server 2017, any edition (Express, Standard, Enterprise…) including Cumulative Update 18 or higher
• Microsoft SQL Server 2019, any edition (Express, Standard, Enterprise…) including Cumulative Update 2 or higher
• Microsoft SQL Server 2022, any edition (Express, Standard, Enterprise…)
• Microsoft SQL Server 2025, any edition (Express, Standard, Enterprise…)

Web browser

Lansweeper has a web interface, which can be viewed in a web browser locally from the Lansweeper server or remotely from other machines. Below is a list of officially supported browsers for interface viewing. Browsers not listed below may work as well, especially if they’re Chromium-based. Unsupported browsers have not been tested for possible layout issues and may not be able to run asset or user actions.

The minimum supported screen resolution for viewing the Lansweeper interface is 1280 x 720 pixels. This applies to all supported web browsers.

• Google Chrome, updated to the latest version
• Mozilla Firefox, updated to the latest version
• Opera, updated to the latest version
• Microsoft Edge, updated to the latest (Chromium-based) version

Other installed software

• The computer you install Lansweeper on must have .NET Framework 4.8 or a more recent .NET version installed, updated to the latest service pack.
• The computer you install Lansweeper on must have Windows Installer 2.0.
• If you are running an old Lansweeper version and chose SQL Compact as your database server, Visual C++ 2012 is required on your Lansweeper server as well. SQL Compact is no longer supported or offered as a database server option for Lansweeper. If you are still using SQL Compact as your Lansweeper database server, you should convert your database to SQL LocalDB or SQL Server.

If you do not already have .NET Framework 4.8, the Lansweeper installer will automatically try to download and install this for you. If your machine does not have Internet access, you may have to download and install this component manually in order to meet the Lansweeper installation requirements. When .NET Framework 4.8 is manually or automatically installed, a reboot of your Lansweeper server may be required.

Lansweeper Ports and Protocols

Lansweeper Agentless Scanning Prequisites:

For IP address discovery and domain-based assets agentless scanning is required.

Please note that agentless scanning has certain prerequisites that must be met: appropriate scanning credentials need to be configured, and the required ports and protocols must be open on the target machines for successful discovery.

Scanning Credentials Required for Agentless Scanning

To perform agentless scanning, the following scanning credentials and prerequisites must be configured based on the asset type:

• IP Range & Active Directory Asset Scanning: For scanning IP ranges the scanning account must have domain-level local administrator rights on the target machines.
• Windows Asset Scanning: Windows devices require domain-level local administrator credentials on the target machines for successful agentless scanning.
• Linux Asset Scanning
  • SSH (preferably OpenSSH) must be enabled on the target system.
  • The scanning account must have permission to run basic commands, at minimum the uname command.
• Network Device Scanning: SNMP credentials are required to scan and collect information from network devices.
• For Configuring Windows Firewall for agentless scanning of computers refer 10^th page
• Ports and protocol should open on the target machine for scanning

Windows Machine:

Lansweeper service to scanned Windows computers

• Port: 135/TCP (to establish the initial WMI session with the computer)
• Port: 139/TCP (NetBIOS Session Service)
• Port: 445/TCP (SMB)

Lansweeper relies on WMI protocols to gather asset information from Windows machines.

If these required ports are disabled, then you can set up target Windows machines to operate on a designated WMI port, such as TCP 24158.

Then “Allow an app or feature through Windows Defender Firewall” and include an exception for TCP port 24158.

Linux & MAC: Lansweeper service to scanned Linux, Unix and Mac computers Port: 22/TCP (SSH)

Lansweeper service to scanned network devices

• Port: 22/TCP (SSH) or a custom SSH port of your choice
• Port: 161 (SNMP)
• The primary protocols used for network asset discovery are SNMP and SSH. If these two are not available, alternative protocols listed below can be used. However, priority should be given to SNMP and SSH for accurate and efficient discovery.
• Port: 23/TCP (Telnet)
• Port: 25/TCP (SMTP)
• Port: 80/TCP (HTTP)
• Port: 443/TCP (HTTPS)
• Port: 8080/TCP (HTTP)
• Port: 8443/TCP (HTTPS)

We have added a reference guide on how to perform agentless scanning. Please review it and let us know if you have any questions. – https://www.youtube.com/watch?v=gsBzRMpkdAw

Ip Range scanning – https://community.lansweeper.com/t5/scanning-your-network/scanning-with-an-ip-range-scanning-target/ta-p/64330

Windows Domain Scanning – https://community.lansweeper.com/t5/scanning-your-network/scan-an-active-directory-domain-scanning-target/ta-p/64349

Here, Scanning Troubleshoot Guide – https://community.lansweeper.com/t5/troubleshooting-scanning-issues/scanning-troubleshoot-guide/ta-p/64244

Configuring Windows Firewall for agentless scanning of computers:

• Lansweeper pulls Windows computer data from WMI , a management infrastructure built into Windows operating systems. The initial connection to a client machine is made over TCP port 135. By default, Windows then sends the WMI data over random ports in the 1025-5000 or 49152-65535 range.
• To remotely scan Windows computers, you must ensure that the machines firewalls are properly configured to allow all WMI traffic.
• Windows Firewall has a remote administration setting you can enable to allow WMI traffic. The easiest way to enable this setting for all of your domain computers is using group policies.

Configuring Windows Firewall visually

To configure Windows Firewall on your client machines to allow WMI traffic, do the following:

1. Open the group policy editor for your client machines.
2. Browse to one of the sections listed below. Which one you have depends on your OS.

Computer Configuration\Administrative Templates\Network\Network Connections\Windows Defender Firewall\Domain Profile

Computer Configuration\Administrative Templates\Network\Network Connections\Windows Firewall\Domain Profile.

3. Right-click one of the settings listed below and choose Edit. Which one you have depends on your OS.

Windows Defender Firewall: Allow inbound remote administration exception

Windows Firewall: Allow inbound remote administration exception

Windows Firewall: Allow remote administration exception

4. Select the Enabled option to enable the group policy.
5. In the options under Allow unsolicited incoming messages from these IP addresses, enter your Lansweeper scanning server’s IP address and hit OK. Alternatively, submit the * wildcard to allow traffic from all IP addresses.
6. Wait for your policy to take effect on your client machines, which may take several hours. Alternatively, run the below command on your machines to force the group policy to apply.

gpupdate /force

7. Verify whether your policy is correctly applied. You can do this by running the below command on a machine.

netsh firewall show state

Configuring Windows Firewall through commands or scripts:

If you prefer to configure Windows Firewall through commands or scripts, you can either:

• Run the commands below in an elevated Command Prompt on the client machine. These commands will run successfully on both older and newer operating systems. They may generate deprecation warnings on newer operating systems but are functional there as well.

               call netsh firewall set service RemoteAdmin enable

               call netsh firewall add portopening protocol=tcp port=135 name=DCOM_TCP135

• Download (right-click and Save Link As) and run this script in an elevated Command Prompt on the client machine. This ensures that DCOM(Distributed Component Object Model) is a collection of Microsoft concepts and program interfaces where. Windows Firewall and other settings are correct. You can open the script in a text editor to review its contents, before executing in Command Prompt.

Windows workgroup scanning requirements

There are two main ways you can scan a Windows computer: with a scanning agent or without a scanning agent. Both options return the same data, but the scanning agent allows for offsite scanning and is immune to credential and firewall issues. Outlined below are the requirements for scanning Windows workgroup computers with or without an agent.

Regardless of which option you choose, Lansweeper will pull most Windows computer data from WMI a management framework built into Windows operating systems. Some data is pulled directly from the client machine’s registry as well.

LsAgent Installation Requirements

• 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 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.

LsAgent requirements for Windows:

Windows client machines must have .NET Framework 4.8(or higher) installed in order to run and be scanned by LsAgent. The following operating systems support .NET Framework 4.8 and hence can be scanned by LsAgent, if .NET 4.8 (or higher) is installed:

• Windows 7, SP1 (x86 and x64)
• Windows 8 (x86 and x64)
• Windows 8.1 (x86 and x64)
• Windows 10 (x86 and x64)
• Windows Server 2008 R2, SP1 (x64)
• Windows Server 2012 (x64)
• Windows Server 2012 R2 (x64)
• Windows Server 2016 (x64)
• Windows Server 2019 (x64) & Windows Server 2022 (x64)

Linux:

LsAgent for Linux comes packaged with .NET Core 3.1, which it requires to run successfully.

The following Linux operating systems support .NET Core 3.1 and hence meet the LsAgent installation requirements:

• Alpine Linux, version 3.10 or higher (x64)
• CentOS, version 7 or higher (x64)
• Debian, version 9 or higher (x64)
• Fedora, version 29 or higher (x64)
• Linux Mint, version 17 or higher (x64)
• openSUSE, version 15 or higher (x64)
• Oracle Linux, version 7 or higher (x64)
• Red Hat Enterprise Linux, version 7 or higher (x64)
• SUSE Enterprise Linux (SLES), version 12 SP2 or higher (x64)
• Ubuntu, version 16.04 or higher (x64)

Mac:

LsAgent for Mac comes packaged with .NET Core 3.1, which it requires to run successfully. The following Mac operating systems support .NET Core 3.1 and hence meet the LsAgent installation requirements:

• macOS 10.13 High Sierra (64-bit)
• macOS 10.14 Mojave (64-bit)
• macOS 10.15 Catalina (64-bit)
• macOS 11 Big Sur (64-bit)
• macOS 12 Monterey (64-bit)

Contact us to discuss your requirements

Facilitate Data Access with Seamless Integrations