Most trials already include one hub and sensor. Use these instructions when you need to add a second or third sensor, if you have additional networks, want to balance performance, or need redundancy.
Learn this in the Academy
For a guided walkthrough of installing and configuring discovery, take the free Deploy & configure the Lansweeper Platform learning path in the Lansweeper Customer Academy.
Prerequisites
- Review the Discovery Hub and Sensor requirements
- Ensure this is the correct discovery system for your use case
- Review the supported operating systems
Supported operating systems
- Windows 10 (21H2, x64; 1809 and 1607 LTSC/Enterprise only)
- Windows 11 (23H2, 24H2, 25H2, 26H1, x64)
- Windows Server (Core) 2012, 2012 R2, 2016, 2019, 2022, 2023H, 2025 (x64)
Install the sensor and hub
Recommended for most users.
In your preferred site, go to Discovery > Systems > Download installers/packages.
Select Network Discovery > Download Network Discovery installer.
Open the installation file.
Specify the installation directory.
Select which component you want to install. For first-time installations, you will likely want the IT sensor, OT sensor, and hub. However, if you’ve already installed the hub as part of your trial, you do not require another.
Optionally, enter:
Hostname: Specify another hostname for the machine hosting the hub if you’re only installing the IT Sensor.
TCP port: Specify an alternative TCP port if you want to override the default port for hub-to-sensor communication.
Once the installation is complete, you will be redirected to your Lansweeper Platform. Select the site you want to link with.
Ideal for repeatable deployments in enterprise environments.
In your preferred site, go to Discovery > Systems > Download installers/packages.
Select Network Discovery > Download Network Discovery silent installation configuration.
In your site, select Systems > Link discovery system > Create new code. Specify an expiration date, then select Apply and copy the generated code.
NOTE
The expiration date indicates when the linking code can no longer be used to establish a new connection between a site and your discovery system. Any existing connection between the system and your site will remain active after the expiration date.
On your computer, open the downloaded lansweepernetworkdiscoveryinstallation.cfg file.
In the file, replace
cloudtokenvaluewith your copied linking code. If the computer requires a proxy server, remove the#forproxyserver=myproxyserver.domain.localandproxyport=8080.mode=unattended accepteula=1 path=C:\Program Files\Lansweeper Network Discovery components=hub,itsensor,otsensor hubinstance=localhost hubport=59525 installnpcapdriver=1 dcomautoconfig=1 #cloudtoken=cloudtokenvalue #proxyserver=myproxyserver.domain.local #proxyport=8080 #hubcode=MyHubCode generated in the hub > Settings > Data transfer > Hub code (only required for distributed deployment of sensors across multiple systems, connecting to a remote hub)In an elevated command prompt, enter the following command, replacing
X.X.XinLansweeper-network-discovery-X.X.Xwith the version number of your installer:Installer version
The version numbers for your installer can be found in your downloaded file name.
Lansweeper-network-discovery-X.X.X-windows-x64-installer.exe --optionfile lansweepernetworkdiscoveryinstallation.cfg
Ideal for scripted installs without editing a .cfg.
In your preferred site, go to Discovery > Systems > Download installers/packages.
Select Network Discovery > Download Network Discovery silent installation configuration.
In your site, select Systems > Link discovery system > Create new code. Specify an expiration date, then select Apply and copy the generated code.
NOTE
The expiration date indicates when the linking code can no longer be used to establish a new connection between a site and your discovery system. Any existing connection between the system and your site will remain active after the expiration date.
In an elevated command prompt, enter the following command with the following edits:
Replace
cloudtokenvaluewith your copied linking code.If the computer requires a proxy server, remove the
#forproxyserver=myproxyserver.domain.localandproxyport=8080.Replace
X.X.XinLansweeper-network-discovery-X.X.Xwith the version number of your installer.
Version installer
The version numbers for your installer can be found in your downloaded file name.
Lansweeper-network-discovery-X.X.X-windows-x64-installer.exe --mode unattended --accepteula 1 --path "C:\Program Files\Lansweeper Network Discovery Discovery" --cloudtoken cloudtokenvalueTroubleshooting
Installation fails because the hub service couldn't start
The full message reads: "There has been an error. Could not start Lansweeper IT Network Discovery Hub Service. The application will exit now." This can happen on machines with a slow hard disk, low memory, or limited CPU resources, where the service takes longer to start than Windows allows. To resolve it:
- Press Windows + R to open Run.
- Enter
regeditto open the Registry Editor. - Go to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control. - In the Control folder, create a new DWORD (32-bit) value named
ServicesPipeTimeout. - Open the value, set Base to Decimal, and enter
600000in Value data. - Select OK.
- Restart your system. The change doesn't apply until you restart.
- Run the Network Discovery installer again.
Installation fails with "Unable to initialize installer"
This error occurs when the TMP or TEMP environment variable points to a path that doesn't exist. To fix it:
- Press Windows + R to open Run.
- Enter
sysdm.cpland press Enter to open System Properties. - In the Advanced tab, select Environment Variables.
- Find TMP or TEMP under User variables or System variables.
- Select the variable and select Edit.
- Set Variable value to a valid folder path, such as
C:\Windows\Temp. - Select OK to save your changes.
- Run the installer again.
Next steps
Now that your hub and sensors are installed, you can create a discovery credential to access more asset details, create a discovery action to specify specifically what to scan and when, and manage discovery exclusions to keep unwanted assets out of your inventory.