How to use RMS commands to upgrade Windows Probes
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. Background InformationInstallation The Netprobe setup installer on Windows has command line parameters to start the installation in unattended mode. If the user organization has 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: Option Usage /dir Sets the Netprobe installation path. /netport Sets the Netprobe listening port. Default: 7036 /servicename Sets the Netprobe service name. Default: NetprobeNT /silent Runs the install with no user interaction, but you can see the installation progress. /verysilent Does the same as /silent but it does not show the installer files being extracted. Uninstallation In the same way, the unins000.exe program located in the Netprobe directory supports /silent and /veryslient switches for silent mode uninstallation. Preparation
-
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.
-
The Netprobe installer should be extracted to obtain the setup.exe file, and it should be placed on the gateway machine (e.g. under /opt/itrs/downloads/netprobe/).
-
Obtain the batch files (rms-validate-x64.bat and rms-setup-x64.bat) attached in this article, and place them on the gateway machine (e.g. under /opt/itrs/downloads/tools/).
-
Obtain the configuration XML files from this article, and import them into the Gateway Setup Editor. The configuration should be pasted to the Commands, and Operating Environment (variables) sections. Geneos - How to use RMS commands to upgrade Windows Probes
-
Edit the variables in the Operating Environment to match the appropriate installation options.
Variable
Description
rms_source_tools_dir
File path on the gateway with the batch files (e.g. /opt/itrs/downloads/tools)
rms_source_netprobe_dir
File path on the gateway with the Netprobe setup installer (e.g. /opt/itrs/downloads/netprobe)
rms_source_netprobe_win_x64_exe
Filename of the Netprobe installer (e.g. geneos-netprobe-4.10.2.windows-x64.setup.exe)
rms_target_dir
Target installation directory for the Netprobe (optional, e.g. “C:\Program Files\NetprobeNT_prod”). Default: if not specified the existing Netprobe installation directory will be used. -
In the Gateway Setup Editor => Probe (or Probe Group) => Advanced tab, go to the Permissions option and select RMSPUT and RMSEXEC from the drop-down list. Geneos - How to use RMS commands to upgrade Windows Probes Deployment 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.
-
The gateway will use /RMS:putFile command to transfer the setup executable and batch files to the Netprobe.
-
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.
-
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. Further Reading 1. This article uses mostly default options for the Netprobe installer. Users can refer to the Command line options section in the Netprobe Documentations 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).