Geneos includes a number of Remote Management Service (RMS) functions to help automate tasks on the Netprobe. The Netprobe setup installer on Windows also has command line parameters to start the installation unattended. This article provides an example with configuration and batch files using these functions together.
The Netprobe setup installer on Windows has command line parameters to start the installation in unattended mode. If the user organization have existing Software Configuration Management tools, they may consider integrating this with their company practice.
Here we have listed out the common options in the Netprobe setup installer:
In the same way, the unins000.exe program located in the Netprobe directory supports /silent and /veryslient switches for silent mode uninstallation.
1. ITRS Geneos users can download the Windows Netprobe installer (e.g. geneos-netprobe-4.10.2.windows-x64.setup.zip) from the ITRS download site.
6. In Gateway Setup Editor => Probe (or Probe Group) => Advanced tab, go to the Permissions option and select RMSPUT and RMSEXEC from the drop-down list.
On the Active Console, users can right-click on the Probes or Managed Entity level to select the Netprobe RMS update for Windows x64 menu. This will start the following tasks to perform the Windows Netprobe deployment.
1. The gateway will use /RMS:putFile command to transfer the setup executable and batch files to the Netprobe.
2. The /RMS:exec command will execute the rms-validate-x64.bat. This will detect the existing Netprobe installation parameters, including the installation directory, service name and port number.
3. The /RMS:launch command will run the rms-setup-x64.bat as a separate process from the running Netprobe. This is needed to stop the current Netprobe, uninstall the existing version, and then install the new version.
1. This article uses mostly default options for the Netprobe installer. Users can refer to the Command line options section in the Netprobe User Guide for details and additional options.
2. The Netprobe service will be installed to run under Local System account. If it is needed to switch to another account, user may configure this manually using Windows Control Panel, or create a custom script with SC Config (linked to Microsoft documentations).