Showing results for 
Show  only  | Search instead for 
Did you mean: 
Lansweeper Alumni

TL;DR-Sweepy-Icon (1).png
This page explains how to add a secondary sensor to Lansweeper OT.

A Lansweeper OT installation consists of the Lansweeper Network Discovery Hub, one or more sensors, and an update service. A sensor is what actually scans your OT devices and sends scanned data back to the Hub. If you need to, you can add a secondary sensor to an existing Lansweeper OT installation

Change Hub settings and grab the certificate

  1. On the machine that has your Hub installed, open Notepad or your preferred text editor as an administrator.
  2. In your text editor, open the following file: Program Files\Lansweeper Network Discovery\hub\appsettings.json.
  3. In the Hosting section of the file, replace "localhost" with the IP address of your machine. You can leave the HTTPS URL as is.
  4. Copy the certificate password in the Endpoints section of the appsettings file. You will need this later when configuring your new sensor.How to add a secondary ot sensor 1.png
  5. Finally, copy the following certificate found on your Hub machine: Program Files\Lansweeper Network Discovery\Lansweeper_OT_Internal_Communication.pfx
When you're done editing the Hub's appsettings file, restart the Lansweeper Network Discovery Hub Service in Windows Services to make your changes take effect.

Install the new sensor

  1. Run the Lansweeper OT installer on the machine you want to use as your secondary sensor.
  2. Uncheck Install OT Hub and only check Install OT Sensor.
  3. On the OT sensor screen, submit the IP address of your Hub machine and your communication port, as found in your Hub's appsettings file. 

Install the certificate on the new sensor

  1. Copy Lansweeper_OT_Internal_Communication.pfx to the machine where you installed the sensor.
  2. On this machine, select Start and then select Run.
  3. Run the below command, which opens the Local Computer Certificates of the machine.
    mmc.exe certlm.msc -s -r localMachine root
  4. Right-click Trusted Root Certification Authorities and select All Tasks\Import... from the available options.
  5. Select Next and browse to the location of the Lansweeper_OT_Internal_Communication.pfx certificate. You may need to change the display settings of the pop-up to include all file types.
  6. Select Next again and paste the certificate password that you grabbed from your Hub's appsettings file earlier. Once you've done that, you can leave all other settings as they are and complete the wizard.
When you're done installing the certificate, restart the Lansweeper OT Sensor Service in Windows Services to make your changes take effect.

Update the Hub URL in the appsettings files

Your new sensor should now be fully operational. You should see it listed in the Sensors menu of your Hub. However, you may need to update the Hub URL of your primary sensor and the Hub URL of your primary sensor's update service.

  1. Open Program Files\Lansweeper Network Discovery\update\appsettings.json and Program Files\Lansweeper Network Discovery\sensors\OT\appsettings.json on your primary sensor.
  2. Ensure the Hub URL listed at the top of these files points to the correct endpoint:
    • Sensor: https://[ip address of Hub]:[communication port]/Sensor
    • Update: https://[ip address of Hub]:[communication port]/Update
  3. If the Hub URL isn't listed, update the URL in these files and restart both the Lansweeper OT Sensor and Lansweeper OT Update services afterward.

Double-check the Hub firewall

If your new sensor fails to appear in the Hub, ensure incoming traffic can reach your Hub over whichever port you configured as your communication port. The default communication port is 85, but you may have selected a different one in the OT installer. If incoming traffic over the communication port is blocked on your Hub server, remote sensors won't be able to communicate with the Hub.

The OT installer, by default, adds a rule to Windows Firewall on your Hub server to allow for communication to the Hub. However, if you are using custom firewalls, you may need to manually adjust your Hub server's incoming firewall configuration.

Was this post helpful? Select Yes or No below!
Did you have a similar issue and a different solution? Or did you not find the information you needed? Create a post in our Community Forum for your fellow IT Heroes!
More questions? Browse our Quick Tech Solutions.

Was this article helpful? Yes No
No ratings

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now
Version history
Last update:
‎02-09-2024 03:26 PM
Updated by: