FAQ and Troubleshooting the Nodinite Monitoring Agents
- If you cannot launch the .MSI executable, ensure it is not blocked by Windows (right-click on the file, click properties, uncheck the block if it exists).
UAC may interfere with installation. Sometimes, users need to launch the MSI using an administrative command prompt or even start the installation using the following command:
msiexec /i Nodinite.MonitoringAgent.XYZ.Installer-x.x.x.x.msi
You can perform unattended installations and updates. Use the command below as a template.
msiexec /i C:\<path>\Nodinite.MonitoringAgent.WindowsServer.Installer-220.127.116.11-beta.msi /qn /norestart SERVICEACCOUNTUSER=<AccountName> SERVICEACCOUNTPASSWORD=<Password>
After the first installation, you must add the Monitoring Agent to Nodinite.
If the agent is operational and Nodinite can reach the agent, you can download the diagnostics files as a ZIP directly from the Nodinite Web Client.
The download operation gives you a ZIP file with the diagnostic.log.json files and a file info.txt that contains information about the agent type, version and generation time. Attach this file with the support ticket.
- Log on to the server with the installation of the Monitoring Agent.
- Open the installation folder; the default root path is:
- Attach to a zip file with the support ticket. We prefer if you ZIP the files. Instead of 15MB+ it will take less than 1 MB in size.
Installing multiple Monitoring Agents on the same server is an advanced topic. You should follow these instructions to install multiple instances of the same type of Monitoring Agent on the same server.
Any number of the same type of Monitoring Agent can be installed on the same Windows Server if:
- The address from the endpoint section in the
%MonitorAgent%.exe.configis unique. Either change the Name part (preferred change) or Port.
- The name of the Windows Service is unique (as seen in Services.msc).
NOTE: You cannot use the installer when updating other than the first installed service if you install multiple instances. Then, manually perform a copy/paste operation from the first installation to later.
- Install the first Monitoring Agent according to the default documentation.
This installation acts as the master for future manual copy/paste operations.
Copy the folder to a new location. Rename the folder to make it unique and easy to distinguish.
In the new folder; Edit the
%.exe.configfile using Notepad or Notepad++ with elevated privileges.
Find the endpoint XML element
<endpoint ...and change the address to be unique on that server.
Change the path to the
Settings.json file(target the path in step 2). It is imperative you perform this step, otherwise, the other Settings.json for the other agent instance file will be overwritten with data from this instance.
- Copy the Service Name from the first Monitoring Agent to a row in Notepad++.
- Rename the service (for example, PROD, TEST), making this Windows service instance unique.
- Copy to another row in the instance.
Open an Administrative Command Prompt and use the following command as a template to install the new Monitoring Agent (replace the path and service name):
sc create "%UNIQUE OTHER NAME OF Monitoring Agent FROM CLIPBOARD%" binpath="C:\Program Files\Nodinite\Nodinite Monitoring Agent - Windows Server TEST\Nodinite.MonitorAgent.WindowsServerHost.exe"
Change The startup type in the Services MMC to Automatic (Delayed)
Enter the credentials
Start the service
The README.txt file in the run-time folder will now have the proper address for use as a Monitoring Agents
NOTE: Remember to copy (backup) the config file before updating the agent.
You will find an overview of all services and functions that Nodinite can monitor on the Monitoring page.
Follow the links to get additional information about the Nodinite monitoring agents: