Internal documentation only
This page has been marked as draft.
Missing details in Windows Platform Netprobe Command Line Options
-
Note: This FAQ aims to clarify command-line option details that may cause confusion: Netprobe Command-line Options
-
It is noticeable in the documentation that certain options were presented with parameters:
/servicename=<servicename> -
While others do not have parameters included, for example:
/netport -
The
/netportoption should technically work, but it defaults to port 7036. Therefore, it’s the same as not using the option at all. To define the port value, the syntax should follow other displayed options, for example:/netport=<portnumber> -
Another example is displayed below:
start C:\path\to\file\geneos-netprobe-6.6.0-windows-x64.setup\geneos-netprobe-6.6.0.windows-x64.setup.exe /verysilent
start C:\path\to\file\geneos-netprobe-6.6.0-windows-x64.setup\geneos-netprobe-6.6.0.windows-x64.setup.exe /netport /servicename /verysilent
start C:\path\to\file\geneos-netprobe-6.6.0-windows-x64.setup\geneos-netprobe-6.6.0.windows-x64.setup.exe /netport=7036 /servicename=NetprobeNT_64 /verysilent
-
The commands above are different technically speaking but logically they will output the same result.
-
Please keep in mind that this behavior does not apply to all Netprobe Command-Line options as some of them do not use parameters to work.
-
This is only for the Windows installation method if you are using the command line instead of the installer.