--- title: "Install IT and OT sensor on Windows | Lansweeper Platform" slug: "install-network-discovery-windows" description: "Install Lansweeper Network Discovery on Windows to add a hub or sensor, cover additional networks, and balance scanning performance across your environment." tags: ["Lansweeper Platform", "Discovery and scanning", "Network Discovery"] status: "update" updated: 2026-11-19T21:07:54Z published: 2026-11-19T21:07:54Z canonical: "docs.lansweeper.com/install-network-discovery-windows" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.lansweeper.com/llms.txt > Use this file to discover all available pages before exploring further. # Install the IT and OT sensor - Windows If you followed [Get started with Lansweeper Free](/docs/get-started-with-lansweeper-free), your site already has 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. > [!TIP] > Learn this in the Academy > > > > > > For a guided walkthrough of installing and configuring discovery, take the free [Deploy & configure the Lansweeper Platform](https://academy.lansweeper.com/content-details/93138/1) learning path in the Lansweeper Customer Academy. ## Prerequisites - Review the [IT and OT sensor requirements](/docs/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) 2016, 2019, 2022, version 23H2, 2025 (x64) ## Install the sensor and hub Interactive (GUI)Silent (config file)Silent (command line) Recommended for most users. 1. In your preferred site, go to **Discovery > Systems > Download installers/packages**. 2. Select **Network Discovery > Download Network Discovery installer**. 3. Open the installation file. 4. Specify the installation directory. 5. Select which components you want to install. For first-time installations, you will likely want **Install hub**, **Install IT sensor**, and **Install OT sensor**. However, if you’ve already installed the hub as part of your trial, you do not require another. 6. 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. 7. 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. 1. In your preferred site, go to **Discovery > Systems > Download installers/packages**. 2. Select **Network Discovery > Download Network Discovery silent installation configuration**. 3. In your site, select **Systems > Link discovery system > Create new code**. Specify an expiration date, then select **Apply** and copy the generated code. > [!NOTE] > 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. 4. On your computer, open the downloaded **lansweepernetworkdiscoveryinstallation.cfg** file. 5. In the file, replace `cloudtokenvalue` with your copied linking code. If the computer requires a proxy server, remove the `#` for `proxyserver=myproxyserver.domain.local` and `proxyport=8080`. ```bash 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) ``` 6. In an elevated command prompt, enter the following command, replacing` X.X.X` in` Lansweeper-network-discovery-X.X.X` with the version number of your installer: > [!NOTE] > Installer version > > The version numbers for your installer can be found in your downloaded file name. ```bash Lansweeper-network-discovery-X.X.X-windows-x64-installer.exe --optionfile lansweepernetworkdiscoveryinstallation.cfg ``` Ideal for scripted installs without editing a `.cfg.` 1. In your preferred site, go to **Discovery > Systems > Download installers/packages**. 2. Select **Network Discovery > Download Network Discovery silent installation configuration**. 3. In your site, select **Systems > Link discovery system > Create new code**. Specify an expiration date, then select **Apply** and copy the generated code. > [!NOTE] > 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. 4. In an elevated command prompt, enter the following command with the following edits: > [!NOTE] > Version installer > > The version numbers for your installer can be found in your downloaded file name. - Replace `cloudtokenvalue `with your copied linking code. - If the computer requires a proxy server, remove the `# `for `proxyserver=myproxyserver.domain.local` and `proxyport=8080`. - Replace `X.X.X` in `Lansweeper-network-discovery-X.X.X` with the version number of your installer. ```bash Lansweeper-network-discovery-X.X.X-windows-x64-installer.exe --mode unattended --accepteula 1 --path "C:\Program Files\Lansweeper Network Discovery Discovery" --cloudtoken cloudtokenvalue ``` --- ## Troubleshooting #### 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: 1. Press **Windows + R** to open **Run**. 2. Enter `regedit` to open the **Registry Editor**. 3. Go to `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control`. 4. In the **Control** folder, create a new DWORD (32-bit) value named `ServicesPipeTimeout`. 5. Open the value, set **Base** to **Decimal**, and enter `600000` in **Value data**. 6. Select **OK**. 7. Restart your system. The change doesn't apply until you restart. 8. 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: 1. Press **Windows + R** to open **Run**. 2. Enter `sysdm.cpl` and press **Enter** to open **System Properties**. 3. In the **Advanced** tab, select **Environment Variables**. 4. Find **TMP** or **TEMP** under **User variables** or **System variables**. 5. Select the variable and select **Edit**. 6. Set **Variable value** to a valid folder path, such as `C:\Windows\Temp`. 7. Select **OK** to save your changes. 8. Run the installer again. ## Next steps Now that your hub and sensors are installed, you can [create a discovery credential](/docs/create-discovery-credentials) to access more asset details, [create a discovery action](/docs/create-a-network-discovery-action) to specify specifically what to scan and when, and [manage discovery exclusions](/docs/manage-discovery-exclusions) to keep unwanted assets out of your inventory. The Network Discovery component that every sensor connects to. The hub holds the sensor configuration, collects the data the sensors gather, and syncs it to your Lansweeper Platform site. A Network Discovery component that runs discovery for a specific asset type or capability. The sensor types are the IT sensor, OT sensor, and traffic sensor.