---
title: "Quickstart: Windows"
description: ""
url: "https://docs.itrsgroup.com/docs/geneos/7.11.0/collection/netprobe/installation/quickstart-windows/index.html"
---
## Overview

The data collected by the Netprobe depends on the plug-ins you choose to run. For most cases, the Netprobe needs to be installed onto the machine or server to be monitored.


This guide walks you through the full setup and installation of a Netprobe on a Windows machine.

## Prerequisites

Beginning Geneos version 5.0.0, this component is only compatible with other Geneos components that are version 3.6.0 or higher. For more information, see the [Geneos Compatibility Matrix](https://docs.itrsgroup.com/docs/all/geneos/7x-release/compat-matrix/).

### System requirements


The following table lays out the minimum requirements for machines running the Netprobe:

| Specification | Minimum requirement |
| --- | --- |
| CPU | Multi-core |
| Memory | 4 GB |
| NIC | 100 Mbps |
| Disk | 500 MB (Minimal); 1 GB (Standard) |
| Port | A port must be open on any system running a Netprobe. The default Netprobe port is `7036`. Each system should be visible to the Gateway. |


For more information on supported Windows versions, see the [Compatibility Matrix](https://docs.itrsgroup.com/docs/all/geneos/7x-geneos-compat-matrix/index.html).

### Java requirements


Java may be required in order to run certain plug-ins. For more information, see [Application and plugin specific information in Geneos Compatibility Matrix](https://docs.itrsgroup.com/docs/all/geneos/7x-geneos-compat-matrix/index.html#application-and-plugin-specific-information).


## Download the Netprobe files


**Note**


You can download the Netprobe package either as a standard or minimal package.

- The standard package includes the Collection Agent plugins and all the other plugins for use in most scenarios. For example, `geneos-netprobe-standard-<version>-linux-x64.tar.gz`.
- The minimal package is smaller in size and does not include the Collection Agent and all its plugins. For example, `geneos-netprobe-minimal-<version>-linux-x64.tar.gz`.




For Windows, you can download the following Netprobe binaries:

- Through an executable installer (`geneos-netprobe-standard-<version>-windows-x64.setup.zip`). This is an installer for the WindowsNetprobe package. The installer is packaged in a ZIP file.
- Through a ZIP package (`geneos-netprobe-standard-<version>-windows-x64.zip`). You can only use this option when upgrading from a previous installation.

You can get the latest binaries from [ITRS Downloads](https://resources.itrsgroup.com/downloads).

## Install a new Netprobe

There are two ways to install a Netprobe. The first one is the default process as described in the procedure below. The second one is the automatic process, where installation prompts are skipped. For more information, see [Silent Installation](#silent-installation).

1. Download the installer package (`geneos-netprobe-standard-<version>-windows-x64.setup.zip`).
2. Extract the installer executable from the package.
3. Run the installer on the machine where you will run the Netprobe.
4. Go through the steps on the Windows Netprobe x64 Setup Wizard. Click **Next >** at the end of each screen:
 
**Note**

 The Setup Wizard walks you through configuring the Netprobe. You may revisit some of these options later, after the Netprobe is installed. 


 5. In **Select Destination Location**, specify the installation directory. By default, this is `C:\Program Files\NetprobeNT`.
 6. In **Geneos NetProbe Options**, specify the service name and listen port. By default, these are `NetprobeNT_64` and `7036`, respectively.
 7. If you would like for the Netprobe to run commands without requiring a password, tick the checkbox.
 8. In **Configure Netprobe Secure Connections**, tick the checkbox if you want to run the Netprobe in secure mode. If you do, you must specify the certificate file and key.
 
**Note**

 You can specify the certificate file and key, regardless of whether or not you want the Netprobe to run securely. This is because a plug-in called the REST API plug-in manages secure connections using the same certificate file and key specified on the Netprobe. 


 9. In **Configure Netprobe Secure Chain**, tick the first checkbox if you want the Netprobe to enforce certificate validation on incoming connections. If you do, you must specify the certificate chain.
 10. If you want the Netprobe to enforce certificate validation on Gateway connections, tick the second checkbox.
 11. In **Configure Self-Announcing or Floating Netprobe**, tick the checkbox if you want to run the Netprobe accordingly. If you do, you must specify the configuration file.
 12. In **Select Components**, check that you are installing the Netprobe as you configured throughout the Setup Wizard.
 13. In **Ready to Install**, complete the installation by clicking **Install**.
 14. After the Setup Wizard loads the next screen, exit by clicking **Finish**.

**Success**

  The Netprobe is now running as a service. You may stop or start the Netprobe at any time from the Windows Services app.Stop the Netprobe service 


### Silent installation

You have an option to skip user input during installation by executing the following command:

```
geneos-netprobe-<version>.windows-x64.setup.exe /silent
```

Another option for silent installation is by using the command-line option `/verysilent`, which also skips user interaction and additionally hides the progress of the extraction of the files.

For more information about the command-line options, see [Installer command-line options](https://docs.itrsgroup.com/docs/geneos/7.11.0/collection/netprobe/configuration/netprobe-command-line-options/index.html#installer-command-line-options).

### Installation using Helm

The Netprobe can also be deployed via Helm. Refer to [Netprobe deployments](https://docs.itrsgroup.com/docs/geneos/7.11.0/administration/orchestrated-environments/installation-using-helm/index.html#netprobe-deployments) for more information.

#### Uninstall the Netprobe

If needed, you can silently uninstall the Netprobe by executing the following command in the Netprobe directory:

```
unins000.exe /silent
```

## Upgrade an existing Netprobe

### Stop the Netprobe service

Before you upgrade a Netprobe, make sure to stop the Netprobe service first:

1. Open the Services app. To find it, press  `⊞ Win` and type `services`.
2. In the Services app, look for `NetprobeNT_64`, or the service name you assigned to the Netprobe.
3. Right-click on the Netprobe service and select **Stop**.

To restart the service, right-click on the Netprobe service and select **Start**.

You can upgrade the Netprobe using either the installer or the ZIP package.

### Upgrade the Netprobe using the installer

When you upgrade the Netprobe using the installer, follow the steps in [Install a new Netprobe](#install-a-new-netprobe). Make sure to provide the same inputs on the Setup Wizard as you did when you installed the Netprobe for the first time.


**Success**

  The Netprobe is upgraded and is once more running as a service. You may stop or start the Netprobe at any time from the Windows Services app. 


### Upgrade the Netprobe using the ZIP package

1. Download the ZIP file (`geneos-netprobe-standard-<version>-windows-x64.zip`).
2. Using a file archiver, extract the `netprobe` folder inside the ZIP file, onto any destination in the local machine.
3. Check the Netprobe service is stopped. For guidance, see [Stop the service](#stop-the-netprobe-service).
4. Move the contents of the `netprobe` folder to the Netprobe installation directory. By default, the installation directory is `C:\Program Files\NetprobeNT`. However, it may be different if you configured a different directory during a new installation.
    - Windows may recognise that the file contents are identical. If prompted, select **Replace the files in the destination**.
    - Windows may enforce administrator permission to move the files. If prompted, select **Continue**.
5. If you used a different service name for the Netprobe during installation, check that the `netprobe.windows_64.exe` application file matches the old one. For example:
    - If your service name is 'my-probe', delete the older instance of `my-probe.exe`, then rename `netprobe.windows_64.exe` to `my-probe.exe`.
6. Restart the Netprobe service from the Windows Services app.


**Success**

  
The Netprobe is upgraded with newer files.



## Start the Netprobe

You can start the Netprobe in the following ways:

- [Installer](#installer)
- [Command line (installer)](#command-line-installer)
- [Command line (process)](#command-line-process)

### Installer

When you install a new Netprobe using the installer, you will be prompted with the most common start options. Afterwards, the Netprobe starts to run as a service.

![Windows Netprobe installer GUI](https://docscdn.itrsgroup.com/geneos/images/netprobe/windows-installer-gui.png)

The Windows Netprobe installer supports configurable [Netprobe start-up parameters](https://docs.itrsgroup.com/docs/geneos/7.11.0/collection/netprobe/configuration/netprobe-command-line-options/index.html#binary-command-line-options). You can define additional command-line options under **Advanced Options** > **Command Line Arguments**.

![Windows Netprobe installer](https://docscdn.itrsgroup.com/geneos/images/netprobe/netprobe-windows-installer-window.png)


**Warning**

 Ensure that you use the correct command-line options, as incorrect options will not be validated. Duplicate options within the CLI string or across configuration pages will prevent installation. 


### Command line (installer)

You can opt to run the installer in the command line and add the start options in the same command. For example:

```
geneos-netprobe-<version>.windows-x64.setup /verysilent /setup=<full path or URL to file>
```

Afterwards, the Netprobe starts to run as a service.

### Command line (process)

You can opt to run the Netprobe as a one-time process by running the executable in the Netprobe package from the command line. This is useful for debugging. For example:

```
netprobe.windows_64.exe -setup <full path or URL to file>
```

### Start options

By default, the Netprobe starts running as a service upon installation on a Windows machine, with `Local System` as the default Netprobe user.

![Windows Netprobe services manager](https://docscdn.itrsgroup.com/geneos/images/netprobe/netprobe-windows-services.png)

To execute services, modify the default Netprobe user to an Active Directory account by changing the **Log on as: This account** property in the Windows Services menu.


**Note**

 Windows has implemented stricter security policies starting from Windows Server 2019. To ensure Netprobe can start as a service and run plugins, the Active Directory account must be a member of the `local administrators group`. 


![Windows Netprobe user account](https://docscdn.itrsgroup.com/geneos/images/netprobe/netprobe-windows-services-account.png)

- For guidance in starting a Self-Announcing Netprobe, see [Manage Self-Announcing Netprobes](https://docs.itrsgroup.com/docs/geneos/7.11.0/collection/netprobe/configuration/manage-self-announcing-netprobes/index.html).
- For guidance in starting a floating Netprobe, see [Manage floating Netprobes](https://docs.itrsgroup.com/docs/geneos/7.11.0/collection/netprobe/configuration/manage-floating-netprobes/index.html).
- For more information about options you can set on the Netprobe, see the following:
  - [Netprobe Command-line Options](https://docs.itrsgroup.com/docs/geneos/7.11.0/collection/netprobe/configuration/netprobe-command-line-options/index.html)
  - [Netprobe variables](https://docs.itrsgroup.com/docs/geneos/7.11.0/collection/netprobe/configuration/netprobe-variables/index.html)

